Hi there, I'm trying to run classic games with RunInUAE inOS4.1.1 I have installed WHDLoad to E-UAE with the respective key in L: and have an hdf with WB 3.9 with WHDLoad installed too. All seems ok but when I try to run a game this error appears always in the cli window:
Now I installed a new fresh WB 3.9 but when tried to run a game in RunInUAE with "Basic Workbench Mode" enabled it opens a window inside WB screen with the title:
"StuntCarRacer starting... Please Wait!"
and nothing more happens.. if I close this window it stays in WB screen
@ChrisH Yes I do reinstall RunInUae. Seems to be a problem in WB 3.9, I discovered that all files in it are write-protected.. could it cause a problem?
@magic Do you reedit .uaerc to include the full path to your roms? Do you already tested your roms so can know if they are not corrupted?.. are they the right version?
I discovered that all files in it are write-protected.. could it cause a problem?
I wouldn't have thought so, but you never know. Open your .uaerc_RunInUAE file, and check that the Workbench partition is declared Read/Write not Read-Only. Specifically, the following line should be "rw" not "ro":
@LiveForIt Thanks for your hint but that lines already are in my UAE S-S from the beginning. What was in fault at S-S is "C: AddDataTypes REFRESH QUIET" but already fixed it.
@ChrisH
I know .uaerc_RunInUAE it?s ok. I installed WB 3.9 in WinUAE and then I made a copy of the folders to SAM440 but they are write-protected from beginning. Now I?m in doubt if it was better to install WB 3.9 directly from E-UAE
@AlfaR0me0 Ah, I assumed you installed OS3.9 directly inside E-UAE (somehow - never tried).
Copying files from WinUAE to E-UAE is likely to mess-up the file attribute flags (protection bits), some of which are important. I would suggest using LHA *inside* E-UAE to archive Sys:, and then just using UnArc on OS4.
If I remember correct its the execute command that generates the temorrary file that fails, when T: is not assigned to ram, because file locking is not freed on the file system, when E-UAE reboots like on a real Amiga, so this is really a E-UAE bug.
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
@LiveForIt That explanation does not seem to fit, because Basic Workbench Mode did not fix the problem, and I know for certain that this creates RAM:T and then assignes T: to it.
After tried hard modifying .uaerc finaly can run whdload but every game I run (no matter if run in WB directly or through RunInUAE) didn't show any image in UAE screen, instead show a black screen and some odd patterns. When tried to configure Picasso 96 it says that there is no gfx card attached so I run in HiRes laced. Any Ideas about what could be wrong?
I have a SAM667EP and run E-UAE 0.8.29 - amigfx, here is my .uaerc: