LoadModule + scsi_4346beta on WinUAE/Amiga running AmigaOS3.1

[Mr B]

Short version. (I'll try and actually keep it short, my texts seam to outgrow my issues)
Testing is run on my WinUAE setup. It's configured as a normal A1200. When i'm satisfyed with my testing, i'll clean up, and put the drive in the real Amiga.

I put LoadModule (v40.12 as per the readme.) in C
Made a directory (Modules) for scsi.device_43.46b4_A600_A1200 in Dev.
Put the line "Loadmodule devs:modules/scsi.device_43.46b4_A600_A1200" as the very first in s:startup-sequence.

After boot i run "Loadmodule list" and it lists the darn thing. But HDInstTools still only see 8GB of a 13GB drive. Am i banging my head against some WinUAE limitation, and this is expected to go away when i put the disc in the real Amiga?
If not, what could i be banging my head against?

B!

[thomas]

Please define "see" in "But HDInstTools still only see 8GB of a 13GB drive."

HDInstTools cannot change the drive size if the drive is already ininitialised If you initialise it again, it should be able to partition the entire drive. Or try this: http://aminet.net/package/disk/misc/fixhddsize

[Mr B]

Originally Posted by thomas

Please define "see" in "But HDInstTools still only see 8GB of a 13GB drive."

When HDInstTools is scanning for devices it should detect actuall hardware parameters, i think?(Not true, i copied this statement from a earlier post in a different thread, just above it was explained that this is not whats happening, and this not happening was the cause of my troubles.) The true spec should be 26550 cylinders, 16 heads and 63 sectors. What i get is 16383 cylinders. The rest is right. Total size reported as 8.062MB. WinUAE, where you add the drive, knows full well it's 12.8GB large. (HD controller IDE0)

Originally Posted by thomas

HDInstTools cannot change the drive size if the drive is already ininitialised If you initialise it again, it should be able to partition the entire drive. Or try this: http://aminet.net/package/disk/misc/fixhddsize

Duh. I figured it was scanning for hardware spec's as well as locating the hardware when "scanning for devices" so i never thought of the possibility that it was simply looking at the drives current settings, and ignored the hardware. The fix, ofcourse, did it. Thanks.
B!