mdivancic wrote:Waiting for disk module to replace my hard drive before I can install. For those of you who have installed this and the Svethlana I'd love to see pictures of the install.

Ok, finally all cabling has arrived so I put mine together (it's been lying all butchered up for far too long).

The goal was to have all of it (PSU, CT63, SuperVidel, SvethLana, RJ45 connector, HDMI connector, SSD drive) in the standard casing without cutting new holes. And it did fit after some fiddle and a few pounds of hot glue.

Well, I finally got my CT-63 updated and the SV installed. I have video! Now I just need video drivers. I can't get the drivers to download from the Nature web site. Is there any place else to get these drivers?

On the plus side, it works! I've got video out of the SuperVidel! I managed to up update the CT-60 without bricking it (always good).

mdivancic wrote:Well, I finally got my CT-63 updated and the SV installed. I have video! Now I just need video drivers. I can't get the drivers to download from the Nature web site. Is there any place else to get these drivers?

Why can't you get them from the web page?

EDIT: Are you using the built-in ZIP-depacker in MS Windows? It's broken by design. Use WinRar, Winzip or some other unarchiver.

shoggoth wrote:EDIT: Are you using the built-in ZIP-depacker in MS Windows? It's broken by design. Use WinRar, Winzip or some other unarchiver.

And it didnt depack on my Kubuntu and Ubuntu machines ( with their default unarchivers + installed one other, but cannt recall now what it was ) I had to send the drivers to a mate with Windows to depack it for me

shoggoth wrote:EDIT: Are you using the built-in ZIP-depacker in MS Windows? It's broken by design. Use WinRar, Winzip or some other unarchiver.

And it didnt depack on my Kubuntu and Ubuntu machines ( with their default unarchivers + installed one other, but cannt recall now what it was ) I had to send the drivers to a mate with Windows to depack it for me

Clearly needs to be fixed. Sorry for this, it'll be taken care of soon. Until then, please use WinRar or Winzip.

mdivancic wrote:That worked, I now have drivers and my SV is working fine in Mint. Now I have a ton of questions! A couple to start.

Is there anyway to switch the video mode from the desktop, or is the only way to edit the xaaes.cnf file (I set video in Xaaes to 0x441f)?

I take it you're not referring to the TOS Desktop, but rather to the XaAES. Currently there is no Supervidel-specific video setup module, no. This might happen in the future though. Until then, either set it in xaaes.cnf, or remove the "video" line from xaaes.cnf and set the "default" line in SV.INF.

I'm geting the following error on my CT63 on reboots only: "Bad ROM CRC in chip E". Should I reprogram my CT63 or do I need to flash the boot rom to 1.03c (still running 2.01)?

I have no idea about that one And unfortunately 2.0x doesn't run properly on my machine, so I really can't test it.

shoggoth wrote:I take it you're not referring to the TOS Desktop, but rather to the XaAES. Currently there is no Supervidel-specific video setup module, no. This might happen in the future though. Until then, either set it in xaaes.cnf, or remove the "video" line from xaaes.cnf and set the "default" line in SV.INF.

Yes, the XaAES desktop, sorry! TOS Desktop is working fine.

I have no idea about that one And unfortunately 2.0x doesn't run properly on my machine, so I really can't test it.

As I wrote somewhere else, I had this CRC error at boot and also a strange "rx read error" or something like that during standard operations.

I solved the CRC thing by swapping a lot of RAM sticks until I found a good one, while I still have the "read error" randomly.

After getting answers from the Nature guys, I understood that my main concern should be to flash the CT60 chips (not the loader itself, that seems to work perfectly). Now I am waiting to buy that Xylinx cable

mdivancic wrote:That would suck, I'm running at 80 mhz now. (Not that it's not crazy fast for an Atari)...

Dropping to 76 mhz solved the crc error.

So more questions now:

So what's the best desktop to use with MINT?

What's the best way to go about setting up the system to dual boot? It would be nice to be able to easily boot into TOS once in a while.

So, what are the rest of you doing for displays on the original videl? I'm not fond of swapping monitor cables back and forth. I was thinking of some type of monitor switch, but just wonder what others are doing?

mdivancic wrote:That would suck, I'm running at 80 mhz now. (Not that it's not crazy fast for an Atari)...

Dropping to 76 mhz solved the crc error.

So more questions now:

So what's the best desktop to use with MINT?

There's no such thing. Jinneee, Gemini, Thing, Teradesk, either one has its benefits and limitations.

mdivancic wrote:What's the best way to go about setting up the system to dual boot? It would be nice to be able to easily boot into TOS once in a while.

Simply dedicate one partition to each task. C: for MagiC, D: for MiNT, E: for TOS, whatever. Set the hard disc driver to boot the partition with your main system, and press the appropriate drive letter upon boot for the other systems. Or press and hold "Control" during boot to bypass AUTO and ACCs entirely (for gaming).

mdivancic wrote:So, what are the rest of you doing for displays on the original videl? I'm not fond of swapping monitor cables back and forth. I was thinking of some type of monitor switch, but just wonder what others are doing?

I ain't got a Super Videl but a Radeon on the CTPCI, yet the solution is the same: I've got a 20" LCD (1600x1200) with dual input. Both inputs are connected to the Falcon, and one single key press on the monitor switches to either signal.

mdivancic wrote:Where do I go to find out about getting a picture on the desktop?

calimero wrote:btw what is speed of SvethLana? Currently I am using NetUSB on ROM port but I guess that SvethLana is faster?

SvethLana is a 100Mbit card on a fast bus, it should be quite a bit faster than the NetUSB. Any speed limitation is more likely to be in the MiNTNet stack (which has some short comings) rather than the hardware.