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: MAMEWAH self corrupting (?)  (Read 913 times)

0 Members and 1 Guest are viewing this topic.

JoeB

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 628
  • Last login:June 27, 2025, 08:23:34 am
  • NES Fanatic
MAMEWAH self corrupting (?)
« on: October 05, 2003, 03:08:45 pm »
I use my regular desktop computer with the XP remote desktop to connect to the arcade machine for remote administration.

I noticed that when I do that, the remote desktop controller connects @ 1024x768, and so the MAMEWAH shows up as a mall box.  I press 2, select exit and off doing maintenance.

What I did notice is when MAMEWAH tries to get back it, and exits with an error.. and the cause is the MAMEWAH.CFG file is corrupt! About 3/4 of it is missing!  Anyone else noticed this problem??

I still haven't figured out the problem with this thread either:

http://www.arcadecontrols.org/yabbse/index.php?board=3;action=display;threadid=11994

Minwah

  • Trade Count: (+3)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 7662
  • Last login:January 18, 2019, 05:03:20 am
    • MAMEWAH
Re:MAMEWAH self corrupting (?)
« Reply #1 on: October 06, 2003, 05:16:29 am »
I noticed that when I do that, the remote desktop controller connects @ 1024x768, and so the MAMEWAH shows up as a mall box.  I press 2, select exit and off doing maintenance.

What I did notice is when MAMEWAH tries to get back it, and exits with an error.. and the cause is the MAMEWAH.CFG file is corrupt! About 3/4 of it is missing!  Anyone else noticed this problem??

I don't really understand this part, but some other users have found their config file to be incomplete.  The only solution that some have found is that there is >1 instance of MW running - check that first...

JoeB

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 628
  • Last login:June 27, 2025, 08:23:34 am
  • NES Fanatic
« Last Edit: October 06, 2003, 02:36:13 pm by JoeB »