Emusaver 3.0 error can't resolve

[iamnaeth]

Hey all, trying to get the Emusaver 3.0 to work on my arcade and I'm running into a small problem.

I followed the steps listed on Howard's website.  I placed the cmd-launch7.exe and the appropriate .ini in my mame directory.  I also placed the .scr and appropriate .ini in to my windows root directory and installed them.

I then opened the screensaver and configured my directories to my mame executable and then my roms directory.  When I hit apply then preview I got the following error:

Run time error "5"
Invalid procedure call or argument

After a little bit of expermenting i found the problem was with the skip disclaimer and skip game info, whenever these were checked this error arose.

When unchecked however, the screensaverwould run however I think it wasn't loading a game.  The background would read, "loading game please wait" however, in the foreground would be a bunch of mame information with an open documentation choice.  Pretty much what happens when you click the mame.exe without specifying a rom to load.  Before you ask, yes I have my mame rom directory correctly specified, it reads as follows: D:\arcade\emulator\mame\roms\   All the roms are .zip in this directory.  

FYI:  I have an Athlon XP, running Windows XP and mame build v.82.

Thanks ahead of time for the help.

[iamnaeth]

No help on this?  

[iamnaeth]

On last try.  No one has had this error or knows how to resolve it?  I'd really like to get this software working.

[Minwah]

FWIW last time I tried to set it up I couldn't get it to work (I did get v1 or 2 working fine)...

I also was asked by email about it the other day from someone else who couldn't get it to work...asking for trouble but does it work Howard!?  

Maybe someone else could give it a try, I am too busy to spend time on it atm...

[Howard_Casto]

That's my problem, there very well could be a bug, I just don't have time to squash it atm.  

[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"

 

[Howard_Casto]

So your roms are in "mamewah/roms" and not "mame/roms"?

[max8061]

Correct, they are in D:\mamewah\roms. My emusaver.ini reads...

[EmuSaver]
WrapperName=cmd-launch7.exe
SkipWarnings=0
SkipBadDumps=0
SkipDisclaimer=0
SkipGameInfo=0
EmuPath=D:\mamewah\
WaitTime=120
ResetTimer=1
GamePaths=D:\mamewah\roms\
ExitKey=27
PauseKey=80
FileType=.zip
NoSound=0

[Howard_Casto]

Filetype should be *.zip , not .zip

[max8061]

Aw man! I have no idea how that got changed from default. Thanks for catching that, it works great now. 

[max8061]

Okay, I guess I lied. I only waited for it to load a game and then came back and posted that it works great. It only loads one game, waits for the timer, tries to load a second and exits to desktop. I found a thread describing the problem here...

http://forum.arcadecontrols.com/index.php?topic=18479.0

The ultimate fix in that thread was to use a different screensaver (link now dead). So, has anyone ever figured out how to get past this or should I give up on emusaver? 

[Howard_Casto]

I've gotta be honest, emusaver is pretty dead at this point.  If anyone wants to continue it I'll be glad to give them the source.  Unfortunately, most of emusaver is actually cmd-launch7 and I'm not sure I still have the source to that.