MAME Reloaded installation glitch

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Have MAME4Droid already installed
2. Install MAME Reloaded
3. At first run, choose to configure it with an alternative ROM Path

What is the expected output? What do you see instead?
Since I have the first MAME4Droid version already installed with its ROMs, I 
wanted to avoid to copy all the ROM files. So I just wanted both versions to 
aim for the same ROM folder. After configuring MAME Reloaded in that way I 
found that it installed itself in the ROM path I had given, rather than use 
that path just for the ROM folder

Just to explain: I wanted it to use \sdcard\roms\mame4all\roms folder (the old 
folder with all the roms), and it creted \sdcard\roms\mame4all\roms\mame4droid, 
with all the program subfolders inside!

I understand some ROMs may need to be different for the two versions, but I 
would prefer to avoid any possible ROM duplication. Am I bound to use two 
totally different installatino paths?

What version of the product are you using? On what operating system?
Mame4Droid on Galaxy S2, last Android OS version.

Please provide any additional information below.

Original issue reported on code.google.com by malha...@gmail.com on 12 Mar 2012 at 2:51

[GoogleCodeExporter]

The two versions romsets are so different that you might as well have different 
folders, very few 37b5 roms work in 134u4.

Original comment by matbur...@gmail.com on 12 Mar 2012 at 9:11

[GoogleCodeExporter]

Ah, if that's the case, I'll skip my tries.

Anyway, the program asks for the ROM path, which it's actually a bit 
misleading, as it is actually asking for an installation path instead.

Original comment by malha...@gmail.com on 13 Mar 2012 at 9:11