Failing to set up a HD for wb1.3

[Doc Mindie]

THis is for WinUAE 1.0.0.0

I've tried to tweak and things in WinUAE

I've tried to boot with the adf "A590 setup" and set the icon tool to "device=uaehf.device"

No luck.

The emulated a500 refuses to find the hardfile.

What am I missing?

[onedevotee75]

You need the file FastFileSystem from the WB 1.3 Disk in the same Windows folder as your Kick13 rom is located. If it is not in the same folder, hardfiles can´t be found under kick 1.3. And finally before you can use the hardfile you need to format the hardfile under kick2.x or higher.

CU

[Toni Wilen]

I've tried to boot with the adf "A590 setup" and set the icon tool to "device=uaehf.device"

Do you have "RDB"-mode enabled in hardfile properties panel? You can't partition regular HDFs.

You need the file FastFileSystem from the WB 1.3 Disk in the same Windows folder as your Kick13 rom is located

Only "ancient" WinUAE versions needed this. In "non-ancient" versions you can simply point FileSys-path in hardfile properties to FastFileSystem from WB1.3 disk. (must be from WB1.3 disk. Newer versions will crash under KS 1.3)

Note, this is only needed with regular (non-rdb) hardfiles.

[Doc Mindie]

Originally Posted by Toni Wilen

Do you have "RDB"-mode enabled in hardfile properties panel? You can't partition regular HDFs.

Yep. tried both with an without RDB-mode enabled.

Originally Posted by Toni Wilen

Only "ancient" WinUAE versions needed this. In "non-ancient" versions you can simply point FileSys-path in hardfile properties to FastFileSystem from WB1.3 disk. (must be from WB1.3 disk. Newer versions will crash under KS 1.3)

Note, this is only needed with regular (non-rdb) hardfiles.

THIS I haven't tried yet......so I load up WB13, copy L:FastFileSystem to somewhere on the PC-drive, to which I point the FileSys properties......righT?

I'll try that, thanks Tony an OneDevotee

EDIT: I've now got a 120MB HD for my "A500"

Was a hassle to figure out, but it's done now.

Thanks again, both of you

[Doc Mindie]

Okay.....I'm not sure about what causes this new fault....but whenever I reboot the WB13 HD....it comes up as not validated. It's a pain to use Diskdoctoreverytime I reboot the emulated drive.

Suggestions I can try? I've copied fastfilesystem from the WB1.3 disk to the rom-dir.....could this have anything todo with it?

I tried the "Park" program on the A590 disk, with the error "Disk not found" or something similar.

[onedevotee75]

Did you format the disk under Kick 2.x or 3.x? When you format the HD, try it with setting the point "Fast File System" in the format screen.

CU

[Doc Mindie]

hmmm...I didn't format it fastfilesystem......

But, on the other hand, when I "reloaded" the wb13, (after formatting under 2.0) it came up as "unreadable" so I formatted it under 1.3

[onedevotee75]

I descirbe you, how i set up a harddisk file, and i have no porblem with it.

First i start WinUAE Then i go to harddrives, then add hardfile, after this i set the size (e.g. 20 MB) and then on create and save this hardfile.
Then i load a WB 2.0 Setup and boot from the WB2.0 Disk. On WB Screen the harddrive is signed "dh0:nodos". Then i format it by clicking the icon one time and the i go to "Icons / Format Disk" After this it is signed "Empty". Then i load a WB 1.3 Config. I don´t do point to the FastFileSystem File. It is placed in the folder where the kick 1.3 rom is located. The i go to the hardfile folder, then add hardfile and select the formated hd. After booting the WB the hd called "Empty" is on the WB Screen. I don´t go the way like described from Toni Willen (soory Toni ), to point to the fastfilesystem file because i get an error message after selecting the hardfile. So i place it in the same folder as my kick13 rom.

Works very well

[Toni Wilen]

Originally Posted by onedevotee75

because i get an error message after selecting the hardfile. So i place it in the same folder as my kick13 rom.

And the error message is? Checking winuaelog.txt may also help..

I just created FFS hardfile that boots under KS 1.3. Worked fine.

I really recommend using filesystems "properly" because in some future version filesystem autoload from Kickstart ROM path will be removed. (it is ugly hack..)

[onedevotee75]

It´s just a small Window, that appears saying "Bad Hardfile". Nothing more. Also in the log file there is no entry why this message appears.

[Toni Wilen]

Check winuaebootlog.txt (sorry, wrong log. winuaelog.txt is only used after configuration is loaded and emulation started)

FileSys-path should have nothing to do with this error. Filesystem is only used after emulation has been started.

[Doc Mindie]

uhm, yeah....I noticed yesterday, it doesn'tcome up as bunvalidated if I don't format it, anymore.....I used a few steps here (ditching the FFS again, just formatting under WB2.0) and it works fine.

But, if I try "enable RDB-mode" I get the error "Hardfile not found" when I exit the hf-selector.....I'll check the uaebootlog to see if there's anything there
EDIT:

from my uaeboot.log:

load config 'D:\WinUAE\Configurations\config_ocs_doc.UAE':0
close handle=00000000
hfd open: 'D:\WinUAE\hardfiles\13Bench.hdf'
HDF 'D:\WinUAE\hardfiles\13Bench.hdf' opened succesfully, handle=0000017C
D:\WinUAE\Roms\Kickstart v1.3 rev 34.5 (1987)(Commodore)(A500-A1000-A2000-CDTV)[o].ROM
save config 'D:\WinUAE\Configurations\config_ocs_doc2.UAE' REM I saved another config here, enabled RDB and used then "new" config
close handle=0000017C
close handle=00000000
hfd open: 'D:\WinUAE\hardfiles\13Bench.hdf'
HDF 'D:\WinUAE\hardfiles\13Bench.hdf' opened succesfully, handle=0000017C
---

okays, I started the OCS with RDB-mode enabled on the hardfile, and it wouldn't boot from the hf.....so I insert the A590-install adf.....loads fine, but no HD in WorkBench. So I try HDToolBox (with tooltype "Device=uaehf.device") which said...."Drive not installed" 'n such

------

Strange, it works just fine without the RDB-mode enabled