Full Version: Windows XP Issue
From: Engravin' Dave (DATAKES) [#6]
30 Dec 2006
To: Laser Image (LASER_IMAGE) [#5] 30 Dec 2006
I did use my XP disk on boot-up to try to repair the existing install, but to no avail.
When the whistle blew at 5:00 today I finally solved the problem. It was the last straw. Below is the description I followed from a support forum. (Another reason to love forums.) :-) I earned $15 in engraving today. A very expensive operating system glitch. :@
---------------------------------------------------
One Last Thing To Try
If, after all this, you still have problems with the .EXE association there is one last thing to try. First, open the File Types dialog from any Explorer window (Tools | Folder Options | File Types Tab). Scroll down to where .EXE would be in the alphabetical order and make certain .EXE is not there (if it is, then fix it there). Finally, select the New button, type in EXE for the extension and select the Advanced button. From the list pick "Application." It should look something like this.
And, hopefully, this should cure the problem (thanks to forum member diginono for finding and posting this solution). [Note: One user reports that a "Restore" button shows up when you do this and that fixes things; I can't replicate that.]
----------------------------------------------------------------------
From: Laser Image (LASER_IMAGE) [#7]
30 Dec 2006
To: Engravin' Dave (DATAKES) [#6] 30 Dec 2006
It's a moot point now because you have it fixed, but the "repair" option is not what I was suggesting. I was suggesting a complete reinstallation of Windows - quite different than a repair. As you found out, "repair", doesn't necessarily repair anything.
If it makes you feel better, I made $0 today. Granted, I am home loafing, but that shouldn't matter much...
Gary
From: Engravin' Dave (DATAKES) [#8]
30 Dec 2006
To: Laser Image (LASER_IMAGE) [#7] 30 Dec 2006
Gary,
I knew what you were referring to, but I wasn't ready to give up on the fix. A complete reinstallation has so many headaches that come along with it, especially trying to round up all the drivers, etc. I'm relieved I didn't have to go down that road.
From: Harvey only (HARVEY-ONLY) [#9]
30 Dec 2006
To: Engravin' Dave (DATAKES) [#8] 30 Dec 2006
My computer problem was that the file ntos-something-.exe was corrupt and so were a few of the dll files. Repair did not even boot from the CD. The second time around that file was there but the repair console would still not come up and nothing worked.
I finally had to reinstall XP and left the data there. If you do this be sure to first copy the driver info elsewhere. It not only deletes the Windows folder but wipes the registry and boots as a brand new installation, including having to re-register - duh.
5 PM to 2 AM to get that system up and nearly in the shape that it was in before the crash. Guess you cannot trust the Repair Console if it does not even boot from the CD.
From: LaserMike [#10]
30 Dec 2006
To: Engravin' Dave (DATAKES) [#1] 31 Dec 2006
Dave, just a thought... do you have system restore active?
I've pulled myself out of a couple of XP jams with this in the past.
http://www.microsoft.com/windowsxp/using/helpandsupport/getstarted/ballew_03may19.mspx
From: Engravin' Dave (DATAKES) [#11]
31 Dec 2006
To: LaserMike [#10] 31 Dec 2006
Mike,
The system restore worked to resolve the same issue on my laptop, but an attempt at restore on the older machine failed.