shutdown and other QNX bugs

We have the same problem here, when typing

shutdown -f

It reboots and the computer ALWAYS freeze
at the Award BIOS screen, we have to press RESET button.

It’s a Pentium 133 with 32 MB desktop mini-tour PC
manufactured by Sygmawave used for development.

If I don’t type ‘shutdown -f’ and just press RESET,
10% of the time QNX have to scandisk
the partition and maybe lost some files… grrr.
[ and if some system files… then reinstall. =( ]

It’s kind of really annoying, another bug
we have is that Watcom C++ 10.6 under QNX latest version (Jan or July2000?),
when used intensively by students, wcc386 stays in memory, after 2-3 hours,
we obtain ‘sin’ something like 10-15 threads of wcc386 in memory
and no more compilation works and they call the Techs complaining…
getting us crazy ! =(

One of the other tech here, recommended to install Virtual Memory
on workstation (like they do on Solaris/Linux),
(which doesn’t exist ?!? I think it’s not really Real-Time to have VM…
right? =)
so we could only reboot machine every day instead of 3-5 times a day,
getting us nuts. We finally chmod 4755 shutdown, so students don’t
screw up the QNX FAT and type shutdown -f and press RESET.
Instead of pressing only RESET. As you can see, it’s very annoying.

Another bug was in xemacs, the indication on the screen does not work well,
it prints extended ASCII instead of real stuff. I will try to get a
screenshot,
so you can see what I mean. Currently, they switched to vi or vedit,
but since we got some emacs purist, it would be nice to have it fully
working too.

We also need to have the default console without Photon to QANSI-M or
preferably
aliased to ANSI (so Solaris/Linux station rlogin are possible).
In Photon, it works great, except they have to type ANSI when they rlogin.

We also try to get ssh working under QNX, for safety,
(Techs don’t feel like rlogin their passwords)
but it does not compile, it jams and after getting
few coffees and waiting for 3 hours,
it’s still jam at compiling… hmmm. Any ideas ?

Last wish, could it be possible to have a screen saver
in console and photon, really stupid blank screen
user password protected will do the trick running at low priority,
so other students don’t fool around other people accounts…
Students tends to cheat if they found a nice account wide open…

Any help greatly appreciated,
we are looking to solve those problems since January 2000 !

Sincerly yours,

Fred.

He said it used to work with QNX 4.23. The method
change around 4.24 I think and the -b option was added
to support various hardware. So to get the behavior
he had with 4.23 he must try the various -b options.

Actually I think it has more to do with the fact that some of the newer
computers don’t like to do the autoreboot thing. I run into the same
problem occasionally on QNX 4 and on Windoze 98. He wasn’t asking how to
keep it shutdown, he was asking why it didnt auto reboot when not using
the -b option. I am pretty sure it is hardware dependent.

Jim

Check the -b option of Proc32, that should do it.

When I use the shutdown command the compter freezes after it counts
down
to
zero rather than restarting.

When I was using QNX 4.23 I had no problems with the shutdown
command.
The
problem started when I upgraded to version 4.25C.

Is there a patch for this?

“Fred” <fprog@users.sourceforge.net> wrote in message
news:8op82u$710$1@inn.qnx.com

We have the same problem here, when typing

shutdown -f

It reboots and the computer ALWAYS freeze
at the Award BIOS screen, we have to press RESET button.

Then try various setup of Proc32 -b option in the image.

It’s a Pentium 133 with 32 MB desktop mini-tour PC
manufactured by Sygmawave used for development.

If I don’t type ‘shutdown -f’ and just press RESET,
10% of the time QNX have to scandisk
the partition and maybe lost some files… grrr.
[ and if some system files… then reinstall. =( ]

Very very very unlikely that you will lose some file…

This is not FAT

It’s kind of really annoying, another bug
we have is that Watcom C++ 10.6 under QNX latest version (Jan or
July2000?),
when used intensively by students, wcc386 stays in memory, after 2-3
hours,
we obtain ‘sin’ something like 10-15 threads of wcc386 in memory
and no more compilation works and they call the Techs complaining…
getting us crazy ! =(

Type sac -i1, you will see that there must be a process that
uses all the CPU at priority 10. You can download
sysmon from ftp.qnx.com to help you find out which
program is eating the CPU.

kill the program (with command slay or kill) will solve the problem.
Then the next step is to figure out why a programme consumes
the CPU.


One of the other tech here, recommended to install Virtual Memory
on workstation (like they do on Solaris/Linux),
(which doesn’t exist ?!? I think it’s not really Real-Time to have VM…
right? =)

Yes and that suggestion indicates that that person doesn’t know
nothing about QNX.

so we could only reboot machine every day instead of 3-5 times a day,
getting us nuts. We finally chmod 4755 shutdown, so students don’t
screw up the QNX FAT and type shutdown -f and press RESET.
Instead of pressing only RESET. As you can see, it’s very annoying.

As I said it’s not a FAT, it’s very different.

Another bug was in xemacs, the indication on the screen does not work
well,
it prints extended ASCII instead of real stuff. I will try to get a
screenshot,
so you can see what I mean. Currently, they switched to vi or vedit,
but since we got some emacs purist, it would be nice to have it fully
working too.

Don’t know about xemac, sorry. Are running X?

We also need to have the default console without Photon to QANSI-M or
preferably
aliased to ANSI (so Solaris/Linux station rlogin are possible).
In Photon, it works great, except they have to type ANSI when they rlogin.

We also try to get ssh working under QNX, for safety,
(Techs don’t feel like rlogin their passwords)
but it does not compile, it jams and after getting
few coffees and waiting for 3 hours,
it’s still jam at compiling… hmmm. Any ideas ?

Must be the same problem above. There is a program

that eats the CPU.

Last wish, could it be possible to have a screen saver
in console and photon, really stupid blank screen
user password protected will do the trick running at low priority,
so other students don’t fool around other people accounts…
Students tends to cheat if they found a nice account wide open…

http://www.schoenbrun.com/~mba/free.htm

Any help greatly appreciated,
we are looking to solve those problems since January 2000 !

Sincerly yours,

Fred.

He said it used to work with QNX 4.23. The method
change around 4.24 I think and the -b option was added
to support various hardware. So to get the behavior
he had with 4.23 he must try the various -b options.

Actually I think it has more to do with the fact that some of the newer
computers don’t like to do the autoreboot thing. I run into the same
problem occasionally on QNX 4 and on Windoze 98. He wasn’t asking how
to
keep it shutdown, he was asking why it didnt auto reboot when not using
the -b option. I am pretty sure it is hardware dependent.

Jim

Check the -b option of Proc32, that should do it.

When I use the shutdown command the compter freezes after it counts
down
to
zero rather than restarting.

When I was using QNX 4.23 I had no problems with the shutdown
command.
The
problem started when I upgraded to version 4.25C.

Is there a patch for this?

Mario Charest wrote in message <8ophj2$bbl$1@inn.qnx.com>…

We have the same problem here, when typing

shutdown -f

It reboots and the computer ALWAYS freeze
at the Award BIOS screen, we have to press RESET button.

Then try various setup of Proc32 -b option in the image.

I will try that, the other guy tell us that also…

It’s a Pentium 133 with 32 MB desktop mini-tour PC
manufactured by Sygmawave used for development.

If I don’t type ‘shutdown -f’ and just press RESET,
10% of the time QNX have to scandisk
the partition and maybe lost some files… grrr.
[ and if some system files… then reinstall. =( ]

Very very very unlikely that you will lose some file…
This is not FAT

Well, it happened at least 3 times that some system files got corrupt after
reset,
it’s annoying to reinstall, even if the install from CD is very friendly and
quick…
I do not have any other name in mind other than FAT…
what’s the real name btw for QNX filesystem File Allocation Table or inode
or whatever ?!

It’s kind of really annoying, another bug
we have is that Watcom C++ 10.6 under QNX latest version
(Jan or July2000?),
when used intensively by students, wcc386 stays in memory,
after 2-3 hours,
we obtain ‘sin’ something like 10-15 threads of wcc386 in memory
and no more compilation works and they call the Techs complaining…
getting us crazy ! =(


Type sac -i1, you will see that there must be a process that
uses all the CPU at priority 10. You can download
sysmon from ftp.qnx.com to help you find out which
program is eating the CPU.

kill the program (with command slay or kill) will solve the problem.
Then the next step is to figure out why a programme consumes
the CPU.

The program is watcom !
yes, we tried to slay wcc386 but furthermore it doesn’t work !
it doesn’t want to slay it jam when we type “slay wcc386”,
we have to press CTRL-BREAK/C to return to the shell.
That’s why it’s a bug in Watcom. I’m pretty satisfied by the optimization
of Watcom compare to gcc almost 4:1 smaller, but still that’s a bug !
The fact that new features and photon IDE are not provide… =(

One of the other tech here, recommended to install Virtual Memory
on workstation (like they do on Solaris/Linux),
(which doesn’t exist ?!? I think it’s not really Real-Time to have VM…
right? =)

Yes and that suggestion indicates that that person doesn’t know
nothing about QNX.

Yes, but he’s a good UNIX tech perhaps… =)
but still it’s not that important for a P133 workstation,
it’s only very important for the target Arcom board.

so we could only reboot machine every day instead of 3-5 times a day,
getting us nuts. We finally chmod 4755 shutdown, so students don’t
screw up the QNX FAT and type shutdown -f and press RESET.
Instead of pressing only RESET. As you can see, it’s very annoying.


As I said it’s not a FAT, it’s very different.

Yeah, I know but you get the idea.

Another bug was in xemacs, the indication on the screen does not work
well,
it prints extended ASCII instead of real stuff. I will try to get a
screenshot,
so you can see what I mean. Currently, they switched to vi or vedit,
but since we got some emacs purist, it would be nice to have it fully
working too.


Don’t know about xemac, sorry. Are running X?

No running under QNX console it’s a port
I found it on QNX website… under usr/free…

http://www.qnx.com/cgi-bin/search/usr/free/?srch=emacs&select=1

GNU emacs

The executable name is ‘./xemacs’ running on console mode…

We also need to have the default console without Photon to QANSI-M or
preferably
aliased to ANSI (so Solaris/Linux station rlogin are possible).
In Photon, it works great, except they have to type ANSI when they
rlogin.

We also try to get ssh working under QNX, for safety,
(Techs don’t feel like rlogin their passwords)
but it does not compile, it jams and after getting
few coffees and waiting for 3 hours,
it’s still jam at compiling… hmmm. Any ideas ?

Must be the same problem above. There is a program
that eats the CPU.

Last wish, could it be possible to have a screen saver
in console and photon, really stupid blank screen
user password protected will do the trick running at low priority,
so other students don’t fool around other people accounts…
Students tends to cheat if they found a nice account wide open…


http://www.schoenbrun.com/~mba/free.htm

Thanks, I will download it ! =)

Any source code of a console mode screensaver ?

Any help greatly appreciated,
we are looking to solve those problems since January 2000 !

Sincerly yours,


Fred.


He said it used to work with QNX 4.23. The method
change around 4.24 I think and the -b option was added
to support various hardware. So to get the behavior
he had with 4.23 he must try the various -b options.

Actually I think it has more to do with the fact that some of the
newer
computers don’t like to do the autoreboot thing. I run into the same
problem occasionally on QNX 4 and on Windoze 98. He wasn’t asking how
to
keep it shutdown, he was asking why it didnt auto reboot when not
using
the -b option. I am pretty sure it is hardware dependent.

Jim

Check the -b option of Proc32, that should do it.

When I use the shutdown command the compter freezes after it
counts
down
to
zero rather than restarting.

When I was using QNX 4.23 I had no problems with the shutdown
command.
The
problem started when I upgraded to version 4.25C.

Is there a patch for this?

Fred <fprog@users.sourceforge.net> wrote in message
news:8op82u$710$1@inn.qnx.com

We have the same problem here, when typing

shutdown -f

It reboots and the computer ALWAYS freeze
at the Award BIOS screen, we have to press RESET button.

It’s a Pentium 133 with 32 MB desktop mini-tour PC
manufactured by Sygmawave used for development.

If I don’t type ‘shutdown -f’ and just press RESET,
10% of the time QNX have to scandisk
the partition and maybe lost some files… grrr.
[ and if some system files… then reinstall. =( ]

Try lowering the write-behind delay in Fsys with the -d option to 1 or 2
seconds. Default is set to 3 seconds. There was at least one version of Fsys
where it was set to 5 seconds. I remember that it caused some Photon users
problems with corrupt files after a shutdown. Later versions of Fsys went
back to 3. I think newer versions of Photon do a better job cleaning up too.

It’s kind of really annoying, another bug
we have is that Watcom C++ 10.6 under QNX latest version (Jan or
July2000?),
when used intensively by students, wcc386 stays in memory, after 2-3
hours,
we obtain ‘sin’ something like 10-15 threads of wcc386 in memory
and no more compilation works and they call the Techs complaining…
getting us crazy ! =(

Maybe you can download watcom (www.openwatcom.org) and fix it :slight_smile:

One of the other tech here, recommended to install Virtual Memory
on workstation (like they do on Solaris/Linux),
(which doesn’t exist ?!? I think it’s not really Real-Time to have VM…
right? =)
so we could only reboot machine every day instead of 3-5 times a day,
getting us nuts. We finally chmod 4755 shutdown, so students don’t
screw up the QNX FAT and type shutdown -f and press RESET.
Instead of pressing only RESET. As you can see, it’s very annoying.

Another bug was in xemacs, the indication on the screen does not work
well,
it prints extended ASCII instead of real stuff. I will try to get a
screenshot,
so you can see what I mean. Currently, they switched to vi or vedit,
but since we got some emacs purist, it would be nice to have it fully
working too.

We also need to have the default console without Photon to QANSI-M or
preferably
aliased to ANSI (so Solaris/Linux station rlogin are possible).
In Photon, it works great, except they have to type ANSI when they rlogin.

We also try to get ssh working under QNX, for safety,
(Techs don’t feel like rlogin their passwords)
but it does not compile, it jams and after getting
few coffees and waiting for 3 hours,
it’s still jam at compiling… hmmm. Any ideas ?

Last wish, could it be possible to have a screen saver
in console and photon, really stupid blank screen
user password protected will do the trick running at low priority,
so other students don’t fool around other people accounts…
Students tends to cheat if they found a nice account wide open…

Any help greatly appreciated,
we are looking to solve those problems since January 2000 !

Sincerly yours,

Fred.

He said it used to work with QNX 4.23. The method
change around 4.24 I think and the -b option was added
to support various hardware. So to get the behavior
he had with 4.23 he must try the various -b options.

Actually I think it has more to do with the fact that some of the newer
computers don’t like to do the autoreboot thing. I run into the same
problem occasionally on QNX 4 and on Windoze 98. He wasn’t asking how
to
keep it shutdown, he was asking why it didnt auto reboot when not using
the -b option. I am pretty sure it is hardware dependent.

Jim

Check the -b option of Proc32, that should do it.

When I use the shutdown command the compter freezes after it counts
down
to
zero rather than restarting.

When I was using QNX 4.23 I had no problems with the shutdown
command.
The
problem started when I upgraded to version 4.25C.

Is there a patch for this?

Stephen Thomas wrote in message <8oprpm$g5n$1@inn.qnx.com>…

Fred <> fprog@users.sourceforge.net> > wrote in message
news:8op82u$710$> 1@inn.qnx.com> …
We have the same problem here, when typing

shutdown -f

It reboots and the computer ALWAYS freeze
at the Award BIOS screen, we have to press RESET button.

It’s a Pentium 133 with 32 MB desktop mini-tour PC
manufactured by Sygmawave used for development.

If I don’t type ‘shutdown -f’ and just press RESET,
10% of the time QNX have to scandisk
the partition and maybe lost some files… grrr.
[ and if some system files… then reinstall. =( ]

Try lowering the write-behind delay in Fsys with the -d option to 1 or 2
seconds. Default is set to 3 seconds. There was at least one version of
Fsys
where it was set to 5 seconds. I remember that it caused some Photon users
problems with corrupt files after a shutdown. Later versions of Fsys went
back to 3. I think newer versions of Photon do a better job cleaning up
too.

Okay I will try that.

It’s kind of really annoying, another bug
we have is that Watcom C++ 10.6 under QNX latest version (Jan or
July2000?),
when used intensively by students, wcc386 stays in memory, after 2-3
hours,
we obtain ‘sin’ something like 10-15 threads of wcc386 in memory
and no more compilation works and they call the Techs complaining…
getting us crazy ! =(

Maybe you can download watcom (> www.openwatcom.org> ) and fix it > :slight_smile:

I heard of that since 2 weeks, but

“There are currently no files available for downloading. Check back again at
a later date.”

Also, it might not be available until next year ?

Another problem is that we are stuck to 10.6,
where on PC the version 11.x is out since a while…
There is no full (Currently maybe 80% ?)
support to STL (some part are not working fully) and other new features…

Also, we might move to RtP once it’s out and stable,
but still it would be nice to solve those bug any how…

At least, to understand why it get stuck in memory after few compile ?

What I mean by intensive compile session is that a student having 2000
errors,
might compile let say 2000 times in 2 hours checking for each error they
made…

They seems to do that, instead of looking at the code and solve most of
them,
before recompiling… like I do.

Sincerly yours,
Fred.

One of the other tech here, recommended to install Virtual Memory
on workstation (like they do on Solaris/Linux),
(which doesn’t exist ?!? I think it’s not really Real-Time to have VM…
right? =)
so we could only reboot machine every day instead of 3-5 times a day,
getting us nuts. We finally chmod 4755 shutdown, so students don’t
screw up the QNX FAT and type shutdown -f and press RESET.
Instead of pressing only RESET. As you can see, it’s very annoying.

Another bug was in xemacs, the indication on the screen does not work
well,
it prints extended ASCII instead of real stuff. I will try to get a
screenshot,
so you can see what I mean. Currently, they switched to vi or vedit,
but since we got some emacs purist, it would be nice to have it fully
working too.

We also need to have the default console without Photon to QANSI-M or
preferably
aliased to ANSI (so Solaris/Linux station rlogin are possible).
In Photon, it works great, except they have to type ANSI when they
rlogin.

We also try to get ssh working under QNX, for safety,
(Techs don’t feel like rlogin their passwords)
but it does not compile, it jams and after getting
few coffees and waiting for 3 hours,
it’s still jam at compiling… hmmm. Any ideas ?

Last wish, could it be possible to have a screen saver
in console and photon, really stupid blank screen
user password protected will do the trick running at low priority,
so other students don’t fool around other people accounts…
Students tends to cheat if they found a nice account wide open…

Any help greatly appreciated,
we are looking to solve those problems since January 2000 !

Sincerly yours,

Fred.

He said it used to work with QNX 4.23. The method
change around 4.24 I think and the -b option was added
to support various hardware. So to get the behavior
he had with 4.23 he must try the various -b options.

Actually I think it has more to do with the fact that some of the
newer
computers don’t like to do the autoreboot thing. I run into the same
problem occasionally on QNX 4 and on Windoze 98. He wasn’t asking how
to
keep it shutdown, he was asking why it didnt auto reboot when not
using
the -b option. I am pretty sure it is hardware dependent.

Jim

Check the -b option of Proc32, that should do it.

When I use the shutdown command the compter freezes after it
counts
down
to
zero rather than restarting.

When I was using QNX 4.23 I had no problems with the shutdown
command.
The
problem started when I upgraded to version 4.25C.

Is there a patch for this?

It’s kind of really annoying, another bug
we have is that Watcom C++ 10.6 under QNX latest version (Jan or
July2000?),
when used intensively by students, wcc386 stays in memory, after 2-3
hours,
we obtain ‘sin’ something like 10-15 threads of wcc386 in memory
and no more compilation works and they call the Techs complaining…
getting us crazy ! =(

Maybe you can download watcom (> www.openwatcom.org> ) and fix it > :slight_smile:

I heard of that since 2 weeks, but

“There are currently no files available for downloading. Check back again
at
a later date.”

That’s irrelavent, the problem is not with Watcom. Because of priority
decay
the compiler often end up running at priority 9 so if a program
at priority 10 uses all the CPU (10 is the default) the program
at priority 9 (wcc386) can’t run.

Also, it might not be available until next year ?

Another problem is that we are stuck to 10.6,
where on PC the version 11.x is out since a while…
There is no full (Currently maybe 80% ?)
support to STL (some part are not working fully) and other new features…

Strange may people use STL version 3 with great success.

That’s irrelavent, the problem is not with Watcom. Because of priority
decay
the compiler often end up running at priority 9 so if a program
at priority 10 uses all the CPU (10 is the default) the program
at priority 9 (wcc386) can’t run.

That happens to me all the time with the ped editor. Sometimes the ped
process stays even though the window is closed. And delays or blocks the
Watcom compiler.

Easy fix: slay -f ped…

Marku