Moderators: Mug UK, moondog/.tSCc., [ProToS], lp, instream, Moderator Team, Nature
mikro wrote:I don't know why but the system just wont boot. I see the CT60 stats/versions, amount of memory (but no logo, naturally) and .. that's it. I see SV must be working somehow (with the empty VGA adaptor) because I do see a nice, clean picture on the DVI output with the same stats. So I'm wondering what could go wrong?
shoggoth wrote:1-2. I'm using a CTCM, but I'd have to check my installation to see how that's possibleI might have cheated somehow.
mikro wrote: I'm going to play with XaAES and stuff to see what happens. Yes, I'm a terrible user and everything, I realize that. But anyway, when I saw the 1920x1080 resolution, I nearly fell of my chair
mikro wrote:Hi all,
just to share my experience with SuperVidel with you, perhaps I'll get smarter here. I assisted Xi, a friend of mine, to install his and everything went flawless (CT63, no wires, just plug&play) even on his old firmware which we were unable to update (my cable stayed at home). After some time / certain operations screen froze but we assumed that's because of the old firmware.
So, before doing anything I have updated my CT60 to the latest ABE/SDR, TOS is 1.03c.
1. I don't whether it's OK but my SV by no way can fit (at least somehow) with CTCM installed. It's just... too high, if I want to fit it, SV is connected maybe 1-2 mm deep, I don't think this is OK. Fortunately, I still have the old 66.6 MHz clock, with that it is much better.
2. Next trouble was actually fitting SV properly because the 2.5->3.5 adapter + IDE cable is like 0.01 mm away from the DVI connector (and I'm unable to use the screw, because it overlaps with it). Not a big deal, just a bit scary.
3. Then my another trouble was that I'm using Falcon in RGB, i.e. having a SCART cable. Yes, I did know that SV doesn't support RGB, first I only wanted to check out whether it's everything all right without drivers. And bam! No picture on DVI, 15 kHz/50 Hz (thank god for these smart LCDs showing me this). OK you say, remove the SCART cable. Sure. And what? TV output, i.e. the same. So I had to dig out a VGA adapter and put it in the monitor slot, even if I didn't have any VGA monitor. I find this as a big design flaw, guys! (I hope it can be corrected)
4. And finally... I don't know why but the system just wont boot. I see the CT60 stats/versions, amount of memory (but no logo, naturally) and .. that's it. I see SV must be working somehow (with the empty VGA adaptor) because I do see a nice, clean picture on the DVI output with the same stats. So I'm wondering what could go wrong? First I thought whether it isn't caused by the fact that I'm using the old clock but the CT60 has got those wires on the back (CTCM mod) but nope. As soon as SV is gone, everything boots up as before.
EDIT: ... and to add 5. to my whining: SV_drivers.zip are in fact SV_drivers.rar. Not cool, guys, not cool!
instream wrote:2) We forgot to mention harddrive troubles in the manual, but it is mentioned on the SV project page at nature.atari.org. Anyway, I would recommend losing the old 3.5" drive and getting a small form factor SSD that sits directly on the 44pin connector. No cables!Can be found on ebay for. I think there is a discussion about those drives on this forum.
mikro wrote:However, there's one more glitch -- if SV_XBIOS.PRG is started without SV.INF in root, I'd expect it to fall back into some safe defaults. Nooo, it's messed up everythingI had to blindly disable it to PRX and then copy over the forgotten file.
Another thing -- what do the 'enabled by NVDI driver' options mean? That if I run NVDI, value specified there doesn't matter because they are enabled by NVDI anyway?
I'm going to play with XaAES and stuff to see what happens. Yes, I'm a terrible user and everything, I realize that. But anyway, when I saw the 1920x1080 resolution, I nearly fell of my chair
mikro wrote:Let's continuesvupd005.app from Nature's website -- 404 error. File for JTAG update is available, it's just this one. I'm wondering how come nobody has noticed this.
But no, seriously, I'm doing also something else than trying to piss you off guys
shoggoth wrote:But no, seriously, I'm doing also something else than trying to piss you off guys :P
Sure you are :) Otherwise you wouldn't be so good at it ;-)
dual = on/off
clone = true/false
primary = VGA
mikro wrote:But we are having so much fun. So here is a couple of new bugs:
- if I specify bootmode = $445c (which is supposed to be 1920x1080/16bit), console output is broken (in Desktop, if you click 'Show' you see only funny colour pixels instead of text). If I let bootmode as it is and boot into Desktop in the same resolution, it works
- the resolution dialog is quite misleading -- I set 1920x1080/16, it's set, all right. Then I go to the dialog again, I see my number ($445c) but the other information (width, height, perhaps others) are (re)set to 1024x768
Question: why can't I set 24 and 32 bit depth? It's a future feature?
EDIT: also, what's the difference between:dual = on/off
clone = true/false
Does 'clone' imply that 'dual' has to be set 'on'? How does this work?
and:primary = VGA
what is the other value? DVI? What does it do in practice?
shoggoth wrote:mikro wrote:- if I specify bootmode = $445c (which is supposed to be 1920x1080/16bit), console output is broken (in Desktop, if you click 'Show' you see only funny colour pixels instead of text). If I let bootmode as it is and boot into Desktop in the same resolution, it works
Oops, I had no idea. Are you using the TOS VDI or NVDI? Makes quite a difference. There are console issues in bitplane modes when using NVDI right now, simply because my SVSCREEN.SYS does not yet implement the console properly (TC and chunky resolutions implement their own consoles for some reason, I guess Behne^2 wanted to save some space and put it in the NVDI.PRG binary (SCREEN.SYS is in there) instead of in the NVDIDRV1-8.SYS files).
Either load NVDI
or enable 32bpp in SV.INF.
Ignore these settings for the time being. They won't have any effect right now, but they will. Basically they'll be used to set dual screen resolutions, and to disable unused output to save bandwidth.
mikro wrote:Yes, it's with NVDI. But how come it works in the same resolution when not using the 'bootmode' (i.e. to me it seems like it switches from something to 1920x1080x16 and therefore there's some initialization happening while when the resolution is set right from the beginning of the boot process, a desktop/console initialization is not happening afterwards).
Apropo, haven't you thought of using NVRAM for this? It would be sweet to see the resolution set after power on (assuming that there's no additional initialization needed).
Either load NVDI
Oh really. I'm using NVDI all the time.or enable 32bpp in SV.INF.
Now who's a doucheHow do I do that?
Maybe it's good idea to hide these for the time being, then. Curious people like me are very frustrated when there isn't anything happening
shoggoth wrote:You are sure that your ASSIGN.SYS is correct?
But I guess that I could read the NVRAM instead of SV.INF for the boot resolution, since it's possible to store an SV modecode in there.
Ok this is weird, then. 32bpp is not available in VIDEL resolutions obviously, but with NVDI it is supposed to be available in all SV resolutions. It is on my machine. Wonder what goes wrong here.
I'm asking mainly because my long(-ish)-term plan is to put the XBIOS driver into the CT60 TOS (1.03c), ideally with your fix for the Atari logo. I'm not planning to use the CTPCI anytime soon and on the other hand I'd like to have nice resolution from the start, having the .PRG only as a fallback solution when something goes wrong.
So you say you boot with NVDI enabled, go to the desktop resolution change dialog, choose SV mode and boom, you can set both 16-bit and 32-bit? I see always 16-bit only
shoggoth wrote:I'm asking mainly because my long(-ish)-term plan is to put the XBIOS driver into the CT60 TOS (1.03c), ideally with your fix for the Atari logo. I'm not planning to use the CTPCI anytime soon and on the other hand I'd like to have nice resolution from the start, having the .PRG only as a fallback solution when something goes wrong.
That's my long term goal as well, and my CTPCI is still in a box somewhere, I'll most likely never use it.So you say you boot with NVDI enabled, go to the desktop resolution change dialog, choose SV mode and boom, you can set both 16-bit and 32-bit? I see always 16-bit only
I'll have to check it. The video dialog is a bit of a hack to say the least. There's no API to change it, which means there's only ugly ways to achieve that..
Dal wrote:Is the bug with the video dialog fixed yet? I am using the latest driver pack, V006 firmware and NVDI but not able to set 32bit true colour mode. Can I 'hack' it by enabling 32bit mode in SV.INF?
**EDIT: Yes - it appears forcing 32bit mode on in the SV.INF does allow me to select it in Video Prefs**
Users browsing this forum: No registered users and 1 guest