Can't partition 4GB CF in UAE

[videofx]

I have deleted the CF from disk management. I tried mounting the drive as IDE0 with toolbox set to scsi.device and toolbox sees nothing. I mount the drive as UAE and toolbox to UAEHF.device and I get drive unknown. OK, so I go and click change drive type. Then click read configuration from drive, then I get an error DRIVE DOES NOT SUPPORT SCSI QUERY. I am trying to do this so I can put the CF in a real Amiga 4000T

Any help would be appreciated

Thanks!

[Toni Wilen]

IDE problem: most likely mismatched hardware and KS ROM version or IDE emulation not enabled. Chipset panel Chipset extra must match ROM version.

UAE: No idea. Ancient hdtoolbox?

[sneeker]

Have you done a clean on cf from in diskpart? If the cf card has an mbr on it the amiga wont see it.

[videofx]

No, how do I clear the MBR in diskpart?

cheers

[Toni Wilen]

Non-empty drive won't cause this kind of problem. WinUAE would only force it in read-only mode.

Are you sure you added the drive as a harddrive (Using "Add Harddrive" button), not as a Windows drive letter directory? (Add Directory/Hardfile)

[videofx]

Hi Tony,

I just downloaded the latest WinUAE,Set CPU 68030, Chipset ECS Agnus, Chipset Extra A2000,My 3.1Boot ROM is for A2000., cick add hard drive, Choose my CF which it MBR Generic CF 3.7GB, choose IDE 0, clcik Read/Write, Click Add hard drive, All I am doing is mounting my 3.1WB floppy and going to HDTools and its set to scsi.device and HDtoolbox doesn't see anything.

Thanks!

Bill

[Toni Wilen]

A2000 does not have on-board IDE. Just use UAE (uaehf.device), drive is less than 4G, no need to test drive limits under emulation. (But remember to change max transfer)

Move the CF card in topmost position in harddrives panel. Some versions of hdtoolbox may stop enumerating after first drive (which normally is directory filesystem drive).

[videofx]

OK, I got the 4000 ROM and changed HDTools to scsi.device., Set Hard drive to IDE 0, went into windows disk manager and removed the drive. Booted WB 3.1 and went into HDtools, it sees the 4GB CF, so it says Changed and save changes, Click partition and made 1 , 4GB partition. Exit HDtools, Run Install for WB3.1, it doesn't see the CF card which I made DH0:, went into HDTools and the card does not appear

[Toni Wilen]

If you boot without startup-sequence with WB3.1 disk, then type "info", does the new partition appear?

[videofx]

I press both left and right mouse buttons while booting but dont get screen to bypass startup sequence. Where do type INFO?

Thanks!

[Toni Wilen]

Originally Posted by videofx

I press both left and right mouse buttons while booting but dont get screen to bypass startup sequence. Where do type INFO?

Thanks!

You are probably not fast enough, it is nearly impossible if JIT is enabled
You can boot to WB, then open CLI/Shell window and type info.

[videofx]

OK, I disabled startup sequence but since WB is not installed I am taken to AmigaDos prompt 1> and of course when I type INFO it doesn't recognize the command

[fitzsteve]

Sometimes it's just easier to create the RDB and partition/format the CF on a real Amiga using a Workbench Install Disk. Then you can move back to the Emulator and continue to do your installation.

Also on the Emulator are you running as 'Administrator?' You might need to actually right click on the icon and choose 'run as admin'

[roy bates]

+1 for steve.

[Toni Wilen]

Originally Posted by videofx

OK, I disabled startup sequence but since WB is not installed I am taken to AmigaDos prompt 1> and of course when I type INFO it doesn't recognize the command

Boot from your WB disk. Do you have some extra drives configured if you get empty CLI screen? Or did you managed to format the CF drive after all?

[videofx]

No extra drives configured. Was not able to format the CF. Now I am back to not being able to have the CF recognized in HDTools

[Toni Wilen]

Don't attempt to randomly change settings until something appears work... You wouldn't do the same with real hardware

Use latest 2.6 beta, tick logging checkbox in paths panel, load your config, make sure drive is selected and read-write checkbox is ticked (if disabled: you don't have admin privileges), boot normally, use hdtoolbox normally (if you use uae controller, open shell window and type "tools/hdtoolbox uaehf.device", no need to change tooltypes). Quit emulation. Attach winuaelog.txt.

[videofx]

I used the 2.6 beta and was able to successfully partition the CF. However WB 3.1 still didnt mount the drive so I could format so I rebooted and WinUAE crashed. Here is the winuaelog.txt

Thanks

[Toni Wilen]

Originally Posted by videofx

I used the 2.6 beta and was able to successfully partition the CF. However WB 3.1 still didnt mount the drive so I could format so I rebooted and WinUAE crashed. Here is the winuaelog.txt

You didn't enable logging, winuaelog.txt is much more important than winuaebootlog.txt. (But at least CF was detected correctly in winuaebootlog.txt and it didn't have any PC partitions)

Also attach the crash dump file (winuae_<something>.dmp)

Please check c:info result. There is FFS/dos bug that mounts the new unformatted partition in "no disk in drive" state if drive has specific old garbage in first block (0xffffffff). This is not too rare.