dml attempts a Raven

[dml]

Did some additional quick tests with video cards.

- ET4000AX card works
- ATI Mach32 card works
- Diamond Hercules W32i card works
- ATI Mach64 card = black screen

I didn't try any of the TIGA cards because (A) I don't expect them to be initialised and (B) they have DB9 video connectors and I don't have the adapter handy.

I also have an older ESS soundcard to play with but probably tomorrow now...

[edit]

With the Mach32 installed and having swapped the 68150 over from the FN33 to FN40, seems like PS2-mouse related crashing has stopped. Or at least, is taking a short break :p

[frank.lukas]

There are ET4000 and MACH32 support in EmuTOS but no MACH64 support ...

[dml]

There are ET4000 and MACH32 support in EmuTOS but no MACH64 support ...

I thought that might be the case but thanks for confirming.

[agranlund]

There are ET4000 and MACH32 support in EmuTOS but no MACH64 support ...

I thought that might be the case but thanks for confirming.

On Raven, the bootrom initializes graphics card by running the vga-bios found on the cards rom.
This happens before an operating system is started, and EmuTOS's gfxcard startup-code is not compiled in for the Raven build.

I suppose it could be many things but it would be interesting to see if the problem lies in the emulated mini x86 environment for vga-bios.
Does it produce anything at all if you break into the monitor and run this:

Code: Select all

vga init

(the cards vga-bios may or may not make something appear on screen, or terminal)

and then this:

Code: Select all

vga test

(this will do a standard x86 vga-bios call to set Mode13h, and then it draws some colors on the screen)

[dml]

Sorry, have been slow with this due to working on the case install and cleaning/polishing the cooler coupling disc for mounting. The machine has mostly been off during this (I was also battling with a grumpy MegaST and an ATW800 setup at the same time which had me super distracted with problems).

I also wasted a bunch of time trying to recover a screw which I dropped into the case and it ended up in a secret channel somewhere. I spent nearly an hour swinging a full sized PC case around my head trying to shake out because nothing else was working. Bit of an unexpected workout.

cool1.jpg

case1.jpg

[dml]

...aaaah more setbacks. The USB-IDE adapter arrived and I just realised both the Hyperdisk & the adapter are female 44pin plugs :( so I would need to use pinheaders to connect them in a sketchy way.

Also, I tried to prepare the Hyperdisk on the Raven itself by PARCP'ing across HDDRIVER - but the device is not recognised on the IDE bus.

Not sure now if that's a problem with the Hyperdisk (quite possible) or the Raven (especially possible since I was involved) or HDDRIVER config.

I believe I did try this disk in the Falcon at some point and had some issues partitioning it for byteswapping but at least it was showing up as a device... Hmmm. A bit too many variables still... maybe I'll check it in the Falcon again with a TOS partition scheme...

[dml]

Have abandoned the Hyperdisk and reverted to more common CFlash adapter - but I think I'm misunderstanding or missing something...

When I mount the CFlash as the master device on the Raven's 44pin IDE slot, the machine behaves flaky and I can't access ROM drive 'C' from EmuTOS, seemingly due to a conflict with the CFlash. If I run HDDRIVER.PRG, it enumerates the CFlash device as a garbage ID (a row of special chars instead of the devicename).

If I switch it to slave, the device is not seen at all but I can access 'C" again from EmuTOS.

I was expecting to at least be able to enumerate the device from EmuTOS, if not actually partition and use it. Is this expected or is something up?

I can go back to trying with the IDE adapter from PC or with HDDRIVER from TOS with byteswapping - but it's not worth starting that if the above already suggests a fault somewhere.

[dml]

Ok I made a little more sense of what's going on.

Not sure yet why the machine is acting flaky but it might be independent from the IDE related activities. Will come back to that later...

So after quick-formatting the CFlash under Windows (using the adapter) and moving it to the Raven, the machine boots with the CFlash as drive 'C' but can't access the partition (its a single 4GB Windows FAT32 partition).

The ROM drive 'C' is now 'D' and so of course doesn't boot the RAM disk 'M'. So I do that manually. I transfer HDDRIVER 12.61 again to 'M' via PARCP tool from ROM disk 'D'.

Running HDDRIVER on the Raven enumerates the drive but with a garbage ID. I can then run HDDRUTIL and see the device enumerated correctly. However I can't operate on the drive - can't partition etc. So I guess I'm going to have to do this on an Atari machine (?)

I'll need to go back and dig through other threads to see how everyone is going about this but I'm always getting myself in a mess with disk setup related things :p

[exxos]

Bad DMA :P cloning Atari with excellence :lol: :hide:

[PhilC]

@dml your partition size is probably far too big and I believe it needs to be fat16? Try a partition under 500mb IIRC.