A question about creating hardfiles

[B14ck W01f]

Hi,

I read that the Amiga 2000HD has a SCSI hard drive, and I am creating a hardfile inside WinUAE that emulates this. I set the HD controller as SCSI unit 6, and when I used HDTools, I was able to partition the hard drive and then eventually format it using FFS. I installed WB1.3 on my main partition, while the other partition is reserved for games and applications.

Everything worked fine up until I tried to boot it using my A2000HD config. Now instead of WB booting, all I get instead is the Kickstart disk logo, as if there is no startup-sequence on the hard drive. So I'm guessing that I used the wrong unit number. So how do I know what unit number I should use?

[Toni Wilen]

All useful information is missing. SCSI ID has nothing to do with it.

[B14ck W01f]

OK, Thanks.

[Toni Wilen]

To add some useful information to my reply:

Assuming A590/A2091 SCSI: ROM version?
HDF size?
Partition sizes?
When formatting FFS checkbox was checked?
Kickstart version?

[B14ck W01f]

I forgot to specify the SCSI ROM file, and it boots now. Oh well, live and learn

Assuming A590/A2091 SCSI: ROM version? A590/A2091 SCSI ROM v7.0 (16k)
HDF size? 40MB
Partition sizes? 20MB System, 20MB Work
When formatting FFS checkbox was checked? Yes
Kickstart version? KS ROM 1.3 (A3000)(SK) rev 34.5 (256k)

I also set DH0: to bootable.

Also, with my Kickstart, it came straight from the Amiga Forever CD and this is the only 1.3 ROM I could find, possibly for a Slovakia A3000? But I thought that A3000's had Kickstart 2.04, not 1.3. Unless we are talking about earlier models.

I was afraid if I set up the hard drive incorrectly (possibly using an incorrect unit number), it would work to start off with, then give me a "Not a DOS disk in unit 0" error. I had this problem but thomas helped me get through it. So that's why I asked. But it works now, so thanks again!

[Toni Wilen]

How did you manage to mount the drive without rom?

Did you boot from A590/A2091 install disk? It loads disk based driver if A590/A2091 is jumpered to non-autoboot mode (which equals ROM disabled).

1.3 A3000 SuperKickstart image is practically identical to normal A500 1.3. Only differences are few tiny bug fixes. (that SetPatch also fixes)

[B14ck W01f]

Originally Posted by Toni Wilen

Did you boot from A590/A2091 install disk? It loads disk based driver if A590/A2091 is jumpered to non-autoboot mode (which equals ROM disabled).

I did not have the install disk handy so I had to use the ROM. I obtained a copy of the disk just recently, and the programs are useless if the driver is not installed so that KS 1.2/1.3 can recognize the unformatted hard drives (eg: HDToolBox reports "No driver installed".) However, I specified the ROM before booting the disk and found ut that the drivers are already built into the ROM. (My hard drive shows up in HDToolBox).

[B14ck W01f]

One more question. I am planning to do the same thing here with my A3000 and A4000 (and their "T" models") configs. WinUAE currently emulates the A590/A2091 and A4091 SCSI interface. How do I know which interface I should use for these configs?

[Toni Wilen]

Originally Posted by B14ck W01f

I did not have the install disk handy so I had to use the ROM. I obtained a copy of the disk just recently, and the programs are useless if the driver is not installed so that KS 1.2/1.3 can recognize the unformatted hard drives (eg: HDToolBox reports "No driver installed".) However, I specified the ROM before booting the disk and found ut that the drivers are already built into the ROM. (My hard drive shows up in HDToolBox).

But you said in first post that you partitioned it in SCSI mode. How does that work without driver?

Originally Posted by B14ck W01f

One more question. I am planning to do the same thing here with my A3000 and A4000 (and their "T" models") configs. WinUAE currently emulates the A590/A2091 and A4091 SCSI interface. How do I know which interface I should use for these configs?

Check the hardware specs and available expansions? There is not always single best or most common option.

A3000 and A3000T have identical hardware. Built-in A3000 SCSI.

A4000 can have A4091 or A2091 (but using A2091 would be stupid). More common use case probably was some accelerator board with SCSI or simply using mainboard IDE. Dozens of different combinations.

A4000T has built-in A4000T SCSI (which is technically A4091 without autoconfig and boot rom moved to KS ROM)

[B14ck W01f]

Originally Posted by Toni Wilen

But you said in first post that you partitioned it in SCSI mode. How does that work without driver?

I created my hard drive with RGB mode turned on, and I forgot to mention that I used the HDToolBox from the WB3.1 install disk, and I think that it has the driver built-in? I forgot to mention this in my original post because I was in a hurry. When specifying the FFS, I used l:fastfilesystem on the WB1.3 disk.

I tried setting up the same hard drive another way (with the A2091 ROM and the install disk) and I was able to partition it the same way I did before. But it was easier than before.