|
14 April 2012, 15:06
|
#1 |
|
Registered User
Join Date: Jan 2002
Location: Germany
Posts: 7,036
|
WinUAE fails to access empty hardfile on IDE0
If I connect an empty (newly created) hardfile (HDF or VHD) of a certain size (20 MB works, 500 MB doesn't), WinUAE fails to access it. Symptoms are: an ADF of Install3.1 in DF0 is unreadable, it returns to the insert disk screen. If another bootable harddrive is present (and no floppy disk), then WinUAE starts to boot but crawls in a completely unusable slow speed so that I never came to the point where I could install the harddrive.
If I connect the same HDF to UAE and initialize it with HDToolbox, then I can connect it to IDE0 without problems. I noticed this since a few WinUAE releases of the 2.x range. |
|
|
14 April 2012, 15:20
|
#2 | |
|
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,576
|
Quote:
("hfd open" line actually means "attempting to open"..) |
|
|
|
|
14 April 2012, 16:36
|
#3 |
|
Registered User
Join Date: Jan 2002
Location: Germany
Posts: 7,036
|
Last test was .vhd, not .hdf, so the log is wrong. I don't know how this could happen, the config file is right. Here is a new log.
|
|
|
|
14 April 2012, 16:47
|
#4 |
|
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,576
|
Does anything change if you also add some HDF to IDE1?
|
|
|
|
14 April 2012, 17:33
|
#5 |
|
Registered User
Join Date: Jan 2002
Location: Germany
Posts: 7,036
|
Yes, with two HDFs it works as expected, boots up and I see two "unknown" devices in HDToolbox, ready to change drive type.
|
|
|
|
14 April 2012, 17:49
|
#6 |
|
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,576
|
I think hack that prevents KS3.1 long IDE detection delay is causing some ROM update to become confused and detects slave drive.
My OS3.9 test installation sends 2 commands to IDE1 (Identify drive and ATAPI identify), when only IDE0 is available. But I don't notice any slowdowns. |
|
|
|
14 April 2012, 19:43
|
#7 |
|
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,576
|
Which AOS version you use? (Exact version)
I assume it hangs after SetPatch has loaded and booted once? |
|
|
|
14 April 2012, 20:25
|
#8 |
|
Registered User
Join Date: Jan 2002
Location: Germany
Posts: 7,036
|
I used expanded high-end example config with A4000 3.1 ROM (40.68), chipset changed to A4000 and 3.1 install disk in DF0. No ROM update or something.
As I said above, it does not boot at all because it cannot read from DF0. It behaves as if an unreadable disk is in the drive: it clicks two times and returns to the insert-disk animation. |
|
|
|
14 April 2012, 21:26
|
#9 |
|
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,576
|
Ok, I can duplicate it now. Don't see any weird IDE hardware accesses. It could be strange ROM scsi.device bug.
|
|
|
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| WinUAE showing Windows drives and folders as empty | timscampi | support.WinUAE | 6 | 22 April 2023 17:24 |
| Speeding Up 2088 Bridgeboard HardFile Access ? | Pioneer500 | support.Hardware | 0 | 16 May 2013 18:15 |
| Transferred Hardfile comes up as NDOS in WinUAE? | rlcarr | support.WinUAE | 0 | 26 April 2008 22:48 |
| Winuae Hardfile | littleb2005 | support.WinUAE | 3 | 03 May 2007 20:05 |
| WinUAE 1.2 fails to start on Windows 95 (OSR2.5) | mark_k | support.WinUAE | 8 | 31 July 2006 13:29 |
|
|
