Re: SNAFU(s) after moving OS

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

From: Mark V (notvalid_at_nul.invalid)
Date: 09/03/04 

Date: Fri, 03 Sep 2004 09:35:59 -0700

In microsoft.public.win2000.registry Michael wrote:

> Switching subjects here...this thread really drifted..
>
> >>Finally, I will probably "start" over--to some degree. That is,
> >>I will remove the few files from C:\--somehow force it to be
> >>fat!!16!!--I don't trust PM---it didn't do it the first time and
> >>am not crazy about fdisk.
> >
> >
> > PM is fine, try to convert to FAT16. IF not, go for fdisk.
> >
> >
> >>I do not believe the repair (for either) will be as intense as
> >>the first time since I "relocated" w2k in addition to the
> >>reformat/resize.
> >
> >
> > Repair will leave permanent damage, most likely. The extent of
> > that
> damage
> > is controlable but it will probably be best to just start over.
> >
> >
> >>All I've read suggests that after "installing" DOS---one only
> >>needs to repair the boot sector (as DOS will have wiped out
> >>Ntldr--->thus not being able to find bot.ini (which I will also
> >>edit). I only hope I need to do "that" once (why not?) as the
> >>"one" boot process serves the w2k on hd1 as well.
> >
> >
> > As I said before, should you restore boot.ini OS declarations.
> > 2k
> in Part1
> > will not fix 2k in Part2. To avoid 2 repair processes, manually
> restore the
> > entry after the boot loader has been fixed.
> >
> >
> >>It just dawned on me! [...]
> >
> >
> > You are confirmed.
> >
> >
> >>So, why isn't it booting to dos? I have Msdos pointing to E:\
> >>where I've installed the a "windows" folder from my 98se command
> >>folder.
> >
> >
> > A suggestion was made above. bootsect version must match the
> > boot files
> > and it most likely doesn't. The file on your C: should hold the
> > W2k
> version
> > (Since W2k was bootable before the files were repaired). 2k just
> backs it up
> > and writes its own. Now, should the initial OS be 2k ...
> >
> >
> >>I suspect something is wrong with my msdos.sys or the pathing?
> >
> >
> > Version, most likely. If something would get screwed, you'd
> > get an
> error
> > message. There is no pathing to io.sys or msdos.sys, that's why
> > the
> reside
> > in the root.
> >
> > --
> > Andrei "Ndi" Dobrin
> > Brainbench MVP
> > www.Brainbench.com
>
>
> Ok, having the necessary DOS files in the newly formatted
> (FAT121!?) partition--I made the move to "fix" the booting
> process. Knowing it would do no good, I took the easy way out with
> the Console---no, fixboot didn't work. So, I went through the
> repair process--manual, choosing examine system start up and the
> boot sector in c:\. Well, I rebooted and while boot.ini had a new
> date and had a read attribute again (proving that it did
> something)?---Well, when I hit MS-DOS on the menue--same, same.
> blank screen and the curser blinking. No error---nuttin. I have
> not read a KB article that differed from the above procedure.
> I am at a loss. I've jumped through every hoop to get DOS to
> boot.
>
> Further, since I moved w2k to E:\ (it works fine)---well, Command
> Console won't work from the hd1 install. When I try to re-install
> it? It's places in the little, reformatted C:\! (It still exitsts
> in F:\, it just won't boot to that install nor "take" a new
> install at that location....
>
> I did go through the registry (from the E: [moved]) install and
> there really were only application links still connected with
> C:\...the OS seemed to do pretty good fix in the repair process.
>
> So---now 1.)I have a new FAT partition w/dos files, did a repair
> (twice) and DOS that won't boot.
> 2.) My other install of w2k is unwilling to intall it's "own"
> Command Console *as it's done for years*. (and/because the one
> there isn't bootable).
>
> God forbid I should try anything w/Mandrake...

So you started a new thread here (microsoft.public.win2000.registry),
but this does not appear to be a registry issue any longer. ;-)

Relevant Pages

  • SNAFU(s) after moving OS
    ... > Repair will leave permanent damage, ... > entry after the boot loader has been fixed. ... So, I went through the repair process--manual, choosing ... Console won't work from the hd1 install. ...
    (microsoft.public.win2000.file_system)
  • SNAFU(s) after moving OS
    ... > Repair will leave permanent damage, ... > entry after the boot loader has been fixed. ... So, I went through the repair process--manual, choosing ... Console won't work from the hd1 install. ...
    (microsoft.public.win2000.registry)
  • Re: SNAFU(s) after moving OS
    ... >> Repair will leave permanent damage, ... >> entry after the boot loader has been fixed. ... I've jumped through every hoop to get DOS to ...
    (microsoft.public.win2000.registry)
  • Re: Boot To Dos CDROM
    ... I just copied the ISO to a CD, now I see why that didn't work. ... I've used XP repair, works good, so I'd better just stay with that method. ... Note that DOS is pretty much useless for working on Windows XP systems, ... What you need is to boot to a Windows XP ...
    (microsoft.public.windowsxp.general)
  • Re: Were OT now... Re: Shared/moved Font Folder
    ... The old boot sector is saved in the ... A repair will do that. ... > Then copy the bootsect.dos and you can boot to previous DOS version. ... You can't have actual DOS to another partition ...
    (microsoft.public.win2000.registry)