Previously, pete@qnx.com wrote in qdn.public.qnxrtp.installation:
Even if it doesn’t, you can install the
boot loader that comes with RTP. It works the same as the QNX4 one…
hit the numeric digit of the partition number you want to boot.
please, where can that QNXRTP bootloader be found?
i was searching, but without luck…
thanks,
*martin
i tried that qnx-bootloader from the .iso, but it only modifies the config.sys-file of win95/98, it is not intented for use with winNT/2000.
i have 3 bootloaders in a row 
the first one (beos-bootmanager) chooses between win/linux/beos.
linux and beos load straight away from that point.
when you choose win, up comes the win2000 bootloader, which lets you choose between win98 and 2000 - here i tried to install the qnx to the menu, but without success (this one is managed by boot.ini on c:/)…
in this win2000 bootloader you can choose win98, (which again calls a ‘fake’ bootmanager for win98 (i.e. the modified config.sys)- made by the qnx-bootloader) and HERE is the point where the original qnx-bootloader would install itself, unfortunately not before that point in a winNT or win2000-bootmenu 
so i still boot up from diskette…
soooo - after looking at that i would say, a QNX-bootmanager would be nice
which ALSO modifies the boot.ini file for NT-systems, NOT ONLY the config.sys for 95/95-systems. maybe that would be an easy job for someone skilled? 
thanks,
*martin
Previously, Arve Bersvendsen wrote in qdn.public.qnxrtp.installation:
Den 11 okt 2000 18:13 skrev > dfkt69@yahoo.com > (dfkt):
please, where can that QNXRTP bootloader be found?
i was searching, but without luck…Afaik only with the qnx rtp distribution (either the download, or
orderable cd). Believe me, it’s not something you want to use, unless
absolutely neccessary.–
Arve Bersvendsen.
Mirror av XNews (03.09.22) -
http://www.bersvendsen.com/usenet/xnews/
i tried that qnx-bootloader from the .iso, but it only modifies
the config.sys-file of win95/98, it is not intented for use with
winNT/2000.
I had no problems with the qnx bootloader and windows 2000, provided
soooo - after looking at that i would say, a QNX-bootmanager would
be nice which ALSO modifies the boot.ini file for NT-systems, NOT
ONLY the config.sys for 95/95-systems. maybe that would be an easy
job for someone skilled? >
Were you perhaps installing qnx on a fat/32 partition? I used a
partition manager to install qnx on it’s own dedicated partition.
My understanding is that if you install it on a fat/32-partition, it
depends on booting from the fat/32-partiton, and be invoked from
autoexec.bat/config.sys-directives.
–
Arve Bersvendsen.
Mirror av XNews (03.09.22) -
http://www.bersvendsen.com/usenet/xnews/
Previously, Arve Bersvendsen wrote in qdn.public.qnxrtp.installation:
Den 12 okt 2000 01:43 skrev > dfkt69@yahoo.com > (dfkt):
i tried that qnx-bootloader from the .iso, but it only modifies
the config.sys-file of win95/98, it is not intented for use with
winNT/2000.I had no problems with the qnx bootloader and windows 2000, provided
- I tried to install qnx on a primary partition
- This primary partition was on hda
could you please send me the lines the qnx-bootloader changed in your config/boot-files? maybe i can change mine then the right way. thanks in advance!
soooo - after looking at that i would say, a QNX-bootmanager would
be nice which ALSO modifies the boot.ini file for NT-systems, NOT
ONLY the config.sys for 95/95-systems. maybe that would be an easy
job for someone skilled? >Were you perhaps installing qnx on a fat/32 partition? I used a
partition manager to install qnx on it’s own dedicated partition.My understanding is that if you install it on a fat/32-partition, it
depends on booting from the fat/32-partiton, and be invoked from
autoexec.bat/config.sys-directives.
i installed to a 500MB-ide-hd, only one primary partition (fat16), which is master (no slave present) on secondary ide-bus.
this should be ok, i think? (since i have no troubles with booting from diskette).
does it make a difference: i installed QNX from win2000 because an installation from the .iso/cdrom wasn’t possible.
or is it the same to install via bootable cd and windows-qnx-installation?
–
*martin
could you please send me the lines the qnx-bootloader changed in
your config/boot-files?
As I tried to explain; there are no config/boot files.
On my Win2k/QnX workstation, qnx is installed on a separate
partition, with it’s own file system. QNX installs a small boot
loader program on the Master Boot Record of the disk. This is fairly
impossible to extract, and send.
What you want to do, is to use a utility like PartitonMagic
URL:http://www.powerquest.com/, for
resizing/moving/deleting/whatever partitions from your hard drive to
free up some space.
Then you setup your bios to boot from cdrom, and boot from the qnx
cdrom. You will then be prompted with options on where to install qnx
to, and where you want to install it from. Finally, it will ask you
whether you want to install the bootmanager or not. Install it.
After qnx is installed, and you have rebooted the computer, the qnx
bootmanager will have replaced the ordinary bootmanager of windows.
Then you’re prompted which partition number you want to boot. It’s a
bit of guesswork, trying to find which partition is your windows
partition.
PS! You might want to uninstall qnx first, if you have it installed
on a FAT/NTFS drive (Win9x/ME/NT/2000 partition)
Anyway; now I have installed Linux on a second HD, and am using Lilo
to boot. For those who have had problems with the qnx boot freezing,
with lilo as a bootmanager, I tried the following lilo.conf, which
worked very well for me.
other=/dev/hda4
label=qnx
optional
unsafe
(which incidentally, is basically the same setting you should use if
you want to use lilo to boot from a floppy, replace hd* with fd*
Arve Bersvendsen.
Mirror av XNews (03.09.22) -
http://www.bersvendsen.com/usenet/xnews/
arve,
many thanks for helping
thanks for helping,
*martin
Previously, Arve Bersvendsen wrote in qdn.public.qnxrtp.installation:
Den 12 okt 2000 05:15 skrev > dfkt69@yahoo.com > (dfkt):
could you please send me the lines the qnx-bootloader changed in
your config/boot-files?As I tried to explain; there are no config/boot files.
On my Win2k/QnX workstation, qnx is installed on a separate
partition, with it’s own file system. QNX installs a small boot
loader program on the Master Boot Record of the disk. This is fairly
impossible to extract, and send.What you want to do, is to use a utility like PartitonMagic
URL:> http://www.powerquest.com/> >, for
resizing/moving/deleting/whatever partitions from your hard drive to
free up some space.Then you setup your bios to boot from cdrom, and boot from the qnx
cdrom. You will then be prompted with options on where to install qnx
to, and where you want to install it from. Finally, it will ask you
whether you want to install the bootmanager or not. Install it.After qnx is installed, and you have rebooted the computer, the qnx
bootmanager will have replaced the ordinary bootmanager of windows.Then you’re prompted which partition number you want to boot. It’s a
bit of guesswork, trying to find which partition is your windows
partition.PS! You might want to uninstall qnx first, if you have it installed
on a FAT/NTFS drive (Win9x/ME/NT/2000 partition)Anyway; now I have installed Linux on a second HD, and am using Lilo
to boot. For those who have had problems with the qnx boot freezing,
with lilo as a bootmanager, I tried the following lilo.conf, which
worked very well for me.other=/dev/hda4
label=qnx
optional
unsafe(which incidentally, is basically the same setting you should use if
you want to use lilo to boot from a floppy, replace hd* with fd* >No: I don’t think you can install lilo without installing linux as
well, but please prove me wrong. You can install linux, edit
lilo.conf, rerun lilo, and then delete your linux partition, but
that’s hardly a good idea.
\Arve Bersvendsen.
Mirror av XNews (03.09.22) -
http://www.bersvendsen.com/usenet/xnews/
–
*martin
Igor.Kovalenko@motorola.com (Igor Kovalenko) wrote in
<39D0EB73.B0A37844@motorola.com>:
Because M$ does not release specs for NTFS. Linux driver is based on
reverse-engineered specs AFAIK. QNX can’t do that because they might be
sued.
Well they can always ‘reverse-engineer’ the Linux NTFS driver.
“Mick” <mickvb@optushome.com.au> wrote in message
news:90406DFAmickvboptushomecomau@209.226.137.7…
Igor.Kovalenko@motorola.com > (Igor Kovalenko) wrote in
39D0EB73.B0A37844@motorola.com> >:Because M$ does not release specs for NTFS. Linux driver is based on
reverse-engineered specs AFAIK. QNX can’t do that because they might be
sued.Well they can always ‘reverse-engineer’ the Linux NTFS driver.
Reverse-engineer is unreliable and in most cases illegal. QSSL being
in the business of making money, it’s very risky legaly wise to
reverse-engineer stuff.
On Mon, 5 Feb 2001, Mario Charest wrote:
Reverse-engineer is unreliable and in most cases illegal. QSSL being
in the business of making money, it’s very risky legaly wise to
The fact that QSSL is in the business of making money can be a benefit.
They can do what Linux can’t do (things like NDA). I’ve seen other
companies having products supporting NTFS. I am sure they got the
blessing from Microsoft via some agreement.
reverse-engineer stuff.
“Frank Liu” <liug@mama.indstate.edu> wrote in message
news:Pine.LNX.4.21.0102051518220.13458-100000@mama.indstate.edu…
On Mon, 5 Feb 2001, Mario Charest wrote:
Reverse-engineer is unreliable and in most cases illegal. QSSL being
in the business of making money, it’s very risky legaly wise toThe fact that QSSL is in the business of making money can be a benefit.
They can do what Linux can’t do (things like NDA). I’ve seen other
companies having products supporting NTFS. I am sure they got the
blessing from Microsoft via some agreement.
Yeah, the agreement is basically this:
a) the product can’t be in competition with microsoft products (being that
QNX is an OS, things already start to look bad).
b) you cut M$ a big cheque (not very doable when the O/S is given away for
non commercial use).
Does partition magic support NTFS, yeah; are they going to be in business
much longer (not likely).
Just saw the announcement of the FIRST public release of Linux-NTFS
project:
http://lwn.net/daily/linux-ntfs.php3
It mentioned that it includes the NTFS docs. Maybe QSSL can use
those docs to write a RTP driver?
Remember the joke about DOS programmers “the job isn’t done until Netware
won’t run”
If you figure that Netware client was like a patch reverse-engineered onto
DOS, then you can guess what’s going to happen to companies that reverse
engineer NTFS…
On the other hand, Autocad has a similar “won’t release” policy for .DWG
format.
However, almost everybody in the CAD industry HAS wound up reverse
engineering it
On the third hand, the complexity of Acad is likely quite low relative to
NTFS
“Frank Liu” <liug@mama.indstate.edu> wrote in message
news:Pine.LNX.4.21.0102051711420.22395-100000@mama.indstate.edu…
Just saw the announcement of the FIRST public release of Linux-NTFS
project:
http://lwn.net/daily/linux-ntfs.php3It mentioned that it includes the NTFS docs. Maybe QSSL can use
those docs to write a RTP driver?