Hi,
after EIDE was detected, QNX RTP can take up to 30 secs to recognize the IDE HD. In fact, on my system, it’s almost 20. That’s ok on first-time-boot, but why does it
have to detect it all again when I reboot? Why it just doesn’t take what it detected last time and goes on with it?
Malte
“thbl” <maltemundt@foni.net> wrote in message
news:1103_976969576@problemchild…
Hi,
after EIDE was detected, QNX RTP can take up to 30 secs to recognize the
IDE HD. In fact, on my system, it’s almost 20. That’s ok on first-time-boot,
but why does it
have to detect it all again when I reboot? Why it just doesn’t take what
it detected last time and goes on with it?
What if you add another device?
What if you move your HD from first to second controller?
Malte
“thbl” <maltemundt@foni.net> wrote in message
news:1103_976969576@problemchild…
That’s ok on first-time-boot, but why does it
have to detect it all again when I reboot? Why it just doesn’t take what
it detected last time and goes on with it?
Because you may have added another hard drive; which you most probably want
detected.
RtP is designed as a development workstation. It should be booted
infrequently (on the order of once a month). When you do reboot the reason
is more than likely that you have added new hardware. For your embedded
targets you should typically start devb-eide manually (you can do this with
RtP if you want, but if I were you I would consider whether the 30 sec once
a month - i.e. 6 min/year - is really that big a deal - I bet it would take
close to 6 minutes to change the boot script). If you hard-code your script
and then change your hardware more than once in a year you are in the
temporal red.
btw: once/month has been my average desktop development station reboot
interval with QNX 4 over the last 13 years (9 times out of 10 to add new
hardware - .8 times out of 10 for configuration purposes - .1 times out of
10 because an interrupt handler I was working on segv’d). My average laptop
development station reboot interval is once/day since I take it with me when
I leave work (and the 30 second boot time has never really bothered me -
even booting once/day).