I have QNX installed on its own partition and I would like to remove it.
Windows 98SE on first partition.
Can I just go into Partition Magic and delete the partition?
What will happen to the boot manager thing? (The one that will only load
QNX, Esc for alternate operating system does nothing.)
Thanks for your help,
Use DOS/WIN Fdisk from Command prompt and type FDISK/MBR
This will overwrite the bootsector with a standard? DOS/WIN one !
Tom © wrote in message …
I have QNX installed on its own partition and I would like to remove it.
Windows 98SE on first partition.Can I just go into Partition Magic and delete the partition?
What will happen to the boot manager thing? (The one that will only load
QNX, Esc for alternate operating system does nothing.)Thanks for your help,
What will happen to the boot manager thing? (The one that will only load
QNX, Esc for alternate operating system does nothing.)
Just to clarify, the QNX bootloader will load other OS’s. You have to type
in a different partition number When it says “loading from partition 1”. The
“press ESC for alternate OS” causes QNX to load an alternate QNX boot
image from the .altboot file.
Stephen Thomas wrote:
What will happen to the boot manager thing? (The one that will only load
QNX, Esc for alternate operating system does nothing.)Just to clarify, the QNX bootloader will load other OS’s. You have to type
in a different partition number When it says “loading from partition 1”. The
“press ESC for alternate OS” causes QNX to load an alternate QNX boot
image from the .altboot file.
I am a new user and have read a number of messages that go around this
issue. I have a couple of questions though.
First - as the result of a mis-reading of the “use QNX boot loader” I
inadvertently chose to use rather than ignore the loader. Although I
have now reversed the selection (by re-formatting and re-installing) and
am able to boot from my OS/2 boot manager the first “boot blob” that
appears is the “QNX partition 4” followed by the boot manager screen
which lists OS/2, QNX, BeOS, and OS/2 Maintenance (as it should). How
does one get rid of the vestiges of the QNX boot loader which loads that
first “boot blob”? It remained when the QNX partition was deleted and
after I had removed and reinstalled the OS/2 boot manager.
Second - like a number of other writers QNX will only boot through the
“ESC” key option. It stalls otherwise. From what I have read in a scan
of the newsgroups it appears that this is the result of some
unsupported hardware or a resource conflict. What is the best way to
track this down?
–
Regards,
Ian
Once you get into Windows, just use the Disk Volume mangager, or some other disk
partitioning software, and set the partition you want to boot from all the time
as the boot partition. Then you won’t have to punch a number into the qnx
loader all the time. If you are removing QNX permanently, follow the fdisk/mbr
suggesting in another message in this thread, to write back the windows boot
manager.
Stephen Thomas wrote:
What will happen to the boot manager thing? (The one that will only load
QNX, Esc for alternate operating system does nothing.)Just to clarify, the QNX bootloader will load other OS’s. You have to type
in a different partition number When it says “loading from partition 1”. The
“press ESC for alternate OS” causes QNX to load an alternate QNX boot
image from the .altboot file.
Ian_Campbell <icampbel@junctionnet.com> wrote in message
news:39EA6AFE.67F2@junctionnet.com…
Second - like a number of other writers QNX will only boot through the
“ESC” key option. It stalls otherwise. From what I have read in a scan
of the newsgroups it appears that this is the result of some
unsupported hardware or a resource conflict. What is the best way to
track this down?
I am new to RtP as is everyone, but based on my QNX4 background, pressing
the ESC key causes QNX to load the OS from the /.altboot file rather than
the /.boot file. Simply copying /.altboot to /.boot will make the alternate
image the default. I think the /.altboot file is the non-DMA version?
In QNX4 there was also an altsysinit file. This was generally used to load a
“safe mode” version of the OS in case of hardware troubles. I don’t know if
having a /etc/system/config/altsysinit will do the same thing.