My old laptop litterly burned itself to death so i'm now using this newer Windows 7 notebooks of which I have 2 of them. Both give the same error when trying to burn firmware, either code 029q or 029y on MS1.
This is what I'm trying to do and I got the first part done but not the 2nd part. Extracting 32-64 bit file?
The error message
FoundSoul26th January 2010, 10:48
I think I have a fix for you. It wasn't too hard for me to correct (still needs some testing) but it is a bit of a pain to implement on Vista/Win7 due to UAC write restriction to the program files directory. They have the default permissions set to not allow write, and I need you to copy two files into that directory to correct this.
-------------------------------------------
<Bullcrap requirements to write to program files in Win7/Vista>
So first, you'll need to browse to your C:\Program Files (x86) directory. Then right click on the MegaSquirt folder and choose properties.
Click the Security Tab. Click the Advanced button. Click the Owner Tab.
Make sure your account is the owner (or you are in the group that's set to owner). If it's not, click the Edit button and fix that.
Once done, click OK, OK, OK until you exit the MegaSquirt folders' properties, and then open it again. (right click on the MegaSquirt folder and choose properties.)
Click the Security Tab, click the EDIT button, and give the 'USERS' group Full Control (check that box). Click OK, OK until you exit the MegaSquirt folders' properties. That should allow you to write to the MegaSquirt subfolders now.
</Bullcrap requirements to write to program files in Win7/Vista>
-------------------------------------------
------------------------------------------
<Actual Resolution>
Extract the attached file (download-firmware_32-64bit.zip) and copy the contents into the MSPNP Firmware folder you are trying to burn to your ECU. (two files total inside the zip)
Make sure you overwrite the current download-firmware.bat with this one.
Make sure you copy the choice.exe file to the src/ subdirectory. This is a new file, not an overwrite.
</Actual Resolution>
-------------------------------------------
Run the script just like you used to on older OS's. Then please let me know if you have any issues. Once fully tested we'll roll this into our software package so others won't have to go through this ;).