On Thu, 14 Jun 2001 21:16:44 -0400, “Dave Grove”
<stevensgrove@igs.net> wrote:
It’s hard to guess what’s happened, but when something does
not work anymore (that worked), then either the software has changed
(a file is missing, a permission is insufficient, a config script is
wrong, a conflicting driver is added, etc.) or the hardware has
changed (a device has been replaced/attached, you name it), or both.
You did more than booting and shutting down during the weeks it
worked, didn’t you? And if you had to switch off the machine without
any chance of a normal shutdown, the filesystem might get corrupted.
If you don’t want to dwell upon, I would recommend a complete
reinstallation of the system. If you want to get back some files
first, and your “host” installation doesn’t work with your removable
either, try to press space when prompted at the boot time and select
F3 for example, that will hopefully boot into the text mode.
ako
Thanks for responding Alex:
Unfortunately I need to reiterate that I am an extreme beginner, and your
very knowledgeable explanation left me scratching my head (!).
I installed QNX on a removable, Win98 formatted harddrive, following the
install instructions on the QNX website. (I am beginning to learn with QNX
at college, and this allows me to continue my work on my own PC). My
config.sys file is exactly as shown in the readme.txt file, and this worked
fine (when selected, QNX booted problem free) for several weeks. Now the
boot process simply stops and displays the dialog I mentioned earlier. I
can find no specific reason this may have started occuring. I am completely
new to QNX, RealTime programming, and multi-OS systems, so this continues to
be a learning experience.
Perhaps you could briefly explain the ‘different reasons’ you mentioned. My
own search of the documentation/KB turned up nothing, but please direct me
to any documentation you feel I may have missed.
Thanks again for any help…
Alex Chapiro <> achapiro@qnx.com> > wrote in message
news:9gb4cn$lv8$> 1@nntp.qnx.com> …
There could be different reasons for that. In order to clarify situation
you
have to see command line (how photon startup scriptvia inputtrap) starts
photon input driver (devi-hirun). If you have a chance to connect to this
computer via local network, just from telnet session slay Photon and
io-graphics. Then you’ll be able to see on the console screen, what really
happened.
Another way is to fix a problem using input file (see online documentation
for inputtrap).
“Dave Grove” <> stevensgrove@igs.net> > wrote in message
news:9gb3bv$932$> 1@inn.qnx.com> …
Hi:
When QNX is booting, it stops during the process and displays a dialog
saying: “waiting for input driver” and then freezes, permanently. I
have
QNX on a removable drive that boots during my computer’s startup if
selected
(default is Win98 on a fixed drive). This problem has only started
recently
and I am at a loss on how to fix it. I am a student learning about
QNX/RealTime programming, so consider me quite the beginner…any help?
TIA
~ Dave
\