Windows NT is usually installed after DOS/Windows 9x on a multiboot machine.
What happens if you try to install Win9x after first installing NT ?
Max
Max
> Windows NT is usually installed after DOS/Windows 9x on a multiboot machine.
> What happens if you try to install Win9x after first installing NT ?
> Max
~REZ~
You could do that,Quote:> Windows NT is usually installed after DOS/Windows 9x on a multiboot
machine.
> What happens if you try to install Win9x after first installing NT ?
> Max
Win95 will overwrite NT's ability to boot.Quote:> Windows NT is usually installed after DOS/Windows 9x on a multiboot
machine.
> What happens if you try to install Win9x after first installing NT ?
--
Richard Dakin
+++ No email please +++
Bill
Quote:> Windows NT is usually installed after DOS/Windows 9x on a multiboot
machine.
> What happens if you try to install Win9x after first installing NT ?
> Max
First, you boot off of a MS-DOS/Win9x floppy. You will need only DEBUG.EXE
on the floppy.
Change to C:
Run A:DEBUG.EXE
DEBUG will give you a "-" prompt, at which you type in the following lines:
L 100 2 0 1
N bootsect.nt
RCX 200
W
Q
- this does is load to memory location 100, from the C drive (0 is drive A,
1 is drive B, 2 is drive c), logical sector 0, and only load 1 sector (l
100 2 0 1),
- "N bootsect.nt" sets the current filename you're working with to
BOOTSECTN.NT,
- "RCX 200" loads register CX with the size of current file, which is 200h
bytes, or 512 bytes,
- "W" writes the file to disk (the current directory),
- "Q" exits debug
Now SYS the drive. This will put the bare minimum files you need to run
MS-DOS on the C: drive (IO.SYS, MSDOS.SYS, and COMMAND.COM). This ALSO put
a new boot sector on your hard drive. Next, you need to save this boot
sector to the root of C: as a file called "BOOTSECT.DOS". Follow the above
DEBUG instructions, substituting in "N bootsect.dos" for "N bootsect.nt".
After this, you need to restore the NT boot sector with DEBUG.EXE. The
commands are, after starting DEBUG.EXE from the root of C:
N bootsect.nt
L
W 100 2 0 1
Q
This loads bootsect.nt at memory location 100, and writes from that memory
to drive 2, logical address 0, 1 sector.
You now have a "boot drive" that is capable of dual booting. There is only
one thing left to do. NTLDR needs to know that you have another OS to
boot, so you will need to modify the file "BOOT.INI" that is in the root of
C: - it's usually hidden, so you'll need ATTRIB.EXE to change the
attributes. Got to C:, and run "ATTRIB -R -S -H BOOT.INI". Edit BOOT.INI,
and add the following line under the [Operating Systems] section (append it
to the file):
C:\="MS-DOS"
Save BOOT.INI, run "ATTRIB +R +S +H BOOT.INI", and you're done.
Note: none of the commands I types are case sensitive - I just used upper
case to avoid confusion between letters like i and l. Also, For the new OS
line you put in your BOOT.INI, the part in quotes can read whatever you
want as it doesn't have to say MS-DOS - it could Windows98, Windows95, or
whatever.
Oh, and one final note. I always save my NT and MS-DOS/Win98 boot sector
to my loyal boot floppy. If anything goes wrong, I always have a backup
(i.e. copy BOOTSECT.DOS and BOOTSECT.NT to a floppy disk). I even save my
MBR, but saving that via DEBUG.EXE is a topic for another day.
> > Windows NT is usually installed after DOS/Windows 9x on a multiboot
> machine.
> > What happens if you try to install Win9x after first installing NT ?
The easiest way to achieve this is via the emergency repair disk in NT.Quote:> If you have installed WinNT, and your boot partition (actually, your first
> partition, or C:) is FAT, then you can install Win9x or MS-DOS after
> installing WinNT - I do it all the time.
> First, you boot off of a MS-DOS/Win9x floppy. You will need only
DEBUG.EXE
> on the floppy.
> Change to C:
> Run A:DEBUG.EXE
> DEBUG will give you a "-" prompt, at which you type in the following
lines:
> L 100 2 0 1
> N bootsect.nt
> RCX 200
> W
> Q
> - this does is load to memory location 100, from the C drive (0 is drive
A,
> 1 is drive B, 2 is drive c), logical sector 0, and only load 1 sector (l
> 100 2 0 1),
> - "N bootsect.nt" sets the current filename you're working with to
> BOOTSECTN.NT,
> - "RCX 200" loads register CX with the size of current file, which is 200h
> bytes, or 512 bytes,
> - "W" writes the file to disk (the current directory),
> - "Q" exits debug
> Now SYS the drive. This will put the bare minimum files you need to run
> MS-DOS on the C: drive (IO.SYS, MSDOS.SYS, and COMMAND.COM). This ALSO
put
> a new boot sector on your hard drive. Next, you need to save this boot
> sector to the root of C: as a file called "BOOTSECT.DOS". Follow the
above
> DEBUG instructions, substituting in "N bootsect.dos" for "N bootsect.nt".
> After this, you need to restore the NT boot sector with DEBUG.EXE. The
> commands are, after starting DEBUG.EXE from the root of C:
> N bootsect.nt
> L
> W 100 2 0 1
> Q
> This loads bootsect.nt at memory location 100, and writes from that memory
> to drive 2, logical address 0, 1 sector.
> You now have a "boot drive" that is capable of dual booting. There is
only
> one thing left to do. NTLDR needs to know that you have another OS to
> boot, so you will need to modify the file "BOOT.INI" that is in the root
of
> C: - it's usually hidden, so you'll need ATTRIB.EXE to change the
> attributes. Got to C:, and run "ATTRIB -R -S -H BOOT.INI". Edit
BOOT.INI,
> and add the following line under the [Operating Systems] section (append
it
> to the file):
> C:\="MS-DOS"
> Save BOOT.INI, run "ATTRIB +R +S +H BOOT.INI", and you're done.
> Note: none of the commands I types are case sensitive - I just used upper
> case to avoid confusion between letters like i and l. Also, For the new
OS
> line you put in your BOOT.INI, the part in quotes can read whatever you
> want as it doesn't have to say MS-DOS - it could Windows98, Windows95, or
> whatever.
> Oh, and one final note. I always save my NT and MS-DOS/Win98 boot sector
> to my loyal boot floppy. If anything goes wrong, I always have a backup
> (i.e. copy BOOTSECT.DOS and BOOTSECT.NT to a floppy disk). I even save my
> MBR, but saving that via DEBUG.EXE is a topic for another day.
--
Richard Dakin
+++ No email please +++
1. Why NT Workstation over Windows '95 on with NT Server
Can anybody help
We are about to have a new NT 4.0 server and probably NT workstations,
but is there any reason why we sould not use Windows '95 on the
workstations instead.
What exactly are the advantages of running NT Workstation over 95.
All we want to do is have two NT 4.0 servers connected over the
internet with a small workstation network either side. We are not
trying to do anything comlicated so is there any advantage?
Does Windows '95 as a workstation work perfectly well connected as a
network to a NT 4.0 server.
I have ready a lot on Microsofts Web pages and here and I not found an
answer.
TIA
Steve Niemiec
2. Reserved IP addressess for internal use only
3. NT Resource Kit, why 'ls', 'cat', etc won't run?
4. refer to asx file from anywhere?
5. Taskbar isn't always on top. Why?
7. Re-installing WinMe 'over the top' - error persists
8. 128 bit for IE6 and Win 2000
9. why can't install windows media player
10. Why I can't install windows media player v7.1?
11. Why users can't use programs administrator install (in windows xp)
12. Can I install Windows 3.1 on top of Windows 3.11 (downgrade)
13. Windows NT won't boot after installing Windows 2000