Hi!
I'm working on a HP computer running XP Pro. When the computer would try to boot up to Windows an error message would appear stating that there was a configuration error and to contact the manufacturer. Then in paranthesis (Code Purple).
I did a search for Code Purple on the internet and got a number of hits, but only one seemed to have any suggestions for a solution.
This is what I found out and this is what I did (Some of these I copied and pasted from this blog - but just changed them to indicate specifically what I did I don't want to take credit for their great suggestions - the blog is at: http://www.billoblog.com/billoblog/?p=152#comments )
Code Purple indicates that there was a booby trap placed in HP and Compaq computers in which a tattoo or numerical signature of the motherboard and hardware configuration is created at the factory and encoded into the restore disks on a particular computer. When you re-install your system, it checks to make sure the system h I removed the hard drive from my Pavilion and put it in the other system. I then looked for the file that was doing the anti-piracy check. I found it at:
I removed the hard drive from their Pavilion and put it in the other system. The writer of the blog had found the file that was doing the anti-piracy check at:
C:\hp\bin\ConfigCheck\cfgchk.bat
The cfgchk.bat file contains the following:
c:\hp\bin\hpdmi r > dmiout.txt
python c:\hp\bin\ConfigCheck\run.py
del dmiout.txt
cd ..
rd /s /q c:\hp\bin\ConfigCheck
The invocation of run.py is the actual check. The way the anti-piracy mechanism seems to work is to loop in the check if the comparison between the motherboard BIOS string (returned by hpdmi.exe) and the expected value fails. By looping in the error message, the check effectively puts the brakes on Syscheck, so the final configuration of XP never completes and you dont get to a functional Windows desktop. Since the loop is in run.py, you can bypass the problem by just removing the invocation of the Python script. In other words, delete the line
python c:\hp\bin\ConfigCheck\run.py
For the writer of this thread this worked and he was able to reboot. However for me, I ran into some complications.
When I reinserted the hard drive to the original computer, it pulled up to Windows after a very long time configuring. When it got into Windows there was a message that said XP Pro could not open because of a missing boot.ini. I went to msconfig and did a boot.ini check and it said everything was running properly. I checked for the boot.ini in the C directory and it was there. (Read it)
Anyway, I rebooted and then it would not open windows, it would only pop up to the safe mode option page. If I tried to go into safe mode it just restarted again. The only option was to turn off the computer.
I did a system restore (I didnt reformat in hopes I could save the data files.) Of course, it reinserted the python. So I was back to where I started.
Another reader in the blog wrote in that he had called Compaq and they told them the only solution was to tatoo the new mobo by deleting the ConfigCheck folder.
So I again piggybacked the hard drive, went to C:\hp\bin\ConfigCheck and deleted the ConfigCheck folder. Again it rebooted to Windows and then I received the same boot.ini error.
I tried using a Windows 98 starte up disk at this point to see if I could bypass the boot.ini and solve the problem but that didn't work.
Any suggestions?
Thanks in advance.
I'm working on a HP computer running XP Pro. When the computer would try to boot up to Windows an error message would appear stating that there was a configuration error and to contact the manufacturer. Then in paranthesis (Code Purple).
I did a search for Code Purple on the internet and got a number of hits, but only one seemed to have any suggestions for a solution.
This is what I found out and this is what I did (Some of these I copied and pasted from this blog - but just changed them to indicate specifically what I did I don't want to take credit for their great suggestions - the blog is at: http://www.billoblog.com/billoblog/?p=152#comments )
Code Purple indicates that there was a booby trap placed in HP and Compaq computers in which a tattoo or numerical signature of the motherboard and hardware configuration is created at the factory and encoded into the restore disks on a particular computer. When you re-install your system, it checks to make sure the system h I removed the hard drive from my Pavilion and put it in the other system. I then looked for the file that was doing the anti-piracy check. I found it at:
I removed the hard drive from their Pavilion and put it in the other system. The writer of the blog had found the file that was doing the anti-piracy check at:
C:\hp\bin\ConfigCheck\cfgchk.bat
The cfgchk.bat file contains the following:
c:\hp\bin\hpdmi r > dmiout.txt
python c:\hp\bin\ConfigCheck\run.py
del dmiout.txt
cd ..
rd /s /q c:\hp\bin\ConfigCheck
The invocation of run.py is the actual check. The way the anti-piracy mechanism seems to work is to loop in the check if the comparison between the motherboard BIOS string (returned by hpdmi.exe) and the expected value fails. By looping in the error message, the check effectively puts the brakes on Syscheck, so the final configuration of XP never completes and you dont get to a functional Windows desktop. Since the loop is in run.py, you can bypass the problem by just removing the invocation of the Python script. In other words, delete the line
python c:\hp\bin\ConfigCheck\run.py
For the writer of this thread this worked and he was able to reboot. However for me, I ran into some complications.
When I reinserted the hard drive to the original computer, it pulled up to Windows after a very long time configuring. When it got into Windows there was a message that said XP Pro could not open because of a missing boot.ini. I went to msconfig and did a boot.ini check and it said everything was running properly. I checked for the boot.ini in the C directory and it was there. (Read it)
Anyway, I rebooted and then it would not open windows, it would only pop up to the safe mode option page. If I tried to go into safe mode it just restarted again. The only option was to turn off the computer.
I did a system restore (I didnt reformat in hopes I could save the data files.) Of course, it reinserted the python. So I was back to where I started.
Another reader in the blog wrote in that he had called Compaq and they told them the only solution was to tatoo the new mobo by deleting the ConfigCheck folder.
So I again piggybacked the hard drive, went to C:\hp\bin\ConfigCheck and deleted the ConfigCheck folder. Again it rebooted to Windows and then I received the same boot.ini error.
I tried using a Windows 98 starte up disk at this point to see if I could bypass the boot.ini and solve the problem but that didn't work.
Any suggestions?
Thanks in advance.
