Main > Software Forum

Emusaver 3.0 error can't resolve

<< < (2/4) > >>

iamnaeth:
Howard, did you ever get a second to look at this bug?

Terry:
This response is a bit late, but I also had this problem.

The fix is to make sure that in the rom path you enter while setting up emusaver.scr you include a / at the end of the path.

For example:  c:/mame/roms/

Then press the ADD button.  If you leave this / off, it will start up mame just as you described.

Hope this helps if you haven't already figured it out.

Terry:
Ooops, I meant to say \ not /   :)

Howard_Casto:
thank you for finding this for me.....

as i manually add most paths this very well could be the issue.

I'll try to check it this week and if this is indeed the culprit, i'll release a new version. 

max8061:
I hate to pull up an old thread, but I'm having this exact issue and have been searching all morning for the answer. Same deal as iamnaeth was experiencing. I do have the trailing backslash on the roms path...

D:\mamewah\roms\

The only thing I see as possibly different in our two cases is that our roms on are the D: drive.

I checked the emusaverstats.txt and this is what is shows...

The last command sent was: 
cmd-launch7.exe  -wait 120 -reset -keyx 27 -pkey 80

It's not sending a rom name.


(Minwah) -
I'm having a related problem with MAMEWAH 1.62b9+. Anytime I change "saver_type" under "Screen-Saver Settings", it will ALWAYS change back to "gamelist_slideshow"

 :banghead: :banghead: :dizzy:

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version