Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Dream Machine ( Build your own PC ) -- Ignore unavailable to you. Want to Upgrade?

To: TH who wrote (14430)	1/1/2004 5:56:15 AM
From: wily	Read Replies (1) \| Respond to of 14778

Thurston, That is some strange behavior. The lesson I'd draw from it is don't expect your disk and OS's to behave predictably if you have at least one instance of WinXP on your disk plus an instance of WinXP or any other OS on the same disk. Maybe too general a rule to draw, but better to err on the cautious side. I've always put my backup OS on a separate disk, preferring to avoid the extra layer of complexity of having them on the same disk. Glad you were able to get things to where you wanted them. 5 hours is pretty small potatoes in my book of disk/OS-Hell stories. wily

To: TH who wrote (14430)	1/7/2004 8:30:49 AM
From: Bruce A. Thompson	Read Replies (1) \| Respond to of 14778

Thurston, After waiting a week to decide what you may have learned, may I offer the following: The key to your boot problem was in this statement: I set the BIOS to boot to the drive with the new install, but no luck In effect, what you had done originally was install XP on the non booting drive and set it as the default OS. By doing so, XP was forced to put some of the boot info on the "Booting" drive in order to start the OS. Dam accomodating of XP to do that for you. If I may say so. When you formatted the booting drive, that boot data was lost. Lesson Learned: Always install your primary OS on the drive that boots. BT