F
frogliver
XP Home OEM on an HP desktop
After installing some MS updates my XP will only normal-boot as far as the
WINXP screen with moving blue bars for a few seconds then black screen. Safe
Mode boots to a screen list of drivers then freezes. Last known config boots
the same as normal-boot.
From what I have read I may have to "recover" the OS using the set of XP
Recovery Disks I got from HP back when they had a HDD recall. The F:\
partition on my HDD contains a Recovery Console but I can't boot to get to
it.
Before I go there and risk losing the whole ball of wax (My Documents,
pictures, programs, etc.) I want to be clear on some things I read.
First, should those Recovery Disks offer a non-destructive OS recovery
option as the internal recovery console does? I understand that even this is
risky to keeping files, but even so I would choose that over the alternative
option, that reformats and does a clean install, if non-destruct is offered
on the disks.
Then, I have several types of "Ultimate Boot" type of disks: I can't get the
ones on floppies to reboot, but so far have gotten the EASUS Partition
Manager CD to boot and analyze the partitions. One has an "X" meaning there
is a boot sector problem (the thing is it is an FAT partition that I don't
recognize, as I know C;\ is NTSF. I think F:\ is supposed to be an FAT ). I
ran Fixboot and it could not fix the boot sector of that partition but
recommends I use Data Recovery Wizard to recover the files, but could I run
them if recovered? If I can recover the F;\ drive would I be able to boot it
and use the Recovery Console files it contains? Will the EASUS Partition
Recovery do any good at all?
Third, the actual Ultimate Boot Disk for Windows offers boot recovery if you
have an XP install CD -- is that the same as my XP installation disks (there
are 7)? Could they function the same way as the actual "install CD" and work
with the UBD?
This appears to be a pretty common effect of some of MS's updates and it
seems like MS should be responsible to have a fix for something as
devastating as this. If so I have yet to find it anywhere.
Any help would be greatly appreciated,
Thanks,
frog
After installing some MS updates my XP will only normal-boot as far as the
WINXP screen with moving blue bars for a few seconds then black screen. Safe
Mode boots to a screen list of drivers then freezes. Last known config boots
the same as normal-boot.
From what I have read I may have to "recover" the OS using the set of XP
Recovery Disks I got from HP back when they had a HDD recall. The F:\
partition on my HDD contains a Recovery Console but I can't boot to get to
it.
Before I go there and risk losing the whole ball of wax (My Documents,
pictures, programs, etc.) I want to be clear on some things I read.
First, should those Recovery Disks offer a non-destructive OS recovery
option as the internal recovery console does? I understand that even this is
risky to keeping files, but even so I would choose that over the alternative
option, that reformats and does a clean install, if non-destruct is offered
on the disks.
Then, I have several types of "Ultimate Boot" type of disks: I can't get the
ones on floppies to reboot, but so far have gotten the EASUS Partition
Manager CD to boot and analyze the partitions. One has an "X" meaning there
is a boot sector problem (the thing is it is an FAT partition that I don't
recognize, as I know C;\ is NTSF. I think F:\ is supposed to be an FAT ). I
ran Fixboot and it could not fix the boot sector of that partition but
recommends I use Data Recovery Wizard to recover the files, but could I run
them if recovered? If I can recover the F;\ drive would I be able to boot it
and use the Recovery Console files it contains? Will the EASUS Partition
Recovery do any good at all?
Third, the actual Ultimate Boot Disk for Windows offers boot recovery if you
have an XP install CD -- is that the same as my XP installation disks (there
are 7)? Could they function the same way as the actual "install CD" and work
with the UBD?
This appears to be a pretty common effect of some of MS's updates and it
seems like MS should be responsible to have a fix for something as
devastating as this. If so I have yet to find it anywhere.
Any help would be greatly appreciated,
Thanks,
frog