Although my general opinion of XP remains somewhat negative, I have it installed on at least two PCs, due to game developers' choices not to support W2K. The newest PC's W2K has suddenly begun throwing BSODs during the startup (bad image checksum).

This followed a recent visit to Microsoft's Updates page, and a security update for MPlayer (I think, but can't recall for certain). WinXP still works fine, but I can imagine that after I've run repairs from the W2K CD to sort out whatever went wrong there, I'll have a problem with the boot menu, or with XP itself, will I not?

Anyone here had to do it lately? Am I right or wrong? Is it simple enough to fix? Thanks.

.

Kiwi

**

[Reply or follow-up to this message]

i can't say if repairing W2K will kill XP or not, but this is what i would do: make an image of the W2K partition, and make an image of the XP partition. you can use the free version of acronis true image, or you can use norton ghost, or something like that. i prefer acronis myself. then if you run the W2K fix and kill XP at the same time, then you can just replay the images and be back to where you are now. (better than nothing!) i think the boot files are on the C:\ partition usually, so it may depend on which OS you have installed on C:. if W2K is on C:\, then repairing the installation may prevent XP from booting. always make an image before trying stuff like this. doing this has saved me many times. maybe you'll get better advice tomorrow, which is monday.


On Sunday, March 30, 2008 at 4:57 am, Kiwi wrote:
>Although my general opinion of XP remains somewhat negative, I have it installed
>on at least two PCs, due to game developers' choices not to support W2K. The newest
>PC's W2K has suddenly begun throwing BSODs during the startup (bad image checksum).
>

>This followed a recent visit to Microsoft's Updates page, and a security update for
>MPlayer (I think, but can't recall for certain). WinXP still works fine, but I can
>imagine that after I've run repairs from the W2K CD to sort out whatever went wrong
>there, I'll have a problem with the boot menu, or with XP itself, will I not?
>

>Anyone here had to do it lately? Am I right or wrong? Is it simple enough to fix?
> Thanks.

[Reply or follow-up to this message]

Image the drive(s) for back up if you need to first, then repair W2K.  If nothing 
changes on the XP installed drive, then just run the fixboot command from the XP 
disc.  That should fix the boot loader and you can edit boot.ini manually if you 
have to, to add the XP install to it, if it isn't correct.  (make a txt copy of the 
boot.ini on the boot drive for reference)  You shouldn't have to do a full repair 
install on XP if the partition/drive it is on wasn't touched by W2K's repair.

If after repairing XP's boot you find W2K won't boot, you can add/fix W2K to the 
boot.ini if for some reason XP's boot repair messed it up.

http://www.webtree.ca/windowsxp/repair_xp.htm#How%20to%20Repair%20the%20Boot%20Sector:







On Sunday, March 30, 2008 at 4:57 am, Kiwi wrote:

>Although my general opinion of XP remains somewhat negative, I have it installed 

>on at least two PCs, due to game developers' choices not to support W2K.  The newest 

>PC's W2K has suddenly begun throwing BSODs during the startup (bad image checksum).

>


>This followed a recent visit to Microsoft's Updates page, and a security update 
for 

>MPlayer (I think, but can't recall for certain).  WinXP still works fine, but I 
can 

>imagine that after I've run repairs from the W2K CD to sort out whatever went wrong 

>there, I'll have a problem with the boot menu, or with XP itself, will I not?  

>


>Anyone here had to do it lately?  Am I right or wrong?  Is it simple enough to fix? 

> Thanks.   

[Reply or follow-up to this message]

• Search this forum
• Start a new thread on a different subject

• Report abuse of the forum