Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Lightguns Arcade1Up Try the site in https mode Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news

  

Author Topic: CMD Wrapper 2.0 Issue  (Read 2400 times)

0 Members and 1 Guest are viewing this topic.

bhille

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 76
  • Last login:January 02, 2003, 11:39:40 pm
  • Be the ball...err...be the arcade machine...
CMD Wrapper 2.0 Issue
« on: November 22, 2002, 07:46:08 pm »
Okay, I've been trying to setup my atari 2600 emulator to work with Laz for awhile now.  I couldn't get it under Laz 3.0 and now I'm struggling with Laz 4.0.  I tried the orignal cmd wrappers (version 1.0) and the newer one with the debug (version 2.0).  I think it has something to do with the z26.cfg file.  There's two options: send rom key and send exit key.  No matter how I set these, with the 1.0 wrapper, the emulator launches and runs great.  When I exit the emulator, Laz hangs....actually I just don't think Laz realizes I quit the emulator.  It also doesn't matter what I put in the {handles} section of the lconfig.ini either.  So, I try version 2.0 of the wrappers and I still have trouble.  I used the debug version so I could document the following:

rom key=0
exit key=1
laz _log=cmd-launchdebug.exe advnture -keyx 27
parsing _log=z26.exe

rom key=0
exit key=0
laz _log=cmd-launchdebug.exe advnture
parsing _log=z26.exe e

rom key=1
exit key=0
laz _log=cmd-launchdebug.exe c:\emulator\atari260\roms\advnture.bin
parsing _log=z26.exe n

rom key=1
exit key=1
laz _log=cmd-launchdebug.exe c:\emulator\atari260\roms\advnture.bin -keyx 27
parsing _log=z26.exe

This is on a Windows98SE box.  In summary, version 1.0 of the wrapper will launch the emulator and rom great, but can't exit properly.  Version 2.0 of the wrapper will exit properly (like when it launches z26.exe without a rom) but can not launch the emulator with a rom.

