ramlib error with whdload 18.8

[Condor-2-4-2]

Hello,

I have an issue with the autostart of whdload games. I'm using Amiga OS 3.2.1 with WHDLoad version is 18.8.6478 under WinUAE 4.9.1.

I use a script file 'START' for each whdload game which I execute with user-startup on boot.

Now when I run a game the whdload info screen appears for a few seconds until the game automatically starts. In a short moment between the disappearance of the info screen and game loading it appears the message:

ramlib
Programm failed (error 80000004)
Wait for disk activity to finish

After this error the game itself is running without problems. But after quitting the game the workbench doesn't load.

But when I run the game and manually override the autoload by pressing spacebar or return at info screen then the error message doesn't appear. And if I quit the game, the workbench is booting without problems.

So it seems to me that the ramlib error is caused by the autoload routine. Has anyone an idea what causes the issue and how to solve it?

My system specifications under WinUAE are:

Kickstart ROM A1200.47.102 / CPU 68020 / cycle exact full / chipset AGA / 2MB Chip RAM / 16MB Z3 Fast RAM / RTG UAE Zorro III

I also attached my user-startup and startup-sequence.

[Condor-2-4-2]

I have to add that the issue appears for me on many (not all) whdload games and only if I run them with autostart on boot. I'm using the same WinUAE settings for all whdload games, which I wrote before.

[daxb]

If you comment the START script in your U-S do you get the same error?

[Condor-2-4-2]

If I comment out the START script in user-startup, there is no error message and the workbench is loading.

If I wrote before, the error does only appear If I wait until whdload automatically starts the game after a few seconds from info screen. If I press return at whdload info screen to load the game immediately, than the error doesn't appear.

[daxb]

If I understand it right everything works fine if you start a game manually and only the START script triggers the ramlib error, right? If yes you may write a bug report including your script, so wepl can reproduce it.

[Condor-2-4-2]

I have tested the games where the error occured with ClassicWB 3.1 and used the same WinUAE configuration as with AmigaOS 3.2.1. And here all the games are loaded without error. There seems to be a problem with my specific Amiga OS 3.2.1 installation, which is causing this issue. I will do a clean reinstall of my system now. Perhaps I can further enclose this issue.