OS 3.1.4 and IDE Drive

[BanisterDK]

Hello

Maybe I'm a little rusty or have light Alzheimer but it looks like I have forgotten how to setup an IDE drive with WinUAE.

I'm using WinUae 4.4.0 64bit and installed 3.1.4 on a HDF
I have Kickstart 3.1.4 as Rom

My 40GB IDE is connected to my PC through an IDE 2 USB and it was detected by my Windows 10 as 40GB drive.

Here is where I have lost track since it is ages ago I installed it in my A1200 and perhaps my knowledge is lost.

I have tried to use IDE, UAE, SCSI

Drive as UAE is detected in HDToolBox and I can partition it. After a reboot it's gone again
For IDE and SCSI, HDToolBox can't see the Harddrive.

Perhaps I'm doing something wrong but as I said, my memory has passed out about this.

[thomas]

Did you click on "save changes to drive" before you left HDToolbox?

Did you try to disable your Windows antivirus? Some block direct access to USB drives.

Did you run WinUAE as administrator? This is required to get full access to real hard drives.

[BanisterDK]

Windows Defender deactivated
WinUae run as Administrator

Using UAE as Controller HDToolBox cant find HDD

Using IDE as Controller HDToolBox found my HDD
Setup Drivetype and saved it in HDToolBox
During partitioning I wrote Partition Device Name and pressed the Enter key after each name. Pressed OK, Saved changes and clicked Exit and did a reboot. No partitions available and HDToolBox did reset the partition table to start all over again.

Using Commodore A60/A1200/A4000 give same as using UAE

Using SCSI give same as using UAE

[Aardvark]

Originally Posted by BanisterDK

Using UAE as Controller HDToolBox cant find HDD

Remebered to put SCSI_DEVICE_NAME=uaehf.device in HDToolBox tooltypes?

[BanisterDK]

SCSI_DEVICE_NAME=uaehf.device added to tooltypes (HDToolbox1.png)

Using IDE or A600/A1200/A4000 gives this error trying to start from WinUae
WinUAE_HDD_HDF_Error.png

Using SCSI no HDD found

Using UAE (WinUae_HDD_UAE_Settings.png)
Gives HDToolbox2.png

Trying to save gives HDToolbox3.png

So have no clue what else I can do

[Thomas Richter]

Originally Posted by BanisterDK

SCSI_DEVICE_NAME=uaehf.device added to tooltypes (HDToolbox1.png)

Error 28 is "disk is write protected". Guess UAE prevents writing to the disk.

[thomas]

If WinUAE marks a harddrive with [OS] then there is some x86 OS installed on it.

Make sure that you select the right harddrive. Selecting the wrong one will destroy all data on it.

Use Windows disk management to remove all PC partitions from it. Or even better use DiskPart command line program and its CLEAN command to completely remove the partition table.

WinUAE should show it as [empty].

[outlawal2]

DISKPART is your friend! (I have seen this issue myself and DISKPART cures it)

[BanisterDK]

Done that.

WinUae found the disk as EMPTY as you wrote

Though it didn't change anything
Info from earlier still exist after DiskPart and Clean

[BanisterDK]

Although now I don't have the hdf handle is not valid.

SCSI, IDE and A600/A1200/A4000 now cant don Anything in ToolBox
UAE makes me make chances but Error 28 is still there when saving changes

Even though WinUae see the disk as empty I know have the full DH1 (my 40GB HDD) as uninitialised on the workbenscreen (Havn't tried formating it yet)

[Toni Wilen]

Applications can't directly write to harddrives if it has PC partition table which explains the first problem before clearing it with diskpart.

Write protection error can mean:
a) HDF/drive really is read-only (double check read/write checkbox is ticked)
b) Drive filehandle fails to open in read-write mode, winuae retries silently in read-only mode. (check the log. easiest way is to run winuae from command line with -log parameter). Usual cause is not running winuae as administrator.
c) Read-write mode open succeeded but writes still fail mysteriously (win32 write function returns 0 bytes written with weird error code). Usually cause has been bad USB adapter, sometimes some overprotective security software. (But this should return different error, unless used Amiga program silently converts all unexpected errors to write protected)

[BanisterDK]

a.) HDD was read/write (Tried all types)
b.) add the log file. Perhaps you can see whats wrong (used the uaehf.device)

[Toni Wilen]

Could you attach your config file?

There is something weird going on, log shows uaehf.device attempting to mount the drive as a partition hardfile (HDF without partition table). Which shouldn't be available for real drives.

Keep copy of your config file, remove the drive. Save config. Quit. Run winuae again, add the drive again. Does this fix it?

[BanisterDK]

It got a bit better. It now let me partion drive but with strange behaviors
See attached picture
I have done a diskpart, and remove partition with CLEAN but harddrive still looks like it's RDB

Also a new log with partition of harddrive

And an error validating partition during format

[BanisterDK]

Some more questions

Why does it set Volume to HDF for all except Uae ?

I simply can't understand why I can't partition my HDD

