Playing with your suggestions here did not help me. I have
partitionMagic in windows, and when I run it, PartitionMagic comes with
an error:
Thanks for your help.
Miguel.
One or two days after the installation windows where no longer booting with
the same
error message as Miguel mentioned.
Looking into the partition table showed the entries of slot 3 and 4 in the
partition table swaped.
I didn’t find out why. And it never again showed up un my PC.
But other people in our company had the same symptoms
with partition 3 and 4 the same and SCO UNIX on the rest of the disk.
I was able to fix it by just exchange the entries 3 and 4 in the partition
table.
Werner Schweizer
“Eduard” <> ed1k@humber.bay> > schrieb im Newsbeitrag
news:> MPG.18b4533aed3e414998968e@inn.qnx.com> …
In article <b2cu7j$92l$> 1@inn.qnx.com> >,
nospamWrnr.Schwzr@ch.mullermartini.com > says…
For some reason Microsoft decided to have the index of the partition
table
entry
hard coded in the \boot.ini.
[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
I had also some situations the partition table entries where rearanged
(Don’t know why).
Werner, I’m sorry, but you’ve messed things up a little bit here.
Partition number in path for
operation system in boot.ini file is not the same what is partition number
of partition table entry
in MBR. Partition number in boot.ini is a number of partition from
Windows’ point of view. It’s a
little bit hard to understand how windows to number partition, but here is
some rules:
- partiton numbers start from 1, as opposite to controller number and
disk number which start from
-
- numbering starts from primary active partition, then primary inactive
partitions and last are
the logical drives, i.e partitions in extended region.
Does it explain your question why it was rearanged in your case? You can
mark another partition as
active… and you have to edit boot.ini > 
> You can creat additional
primary partition on disk… and
you have to edit boot.ini if your windows partition is extended >
This was leading to your error message.
Nope. “Ntldr missing” means exactly it. There is no ntldr in root
directory of boot up disk. Windows
NT second (if loader in MBR is first) loader (boot sector of windows
partition) just can’t find
ntldr. boot.ini file is parsed by ntldr later. You can just put ntldr,
ntdetect.com and boot.ini
files from your bootable flopy or installation CD in root directory of
windows partition and see if
it helps.
Miguel, probably you placed lilo in MBR? Sorry, I don’t understand what
you mean by "destroy the
MBR". If you have partitions on your drive, it means your MBR is OK… but
primary loader is not
that one what you maybe wanted. If you have lilo in MBR you have just
configure your linux loader to
load QNX and WIndows as well. Can you explain more details?
Cheers,
Eduard.
ed1k at qnx-night dot com.
You now have two options:
- Rearange the partition table entries manually with QNX fdisk to the
original state
- Edit \boot.ini to change the partition number to the correct index
containing the windows partition.
Werner Schweizer
“Miguel Simon” <> simon@ou.edu> > schrieb im Newsbeitrag
news:> 3E4A06C9.3050602@ou.edu> …
Hi…
I installed QNX, Linux, Windows2000 in my laptop. Eventually I
managed
to destroy the MBR in such a way that not even QNX loader can undo the
damage (as it has done in the past). I have followed --EVERY–
windows
suggestion to no avail. The system always says: “NTLDR missing” or
something like that.
The only partition that boots well is the Linux partition. The QNX
partition boots off the cd, and the windows partition boots off the
floppy.
I have asked this question before, but perhaps one more time will be
better…
How can I boot QNX from the linux partition?
Thanks…
Miguel.
\