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: Mala Error  (Read 1015 times)

0 Members and 1 Guest are viewing this topic.

stevemartins

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 6
  • Last login:December 09, 2007, 11:59:05 pm
Mala Error
« on: October 22, 2007, 04:28:35 am »
I've been having trouble with errors on Mala. I've only downloaded the program a few days ago so I'm still getting familiar with it but I can't seem to figure this one out. I have Mala set to automatically run when the computer turns on. The problem is, 90% of the time I get this error message when Mala attempts to run after startup:

Mala.exe has encountered a problem and needs to close. We are sorry for the inconvenience.

After I close I can reopen Mala without problems.

The only way I can seem to prevent the error is that Mala must be running when I shut down and I have to manually shut down by clicking the start button and selecting shut down, even then I still sometimes get the error when I turn the computer back on and Mala attempts to run.

This is a problem because I would like Windows to be hidden when I install this computer in the cabinet. If i have to shut down Mala everytime I boot then reopen it to get the program to run then it kinda kills the whole "hide Windows" theme I'm going for. Ideally I would like to open straight into Mala and have the comptuer shut down when I close Mala Or shut down by pressing the power button that will be relocated on the outside of the cabinet somewhere. Problem is, I get the error message above the next time I startup when I try to shut down using either of those methods. As stated before I can only prevent this by manually shutting down windows through the start button (while Mala is running) which then exposes windows :( Can anyone help me out with this problem?

FunWithFire

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 102
  • Last login:July 07, 2009, 01:17:30 am
Re: Mala Error
« Reply #1 on: October 22, 2007, 11:17:58 am »
Can't really help you out, but the best place to post this would be in the Software Forum. They helped me out with all of my Mala issue.

severdhed

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 2975
  • Last login:December 14, 2024, 05:01:52 pm
  • RIP Dinosaur Hippo
Re: Mala Error
« Reply #2 on: October 23, 2007, 12:18:33 pm »
as for that specific problem, i dont know what to tell you.  as for hiding windows and having mala load at startup, you should check out the WIKI, there is a great section in there telling you how to do it.

http://wiki.arcadecontrols.com/wiki/Hiding_Windows

you never see windows on my cabinet at all.  i changed my bios splash screen, windows boot screen, and wallpaper.  the key to really hiding windows though is to have MALA load as the shell, instead of explorer..that way you never see the taskbar or desktop icons or anything like that. the computer boots directly to mala, you can then manually launch explorer if you need to do maintenance. 
Current Projects:      Zak-Man | TMNT Pedestal | SNES Pi | N64 Odroid
Former Projects:     4 Player Showcase | Donkey Kong | iCade

stevemartins

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 6
  • Last login:December 09, 2007, 11:59:05 pm
Re: Mala Error
« Reply #3 on: October 24, 2007, 04:38:46 pm »
I've got windows hidden and I have Mala now loading as the shell. I am no longer getting the error message. I'm not sure what was causing it but I'm guessing it was windows related since the problem has stopped after windows was disabled. Thanks for your help guys.