Not finding any disks - what am I doing wrong?

[NorthWay]

I know I had this working at some time; I have HDF dumps of my old HDs and I'm trying to boot or just plain see them in early startup from the files I have configured as disks.

What obvious thing am I missing? They are set as r/w and bootable. I have enabled uaescsi.device.

(BTW, I find it a bit counter-intuitive that the CS060 MK1 doesn't have both ROM file selectors in the same place and that the processor slot ram selector isn't disabled.)

[Toni Wilen]

Originally Posted by NorthWay

I know I had this working at some time; I have HDF dumps of my old HDs and I'm trying to boot or just plain see them in early startup from the files I have configured as disks

What obvious thing am I missing? They are set as r/w and bootable. I have enabled uaescsi.device.

Not enough information but assuming they are partition HDF, you need the geometry data from your old config.

uaescsi.device has never had anything to do with HDFs.

(BTW, I find it a bit counter-intuitive that the CS060 MK1 doesn't have both ROM file selectors in the same place and that the processor slot ram selector isn't disabled.)

Both ROM selectors? RAM not disabled? (Using some obsolete version?)

[NorthWay]

I moved over from WINE to Win7.
Suddenly it worked. Once. Then it behaved the same again.
I'm using both 3.3.0 and 3.3.4b9.
I'll scratch my head some more.
When deselecting options it doesn't seem to forget the old ones. I still get the colour-bars from the CS060 ROM even with everything deselected (3.3.0).

For the CS060 you can select "ROM -> Extended ROM file" and "Expansions -> Accelerator board ROM file". My memory is telling me that those are two different files, but all I can find on the net suggest they are the same??? I know I patched the SCSI device code to not read from high chipmem and burnt an EPROM with that. Shouldn't I have to specify that as a separate file for the scsi controller?

[Toni Wilen]

Originally Posted by NorthWay

I moved over from WINE to Win7.
Suddenly it worked. Once. Then it behaved the same again.
I'm using both 3.3.0 and 3.3.4b9.

Make also sure your HDFs are not open in some other program. If HDF is read-write, no other program can have it open in read-write mode.

Anyway, check the log.

I'll scratch my head some more.
When deselecting options it doesn't seem to forget the old ones. I still get the colour-bars from the CS060 ROM even with everything deselected (3.3.0).

This is fixed in 3.4 betas.

For the CS060 you can select "ROM -> Extended ROM file" and "Expansions -> Accelerator board ROM file". My memory is telling me that those are two different files, but all I can find on the net suggest they are the same??? I know I patched the SCSI device code to not read from high chipmem and burnt an EPROM with that. Shouldn't I have to specify that as a separate file for the scsi controller?

Thats just a side-effect that it appears to work when using extended ROM file (both use same ROM address space). Don't do it, it isn't enabling anything else that correct emulation requires. (like SCSI or flash ROM emulation etc)

[NorthWay]

So it seems to be about the CS060 expansion option and what Kickstart I use.
I hope I added the right info here.

[Toni Wilen]

winuaelog.txt was not included but I did find problems with CSMKI autoconfig mapping.

Did you get reboot loop or Halt 7 (H7) error code?

[NorthWay]

With 40.68 A4000 ROM I get reboot loop.
With 40.63 A500 ROM I get the insert floppy screen.