Problems with RunInUAE

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:

EXECUTE: Can't open ":T/command-0-T1"
object already exists
execute failed
return code 10

Tried snoopy to trace the error but without sucess because it only traces the OS4 and the error it's in the OS3.9 side :(

Any ideas why this happens?

@AlfaR0me0
I guess you first need to run the 68k SnoopDos inside E-UAE, then we might have a clue.

Alternatively, if you have an AmigaForever CD, then reinstall RunInUAE & just let it create a suitable bootable Workbench.

@AlfaR0me0
Also, you could try using RunInUAE's "Basic Workbench mode". I'd guess the game will run then.

@ChrisH

Thanks for your reply
Tried to run in "Basic Workbench mode" but with no luck, results in same error.

I will try to install a new hdf drive with a fresh Workbench 3.9, maybe it?s something in SS or user-SS of the old WB3.9 that make the error.

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

@AlfaR0me0
Did you re-install RunInUAE after creating a fresh WB 3.9? RunInUAE needs certain files installed, and they are added during installation.

Also, please try without Basic Workbench mode first.

@ChrisH

I have a problem too, I cant get the roms to work :(

@AlfaR0me0

You need this two lines to fix the problem in s:startup-sequence in UAE.

makedir ram:t
assign t: ram:t

@LiveForIt
Since you seem to know what the problem is, can you please tell me how/why it arises in the first place?

@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?

@AlfaR0me0 Quote:
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":

filesystem2=rw,Workbench_:Workbench:your_path_here,1

@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.

@ChrisH

Head the same problem whit my program ?Whdload-To-UAE?

read the comment section her:

http://www.os4depot.net/index.php?fun ... tility/whdload-to-uae.lha

@ChrisH

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.

@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:

#hardfile2=rw,DH0:Work:Storage/Amiga.hdf,32,1,2,512,1,
kickstart_rom_file=Work:EUAE/Kickstarts/Kick31.rom
filesystem2=rw,DH0:System:Work:EUAE/System39,1
filesystem2=rw,DH1:Work:Work:Jogos,0
#filesystem2=ro,CD0:AmigaOS3.9:Work:Storage/AmigaOS,0

joyport0=mouse
joyport1=kbd1

cpu_type=68040
#amiga.screen_type=ask
cpu_speed=max
cpu_compatible=false
cpu_cycle_exact=false
#cpu_24bit_addressing=no
show_leds=true

chipmem_size=4
fastmem_size=0
z3mem_size=32
gfxcard_size=4

chipset=aga
immediate_blits=true
collision_level=full

gfx_framerate=1
gfx_width=1280
gfx_height=1024
gfx_width_windowed=720
gfx_height_windowed=568
#gfxcard_size=16
gfx_fullscreen_amiga=no
gfx_fullscreen_picasso=no
gfx_linemode=double
gfx_correct_aspect=true
gfx_center_vertical=smart
#gfx_lores=no

hide_cursor=true

sound_output=normal
sound_bits=16
sound_frequency=11025
sound_channels=stereo