Bootloader on 20gig drive.

QNX Newsgroups (Archives) qdn.public.qnx4
21

I would tend to agree - at least to the point where it’s something ‘Toshy’ -
a quirk with the disk driver or similar. I certainly can’t see any problem
with your configuration and I can get similar multi-OS partitions to work.
As I said, I’ll try and reproduce the problem on another Tosh.

Regards,

Russ.
“Paul McCormack” <mccormp@mislimited.co.uk> wrote in message
news:memo.20010622181305.2491A@mislimited.compulink.co.uk…

I am almost convinced its something to do with the power management or PCI
bios but using the switches in the boot image makes very little
difference.

Paul

In article <9h05p9$8ni$> 1@inn.qnx.com> >, > russ@bilbey.com > (Russ Bilbey)
wrote:

Paul,

I need to find a Tosh to play with, I’ll get on it Monday if you still
have
the problem. I just created similar partition sizes on a desktop 20Gb
drive
starting with a QNX partition in 0-1024 cylinders (QNX4) then QNY
(QNX2),
QNZ (RTP), then Win98 (FAT32) with 2 logical drives in an extended
partition
with no problems whatsoever. I originally tried to split the partitions
evenly between OS’s but have since tried moving these farther and
farther
away from an ideal split but no hiccups so far. Give me a couple of
days…

Russ.

“Paul McCormack” <> mccormp@mislimited.co.uk> > wrote in message
news:> memo.20010622032115.6087F@mislimited.compulink.co.uk> …
Boot file as requested Joe

No need to apologise I am just thankful you are still trying to help.

sys/boot
$ boot -fv

sys/Proc32
$ Proc32 -l 1

sys/Slib32
$ Slib32

sys/Slib16
$ Slib16

/bin/Fsys
$ Fsys

/bin/Fsys.eide
$ Fsys.eide

/bin/mount
$ mount -p/dev/hd0 /dev/hd0t78 /boot_disk

/bin/mount
$ mount /dev/hd0t77 /

/bin/sinit
$ sinit TERM=qnx




In article <9gtc8h$554$> 1@nntp.qnx.com> >, > hw@qnx.com > (Hardware Support
Account) wrote:

Hi Paul,

Your partition table looks fine.
Can you post your OS build files, sorry I should have asked you to
do
this before.

Regards,

Joe

Paul McCormack <> mccormp@mislimited.co.uk> > wrote:
Joe

Physical disk characteristics: (/dev/hd0)
Driver : EIDE Drvr
Physical Drive # : 0
Disk type : Hard (2)
Cylinders : 2432
Heads : 255
Sectors/Track : 63
Total Sectors : 39070080
Partition table information:
0: (11) beg(h=1,s=1,c=2) end(h=254,s=191,c=125) off=32193,
size=10217277
1: (77) beg(h=0,s=129,c=126) end(h=254,s=255,c=242) off=10249470,
size=5992245
2: (78) beg(h=1,s=1,c=0) end(h=254,s=63,c=1) off=63, size=32067
3: (15) beg(h=0,s=193,c=243) end(h=254,s=255,c=255) off=16241715,
size=22828365
signature1=0x55, signature2=0xAA

output of fdisk /dev/hd0 SHOW

OS Start End _Number
Size
Boot name type Cylinder Cylinder Cylinders Blocks

  1. Extd’d ( 15) 1011 2431 1421 22828365
    11146 MB warning
  2. QNY ( 78) 0 1 2 32067
    15
    MB > 3. QNX ( 77) 638 1010 373
    5992245 2925 MB > 4. FAT32 ( 11) 2
    637
    636 10217277 4988 MB *


    I should also tell you that I ended up having a Technology day
    after
    partition manager hung my machine. I now have a floppy boot disk
    that
    will boot my hard drive seamlessly but even though I set up a
    /boot_disk partition it still wont complete from the hard drive
    itself. I thought it may be something in the bios but now I can
    boot
    from the floppy I am not so sure.

Thanks for getting back to me.

Paul

In article <9gkqkg$kii$> 1@nntp.qnx.com> >, > hw@qnx.com > (Hardware
Support
Account) wrote:

Hi Paul,

Can you post the output to ‘fdisk /dev/hd0 info’ and ‘fdisk
/dev/hd0
show’.

Regards,

Joe


Paul McCormack <> mccormp@mislimited.co.uk> > wrote:
Any more suggestions Joe

This is very inconvenient.

I have access to another node and am going to try and compare
the
two >boot sectors on each to see if I can find anything obvious.

Paul

In article
memo.20010613170518.63177A@mislimited.compulink.co.uk> >,
mccormp@mislimited.co.uk > (Paul McCormack) wrote:

Joe

I did that and no change.

The laptop is a Toshiba Sat pro 4600 pentium 3 trident video
and
IBM >>> 20gig hard drive. Well as reported by Fsys.eide anyway.

it just appears to stick and the disk access stays on.

Paul

In article <9g8b22$gh$> 1@nntp.qnx.com> >, > hw@qnx.com > (Hardware
Support >>> Account) wrote:

Hi Paul,

Try editng the hard.ata build file to use the Fsys.eide
driver.
Also in the sysinit, add the following:
‘set -v’

This will cause the sysinit to be verbos so we can see if it
gets >>> > that far.
What kind of labtop & Hard drive do you have?

Regards,

Joe

Paul McCormack <> mccormp@mislimited.co.uk> > wrote:
Joe

It made no difference I am afraid.

exactly the same message.

Paul

In article <9g7rj3$k6b$> 1@nntp.qnx.com> >, > hw@qnx.com
(Hardware
Support Account) wrote:

Hi Paul,

Try the following:

  1. Goto the /boot/build directory and verify that there
    is
    an >file >>> called hard.ata (or hard.ata.#)

  2. Go back one directory level (cd …)

  3. Enter the following commands
    make b=hard.ata d=Fsys.eide h=/dev/hd0 t=77
    cp -t images/hard.ata /.boot

  4. Re-boot system and see what happens

Regards,

Joe

Paul McCormack <> mccormp@mislimited.co.uk> > wrote:
In article <9g5dpk$5cu$> 1@nntp.qnx.com> >, > hw@qnx.com
(Hardware >>> > > > Support >Account) wrote:

Hi Paul,

What happens when you try to boot into QNX 4?
Any error msgs?

No. It just sits at the press escape prompt with two
dots
at >the >end >and the hard drive light stays on.


Run ‘fdisk /dev/hd0’ and verify that the QNX
partition is
set >as >> >> bootable.
The Boot column should have a ‘*’ in the QNX 4 row
(type
77).

Done. I also tried dinit -hb /dev/hd0t77 and fdisk
/dev/hd0 >>> > > > loader >> > boot qnx



Regards,

Joe

Paul McCormack <> mccormp@mislimited.co.uk> > wrote:
Hi Joe

In article <9g52sc$sde$> 1@nntp.qnx.com> >, > hw@qnx.com
(Hardware >>> > > Support >Account) wrote:

Hi Paul,

If the QNX partition crosses 1024 cylinders it will
not >>> > > > > boot, it >>> > must >start
and end before this limit.

The QNX Partition does not cross the 1024 cylinder
limit


Try booting with a QNX 4 boot disk and set the root
directory to >be >the >primary
partition (on hard disk) using the prefix command.

ex: /hd0/bin/prefix -R /=/hd0

Now try installing the Patch.

Done I even have photon running which was a
surprise as
the >>> > > trident >chipset does not appear to be
supported >by Photon 2.


Dosfsys will only work with FAT16 partitions, you
will
need >to >> > > use >>> Fatfsys to
access a FAT32 partition.

I also got this working but only to a few
directories
deep. I >>> > > really >need to concentrate on it but I
more >concerned with >not >> > > being able to
boot.


Regards,

Joe

Thanks for getting back to me.



Paul McCormack <> mccormp@mislimited.co.uk> > wrote:
I am having major problems booting QNX4 on my
laptop.

I have three partitions

1 QNX4.25A - hd0t77 - This is in the first 1.5
gig
of >the >drive >>> > > and I >can boot from a floppy,
mount the >drive >and see the
installation
no >problem.

3 Extended DOS partition hd0t12 FAT drive. This
is
in >the >last >>> > > 3.5gig >of the drive. I can see
it
as >drive D in >windows 98 and >can >mount it
using >Dosfsys when I try to >write to it says
the
drive is >full.

4 Primary Win98 hd0t15 boots from the QNX
bootloader
no >>> > > > > > problem.

I have tried several times to rewrite the
secondary
boot >loader >>> > > but >with no change.

I thought it may have been that I needed patch E
and
as >it >had >>> >> > fatfsys i tried to mount the
extended FAT >>> > > > > > partition to mount
it.

I have loaded QNX RTP and tried to use that to
copy
the >>> > > > > > patch >to >the >QNX 4 partition. RTP
mounts the partitions >>> > > > > > but I cannot
write
to the >hd0t77. I can read it but it
says
its full when I >try to >copy to it.

How do I get the patch from my FAT32/FAT extended
partition to >the >>> > QNX partition and then how
to I
get >the QNX partition >to boot.

I cannot change the drive translation in bios
because >its >a >> >> > > Toshiba >laptop and I dont
have
the option >so I >stuck with >1024
cylinders.

Paul














\