Can someone please help?  I don't know that it's a program issue.  I'm sure it's a user problem, but I just can't figure this out.  Please help  :'(

Howard_Casto

  • Idiot Police
  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 19427
  • Last login:July 13, 2025, 11:38:27 am
  • Your Post's Soul is MINE!!! .......Again??
    • The Dragon King
Re:CMD Wrapper 2.0 Issue
« Reply #1 on: November 22, 2002, 11:08:51 pm »
It's not a user problem.  The wrappers won't exit on all programs.  However you are missing a rather obvious solution.  After you exit the emulator press the key you assigned to exit.  As nothing will have focus the wrapper should detect the key and exit.  

bhille

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 76
  • Last login:January 02, 2003, 11:39:40 pm
  • Be the ball...err...be the arcade machine...
Re:CMD Wrapper 2.0 Issue
« Reply #2 on: November 23, 2002, 12:04:29 am »
Thanks for the post HC.  I appreciate you trying to help me.

I tried using escape (as I think 27 is), but that doesn't work.  I tried every key on the keyboard, and nothing exits.  I just end up ending the task.  Interested note though, when I do end the task the laz_log.txt isn't updated.  Also, if I end the s-11 launch tast before the lazarus task, lazarus relaunches the emulator.  Not sure if that means anything.

I am curious though, why I have those weird errors with the version 2 wrappers.  It seems to start the emulator right and exit correctly if I could just figure out how to pass the rom to it.  I don't understand.  I must have it setup right according to the laz_log.txt, but the parsing_log.txt would indicate otherwise.  I did notice too that the {handle} section is missing in the 2.0 wrappers, but that didn't seem to make a differece since the 2.0 wrappers work better anyway.

Any other ideas?

)p(

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 964
  • Last login:March 27, 2009, 03:38:15 am
  • We are the Galaxians...
    • Emulaxian:cabinet and frontend
Re:CMD Wrapper 2.0 Issue
« Reply #3 on: November 23, 2002, 02:22:19 am »
-from looking at the laz log's...a suggenstion, put your z26.exe in your 2600 roms folder and set laz up in such a way that it launches: cmd-launchdebug.exe advnture.bin -keyx 27 be sure it only uses the romname with extension.

peter

bhille

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 76
  • Last login:January 02, 2003, 11:39:40 pm
  • Be the ball...err...be the arcade machine...
Re:CMD Wrapper 2.0 Issue
« Reply #4 on: November 23, 2002, 07:32:20 am »
That's what's interesting.  When you look at the laz_log.txt it looks like all the information is getting passed correctly.  I mean, it has the cmd-launchdebug.exe, the romname, and the exit key.

From what I can tell, the parsing_log.txt is what actually gets passed to the emulator.  Because when "z26.exe e" is passed, I have to close the DOS box that has "z26.exe e.bin     ROM not found".  So, it looks like the version 2.0 wrappers won't work for me.

I can get the emulator to startup correctly with the roms with version 1.0 of the wrappers, but then I can't exit the emulator correctly.

Could this be an O/S issue?  I've read that HC programs on XP, maybe the wrapper don't like Windows 98SE.  Is this possible?

Brian

Howard_Casto

  • Idiot Police
  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 19427
  • Last login:July 13, 2025, 11:38:27 am
  • Your Post's Soul is MINE!!! .......Again??
    • The Dragon King
Re:CMD Wrapper 2.0 Issue
« Reply #5 on: November 23, 2002, 01:01:16 pm »
No the wrappers aren't working for z26.....

They are designed for arcade emulators and thus I only try to keep up with supporting arcade emus.  The rest are pretty much tough luck if they don't work.  Sorry.


Also )p( is right next to no emulators will work if you don't send the full romname and extension with it.  When you send it "e" how is it supposed to know what e is and where it's located?  You need to be sending c:\z26roms\e.bin so it doesn't get confused.  :)

bhille

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 76
  • Last login:January 02, 2003, 11:39:40 pm
  • Be the ball...err...be the arcade machine...
Re:CMD Wrapper 2.0 Issue
« Reply #6 on: November 23, 2002, 06:42:35 pm »
Well, I guess if it specific to z26 then I'm SOL.  What I don't understand though, is if the laz_log.txt indicates that I'm sending the full path and not the exit keys, why does the parsing_log.txt indicate it's only sending "z26.exe n"  Shouldn't the parsing_log.txt match what the laz_log.txt indicates?  Maybe I just don't understand the parsing_log.txt purpose.  I thought it showed exactly what was getting passed to the emulator it was wrapping.  If that's the case, then wouldn't this be an issue no matter what I was wrapping (z26 or arcade emulator)?

Howard_Casto

  • Idiot Police
  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 19427
  • Last login:July 13, 2025, 11:38:27 am
  • Your Post's Soul is MINE!!! .......Again??
    • The Dragon King
Re:CMD Wrapper 2.0 Issue
« Reply #7 on: November 23, 2002, 10:38:29 pm »
The lazarus log file is updated AFTER the emulator you launched has successfully closed. In other words if you are having to use the 3 finger salute to get out then it doesn't get updated.  

And no they shouldn't be the same....

The exit keys and other misc junk are filtered off by the wrapper.  If they were to be sent to the emulator it would cause syntax errors.... it reads the supplemental data, removes it, and re-sends the command line.  

Also the debug data is pretty much greek to anyone but me.  :)  You need to send me the laz log.txt (if it's getting written)  the debug log, and other useful info... (like the z26.cfg file... where your roms are located, ect.)  

I'll try to help out just this once, but no console questions.!!! :P

bhille

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 76
  • Last login:January 02, 2003, 11:39:40 pm
  • Be the ball...err...be the arcade machine...
Re:CMD Wrapper 2.0 Issue
« Reply #8 on: November 24, 2002, 06:03:12 pm »
I'll try to help out just this once, but no console questions.!!! :P

I just emailed you.  Thanks again HC!