Main > Software Forum
MAME Compiler 64 v2.0.197
Yoeddy1:
--- Quote from: headkaze on February 28, 2016, 06:57:43 pm ---
--- Quote from: WindDrake on February 28, 2016, 06:32:50 pm ---Not working for me. About half way through the build tools extraction, I get a .Net error. If I hit continue, MC64 will sit on 100% file progress once everything is extracted, with OK greyed out.
--- End quote ---
Can you please post the .NET error?
--- End quote ---
Here's mine. Basically the same activity as above with the OK button staying grayed out.
Jason
ArrogANT:
The only things that I did differently was to download and extract the build tools myself. I also used the 171 patch from the GroovyMAME thread.
EMDB:
--- Quote from: Yoeddy1 on February 28, 2016, 07:22:40 pm ---
--- Quote from: headkaze on February 28, 2016, 06:57:43 pm ---
--- Quote from: WindDrake on February 28, 2016, 06:32:50 pm ---Not working for me. About half way through the build tools extraction, I get a .Net error. If I hit continue, MC64 will sit on 100% file progress once everything is extracted, with OK greyed out.
--- End quote ---
Can you please post the .NET error?
--- End quote ---
Here's mine. Basically the same activity as above with the OK button staying grayed out.
Jason
--- End quote ---
Same here...
headkaze:
--- Quote from: Yoeddy1 on February 28, 2016, 07:22:40 pm ---Here's mine. Basically the same activity as above with the OK button staying grayed out.
--- End quote ---
According to the error a file is locked because it is in use by another process. Try rebooting your PC.
Yoeddy1:
--- Quote from: headkaze on February 29, 2016, 07:37:38 pm ---
--- Quote from: Yoeddy1 on February 28, 2016, 07:22:40 pm ---Here's mine. Basically the same activity as above with the OK button staying grayed out.
--- End quote ---
According to the error a file is locked because it is in use by another process. Try rebooting your PC.
--- End quote ---
When? This PC/MAME cab is rebooted every day. I've done it several times after uninstalling and reinstalling this software as part of the troubleshooting process. This also happened on a clean Windows 10 64-bit machine.
Jason
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version