Cannot repair or restore after sp2 , can i restore manually

[Guest]

I installed the sp2 through out System Builder site and 1
computer has run fine since the other crashed during the
install. I tried to to do a lastgoodknown, or a safe mode
remove update too and neither will work. During the boot
up it says there is a " stop: c0000269 user32.dll was
relocated in memory .
then something about nt32dll.dll tried to occupy the same
memory space and an error occured . then it restarts.

1# Tried the recovery console ,after getting the SATA
drive recognized by installing the extra drivers in gets
to the screen asking for which os, c:\windows, then the
password . the i get the dos prompt and shortly after i
get a blue screen error about a cache access and it says
to disable cache in bios,which it is,.
So before i reinstall the os over and fight that fight,is
there a way to access the restore point through win 98 on
another ide drive i have and repair the sata drive files
or wind them back? I know i can reinstall it all over but
this is my System builder drive with tons of files and
programs for my business of pc repair and building.
usually a reinstall screws up so much i spend hours fixing
and reinstall all the programs anyway, but if it has to be
so be it, but if anyone has any ideas about fixinghte
drive from anothe os let me know asap
Thanks
System is running AMD barton runing 2300mgz 750mhz rdr ram,A7n8xdeluxe 2.0 version ,bios is 1007 the newest. 1 120gb SATA drive 1 cd-rw -1 dvdrw, nvidia 5200 128 video .

Gary L Greco

 

[Rock]

I installed the sp2 through out System Builder site and 1
computer has run fine since the other crashed during the
install. I tried to to do a lastgoodknown, or a safe mode
remove update too and neither will work. During the boot
up it says there is a " stop: c0000269 user32.dll was
relocated in memory .
then something about nt32dll.dll tried to occupy the same
memory space and an error occured . then it restarts.

1# Tried the recovery console ,after getting the SATA
drive recognized by installing the extra drivers in gets
to the screen asking for which os, c:\windows, then the
password . the i get the dos prompt and shortly after i
get a blue screen error about a cache access and it says
to disable cache in bios,which it is,.
So before i reinstall the os over and fight that fight,is
there a way to access the restore point through win 98 on
another ide drive i have and repair the sata drive files
or wind them back? I know i can reinstall it all over but
this is my System builder drive with tons of files and
programs for my business of pc repair and building.
usually a reinstall screws up so much i spend hours fixing
and reinstall all the programs anyway, but if it has to be
so be it, but if anyone has any ideas about fixinghte
drive from anothe os let me know asap
Thanks
System is running AMD barton runing 2300mgz 750mhz rdr ram,A7n8xdeluxe 2.0 version ,bios is 1007 the newest. 1 120gb SATA drive 1 cd-rw -1 dvdrw, nvidia 5200 128 video .

Gary L Greco

You might want to post to one of the SP2 newsgroups since it's not been
finished and released yet.

http://communities.microsoft.com/newsgroups/default.asp?icp=xpsp2&slcid=us

 

[Malke]

I installed the sp2 through out System Builder site and 1
computer has run fine since the other crashed during the
install. I tried to to do a lastgoodknown, or a safe mode
remove update too and neither will work. During the boot
up it says there is a " stop: c0000269 user32.dll was
relocated in memory .
then something about nt32dll.dll tried to occupy the same
memory space and an error occured . then it restarts.

1# Tried the recovery console ,after getting the SATA
drive recognized by installing the extra drivers in gets
to the screen asking for which os, c:\windows, then the
password . the i get the dos prompt and shortly after i
get a blue screen error about a cache access and it says
to disable cache in bios,which it is,.
So before i reinstall the os over and fight that fight,is
there a way to access the restore point through win 98 on
another ide drive i have and repair the sata drive files
or wind them back? I know i can reinstall it all over but
this is my System builder drive with tons of files and
programs for my business of pc repair and building.
usually a reinstall screws up so much i spend hours fixing
and reinstall all the programs anyway, but if it has to be
so be it, but if anyone has any ideas about fixinghte
drive from anothe os let me know asap
Thanks
System is running AMD barton runing 2300mgz 750mhz rdr ram,A7n8xdeluxe
2.0 version ,bios is 1007 the newest. 1 120gb SATA drive 1 cd-rw -1
dvdrw, nvidia 5200 128 video .

Gary L Greco

I'm sorry, but there was a clear warning on the download site that SP2
is still beta and should not be installed on a production machine.
There is no way to access System Restore from another operating system.
You might try a Repair Install, but my gut feel is you are looking at a
full clean install.

If you need to back up data first, try booting with Knoppix and burning
the files or slaving the drive in a working XP box. And when the dust
settles, invest in some imaging software like Ghost or BootItNG.

Malke

 

[Malke]

Gary L Greco wrote:

See my answers inline:

As far as the warning goes i think we can agree that installing
windows on any machine is taking a big chance,let alone a beta of it.
That being said After attending 2 T2 meetings and a systembulider
meeting regarding the deployment of this service pack and what it will
do i think i have a pretty good idea on how to implement it and the
chances of problems occuring.

I don't agree that installing Windows is taking a big chance, but then
you always have the choice to use other operating systems. I've got 4
XP boxen here that are quite stable and behave themselves very well.
Even the Win9x boxen are good boys. Of course, this machine runs SuSE
9.1, as does my laptop.

i do have a back of important files ,but
as we get bigger in drive size ,partitions get bigger and doing back
ups on a weekly basis often get to be major time issues. As i said in
my post i am looking into finding a way to repair the os installing it
as a slave in case i run across this in clients house.

You might want to look into Bart's PE builder, but basically you can't
fix XP from a different operating system. At this point, there is a
very rough project to enable Linux to write to ntfs, but I personally
wouldn't do it yet.

Which i might
add will probably happen along the way here in the near future. I also
know i can install the os over the top of the existing corruted files
and probably save 99% percent of the files on it without to much work.
And yes i can ghost the drive, but how often do you do that as backup?

For business machines, imaging is a good idea to do on a fairly regular
basis, along with normal backup. How often really depends on the
business. Certainly servers should be imaged or have RAID mirroring so
if things get fouled up you can recover quickly. For my own home
machines, what I usually do is have a second hard drive and after a
fresh install, with all updates and the programs I always want and
everything just nice, I make an image with Ghost. All data is kept on
the second drive and backed up to cd-r. That way when the boys mess up
their Windows boxen, it is only a matter of quickly deploying the
image.

Isnt the restore for that ?

No, System Restore is a good, simple fix for fouled up files when it
works. I have used it on clients' machines successfully, but I
certainly wouldn't rely on it for back up purposes.

Want my secret to having stable computers (Windows and Linux) that just
chug along beautifully year after year? I'm happy to share:

1. Use good quality hardware that is compatible with your operating
system.
2. Don't install beta software.
3. Do regular maintenance appropriate for your os.
4. Keep the machine clean and cool.
5. Don't install alpha software.
6. For Windows, have a full-featured current antivirus installed and
keep the definitions updated.
7. Make regular backups so if there are sunspots, a power surge (ups's
are Good Things), your hard drive dies, the Glitch Monster gets you,
etc. you can recover quickly without having to resort to heavy
drinking.
8. Don't install beta software.

That's most of it, although I may have left something out. Now I've got
to get back to work, cleaning up viruses and spyware off a client's
machine. BTW, he didn't keep his av subscription current and he clicked
on all those flashy little banners.

Cheers,

Malke