Disk has been set up with a Windows formating (everytime)
Used DiskPart and Clean (everytime)

Tried to Install 3.1.4 on a HDF file and attached HDD afterwards but problems are the same as earlier

Tried to boot from copy of Install disk and set SCSI_DEVICE_NAME to uaehf.device in Tooltypes of HDToolBox but still same results as earlier

Strange though that it worked before with 3.1. Disk was installed with ClassicWB

[Toni Wilen]

Did you attach wrong config file? It does not have real HDD configured but log has "ST94813A 152D20337A0C". (Which at least now mounts correctly in RDB mode so there probably isn't need for new config file anyway. But i'd still would like to see the old one)

Drive appears to have 3 Amiga partitions. Do you mean you still get errors or you managed to partition it but there are some other problems?

:ST94813A 152D20337A0C:\\?\usbstor#disk&ven_st94813a&prod_&rev_#813a22222222&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}:
RDSK dump start
RDSK at 0, C=19077 S=256 H=16
RDB: HostID: 00000007 Flags: 00000017
RDB: BL: 0 BH: 8191 LC: 2 HC: 19076 CB: 4096 HB: 66
RDB: PART block 1:
Partition 'SDH0' Dostype=444F5303 (DOS\3) Flags: 00000001
BlockSize: 512, Surfaces: 16, SectorsPerBlock 1
SectorsPerTrack: 256, Reserved: 2, LowCyl 2, HighCyl 3559, Size 7116M
Buffers: 30, BufMemType: 00000000, MaxTransfer: 00ffffff, Mask: 7ffffffe, BootPri: 0
Total blocks: 14573568, Total disk blocks: 78140160
First block 8192 dostype: 444F5303 (DOS\3)
RDB: PART block 2:
Partition 'SDH1' Dostype=444F5303 (DOS\3) Flags: 00000000
BlockSize: 512, Surfaces: 16, SectorsPerBlock 1
SectorsPerTrack: 256, Reserved: 2, LowCyl 3591, HighCyl 10770, Size 14360M
Buffers: 30, BufMemType: 00000000, MaxTransfer: 00ffffff, Mask: 7ffffffe, BootPri: 0
Total blocks: 29409280, Total disk blocks: 78140160
First block 14708736 dostype: 4469736B (Disk)
RDB: PART block 3:
Partition 'SDH2' Dostype=444F5303 (DOS\3) Flags: 00000000
BlockSize: 512, Surfaces: 16, SectorsPerBlock 1
SectorsPerTrack: 256, Reserved: 2, LowCyl 10771, HighCyl 19075, Size 16610M
Buffers: 30, BufMemType: 00000000, MaxTransfer: 00ffffff, Mask: 7ffffffe, BootPri: 0
Total blocks: 34017280, Total disk blocks: 78140160
First block 44118016 dostype: 78BFB2EE (x\191\178\238)
RDB: LSEG block 4:
LSEG: 444f5303 (DOS\3) 46.13

First appears to be formatted (has DOS\3 identifier but it could be also some old data) but remaining 2 are unformatted ("Disk" and "0x78BFB2EE"). AmigaDOS shows unknown dostypes that way in Workbench (I am not sure if all OS versions do it). and by coincidence first 4 bytes of second partition started with ASCII characters and you got unexpected "Disk" on WB

This issue should go away after format. (but remember to use quick format, full format only wastes time)

btw, you should change max transfer to 1FFFF using hdtoolbox if you want to use it safely in real A600/A1200/A4000 IDE.

[BanisterDK]

ST94813A is my 40GB Seagate disk



Change the max transfer to 1FFFF as stated

It seems to me that I have Size Limit on partitions

I tried 3 partitions (4GB,15GB and 19GB)
First 2 partitions went well but the third (19GB) made an error

When I deleted that partition and created 2 other partitions (15GB and 4GB) then formating went well

I used the -log to make a new log file and there is a lot of 'Out of Events'
Is that a good or bad sign (log file attached)

[BanisterDK]

Shows my 4 partitions which works but with a 15GB limit

Other picture is from my 19GB partition which fails to format

Included the new logfile with thos 'Out of Events' in it

[Thomas Richter]

Originally Posted by BanisterDK

Included the new logfile with thos 'Out of Events' in it

That reads by my eyes "out of memory", and it means exactly that. There is insufficient memory to validate the partition, i.e. it is too large for the amount of memory available in your system.


To avoid that, go back to HDToolBox, expert settings, file system parameters, and set the block size to something larger than 512 bytes. Many if not all modern drivers have a physical block size of 4096 bytes today, and it is in general a good idea to use a larger size here as well. This will reduce the amount of memory by a factor of 8 already.

[BanisterDK]

So now I deleted the HDD with diskpart and my config is still the same.

I use uae when adding HDD in WinUae
I set 1FFFF as max fil transfer
I set 4096 bytes as block size

Making my 3 partitions as earlier but none of them is showing as uninitialised
Like in not showing up at all after reboot.