Re: Housekeeping after enforced new Windows install


"Jaimie Vandenbergh" <jaimie@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:81a5p217tc0ev2op2c251mrthk2sbdp9d0@xxxxxxxxxxxxxxxxxxxxxxxxxx
On Wed, 27 Dec 2006 17:57:51 +0100, "Roger Moss"
<roger.moss(BINTHISBIT)@tiscali.fr> wrote:

Had to perform a new (parallel) W2K Pro install, after major boot problems
following repeated attempted Service Pack installs... :-(

Question is, does anyone have a source of information on how to clean up
the
remnants of the previous (now redundant) OS files?

You can bin the old C:\Windows folder, and probably some now-dead user
folders out of c:\Documents and Settings. That's the lot - the
remaining items in c:\Program Files\ will have been overwritten.

Did a reinstall over the top not work? That usually fixes w2k boot
issues. As does booting off a handy WinXP disk, going to the recovery
console, and running a chkdsk, fixmbr, fixboot.

Cheers - Jaimie
--
"Shellfish are the prime cause of the decline of morals and the
adoption of an extravagant life style" -- Pliny the Elder

Thanks for this.

Well, it was something of an act of desperation - tried an ott reinstall,
but had a failure again as soon as I applied the SP4 package.

Thing is, a parallel install turned out to produce exactly the same problem.
:-(

I'm now wondering about the HDD, which I recently upgraded and migrated
across the contents of the old one (on which I'd successfully applied
Service Packs as required). I ran the detailed analysis tool on the Western
Digital utilities disk, which reported no problems at all.

I then reset the bios settings to defaults, and tried again - same failure
as soon as I applied SP4. So then, I tried installing SP2, intending to go
sequentially up to 4... same failure to boot:
STOP: 0x0000007B (0x81669AB0,0xC000014F, 0x00000000, 0x00000000)
INACCESSIBLE_BOOT_DEVICE

Needless to say, I don't intend to attempt an update until I'm confident
I've found the problem cause.

Next stop: Western Digital website support...

RM


.