I had this great program working, then had to format my comp due to a stupid virus I somewhat willingly opened... ( instinct told me it was a virus, finger clicked anyway... ) Anyway, I'm trying to compile mame for an Athlon 64 processor running WinXP MCE 2005. These are the directions I followed exactly (except for the name of the mame folder of course seeing as how it is 127) Also, I installed MinGW by following "The Hard Way" shown in the Developers Tools section of mamedev.org 1. Install Mame Compiler 2. Download the Mame source from mamedev.org (ie. mame0126s.exe) 3. Download the Intermediate Updates from mamedev.org (ie. 0126u1_diff.zip, 0126u2_diff.zip, 0126u3_diff.zip, 0126u4_diff.zip) 5. Download the hiscore diff patch from here (ie. hi_126u4.txt) 7. Extract the Intermediate Update diff's to C:\MinGW\patches 8. Run mame0126s.exe and extract it to C:\MinGW\source\Mame0126u4 10. Run Mame Compiler (Start->Program Files->Mame Compiler->MameCompiler) 11. Click the [...] button to browse for the "Mame Source Folder" and point it to C:\MinGW\source\Mame0126u4 12. Click the [...] button to browse for the "Diff Patch File" and point it to C:\MinGW\patches\126u1.diff 13. Click the "Apply Patch" button. 14. Repeat step 12 for 0126u2.diff, 0126u3.diff and 0126u4.diff, then hi_126u4.diff 15. Put a tick next to the "Mame UI" option if your compiling MameUI 16. Press the "GO!" button to compile Mame 17. When it's finished compiling it should create a "mame.exe" file in the C:\MinGW\source\Mame0126u4 folder This is the error I keep getting. Deleting Object Folder... Compiling Mame... Using Parameters -j3 ARCHOPTS=-march=athlon64 mkdir.exe -p obj/windows/mame process_easy: DuplicateHandle(In) failed (e=6) process_easy() failed to launch process (e=6) mkdir.exe -p obj/windows/mame Counted 3 args in failed launch Finished! 0 Hours 0 Minutes and 0 Seconds Elapsed. I'm using a Vista Ultimate computer with an Athlon64 processor. The only thing left I can think of is user access permissions, which I granted myself, but have still left the dumb User Access Control system on, which I will soon turn off. Any idea on what is happening? Thanks in advance!