ResellerRatings Store Ratings - View Single Post

DakotaFox · 12-03-2002, 08:57 AM

I've gotten a few emails from people wondering if I found a fix to this problem it seems to be a fairly common problem. This is for the information of anybody else that has to deal with the lsass.exe error . I didn't find any way to get the computer back into operating condition. I hope you have better luck.

This is the only way I found to deal with this problem.
I was able to get ahold of an older 3 gig HDD. I installed the 3 gig into the Emachine as the primary and then I ran the resore disk on this to install Emachines version of XP. I had thought I would copy the information from the 60 gig to the 3 gig but the installation took about 2.5 gig of space. I installed the failing 60 gig as slave. I was able to read the data on the 60 gig in Windows explorer. I networked the Emachines to my New Trend. I then was able to find and copy my much needed files to the older machine.

After that I put the 60 gig back as the primary and restored it. It seems to be working now.

I think that having to do this to a machine with the "Latest and Greatest Windows" to save one's data is BULL$HIT. I have never had to deal with a problem like this with Win95a, 95b, 98, 98SE, or ME. And the "support" from micro$oft is shameful.

I have been on the Internet for the past week finding and installing the XP drivers for the printer, scanner, camera, burner, modem, and all of the hardware that didn't come with XP drivers. It is a real pain in the a$$. I wish that the money grubbers at Micro$oft would support their product and spend some time refining the functionality of their op sys instead of figuring out how to keep a homeowner from putting a copy on their kid's computer.

The soulution seems to be to try a different operating system or to make sure you have a spare computer and hard drive around so you can save your data when XP craps on you.

12-03-2002, 08:57 AM	#12 (permalink)
DakotaFox Registered User Join Date: Nov 2002 Posts: 9	I've gotten a few emails from people wondering if I found a fix to this problem it seems to be a fairly common problem. This is for the information of anybody else that has to deal with the lsass.exe error . I didn't find any way to get the computer back into operating condition. I hope you have better luck. This is the only way I found to deal with this problem. I was able to get ahold of an older 3 gig HDD. I installed the 3 gig into the Emachine as the primary and then I ran the resore disk on this to install Emachines version of XP. I had thought I would copy the information from the 60 gig to the 3 gig but the installation took about 2.5 gig of space. I installed the failing 60 gig as slave. I was able to read the data on the 60 gig in Windows explorer. I networked the Emachines to my New Trend. I then was able to find and copy my much needed files to the older machine. After that I put the 60 gig back as the primary and restored it. It seems to be working now. I think that having to do this to a machine with the "Latest and Greatest Windows" to save one's data is BULL$HIT. I have never had to deal with a problem like this with Win95a, 95b, 98, 98SE, or ME. And the "support" from micro$oft is shameful. I have been on the Internet for the past week finding and installing the XP drivers for the printer, scanner, camera, burner, modem, and all of the hardware that didn't come with XP drivers. It is a real pain in the a$$. I wish that the money grubbers at Micro$oft would support their product and spend some time refining the functionality of their op sys instead of figuring out how to keep a homeowner from putting a copy on their kid's computer. The soulution seems to be to try a different operating system or to make sure you have a spare computer and hard drive around so you can save your data when XP craps on you.