SNAFU(s) after moving OS

[Michael]

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.

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...

Michael

 

[Mark V]

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.

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. ;-)

 

[Michael]

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.

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. ;-)

One never knows? That is, I've found many problems or at least their
resolution led to the registry. And, well, as you'll see? Nuttin' else
(following standard procedure) seems to work anyway. Find me a KB
article that differs from my tactics and I'll try it. I hate to admit
it, but I'm damn near ready to try a third party boot manager. However
1) I don't like 'em. 2.) They open a whole 'nother kettle of fish and 3)
Which one---?

The latest:

Well, I sysed the partition (c:\---200 meg) with 98se---rebooted and was
pleased to see a new copy of bootsect.dos and boot.ini. The entry on
the .ini even saied "Microsoft Windows". I figured I was home free

So, I go to repair (manual) "checked" to fix the boot.

Rebooted---to the Window line.....same, same. Black screen, curser
blinking.

I checked the MBR and it *and* the bootsect.dos are both FAT12.

Michael

 

[Michael]

Top posting--only a few care and they know the story..


Well, all is fine. I reformatted c:\ in fat16, *re-sysed* with Win98se
(one file?)--- Added io.sys & msdos.sys----
Then did a repair on both os's *before* rebooting to either. Voila, I
now can boot to DOS--

By the way---(Mark--arch defender of registry responsibilities) This was
*probably* registry related.

The new MBR was *not* leaving the proper Disk Signature in HKLM under
Disk. I didn't bother figuring out how to put in a binary code----so I
did the above.

!!!!There is a great, expansive discription of file systems/disks in
Chapter 17 (File Systems) in "Resource Kit", online at MS---it's in the
other machine...I don't have the URL. There are several chapters (all of
'em) that are among the best free tech stuff around.

So, thanks to Andrei for pointing me in the right direction. There is
still hope for boot.ini---though its days may be numbered if I'm forced
to experiment on Mandrake.

Sorry to bore you all. Then again, DOS is history, to most.

Thanks, again.

Michael

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. ;-)

One never knows? That is, I've found many problems or at least their
resolution led to the registry. And, well, as you'll see? Nuttin' else
(following standard procedure) seems to work anyway. Find me a KB
article that differs from my tactics and I'll try it. I hate to admit
it, but I'm damn near ready to try a third party boot manager. However
1) I don't like 'em. 2.) They open a whole 'nother kettle of fish and 3)
Which one---?

The latest:

Well, I sysed the partition (c:\---200 meg) with 98se---rebooted and was
pleased to see a new copy of bootsect.dos and boot.ini. The entry on
the .ini even saied "Microsoft Windows". I figured I was home free

So, I go to repair (manual) "checked" to fix the boot.

Rebooted---to the Window line.....same, same. Black screen, curser
blinking.

I checked the MBR and it *and* the bootsect.dos are both FAT12.

Michael