Re: It gets worse -- Uninstall of W2k? Not simple for me!

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Slip Kid (G-2_at_worldnet.att.net)
Date: 02/11/05 

Date: Fri, 11 Feb 2005 19:05:59 GMT

On or about 2/11/2005 11:55 AM, R. C. White with due consideration,
replied :

<Snip>

You've been more than kind and patient - thanks!

>> How serious of a change in one in the other requires "what kind of
>> attention" to either or both?

>
>
> No need to create this boogeyman, Michael. You are imagining problems
> that don't exist. You can delete E:\WinNT entirely, or reinstall it -
> or even reformat E: completely - with no effect on D:\WinNT. Then you
> can install WinXP into E:\Windows (or X:\Windows), if you like, with no
> effect on D:\WinNT. When you install WinXP (into any volume), WinXP
> Setup will update C:\NTLDR, C:\NTDETECT.COM and C:\Boot.ini, plus the
> boot sector on C:. But it will not touch anything on D: - or any other
> volume.
>
>> So, give me the lowdown of a multiboot with SP and W2k.
>
>
> I've tried.
>
> Post back and tell us exactly what you did and what results you saw.

Why am I worried?

OK, I bought a new machine. It had XP installed. I wanted a FAT/DOS
partition - I'm goofy and use a lot of DOS utilities and floppys are
garbage - plus it had XP in a single partition and I needed to move
multiple partitions over from the old box..

So! The new drive is all formatted with the FAT (And my DOS apps) and a
couple of FAT32's for W2k and the new XP. I then intalled XP and
planned to use it to bring my W2k over from the old box (via network).

The plan (against all advice) to migrate the W2k from an old machine to
the new one (via a network). Hey, with a quick repair (mainly the HAL
and other hardware fixes) W2k was up and running.

Yes, I knew 2K should go in first but I figured
1. It might not make the migration and I would at least have a viable XP
in place.an
Plus, the 2k it had a buttload of apps with it I figured I could be up
and running if it made it through the migration. It was a wise choice
to use XP to migrate the 2k over -- Hey, it worked!

To repair the XP? It wasn't a 'repair'. Check my posts from October.
An XP 'repair' is nothing like repair in 2k -- it is an install.

Then,later? I had another minor problem with W2k...easily fixed? But?!
  XP 'acted' as though I'd installed W2k again!

So? If XP is so sensitive to changes to W2k (indicatiing to XP an
"older" Windows version appeared?) I reallly am not looking forward to
the potential grief I will face because of all the updates that OS's need.

Yeah, I am a little concerned that XP will overreact to changes that are
made to W2k.

I've heard that just about any major change to 2k (that will impact XP)
can be easily solved by simply using the repair console and using
FIXBOOT as that is all a w2k change will effect in XP. If that is true?
  I'm not worried. However? I did experience more time than was
necessary to bring back XP after changes were made to 2k. If a few
moves can be made in the Repair Console? Fine! But if it mean using XP
"repair"? Forget it!

So, the ball is in your court. Is XP sensitive to changes made in 2k in
a multiboot environment?

Thanks!

Michael

> RC

Quantcast