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: path issue  (Read 2506 times)

0 Members and 2 Guests are viewing this topic.

kortina

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 54
  • Last login:March 15, 2019, 05:06:26 am
  • I want to build my own arcade controls!
path issue
« on: May 08, 2015, 09:46:43 am »
Hi Guys,

Finally got a HD3450, and setup CRT_Emu and groovymame.

What an amazing difference to the picture quality! (PC-CRT)

I have hit a snag with launching mame.exe (groovymame64 - 0.160)

Please take a look at the screenshot as I am stumped as to what is wrong...

This is causing me issues with Hyperspin, as I can no longer launch correctly.

big10p

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 698
  • Last login:May 01, 2023, 01:46:23 pm
  • Mmmm, arcade classics!
Re: path issue
« Reply #1 on: May 08, 2015, 10:28:02 am »
Do you have the correct romset for mame .160?

Ah, forget that - I wasn't paying attention to the screenshot.
« Last Edit: May 08, 2015, 10:30:42 am by big10p »

Chainsaw

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 49
  • Last login:May 15, 2022, 10:26:53 am
  • Pac-Men
    • Chainsaw Films
Re: path issue
« Reply #2 on: May 08, 2015, 01:46:25 pm »
Hi Guys,

Finally got a HD3450, and setup CRT_Emu and groovymame.

What an amazing difference to the picture quality! (PC-CRT)

I have hit a snag with launching mame.exe (groovymame64 - 0.160)

Please take a look at the screenshot as I am stumped as to what is wrong...

This is causing me issues with Hyperspin, as I can no longer launch correctly.

It looks like you've a random character string at the end of the ROMS path. Check the SwitchRes ini file (assuming there is one!) and delete the whole line and retype it.
« Last Edit: May 08, 2015, 01:48:04 pm by Chainsaw »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 7463
  • Last login:July 19, 2025, 04:03:33 am
  • Quote me with care
Re: path issue
« Reply #3 on: May 08, 2015, 02:03:37 pm »
I'd say your HS is not properly configured. Instead of passing the full rom path to MAME, it should only pass the rom name, then you just put the proper rom path in mame.ini as you'll probably have done already.

Also remind that MAME belongs to you, not to HS (not being serious, just saying this because your MAME folder is inside HS').
Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead of pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

tw33die

  • Trade Count: (0)
  • Newbie
  • *
  • Offline Offline
  • Posts: 1
  • Last login:October 04, 2015, 01:11:01 pm
  • I want to build my own arcade controls!
Re: path issue
« Reply #4 on: May 09, 2015, 03:16:41 pm »
For MAME .160 I had to copy pasta my mame.ini to the root folder of my MAME install before HS would play games properly. Not sure if this helps, but it's worth a shot.

kortina

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 54
  • Last login:March 15, 2019, 05:06:26 am
  • I want to build my own arcade controls!
Re: path issue
« Reply #5 on: May 10, 2015, 01:02:59 am »
I figured it out... the path issue was a bit of a miss-lead.

I took Calamity's advise and moved my folder structure around, so that all my stuff in a root folder of Arcade. This doesn't really matter, but I respect Calamity for all the work he has put in, so the least I could do is follow his reccomendation.

The fix - Windows8.1
1) Right click on groovymame.exe (or whatever you may have renamed it to). Select - Properties, Compatibility. Then select "Run this program as administrator"
This is important so that goovymame and switchres can read the required reg stuff.

2) When you are running a frontend like hyperspin, which then launches groovymame, you should ALSO enable the compatibility mode!
3) Same for LEDBlinky too.

Not exactly sure on the reason, but I suspect that it has something to do with Windows security and stopping apps from escalating priv.

Thanks to all of those who took the time to look at this, and a special thankyou to all those involved in the CRT_Emu drivers and Groovymame.
My cabinet looks better than ever!


kortina

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 54
  • Last login:March 15, 2019, 05:06:26 am
  • I want to build my own arcade controls!
Re: path issue
« Reply #6 on: May 10, 2015, 07:14:28 am »
Just to chime in (again).

Turns out that using Win8.1 and setting the "Runas Administrator" property is not viable.

With this option turned on, you can't use Hyperspin as a replacement shell.

Use this instead to turn OFF the user account control, and all extra security features. Basically this runs just like XP did with full admin rights:
Code: [Select]
Set-ItemProperty -Path "HKLM:\Software\Microsoft\Windows\CurrentVersion\Policies\System" -Name "EnableLUA" -Value "0"
Reboot required

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 7463
  • Last login:July 19, 2025, 04:03:33 am
  • Quote me with care
Re: path issue
« Reply #7 on: May 10, 2015, 03:24:13 pm »
Hi kortina,

Thanks for sharing this. Yes, GroovyMAME currently requires admin rights because it needs to access the registry. This is a bit annoying with modern operating systems, unless you disable the UAC as you mentioned, which is far from ideal but works. Hopefully future versions won't need to access the registry at all.
Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead of pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi