Win98 qnxrtp610.exe: on boot, EIDE scan failure

I’m a QNX newbie trying to install the small Windows platform
(qnxrtp610.exe) on an eMachines etower 266 box. The Setup installation goes
fine (I select the default 600MB working set size). Upon reboot, I choose
QNX (DMA disabled), and select the verbose boot option (F6). The boot
sequence always hangs during the EIDE scan:

Range check failed - Dev 571 - Vend 1106 - Class 1018a - Addr ffa0 - Size 10
Trying to detect EIDE
[…]
Detected EIDE. Scanning for devices.
Starting devb-eide blk auto=partition dos exec=all
Path=0 - EIDE
target=0 lun=0 Direct Access(0) - WDC WD600BB-00CF Rev:
Path=1 - EIDE
target=0 lun=0 CD-ROM(5) - LITE-ON LTR-12101B Rev: LS3B
target=1 lun=0 CD-ROM(5) - MT1316B BDV212B Rev: 0.36
simq_timer: building abort ccb
simq_timer: building reset ccb
[long delay here…]
simq_timer: building abort ccb
simq_timer: building reset ccb

Finally, I have to force a reset and reboot.

In a second scenario, I have a slightly different failure symptom (no
verbose mode this time, sorry).
Following the reboot with DMA disabled, the EIDE scan completes, then I see:

Generating helpviewer search database.
/etc/system/sysinit[81]: getconf: No such file or directory

Does either of these suggest to you what might be going wrong here? The hdd
is a Western Digital 60MB drive, and I must admit there is a problem with my
AMIBIOS recognizing its full size – when I select the BIOS’ Autodetect, it
under-detects the size of the drive; but under Win98, this does not
prevent the drive’s actual size from being correctly determined as 60MB.

So I tried this same procedure on a smaller drive (2.1GB), and got very
similar results. I would tend not to suspect the drive size as the only
issue here…

Thanks for any help anyone can offer,

–dave

Hi Dave,

What is the setup of your ATA/EIDE devices? What is set to master
and what is set to slave?

Thanks

Erick.


Dave Jacobs <jacobs-dave@home.com> wrote:

I’m a QNX newbie trying to install the small Windows platform
(qnxrtp610.exe) on an eMachines etower 266 box. The Setup installation goes
fine (I select the default 600MB working set size). Upon reboot, I choose
QNX (DMA disabled), and select the verbose boot option (F6). The boot
sequence always hangs during the EIDE scan:

Range check failed - Dev 571 - Vend 1106 - Class 1018a - Addr ffa0 - Size 10
Trying to detect EIDE
[…]
Detected EIDE. Scanning for devices.
Starting devb-eide blk auto=partition dos exec=all
Path=0 - EIDE
target=0 lun=0 Direct Access(0) - WDC WD600BB-00CF Rev:
Path=1 - EIDE
target=0 lun=0 CD-ROM(5) - LITE-ON LTR-12101B Rev: LS3B
target=1 lun=0 CD-ROM(5) - MT1316B BDV212B Rev: 0.36
simq_timer: building abort ccb
simq_timer: building reset ccb
[long delay here…]
simq_timer: building abort ccb
simq_timer: building reset ccb

Finally, I have to force a reset and reboot.

In a second scenario, I have a slightly different failure symptom (no
verbose mode this time, sorry).
Following the reboot with DMA disabled, the EIDE scan completes, then I see:

Generating helpviewer search database.
/etc/system/sysinit[81]: getconf: No such file or directory

Does either of these suggest to you what might be going wrong here? The hdd
is a Western Digital 60MB drive, and I must admit there is a problem with my
AMIBIOS recognizing its full size – when I select the BIOS’ Autodetect, it
under-detects the size of the drive; but under Win98, this does not
prevent the drive’s actual size from being correctly determined as 60MB.

So I tried this same procedure on a smaller drive (2.1GB), and got very
similar results. I would tend not to suspect the drive size as the only
issue here…

Thanks for any help anyone can offer,

–dave

The WDC 60GB hdd is the primary master, jumpered as “single”, with no
primary slave. The secondary master is a CD-RW drive and the secondary slave
is a DVD-ROM.

Thanks,
–dave


“Hardware Support Account” <hw@qnx.com> wrote in message
news:9r1d6o$fn4$4@nntp.qnx.com

Hi Dave,

What is the setup of your ATA/EIDE devices? What is set to master
and what is set to slave?

Thanks

Erick.


Dave Jacobs <> jacobs-dave@home.com> > wrote:
I’m a QNX newbie trying to install the small Windows platform
(qnxrtp610.exe) on an eMachines etower 266 box. The Setup installation
goes
fine (I select the default 600MB working set size). Upon reboot, I
choose
QNX (DMA disabled), and select the verbose boot option (F6). The boot
sequence always hangs during the EIDE scan:

Range check failed - Dev 571 - Vend 1106 - Class 1018a - Addr ffa0 -
Size 10
Trying to detect EIDE
[…]
Detected EIDE. Scanning for devices.
Starting devb-eide blk auto=partition dos exec=all
Path=0 - EIDE
target=0 lun=0 Direct Access(0) - WDC WD600BB-00CF Rev:
Path=1 - EIDE
target=0 lun=0 CD-ROM(5) - LITE-ON LTR-12101B Rev: LS3B
target=1 lun=0 CD-ROM(5) - MT1316B BDV212B Rev:
0.36
simq_timer: building abort ccb
simq_timer: building reset ccb
[long delay here…]
simq_timer: building abort ccb
simq_timer: building reset ccb

Finally, I have to force a reset and reboot.

In a second scenario, I have a slightly different failure symptom (no
verbose mode this time, sorry).
Following the reboot with DMA disabled, the EIDE scan completes, then I
see:

Generating helpviewer search database.
/etc/system/sysinit[81]: getconf: No such file or directory

Does either of these suggest to you what might be going wrong here? The
hdd
is a Western Digital 60MB drive, and I must admit there is a problem
with my
AMIBIOS recognizing its full size – when I select the BIOS’ Autodetect,
it
under-detects the size of the drive; but under Win98, this does not
prevent the drive’s actual size from being correctly determined as 60MB.

So I tried this same procedure on a smaller drive (2.1GB), and got very
similar results. I would tend not to suspect the drive size as the only
issue here…

Thanks for any help anyone can offer,

–dave

Hi Dave,

What happens when you disconnect the secondary chain all together?

Thanks

E.


Dave Jacobs <jacobs-dave@home.com> wrote:

The WDC 60GB hdd is the primary master, jumpered as “single”, with no
primary slave. The secondary master is a CD-RW drive and the secondary slave
is a DVD-ROM.

Thanks,
–dave



“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9r1d6o$fn4$> 4@nntp.qnx.com> …
Hi Dave,

What is the setup of your ATA/EIDE devices? What is set to master
and what is set to slave?

Thanks

Erick.


Dave Jacobs <> jacobs-dave@home.com> > wrote:
I’m a QNX newbie trying to install the small Windows platform
(qnxrtp610.exe) on an eMachines etower 266 box. The Setup installation
goes
fine (I select the default 600MB working set size). Upon reboot, I
choose
QNX (DMA disabled), and select the verbose boot option (F6). The boot
sequence always hangs during the EIDE scan:

Range check failed - Dev 571 - Vend 1106 - Class 1018a - Addr ffa0 -
Size 10
Trying to detect EIDE
[…]
Detected EIDE. Scanning for devices.
Starting devb-eide blk auto=partition dos exec=all
Path=0 - EIDE
target=0 lun=0 Direct Access(0) - WDC WD600BB-00CF Rev:
Path=1 - EIDE
target=0 lun=0 CD-ROM(5) - LITE-ON LTR-12101B Rev: LS3B
target=1 lun=0 CD-ROM(5) - MT1316B BDV212B Rev:
0.36
simq_timer: building abort ccb
simq_timer: building reset ccb
[long delay here…]
simq_timer: building abort ccb
simq_timer: building reset ccb

Finally, I have to force a reset and reboot.

In a second scenario, I have a slightly different failure symptom (no
verbose mode this time, sorry).
Following the reboot with DMA disabled, the EIDE scan completes, then I
see:

Generating helpviewer search database.
/etc/system/sysinit[81]: getconf: No such file or directory

Does either of these suggest to you what might be going wrong here? The
hdd
is a Western Digital 60MB drive, and I must admit there is a problem
with my
AMIBIOS recognizing its full size – when I select the BIOS’ Autodetect,
it
under-detects the size of the drive; but under Win98, this does not
prevent the drive’s actual size from being correctly determined as 60MB.

So I tried this same procedure on a smaller drive (2.1GB), and got very
similar results. I would tend not to suspect the drive size as the only
issue here…

Thanks for any help anyone can offer,

–dave

OK, that gets me past the hang following the EIDE scan. But then I hit the
next problem (“second scenario,” below); this time I got a verbose log:

Generating helpviewer search database.
[…]
Starting /pkgs/base/qnx/os/drivers-2.1.2/x86/sbin/devc-con -n4
Starting
/pkgs/base/qnx/os/core-2.1.2/x86/sbin/fs-pkg -a/pkgs/base/safe-config/etc/sy
stem/package/packages
[8] fs-pkg built: Jun 22 2001 04:30:34 dPackage config file
[/etc/system/package/packages] s
Shutdown[0,0] S/C/F=11/1/11 C/D=ff80e517/ff841050 state(c0)= now lock
[0]PID-TID=6-5? P/T FL=00023010/84020002 “/proc/boot/devb-eide”
[0]ACTIVE-PID=1 PF=00019001 “/daily/x86/boot/sys/procnto”

[This is followed by an x86 context dump.]

Over,
–dave


“Hardware Support Account” <hw@qnx.com> wrote in message
news:9r4dvt$dt2$2@nntp.qnx.com

Hi Dave,

What happens when you disconnect the secondary chain all together?

Thanks

E.


Dave Jacobs <> jacobs-dave@home.com> > wrote:
The WDC 60GB hdd is the primary master, jumpered as “single”, with no
primary slave. The secondary master is a CD-RW drive and the secondary
slave
is a DVD-ROM.

Thanks,
–dave


“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9r1d6o$fn4$> 4@nntp.qnx.com> …
Hi Dave,

What is the setup of your ATA/EIDE devices? What is set to master
and what is set to slave?

Thanks

Erick.


Dave Jacobs <> jacobs-dave@home.com> > wrote:
I’m a QNX newbie trying to install the small Windows platform
(qnxrtp610.exe) on an eMachines etower 266 box. The Setup
installation
goes
fine (I select the default 600MB working set size). Upon reboot, I
choose
QNX (DMA disabled), and select the verbose boot option (F6). The boot
sequence always hangs during the EIDE scan:

Range check failed - Dev 571 - Vend 1106 - Class 1018a - Addr ffa0 -
Size 10
Trying to detect EIDE
[…]
Detected EIDE. Scanning for devices.
Starting devb-eide blk auto=partition dos exec=all
Path=0 - EIDE
target=0 lun=0 Direct Access(0) - WDC WD600BB-00CF Rev:
Path=1 - EIDE
target=0 lun=0 CD-ROM(5) - LITE-ON LTR-12101B Rev:
LS3B
target=1 lun=0 CD-ROM(5) - MT1316B BDV212B Rev:
0.36
simq_timer: building abort ccb
simq_timer: building reset ccb
[long delay here…]
simq_timer: building abort ccb
simq_timer: building reset ccb

Finally, I have to force a reset and reboot.

In a second scenario, I have a slightly different failure symptom (no
verbose mode this time, sorry).
Following the reboot with DMA disabled, the EIDE scan completes, then
I
see:

Generating helpviewer search database.
/etc/system/sysinit[81]: getconf: No such file or directory

Does either of these suggest to you what might be going wrong here?
The
hdd
is a Western Digital 60MB drive, and I must admit there is a problem
with my
AMIBIOS recognizing its full size – when I select the BIOS’
Autodetect,
it
under-detects the size of the drive; but under Win98, this does not
prevent the drive’s actual size from being correctly determined as
60MB.

So I tried this same procedure on a smaller drive (2.1GB), and got
very
similar results. I would tend not to suspect the drive size as the
only
issue here…

Thanks for any help anyone can offer,

–dave
\

Hmmm, gonna point the OS guys to this and see what that dump is about.

Erick.


Dave Jacobs <jacobs-dave@home.com> wrote:

OK, that gets me past the hang following the EIDE scan. But then I hit the
next problem (“second scenario,” below); this time I got a verbose log:

Generating helpviewer search database.
[…]
Starting /pkgs/base/qnx/os/drivers-2.1.2/x86/sbin/devc-con -n4
Starting
/pkgs/base/qnx/os/core-2.1.2/x86/sbin/fs-pkg -a/pkgs/base/safe-config/etc/sy
stem/package/packages
[8] fs-pkg built: Jun 22 2001 04:30:34 dPackage config file
[/etc/system/package/packages] s
Shutdown[0,0] S/C/F=11/1/11 C/D=ff80e517/ff841050 state(c0)= now lock
[0]PID-TID=6-5? P/T FL=00023010/84020002 “/proc/boot/devb-eide”
[0]ACTIVE-PID=1 PF=00019001 “/daily/x86/boot/sys/procnto”

[This is followed by an x86 context dump.]

Over,
–dave



“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9r4dvt$dt2$> 2@nntp.qnx.com> …
Hi Dave,

What happens when you disconnect the secondary chain all together?

Thanks

E.


Dave Jacobs <> jacobs-dave@home.com> > wrote:
The WDC 60GB hdd is the primary master, jumpered as “single”, with no
primary slave. The secondary master is a CD-RW drive and the secondary
slave
is a DVD-ROM.

Thanks,
–dave


“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9r1d6o$fn4$> 4@nntp.qnx.com> …
Hi Dave,

What is the setup of your ATA/EIDE devices? What is set to master
and what is set to slave?

Thanks

Erick.


Dave Jacobs <> jacobs-dave@home.com> > wrote:
I’m a QNX newbie trying to install the small Windows platform
(qnxrtp610.exe) on an eMachines etower 266 box. The Setup
installation
goes
fine (I select the default 600MB working set size). Upon reboot, I
choose
QNX (DMA disabled), and select the verbose boot option (F6). The boot
sequence always hangs during the EIDE scan:

Range check failed - Dev 571 - Vend 1106 - Class 1018a - Addr ffa0 -
Size 10
Trying to detect EIDE
[…]
Detected EIDE. Scanning for devices.
Starting devb-eide blk auto=partition dos exec=all
Path=0 - EIDE
target=0 lun=0 Direct Access(0) - WDC WD600BB-00CF Rev:
Path=1 - EIDE
target=0 lun=0 CD-ROM(5) - LITE-ON LTR-12101B Rev:
LS3B
target=1 lun=0 CD-ROM(5) - MT1316B BDV212B Rev:
0.36
simq_timer: building abort ccb
simq_timer: building reset ccb
[long delay here…]
simq_timer: building abort ccb
simq_timer: building reset ccb

Finally, I have to force a reset and reboot.

In a second scenario, I have a slightly different failure symptom (no
verbose mode this time, sorry).
Following the reboot with DMA disabled, the EIDE scan completes, then
I
see:

Generating helpviewer search database.
/etc/system/sysinit[81]: getconf: No such file or directory

Does either of these suggest to you what might be going wrong here?
The
hdd
is a Western Digital 60MB drive, and I must admit there is a problem
with my
AMIBIOS recognizing its full size – when I select the BIOS’
Autodetect,
it
under-detects the size of the drive; but under Win98, this does not
prevent the drive’s actual size from being correctly determined as
60MB.

So I tried this same procedure on a smaller drive (2.1GB), and got
very
similar results. I would tend not to suspect the drive size as the
only
issue here…

Thanks for any help anyone can offer,

–dave
\

Do you get the Proc fault if you boot from the 2.1GB drive?

Also have you tried installing QNX onto its own partition?

Erick.


Dave Jacobs <jacobs-dave@home.com> wrote:

OK, that gets me past the hang following the EIDE scan. But then I hit the
next problem (“second scenario,” below); this time I got a verbose log:

Generating helpviewer search database.
[…]
Starting /pkgs/base/qnx/os/drivers-2.1.2/x86/sbin/devc-con -n4
Starting
/pkgs/base/qnx/os/core-2.1.2/x86/sbin/fs-pkg -a/pkgs/base/safe-config/etc/sy
stem/package/packages
[8] fs-pkg built: Jun 22 2001 04:30:34 dPackage config file
[/etc/system/package/packages] s
Shutdown[0,0] S/C/F=11/1/11 C/D=ff80e517/ff841050 state(c0)= now lock
[0]PID-TID=6-5? P/T FL=00023010/84020002 “/proc/boot/devb-eide”
[0]ACTIVE-PID=1 PF=00019001 “/daily/x86/boot/sys/procnto”

[This is followed by an x86 context dump.]

Over,
–dave



“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9r4dvt$dt2$> 2@nntp.qnx.com> …
Hi Dave,

What happens when you disconnect the secondary chain all together?

Thanks

E.


Dave Jacobs <> jacobs-dave@home.com> > wrote:
The WDC 60GB hdd is the primary master, jumpered as “single”, with no
primary slave. The secondary master is a CD-RW drive and the secondary
slave
is a DVD-ROM.

Thanks,
–dave


“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9r1d6o$fn4$> 4@nntp.qnx.com> …
Hi Dave,

What is the setup of your ATA/EIDE devices? What is set to master
and what is set to slave?

Thanks

Erick.


Dave Jacobs <> jacobs-dave@home.com> > wrote:
I’m a QNX newbie trying to install the small Windows platform
(qnxrtp610.exe) on an eMachines etower 266 box. The Setup
installation
goes
fine (I select the default 600MB working set size). Upon reboot, I
choose
QNX (DMA disabled), and select the verbose boot option (F6). The boot
sequence always hangs during the EIDE scan:

Range check failed - Dev 571 - Vend 1106 - Class 1018a - Addr ffa0 -
Size 10
Trying to detect EIDE
[…]
Detected EIDE. Scanning for devices.
Starting devb-eide blk auto=partition dos exec=all
Path=0 - EIDE
target=0 lun=0 Direct Access(0) - WDC WD600BB-00CF Rev:
Path=1 - EIDE
target=0 lun=0 CD-ROM(5) - LITE-ON LTR-12101B Rev:
LS3B
target=1 lun=0 CD-ROM(5) - MT1316B BDV212B Rev:
0.36
simq_timer: building abort ccb
simq_timer: building reset ccb
[long delay here…]
simq_timer: building abort ccb
simq_timer: building reset ccb

Finally, I have to force a reset and reboot.

In a second scenario, I have a slightly different failure symptom (no
verbose mode this time, sorry).
Following the reboot with DMA disabled, the EIDE scan completes, then
I
see:

Generating helpviewer search database.
/etc/system/sysinit[81]: getconf: No such file or directory

Does either of these suggest to you what might be going wrong here?
The
hdd
is a Western Digital 60MB drive, and I must admit there is a problem
with my
AMIBIOS recognizing its full size – when I select the BIOS’
Autodetect,
it
under-detects the size of the drive; but under Win98, this does not
prevent the drive’s actual size from being correctly determined as
60MB.

So I tried this same procedure on a smaller drive (2.1GB), and got
very
similar results. I would tend not to suspect the drive size as the
only
issue here…

Thanks for any help anyone can offer,

–dave
\

Do you get the Proc fault if you boot from the 2.1GB drive?

Sorry, I didn’t take notes on that attempt. But it did fail, with one of
the two scenarios below; I just don’t remember which one. In any case,
doing the Windows-file install on that drive as it stands now isn’t a viable
“real” environment anyway, as there’s only 500MB free on the drive. It was
just an experiment to rule out the drive-size issue as a suspect.

Also have you tried installing QNX onto its own partition?

No, I’d been hoping to avoid that approach – I just wanted to get something
up and running quickly. I don’t really have a “spare” drive to use, and
didn’t want to clobber the 2.1GB drive altogether. But I’m getting closer to
abandoning the current contents of that drive and doing a
dedicated-partition install…

–dave


“Hardware Support Account” <hw@qnx.com> wrote in message
news:9r71vq$9fv$5@nntp.qnx.com

Do you get the Proc fault if you boot from the 2.1GB drive?

Also have you tried installing QNX onto its own partition?

Erick.


Dave Jacobs <> jacobs-dave@home.com> > wrote:
OK, that gets me past the hang following the EIDE scan. But then I hit
the
next problem (“second scenario,” below); this time I got a verbose log:

Generating helpviewer search database.
[…]
Starting /pkgs/base/qnx/os/drivers-2.1.2/x86/sbin/devc-con -n4
Starting

/pkgs/base/qnx/os/core-2.1.2/x86/sbin/fs-pkg -a/pkgs/base/safe-config/etc/sy
stem/package/packages
[8] fs-pkg built: Jun 22 2001 04:30:34 dPackage config file
[/etc/system/package/packages] s
Shutdown[0,0] S/C/F=11/1/11 C/D=ff80e517/ff841050 state(c0)= now lock
[0]PID-TID=6-5? P/T FL=00023010/84020002 “/proc/boot/devb-eide”
[0]ACTIVE-PID=1 PF=00019001 “/daily/x86/boot/sys/procnto”

[This is followed by an x86 context dump.]

Over,
–dave


“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9r4dvt$dt2$> 2@nntp.qnx.com> …
Hi Dave,

What happens when you disconnect the secondary chain all together?

Thanks

E.


Dave Jacobs <> jacobs-dave@home.com> > wrote:
The WDC 60GB hdd is the primary master, jumpered as “single”, with no
primary slave. The secondary master is a CD-RW drive and the
secondary
slave
is a DVD-ROM.

Thanks,
–dave


“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9r1d6o$fn4$> 4@nntp.qnx.com> …
Hi Dave,

What is the setup of your ATA/EIDE devices? What is set to master
and what is set to slave?

Thanks

Erick.


Dave Jacobs <> jacobs-dave@home.com> > wrote:
I’m a QNX newbie trying to install the small Windows platform
(qnxrtp610.exe) on an eMachines etower 266 box. The Setup
installation
goes
fine (I select the default 600MB working set size). Upon reboot, I
choose
QNX (DMA disabled), and select the verbose boot option (F6). The
boot
sequence always hangs during the EIDE scan:

Range check failed - Dev 571 - Vend 1106 - Class 1018a - Addr
ffa0 -
Size 10
Trying to detect EIDE
[…]
Detected EIDE. Scanning for devices.
Starting devb-eide blk auto=partition dos exec=all
Path=0 - EIDE
target=0 lun=0 Direct Access(0) - WDC WD600BB-00CF Rev:
Path=1 - EIDE
target=0 lun=0 CD-ROM(5) - LITE-ON LTR-12101B
Rev:
LS3B
target=1 lun=0 CD-ROM(5) - MT1316B BDV212B
Rev:
0.36
simq_timer: building abort ccb
simq_timer: building reset ccb
[long delay here…]
simq_timer: building abort ccb
simq_timer: building reset ccb

Finally, I have to force a reset and reboot.

In a second scenario, I have a slightly different failure symptom
(no
verbose mode this time, sorry).
Following the reboot with DMA disabled, the EIDE scan completes,
then
I
see:

Generating helpviewer search database.
/etc/system/sysinit[81]: getconf: No such file or directory

Does either of these suggest to you what might be going wrong
here?
The
hdd
is a Western Digital 60MB drive, and I must admit there is a
problem
with my
AMIBIOS recognizing its full size – when I select the BIOS’
Autodetect,
it
under-detects the size of the drive; but under Win98, this does
not
prevent the drive’s actual size from being correctly determined as
60MB.

So I tried this same procedure on a smaller drive (2.1GB), and got
very
similar results. I would tend not to suspect the drive size as
the
only
issue here…

Thanks for any help anyone can offer,

–dave


\

[…] I’m getting closer to
abandoning the current contents of that drive and doing a
dedicated-partition install…

Of course, for that, I’ll need a working CD-ROM drive, which means debugging
the EIDE scan problem… :confused:

Is it, say, something as simple as, “QNX doesn’t handle DVD-ROM nor
CD-writer drives”? I have one of each of those, and no “plain vanilla”
CD-ROM drive. That might avoid some wasted debugging effort…

–dave


“Dave Jacobs” <jacobs-dave@home.com> wrote in message
news:9r7flv$ibl$1@inn.qnx.com

Do you get the Proc fault if you boot from the 2.1GB drive?

Sorry, I didn’t take notes on that attempt. But it did fail, with one of
the two scenarios below; I just don’t remember which one. In any case,
doing the Windows-file install on that drive as it stands now isn’t a
viable
“real” environment anyway, as there’s only 500MB free on the drive. It
was
just an experiment to rule out the drive-size issue as a suspect.

Also have you tried installing QNX onto its own partition?

No, I’d been hoping to avoid that approach – I just wanted to get
something
up and running quickly. I don’t really have a “spare” drive to use, and
didn’t want to clobber the 2.1GB drive altogether. But I’m getting closer
to
abandoning the current contents of that drive and doing a
dedicated-partition install…

–dave


“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9r71vq$9fv$> 5@nntp.qnx.com> …
Do you get the Proc fault if you boot from the 2.1GB drive?

Also have you tried installing QNX onto its own partition?

Erick.


Dave Jacobs <> jacobs-dave@home.com> > wrote:
OK, that gets me past the hang following the EIDE scan. But then I
hit
the
next problem (“second scenario,” below); this time I got a verbose
log:

Generating helpviewer search database.
[…]
Starting /pkgs/base/qnx/os/drivers-2.1.2/x86/sbin/devc-con -n4
Starting


/pkgs/base/qnx/os/core-2.1.2/x86/sbin/fs-pkg -a/pkgs/base/safe-config/etc/sy
stem/package/packages
[8] fs-pkg built: Jun 22 2001 04:30:34 dPackage config file
[/etc/system/package/packages] s
Shutdown[0,0] S/C/F=11/1/11 C/D=ff80e517/ff841050 state(c0)= now lock
[0]PID-TID=6-5? P/T FL=00023010/84020002 “/proc/boot/devb-eide”
[0]ACTIVE-PID=1 PF=00019001 “/daily/x86/boot/sys/procnto”

[This is followed by an x86 context dump.]

Over,
–dave


“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9r4dvt$dt2$> 2@nntp.qnx.com> …
Hi Dave,

What happens when you disconnect the secondary chain all together?

Thanks

E.


Dave Jacobs <> jacobs-dave@home.com> > wrote:
The WDC 60GB hdd is the primary master, jumpered as “single”, with
no
primary slave. The secondary master is a CD-RW drive and the
secondary
slave
is a DVD-ROM.

Thanks,
–dave


“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9r1d6o$fn4$> 4@nntp.qnx.com> …
Hi Dave,

What is the setup of your ATA/EIDE devices? What is set to master
and what is set to slave?

Thanks

Erick.


Dave Jacobs <> jacobs-dave@home.com> > wrote:
I’m a QNX newbie trying to install the small Windows platform
(qnxrtp610.exe) on an eMachines etower 266 box. The Setup
installation
goes
fine (I select the default 600MB working set size). Upon reboot,
I
choose
QNX (DMA disabled), and select the verbose boot option (F6). The
boot
sequence always hangs during the EIDE scan:

Range check failed - Dev 571 - Vend 1106 - Class 1018a - Addr
ffa0 -
Size 10
Trying to detect EIDE
[…]
Detected EIDE. Scanning for devices.
Starting devb-eide blk auto=partition dos exec=all
Path=0 - EIDE
target=0 lun=0 Direct Access(0) - WDC WD600BB-00CF
Rev:
Path=1 - EIDE
target=0 lun=0 CD-ROM(5) - LITE-ON LTR-12101B
Rev:
LS3B
target=1 lun=0 CD-ROM(5) - MT1316B BDV212B
Rev:
0.36
simq_timer: building abort ccb
simq_timer: building reset ccb
[long delay here…]
simq_timer: building abort ccb
simq_timer: building reset ccb

Finally, I have to force a reset and reboot.

In a second scenario, I have a slightly different failure
symptom
(no
verbose mode this time, sorry).
Following the reboot with DMA disabled, the EIDE scan completes,
then
I
see:

Generating helpviewer search database.
/etc/system/sysinit[81]: getconf: No such file or directory

Does either of these suggest to you what might be going wrong
here?
The
hdd
is a Western Digital 60MB drive, and I must admit there is a
problem
with my
AMIBIOS recognizing its full size – when I select the BIOS’
Autodetect,
it
under-detects the size of the drive; but under Win98, this does
not
prevent the drive’s actual size from being correctly determined
as
60MB.

So I tried this same procedure on a smaller drive (2.1GB), and
got
very
similar results. I would tend not to suspect the drive size as
the
only
issue here…

Thanks for any help anyone can offer,

–dave




\

Of course, for that, I’ll need a working CD-ROM drive, which means
debugging
the EIDE scan problem… :confused:

OK, done that. It was the DVD drive it didn’t like. Removing it, but
leaving the CD-writer connected, got me past the EIDE scan hang. Which
leaves us at the “No such file…” error in sysinit[81]:

Generating helpviewer search database.
/etc/system/sysinit[81]: getconf: No such file or directory

Any ideas on this one? It sounds worryingly like either a missing or a
corrupted file(system)…?

Meanwhile, I’m gonna go try the big ISO install (qnxrtp.iso) from CD onto
the 2.1GB drive for a change of pace…

Thanks,
–dave


“Dave Jacobs” <jacobs-dave@home.com> wrote in message
news:9r7lrf$lj9$1@inn.qnx.com

[…] I’m getting closer to
abandoning the current contents of that drive and doing a
dedicated-partition install…

Of course, for that, I’ll need a working CD-ROM drive, which means
debugging
the EIDE scan problem… :confused:

Is it, say, something as simple as, “QNX doesn’t handle DVD-ROM nor
CD-writer drives”? I have one of each of those, and no “plain vanilla”
CD-ROM drive. That might avoid some wasted debugging effort…

–dave


“Dave Jacobs” <> jacobs-dave@home.com> > wrote in message
news:9r7flv$ibl$> 1@inn.qnx.com> …
Do you get the Proc fault if you boot from the 2.1GB drive?

Sorry, I didn’t take notes on that attempt. But it did fail, with one
of
the two scenarios below; I just don’t remember which one. In any case,
doing the Windows-file install on that drive as it stands now isn’t a
viable
“real” environment anyway, as there’s only 500MB free on the drive. It
was
just an experiment to rule out the drive-size issue as a suspect.

Also have you tried installing QNX onto its own partition?

No, I’d been hoping to avoid that approach – I just wanted to get
something
up and running quickly. I don’t really have a “spare” drive to use, and
didn’t want to clobber the 2.1GB drive altogether. But I’m getting
closer
to
abandoning the current contents of that drive and doing a
dedicated-partition install…

–dave


“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9r71vq$9fv$> 5@nntp.qnx.com> …
Do you get the Proc fault if you boot from the 2.1GB drive?

Also have you tried installing QNX onto its own partition?

Erick.


Dave Jacobs <> jacobs-dave@home.com> > wrote:
OK, that gets me past the hang following the EIDE scan. But then I
hit
the
next problem (“second scenario,” below); this time I got a verbose
log:

Generating helpviewer search database.
[…]
Starting /pkgs/base/qnx/os/drivers-2.1.2/x86/sbin/devc-con -n4
Starting



/pkgs/base/qnx/os/core-2.1.2/x86/sbin/fs-pkg -a/pkgs/base/safe-config/etc/sy
stem/package/packages
[8] fs-pkg built: Jun 22 2001 04:30:34 dPackage config file
[/etc/system/package/packages] s
Shutdown[0,0] S/C/F=11/1/11 C/D=ff80e517/ff841050 state(c0)= now
lock
[0]PID-TID=6-5? P/T FL=00023010/84020002 “/proc/boot/devb-eide”
[0]ACTIVE-PID=1 PF=00019001 “/daily/x86/boot/sys/procnto”

[This is followed by an x86 context dump.]

Over,
–dave


“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9r4dvt$dt2$> 2@nntp.qnx.com> …
Hi Dave,

What happens when you disconnect the secondary chain all together?

Thanks

E.


Dave Jacobs <> jacobs-dave@home.com> > wrote:
The WDC 60GB hdd is the primary master, jumpered as “single”,
with
no
primary slave. The secondary master is a CD-RW drive and the
secondary
slave
is a DVD-ROM.

Thanks,
–dave


“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9r1d6o$fn4$> 4@nntp.qnx.com> …
Hi Dave,

What is the setup of your ATA/EIDE devices? What is set to
master
and what is set to slave?

Thanks

Erick.


Dave Jacobs <> jacobs-dave@home.com> > wrote:
I’m a QNX newbie trying to install the small Windows platform
(qnxrtp610.exe) on an eMachines etower 266 box. The Setup
installation
goes
fine (I select the default 600MB working set size). Upon
reboot,
I
choose
QNX (DMA disabled), and select the verbose boot option (F6).
The
boot
sequence always hangs during the EIDE scan:

Range check failed - Dev 571 - Vend 1106 - Class 1018a - Addr
ffa0 -
Size 10
Trying to detect EIDE
[…]
Detected EIDE. Scanning for devices.
Starting devb-eide blk auto=partition dos exec=all
Path=0 - EIDE
target=0 lun=0 Direct Access(0) - WDC WD600BB-00CF
Rev:
Path=1 - EIDE
target=0 lun=0 CD-ROM(5) - LITE-ON LTR-12101B
Rev:
LS3B
target=1 lun=0 CD-ROM(5) - MT1316B BDV212B
Rev:
0.36
simq_timer: building abort ccb
simq_timer: building reset ccb
[long delay here…]
simq_timer: building abort ccb
simq_timer: building reset ccb

Finally, I have to force a reset and reboot.

In a second scenario, I have a slightly different failure
symptom
(no
verbose mode this time, sorry).
Following the reboot with DMA disabled, the EIDE scan
completes,
then
I
see:

Generating helpviewer search database.
/etc/system/sysinit[81]: getconf: No such file or directory

Does either of these suggest to you what might be going wrong
here?
The
hdd
is a Western Digital 60MB drive, and I must admit there is a
problem
with my
AMIBIOS recognizing its full size – when I select the BIOS’
Autodetect,
it
under-detects the size of the drive; but under Win98, this
does
not
prevent the drive’s actual size from being correctly
determined
as
60MB.

So I tried this same procedure on a smaller drive (2.1GB), and
got
very
similar results. I would tend not to suspect the drive size
as
the
only
issue here…

Thanks for any help anyone can offer,

–dave






\

Damn. I booted from the qnxrtp.iso CD, gave it the entire 2.1GB for a new
QNX partition, installation onto the disk appeared to go well, and it
prompted me to reboot (from disk). It got past the EIDE scan just fine, then
gave me exactly the same “sysinit[81]” error as before:

[…]
Creating a 128M swapfile “/.swapfile”. You must have 256M free to create it.
Generating helpviewer search database.
/etc/system/sysinit[81]: getconf: No such file or directory
[hangs here]

So I have the same missing file error, whether I boot from the qnxrtp610.exe
install or the qnxrtp.iso CD install. Help.

Thanks,
–dave


“Dave Jacobs” <jacobs-dave@home.com> wrote in message
news:9r7nu4$mqc$1@inn.qnx.com

Of course, for that, I’ll need a working CD-ROM drive, which means
debugging
the EIDE scan problem… :confused:

OK, done that. It was the DVD drive it didn’t like. Removing it, but
leaving the CD-writer connected, got me past the EIDE scan hang. Which
leaves us at the “No such file…” error in sysinit[81]:

Generating helpviewer search database.
/etc/system/sysinit[81]: getconf: No such file or directory

Any ideas on this one? It sounds worryingly like either a missing or a
corrupted file(system)…?

Meanwhile, I’m gonna go try the big ISO install (qnxrtp.iso) from CD onto
the 2.1GB drive for a change of pace…

Thanks,
–dave


“Dave Jacobs” <> jacobs-dave@home.com> > wrote in message
news:9r7lrf$lj9$> 1@inn.qnx.com> …
[…] I’m getting closer to
abandoning the current contents of that drive and doing a
dedicated-partition install…

Of course, for that, I’ll need a working CD-ROM drive, which means
debugging
the EIDE scan problem… :confused:

Is it, say, something as simple as, “QNX doesn’t handle DVD-ROM nor
CD-writer drives”? I have one of each of those, and no “plain vanilla”
CD-ROM drive. That might avoid some wasted debugging effort…

–dave


“Dave Jacobs” <> jacobs-dave@home.com> > wrote in message
news:9r7flv$ibl$> 1@inn.qnx.com> …
Do you get the Proc fault if you boot from the 2.1GB drive?

Sorry, I didn’t take notes on that attempt. But it did fail, with one
of
the two scenarios below; I just don’t remember which one. In any
case,
doing the Windows-file install on that drive as it stands now isn’t a
viable
“real” environment anyway, as there’s only 500MB free on the drive.
It
was
just an experiment to rule out the drive-size issue as a suspect.

Also have you tried installing QNX onto its own partition?

No, I’d been hoping to avoid that approach – I just wanted to get
something
up and running quickly. I don’t really have a “spare” drive to use,
and
didn’t want to clobber the 2.1GB drive altogether. But I’m getting
closer
to
abandoning the current contents of that drive and doing a
dedicated-partition install…

–dave


“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9r71vq$9fv$> 5@nntp.qnx.com> …
Do you get the Proc fault if you boot from the 2.1GB drive?

Also have you tried installing QNX onto its own partition?

Erick.


Dave Jacobs <> jacobs-dave@home.com> > wrote:
OK, that gets me past the hang following the EIDE scan. But then
I
hit
the
next problem (“second scenario,” below); this time I got a verbose
log:

Generating helpviewer search database.
[…]
Starting /pkgs/base/qnx/os/drivers-2.1.2/x86/sbin/devc-con -n4
Starting




/pkgs/base/qnx/os/core-2.1.2/x86/sbin/fs-pkg -a/pkgs/base/safe-config/etc/sy
stem/package/packages
[8] fs-pkg built: Jun 22 2001 04:30:34 dPackage config file
[/etc/system/package/packages] s
Shutdown[0,0] S/C/F=11/1/11 C/D=ff80e517/ff841050 state(c0)= now
lock
[0]PID-TID=6-5? P/T FL=00023010/84020002 “/proc/boot/devb-eide”
[0]ACTIVE-PID=1 PF=00019001 “/daily/x86/boot/sys/procnto”

[This is followed by an x86 context dump.]

Over,
–dave


“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9r4dvt$dt2$> 2@nntp.qnx.com> …
Hi Dave,

What happens when you disconnect the secondary chain all
together?

Thanks

E.


Dave Jacobs <> jacobs-dave@home.com> > wrote:
The WDC 60GB hdd is the primary master, jumpered as “single”,
with
no
primary slave. The secondary master is a CD-RW drive and the
secondary
slave
is a DVD-ROM.

Thanks,
–dave


“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9r1d6o$fn4$> 4@nntp.qnx.com> …
Hi Dave,

What is the setup of your ATA/EIDE devices? What is set to
master
and what is set to slave?

Thanks

Erick.


Dave Jacobs <> jacobs-dave@home.com> > wrote:
I’m a QNX newbie trying to install the small Windows
platform
(qnxrtp610.exe) on an eMachines etower 266 box. The Setup
installation
goes
fine (I select the default 600MB working set size). Upon
reboot,
I
choose
QNX (DMA disabled), and select the verbose boot option (F6).
The
boot
sequence always hangs during the EIDE scan:

Range check failed - Dev 571 - Vend 1106 - Class 1018a -
Addr
ffa0 -
Size 10
Trying to detect EIDE
[…]
Detected EIDE. Scanning for devices.
Starting devb-eide blk auto=partition dos exec=all
Path=0 - EIDE
target=0 lun=0 Direct Access(0) - WDC WD600BB-00CF
Rev:
Path=1 - EIDE
target=0 lun=0 CD-ROM(5) - LITE-ON LTR-12101B
Rev:
LS3B
target=1 lun=0 CD-ROM(5) - MT1316B BDV212B
Rev:
0.36
simq_timer: building abort ccb
simq_timer: building reset ccb
[long delay here…]
simq_timer: building abort ccb
simq_timer: building reset ccb

Finally, I have to force a reset and reboot.

In a second scenario, I have a slightly different failure
symptom
(no
verbose mode this time, sorry).
Following the reboot with DMA disabled, the EIDE scan
completes,
then
I
see:

Generating helpviewer search database.
/etc/system/sysinit[81]: getconf: No such file or directory

Does either of these suggest to you what might be going
wrong
here?
The
hdd
is a Western Digital 60MB drive, and I must admit there is a
problem
with my
AMIBIOS recognizing its full size – when I select the BIOS’
Autodetect,
it
under-detects the size of the drive; but under Win98, this
does
not
prevent the drive’s actual size from being correctly
determined
as
60MB.

So I tried this same procedure on a smaller drive (2.1GB),
and
got
very
similar results. I would tend not to suspect the drive size
as
the
only
issue here…

Thanks for any help anyone can offer,

–dave








\

Umm…so, do you have anything to recommend for getting around this “missing
getconf binary” issue?
I’m dead in the water with installing 6.1 at this point. Help?!?

Thanks,
–dave


“Dave Jacobs” <jacobs-dave@home.com> wrote in message
news:9r7r23$od8$1@inn.qnx.com

Damn. I booted from the qnxrtp.iso CD, gave it the entire 2.1GB for a new
QNX partition, installation onto the disk appeared to go well, and it
prompted me to reboot (from disk). It got past the EIDE scan just fine,
then
gave me exactly the same “sysinit[81]” error as before:

[…]
Creating a 128M swapfile “/.swapfile”. You must have 256M free to create
it.
Generating helpviewer search database.
/etc/system/sysinit[81]: getconf: No such file or directory
[hangs here]

So I have the same missing file error, whether I boot from the
qnxrtp610.exe
install or the qnxrtp.iso CD install. Help.

Thanks,
–dave


“Dave Jacobs” <> jacobs-dave@home.com> > wrote in message
news:9r7nu4$mqc$> 1@inn.qnx.com> …
Of course, for that, I’ll need a working CD-ROM drive, which means
debugging
the EIDE scan problem… :confused:

OK, done that. It was the DVD drive it didn’t like. Removing it, but
leaving the CD-writer connected, got me past the EIDE scan hang. Which
leaves us at the “No such file…” error in sysinit[81]:

Generating helpviewer search database.
/etc/system/sysinit[81]: getconf: No such file or directory

Any ideas on this one? It sounds worryingly like either a missing or a
corrupted file(system)…?

Meanwhile, I’m gonna go try the big ISO install (qnxrtp.iso) from CD
onto
the 2.1GB drive for a change of pace…

Thanks,
–dave


“Dave Jacobs” <> jacobs-dave@home.com> > wrote in message
news:9r7lrf$lj9$> 1@inn.qnx.com> …
[…] I’m getting closer to
abandoning the current contents of that drive and doing a
dedicated-partition install…

Of course, for that, I’ll need a working CD-ROM drive, which means
debugging
the EIDE scan problem… :confused:

Is it, say, something as simple as, “QNX doesn’t handle DVD-ROM nor
CD-writer drives”? I have one of each of those, and no “plain vanilla”
CD-ROM drive. That might avoid some wasted debugging effort…

–dave


“Dave Jacobs” <> jacobs-dave@home.com> > wrote in message
news:9r7flv$ibl$> 1@inn.qnx.com> …
Do you get the Proc fault if you boot from the 2.1GB drive?

Sorry, I didn’t take notes on that attempt. But it did fail, with
one
of
the two scenarios below; I just don’t remember which one. In any
case,
doing the Windows-file install on that drive as it stands now isn’t
a
viable
“real” environment anyway, as there’s only 500MB free on the drive.
It
was
just an experiment to rule out the drive-size issue as a suspect.

Also have you tried installing QNX onto its own partition?

No, I’d been hoping to avoid that approach – I just wanted to get
something
up and running quickly. I don’t really have a “spare” drive to use,
and
didn’t want to clobber the 2.1GB drive altogether. But I’m getting
closer
to
abandoning the current contents of that drive and doing a
dedicated-partition install…

–dave


“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9r71vq$9fv$> 5@nntp.qnx.com> …
Do you get the Proc fault if you boot from the 2.1GB drive?

Also have you tried installing QNX onto its own partition?

Erick.


Dave Jacobs <> jacobs-dave@home.com> > wrote:
OK, that gets me past the hang following the EIDE scan. But
then
I
hit
the
next problem (“second scenario,” below); this time I got a
verbose
log:

Generating helpviewer search database.
[…]
Starting /pkgs/base/qnx/os/drivers-2.1.2/x86/sbin/devc-con -n4
Starting





/pkgs/base/qnx/os/core-2.1.2/x86/sbin/fs-pkg -a/pkgs/base/safe-config/etc/sy
stem/package/packages
[8] fs-pkg built: Jun 22 2001 04:30:34 dPackage config file
[/etc/system/package/packages] s
Shutdown[0,0] S/C/F=11/1/11 C/D=ff80e517/ff841050 state(c0)= now
lock
[0]PID-TID=6-5? P/T FL=00023010/84020002 “/proc/boot/devb-eide”
[0]ACTIVE-PID=1 PF=00019001 “/daily/x86/boot/sys/procnto”

[This is followed by an x86 context dump.]

Over,
–dave


“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9r4dvt$dt2$> 2@nntp.qnx.com> …
Hi Dave,

What happens when you disconnect the secondary chain all
together?

Thanks

E.


Dave Jacobs <> jacobs-dave@home.com> > wrote:
The WDC 60GB hdd is the primary master, jumpered as “single”,
with
no
primary slave. The secondary master is a CD-RW drive and the
secondary
slave
is a DVD-ROM.

Thanks,
–dave


“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9r1d6o$fn4$> 4@nntp.qnx.com> …
Hi Dave,

What is the setup of your ATA/EIDE devices? What is set to
master
and what is set to slave?

Thanks

Erick.


Dave Jacobs <> jacobs-dave@home.com> > wrote:
I’m a QNX newbie trying to install the small Windows
platform
(qnxrtp610.exe) on an eMachines etower 266 box. The Setup
installation
goes
fine (I select the default 600MB working set size). Upon
reboot,
I
choose
QNX (DMA disabled), and select the verbose boot option
(F6).
The
boot
sequence always hangs during the EIDE scan:

Range check failed - Dev 571 - Vend 1106 - Class 1018a -
Addr
ffa0 -
Size 10
Trying to detect EIDE
[…]
Detected EIDE. Scanning for devices.
Starting devb-eide blk auto=partition dos exec=all
Path=0 - EIDE
target=0 lun=0 Direct Access(0) - WDC WD600BB-00CF
Rev:
Path=1 - EIDE
target=0 lun=0 CD-ROM(5) - LITE-ON LTR-12101B
Rev:
LS3B
target=1 lun=0 CD-ROM(5) - MT1316B BDV212B
Rev:
0.36
simq_timer: building abort ccb
simq_timer: building reset ccb
[long delay here…]
simq_timer: building abort ccb
simq_timer: building reset ccb

Finally, I have to force a reset and reboot.

In a second scenario, I have a slightly different failure
symptom
(no
verbose mode this time, sorry).
Following the reboot with DMA disabled, the EIDE scan
completes,
then
I
see:

Generating helpviewer search database.
/etc/system/sysinit[81]: getconf: No such file or
directory

Does either of these suggest to you what might be going
wrong
here?
The
hdd
is a Western Digital 60MB drive, and I must admit there is
a
problem
with my
AMIBIOS recognizing its full size – when I select the
BIOS’
Autodetect,
it
under-detects the size of the drive; but under Win98, this
does
not
prevent the drive’s actual size from being correctly
determined
as
60MB.

So I tried this same procedure on a smaller drive (2.1GB),
and
got
very
similar results. I would tend not to suspect the drive
size
as
the
only
issue here…

Thanks for any help anyone can offer,

–dave










\

I corrected by Installing on a FAT 16 Partition of size 1.5, I partitioned
my drive into 1.5mb slices of FAT 16 and Succeeded
Dave Jacobs <jacobs-dave@home.com> wrote in message
news:9r7flv$ibl$1@inn.qnx.com

Do you get the Proc fault if you boot from the 2.1GB drive?

Sorry, I didn’t take notes on that attempt. But it did fail, with one of
the two scenarios below; I just don’t remember which one. In any case,
doing the Windows-file install on that drive as it stands now isn’t a
viable
“real” environment anyway, as there’s only 500MB free on the drive. It
was
just an experiment to rule out the drive-size issue as a suspect.

Also have you tried installing QNX onto its own partition?

No, I’d been hoping to avoid that approach – I just wanted to get
something
up and running quickly. I don’t really have a “spare” drive to use, and
didn’t want to clobber the 2.1GB drive altogether. But I’m getting closer
to
abandoning the current contents of that drive and doing a
dedicated-partition install…

–dave


“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9r71vq$9fv$> 5@nntp.qnx.com> …
Do you get the Proc fault if you boot from the 2.1GB drive?

Also have you tried installing QNX onto its own partition?

Erick.


Dave Jacobs <> jacobs-dave@home.com> > wrote:
OK, that gets me past the hang following the EIDE scan. But then I
hit
the
next problem (“second scenario,” below); this time I got a verbose
log:

Generating helpviewer search database.
[…]
Starting /pkgs/base/qnx/os/drivers-2.1.2/x86/sbin/devc-con -n4
Starting


/pkgs/base/qnx/os/core-2.1.2/x86/sbin/fs-pkg -a/pkgs/base/safe-config/etc/sy
stem/package/packages
[8] fs-pkg built: Jun 22 2001 04:30:34 dPackage config file
[/etc/system/package/packages] s
Shutdown[0,0] S/C/F=11/1/11 C/D=ff80e517/ff841050 state(c0)= now lock
[0]PID-TID=6-5? P/T FL=00023010/84020002 “/proc/boot/devb-eide”
[0]ACTIVE-PID=1 PF=00019001 “/daily/x86/boot/sys/procnto”

[This is followed by an x86 context dump.]

Over,
–dave


“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9r4dvt$dt2$> 2@nntp.qnx.com> …
Hi Dave,

What happens when you disconnect the secondary chain all together?

Thanks

E.


Dave Jacobs <> jacobs-dave@home.com> > wrote:
The WDC 60GB hdd is the primary master, jumpered as “single”, with
no
primary slave. The secondary master is a CD-RW drive and the
secondary
slave
is a DVD-ROM.

Thanks,
–dave


“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9r1d6o$fn4$> 4@nntp.qnx.com> …
Hi Dave,

What is the setup of your ATA/EIDE devices? What is set to master
and what is set to slave?

Thanks

Erick.


Dave Jacobs <> jacobs-dave@home.com> > wrote:
I’m a QNX newbie trying to install the small Windows platform
(qnxrtp610.exe) on an eMachines etower 266 box. The Setup
installation
goes
fine (I select the default 600MB working set size). Upon reboot,
I
choose
QNX (DMA disabled), and select the verbose boot option (F6). The
boot
sequence always hangs during the EIDE scan:

Range check failed - Dev 571 - Vend 1106 - Class 1018a - Addr
ffa0 -
Size 10
Trying to detect EIDE
[…]
Detected EIDE. Scanning for devices.
Starting devb-eide blk auto=partition dos exec=all
Path=0 - EIDE
target=0 lun=0 Direct Access(0) - WDC WD600BB-00CF
Rev:
Path=1 - EIDE
target=0 lun=0 CD-ROM(5) - LITE-ON LTR-12101B
Rev:
LS3B
target=1 lun=0 CD-ROM(5) - MT1316B BDV212B
Rev:
0.36
simq_timer: building abort ccb
simq_timer: building reset ccb
[long delay here…]
simq_timer: building abort ccb
simq_timer: building reset ccb

Finally, I have to force a reset and reboot.

In a second scenario, I have a slightly different failure
symptom
(no
verbose mode this time, sorry).
Following the reboot with DMA disabled, the EIDE scan completes,
then
I
see:

Generating helpviewer search database.
/etc/system/sysinit[81]: getconf: No such file or directory

Does either of these suggest to you what might be going wrong
here?
The
hdd
is a Western Digital 60MB drive, and I must admit there is a
problem
with my
AMIBIOS recognizing its full size – when I select the BIOS’
Autodetect,
it
under-detects the size of the drive; but under Win98, this does
not
prevent the drive’s actual size from being correctly determined
as
60MB.

So I tried this same procedure on a smaller drive (2.1GB), and
got
very
similar results. I would tend not to suspect the drive size as
the
only
issue here…

Thanks for any help anyone can offer,

–dave




\