re: boot.ini and NTOSKRNL.exe whats the deal???
Sunday, July 1, 2007 at 9:38 am
Windows 2000 Annoyances Discussion Forum
Posted by Steve Dunn
(911 messages posted)
I would guess that something is changing the way windows recognises the order of
your hard drives. With your set up I'd expect the IDE drives to be first (0 & 1)
and then the SATA drives as 2 & 3. which looking at your boot.ini would have been
the case when it worked (1st SATA = rdisk(2) - ie, 3rd drive in the boot order).
This also presupposes that which disk the C: drive is on is always picked up by the
bios as the boot drive (looking at your list it looks like its actually the second
IDE drive as 1st doesn't have a primary partition, and boot.ini only works from a
primary partition.
Are you changing physical connections/bios settings at all?
Have you considered using a separate boot manager? - eg, www.boot-us.com - and making
your SATA based clean install properly independent (by giving it is own boot sector
- when you install 2k where an MS boot sector already exists, it always uses that
- your situation. If you install it with other drives disconnected, it creates boot
sector on the drive of course. This makes the installation independent, as it doesn't
need the 'main' boot sector to load. You can create a boot sector by having the drive
connected on its own, previously having copied the files ntldr and ntdetect.com to
its root with a boot.ini which looks like:-
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect
Then load recovery console, and run the command fixboot.
Also, boot managers like boot-us can then directly boot such installations from their
menu (would suggest putting menu on a floppy if you do use boot-us - so your hard
drives are not affected).
HTH
On Saturday, June 30, 2007 at 6:32 pm, Airwreck wrote:
>Sure I can tell you the set up..But do you really wan to know..LOL
>it goes like this
>Triple boot
>Option 1 Upgrade98 to Win2k this is an upgrade from win311 to 95 then 98 Hence the
>reason for the clean install but some software I use will not install under win2k
>and I don't own the Version of the software that will.
>
>Option 2 Clean Install win2k on a SATA Drive
>Option 3 DOS BOOT
>
>Everything is FAT32
>
>4 HD 2 IDE 2 SATA Drives
>Active Partion on Drive C
>Drive 1 IDE partioned into 6 extended
>Drive 2 IDE partioned into 1 primary 8 extended
>Drive 3 SATA 1 primary 2 extended
>Drive 4 SATA 1 Primanry no Extions
>
>Boot.ini that worked yesterday but not today
>[boot loader]
>timeout=30
>default=multi(0)disk(0)rdisk(2)partition(1)\WINNT
>[operating systems]
>multi(0)disk(0)rdisk(2)partition(1)\WINNT="Microsoft Windows 2000 Professional"
/fastdetect
>multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows 2000 Professional"
>/fastdetect
>C:\=MS-DOS
>
>At presnt I have 3 boot.ini's One called Boot.ini one called bootmine.ini one called
>bootold.ini
>That way I can rotate the boot.ini that works.. by renaming..
>
>So there the nightmare..ROFL.. Now aren't you glad you asked..
>Cheers
>Airwreck
|
All messages in this thread [show all]
 | | |  | re: boot.ini and NTOSKRNL.exe whats the deal??? (Steve Dunn: Sun, Jul 1, 2007, 9:38 am) |
| |
| |
Return to the Windows 2000 Discussion Forum
|
|
