All of the sudden a "RAM Disk 2" started appearing on the screen of the emulated Workbench in RunInUAE when launching WHDLoad games.

Why is this happening? Is it normal? If not, how to get rid of that second RAM unit?

You don't, the second ram disk is the actual real ram disk iirc. very useful for copying files between os4 and uae.

Nice feature indeed. Maybe.changing its icon would be easier

@AmigOS
You started a "HD-installed" game from RAM:, so RunInUAE had to make E-UAE able to see OS4's RAM: disk. Since OS3 already has a RAM: disk, you end up with two RAM disks.

If you won't run games from RAM: any more, then it can be manually removed from the .uaerc_RunInUAE config file (a single line, likely near the bottom of the file).

Actually, since RAM: gets emptied on a reboot, it might make sense for RunInUAE to automatically remove RAM: unless it is being used to start a game....

@Chris

so if you start a game from RAM *once* RunInUAE modifies the config file?
It shouldn't IMO. The config should be "rock solid" or you cannot rely on it and every start is just random :-/

I understand you need to write a specific config file to run the selected file/game. Maybe you can use a file in T: which is overwritten everytime a game is started.

@Elwood
I don't really understand your objection. The positive side of the current behaviour is that you can access previously-used games/etc directly from Workbench 3.x . How is having partitions, previously used for E-UAE games, persisting between E-UAE reboots "random" & not stable?

In any event, the current behaviour was a side-effect of wanting to *prevent* the config file from being modified every time you launched something using RunInUAE. Improvements in the beta version of RunInUAE (*) mean this is technically no-longer necessary, but I'm not yet convinced a change of behaviour is needed.

* = which mean it does (usually) create a temporary config file in T: each time something is run.