CC Hang Problem

I am having a problem with cc. If qcc gets an error (eg error 33) it
hangs in the shell and ctrl-c will break it but the “as” process
continues
running.

I am new to QNX development.
I am running what I believe to be the latest version of RTP or
Nuetrino. It is difficult for me to tell what version this is since the
names and version of QNX are not making much sense as far as the actual
image and the associated development tools. I downloaded the image that
was posted at QNX on Jan. 18, 2001

For my initial stab at coding I am
mounting a windows 98 shared area using fs-cifs in QNX. This allows me
to edit my
code from a windows environment but perform the compilation on the QNX
system.
It appears that the “as” process is blocking on the “fs-cifs” process
somehow.
I am including the complete listing of pidin that shows one instance of
the
“as” process which is just about pegging my processor usage (in photon
desktop). Any help would be greatly appreciated. Having to reboot the
system
for every compiler error is getting a little cumbersome.

A few years back I was fairly proficient at writing device drivers in
VxWorks but
have been sidetracked writing Windows applications for the last three
years. I
am still a bit “culture-shocked” trying to re-awaken my Unix skills and
experience. Please Help.

pid tid name prio STATE Blocked
1 1 (n/a) 0f READY
1 2 (n/a) 10r RECEIVE 1
1 3 (n/a) 10r RECEIVE 1
1 4 (n/a) 15r RECEIVE 1
1 5 (n/a) 10r RUNNING
1 6 (n/a) 10r RECEIVE 1
1 7 (n/a) 6r NANOSLEEP
1 8 (n/a) 15r RECEIVE 1
2 1 sbin/tinit 10o REPLY 204820
3 1 proc/boot/slogger 10o RECEIVE 1
12292 1 queue/x86/o/mqueue 10o RECEIVE 1
5 1 proc/boot/pci-bios 12o RECEIVE 1
6 1 roc/boot/devb-eide 10o SIGWAITINFO
6 2 roc/boot/devb-eide 21r RECEIVE 1
6 3 roc/boot/devb-eide 21r RECEIVE 4
6 4 roc/boot/devb-eide 10o RECEIVE 10
6 5 roc/boot/devb-eide 10r CONDVAR b0374468
6 6 roc/boot/devb-eide 10o RECEIVE 7
6 7 roc/boot/devb-eide 10o RECEIVE 7
6 8 roc/boot/devb-eide 9o RECEIVE 7
7 1 devc-con 10o RECEIVE 1
8 1 .1/x86/sbin/fs-pkg 10o RECEIVE 1
8 2 .1/x86/sbin/fs-pkg 10o SIGWAITINFO
8 3 .1/x86/sbin/fs-pkg 9o RECEIVE 1
8 4 .1/x86/sbin/fs-pkg 10o RECEIVE 1
8 5 .1/x86/sbin/fs-pkg 9o RECEIVE 1
8 6 .1/x86/sbin/fs-pkg 10o RECEIVE 1
4105 1 to/pipe/x86/o/pipe 10o RECEIVE 1
4105 2 to/pipe/x86/o/pipe 9o RECEIVE 1
4105 3 to/pipe/x86/o/pipe 9o RECEIVE 1
4105 4 to/pipe/x86/o/pipe 9o RECEIVE 1
147466 1 usr/sbin/dumper 10o RECEIVE 1
57355 1 devc-pty 20o RECEIVE 1
90124 1 devc-ser8250 24o RECEIVE 1
122893 1 sbin/devb-fdc 10o SIGWAITINFO
122893 2 sbin/devb-fdc 21r RECEIVE 1
122893 3 sbin/devb-fdc 10o RECEIVE 7
122893 4 sbin/devb-fdc 10o CONDVAR b0374468
122893 5 sbin/devb-fdc 10o RECEIVE 4
122893 6 sbin/devb-fdc 10o RECEIVE 4
118798 1 bin/dhcp.client 10o NANOSLEEP
90127 1 devc-par 10o RECEIVE 1
90127 2 devc-par 9r CONDVAR 804e83c
4628496 1 r/photon/bin/pterm 10r RECEIVE 1
90129 1 sbin/io-net 10o SIGWAITINFO
90129 2 sbin/io-net 9o READY
90129 4 sbin/io-net 21o RECEIVE 4
90129 5 sbin/io-net 10o RECEIVE 1
90129 6 sbin/io-net 17f CONDVAR 805d8d4
90129 7 sbin/io-net 21r RECEIVE 11
90129 8 sbin/io-net 10o RECEIVE 1
90129 9 sbin/io-net 19f CONDVAR 80522ec
90129 10 sbin/io-net 10o RECEIVE 1
90129 12 sbin/io-net 18f CONDVAR 805bdb4
405522 1 usr/photon/bin/pwm 10r RECEIVE
106515 1 oler/x86/o/spooler 10o RECEIVE 1
106515 2 oler/x86/o/spooler 10o SIGWAITINFO
204820 1 /photon/bin/Photon 12r RECEIVE 1
249877 1 ton/bin/fontsleuth 6o RECEIVE 1
4628502 1 bin/sh 10r SIGSUSPEND
241687 1 hoton/bin/phfontFA 12r RECEIVE 1
282648 1 io-graphics 12r REPLY 204820
450585 1 r/photon/bin/shelf 10r RECEIVE 1
450585 2 r/photon/bin/shelf 10r CONDVAR b04f9ea4
299034 1 o/x86/o/devi-hirun 15o RECEIVE 1
299034 2 o/x86/o/devi-hirun 10o REPLY 7
299034 3 o/x86/o/devi-hirun 12o SIGWAITINFO
299034 4 o/x86/o/devi-hirun 15o RECEIVE 1
487451 1 photon/bin/bkgdmgr 10r REPLY 204820
487452 1 hoton/bin/wmswitch 10r RECEIVE 2
487453 1 r/photon/bin/saver 10r REPLY 204820
4161566 1 r/photon/bin/pterm 10r RECEIVE 1
499743 1 ./Xphoton 10r SIGWAITINFO
499744 1 gtwm 10r SIGWAITINFO
4161569 1 bin/sh 10r REPLY 57355
557090 1 usr/sbin/fs-cifs 9r READY
557090 2 usr/sbin/fs-cifs 9r RECEIVE 1
557090 3 usr/sbin/fs-cifs 10r RECEIVE 1
557090 4 usr/sbin/fs-cifs 9r RECEIVE 1
557090 5 usr/sbin/fs-cifs 10r RECEIVE 1
4796451 1 bin/pidin 10r REPLY 1
4554789 1 usr/ntox86/bin/as 9r REPLY 557090

It looks like there is an error in fs-cifs. as is not getting signals
delivered to it after cc1 exits and closes the pipe.

The workaround for now is to tell qcc not to use pipes, rather to use
tempfiles. To do this, pass the -nopipe option to qcc

FibreBoy <fibreboy777@hotmail.com> wrote:

I am having a problem with cc. If qcc gets an error (eg error 33) it
hangs in the shell and ctrl-c will break it but the “as” process
continues
running.

I am new to QNX development.
I am running what I believe to be the latest version of RTP or
Nuetrino. It is difficult for me to tell what version this is since the
names and version of QNX are not making much sense as far as the actual
image and the associated development tools. I downloaded the image that
was posted at QNX on Jan. 18, 2001

For my initial stab at coding I am
mounting a windows 98 shared area using fs-cifs in QNX. This allows me
to edit my
code from a windows environment but perform the compilation on the QNX
system.
It appears that the “as” process is blocking on the “fs-cifs” process
somehow.
I am including the complete listing of pidin that shows one instance of
the
“as” process which is just about pegging my processor usage (in photon
desktop). Any help would be greatly appreciated. Having to reboot the
system
for every compiler error is getting a little cumbersome.

A few years back I was fairly proficient at writing device drivers in
VxWorks but
have been sidetracked writing Windows applications for the last three
years. I
am still a bit “culture-shocked” trying to re-awaken my Unix skills and
experience. Please Help.

pid tid name prio STATE Blocked
1 1 (n/a) 0f READY
1 2 (n/a) 10r RECEIVE 1
1 3 (n/a) 10r RECEIVE 1
1 4 (n/a) 15r RECEIVE 1
1 5 (n/a) 10r RUNNING
1 6 (n/a) 10r RECEIVE 1
1 7 (n/a) 6r NANOSLEEP
1 8 (n/a) 15r RECEIVE 1
2 1 sbin/tinit 10o REPLY 204820
3 1 proc/boot/slogger 10o RECEIVE 1
12292 1 queue/x86/o/mqueue 10o RECEIVE 1
5 1 proc/boot/pci-bios 12o RECEIVE 1
6 1 roc/boot/devb-eide 10o SIGWAITINFO
6 2 roc/boot/devb-eide 21r RECEIVE 1
6 3 roc/boot/devb-eide 21r RECEIVE 4
6 4 roc/boot/devb-eide 10o RECEIVE 10
6 5 roc/boot/devb-eide 10r CONDVAR b0374468
6 6 roc/boot/devb-eide 10o RECEIVE 7
6 7 roc/boot/devb-eide 10o RECEIVE 7
6 8 roc/boot/devb-eide 9o RECEIVE 7
7 1 devc-con 10o RECEIVE 1
8 1 .1/x86/sbin/fs-pkg 10o RECEIVE 1
8 2 .1/x86/sbin/fs-pkg 10o SIGWAITINFO
8 3 .1/x86/sbin/fs-pkg 9o RECEIVE 1
8 4 .1/x86/sbin/fs-pkg 10o RECEIVE 1
8 5 .1/x86/sbin/fs-pkg 9o RECEIVE 1
8 6 .1/x86/sbin/fs-pkg 10o RECEIVE 1
4105 1 to/pipe/x86/o/pipe 10o RECEIVE 1
4105 2 to/pipe/x86/o/pipe 9o RECEIVE 1
4105 3 to/pipe/x86/o/pipe 9o RECEIVE 1
4105 4 to/pipe/x86/o/pipe 9o RECEIVE 1
147466 1 usr/sbin/dumper 10o RECEIVE 1
57355 1 devc-pty 20o RECEIVE 1
90124 1 devc-ser8250 24o RECEIVE 1
122893 1 sbin/devb-fdc 10o SIGWAITINFO
122893 2 sbin/devb-fdc 21r RECEIVE 1
122893 3 sbin/devb-fdc 10o RECEIVE 7
122893 4 sbin/devb-fdc 10o CONDVAR b0374468
122893 5 sbin/devb-fdc 10o RECEIVE 4
122893 6 sbin/devb-fdc 10o RECEIVE 4
118798 1 bin/dhcp.client 10o NANOSLEEP
90127 1 devc-par 10o RECEIVE 1
90127 2 devc-par 9r CONDVAR 804e83c
4628496 1 r/photon/bin/pterm 10r RECEIVE 1
90129 1 sbin/io-net 10o SIGWAITINFO
90129 2 sbin/io-net 9o READY
90129 4 sbin/io-net 21o RECEIVE 4
90129 5 sbin/io-net 10o RECEIVE 1
90129 6 sbin/io-net 17f CONDVAR 805d8d4
90129 7 sbin/io-net 21r RECEIVE 11
90129 8 sbin/io-net 10o RECEIVE 1
90129 9 sbin/io-net 19f CONDVAR 80522ec
90129 10 sbin/io-net 10o RECEIVE 1
90129 12 sbin/io-net 18f CONDVAR 805bdb4
405522 1 usr/photon/bin/pwm 10r RECEIVE
106515 1 oler/x86/o/spooler 10o RECEIVE 1
106515 2 oler/x86/o/spooler 10o SIGWAITINFO
204820 1 /photon/bin/Photon 12r RECEIVE 1
249877 1 ton/bin/fontsleuth 6o RECEIVE 1
4628502 1 bin/sh 10r SIGSUSPEND
241687 1 hoton/bin/phfontFA 12r RECEIVE 1
282648 1 io-graphics 12r REPLY 204820
450585 1 r/photon/bin/shelf 10r RECEIVE 1
450585 2 r/photon/bin/shelf 10r CONDVAR b04f9ea4
299034 1 o/x86/o/devi-hirun 15o RECEIVE 1
299034 2 o/x86/o/devi-hirun 10o REPLY 7
299034 3 o/x86/o/devi-hirun 12o SIGWAITINFO
299034 4 o/x86/o/devi-hirun 15o RECEIVE 1
487451 1 photon/bin/bkgdmgr 10r REPLY 204820
487452 1 hoton/bin/wmswitch 10r RECEIVE 2
487453 1 r/photon/bin/saver 10r REPLY 204820
4161566 1 r/photon/bin/pterm 10r RECEIVE 1
499743 1 ./Xphoton 10r SIGWAITINFO
499744 1 gtwm 10r SIGWAITINFO
4161569 1 bin/sh 10r REPLY 57355
557090 1 usr/sbin/fs-cifs 9r READY
557090 2 usr/sbin/fs-cifs 9r RECEIVE 1
557090 3 usr/sbin/fs-cifs 10r RECEIVE 1
557090 4 usr/sbin/fs-cifs 9r RECEIVE 1
557090 5 usr/sbin/fs-cifs 10r RECEIVE 1
4796451 1 bin/pidin 10r REPLY 1
4554789 1 usr/ntox86/bin/as 9r REPLY 557090






cburgess@qnx.com

I had problems with fs-cifs, I switched to fs-nfs2 and never looked back.
The downside to fs-nfs2 is that you need to purchase, Windows Services for
Unix 2.0 and install it on Window NT or Windows 2000. The connection is alot
more stable.

“Colin Burgess” <cburgess@qnx.com> wrote in message
news:96rjm3$qgb$1@nntp.qnx.com

It looks like there is an error in fs-cifs. as is not getting signals
delivered to it after cc1 exits and closes the pipe.

The workaround for now is to tell qcc not to use pipes, rather to use
tempfiles. To do this, pass the -nopipe option to qcc

FibreBoy <> fibreboy777@hotmail.com> > wrote:
I am having a problem with cc. If qcc gets an error (eg error 33) it
hangs in the shell and ctrl-c will break it but the “as” process
continues
running.

I am new to QNX development.
I am running what I believe to be the latest version of RTP or
Nuetrino. It is difficult for me to tell what version this is since the
names and version of QNX are not making much sense as far as the actual
image and the associated development tools. I downloaded the image that
was posted at QNX on Jan. 18, 2001

For my initial stab at coding I am
mounting a windows 98 shared area using fs-cifs in QNX. This allows me
to edit my
code from a windows environment but perform the compilation on the QNX
system.
It appears that the “as” process is blocking on the “fs-cifs” process
somehow.
I am including the complete listing of pidin that shows one instance of
the
“as” process which is just about pegging my processor usage (in photon
desktop). Any help would be greatly appreciated. Having to reboot the
system
for every compiler error is getting a little cumbersome.

A few years back I was fairly proficient at writing device drivers in
VxWorks but
have been sidetracked writing Windows applications for the last three
years. I
am still a bit “culture-shocked” trying to re-awaken my Unix skills and
experience. Please Help.

pid tid name prio STATE Blocked
1 1 (n/a) 0f READY
1 2 (n/a) 10r RECEIVE 1
1 3 (n/a) 10r RECEIVE 1
1 4 (n/a) 15r RECEIVE 1
1 5 (n/a) 10r RUNNING
1 6 (n/a) 10r RECEIVE 1
1 7 (n/a) 6r NANOSLEEP
1 8 (n/a) 15r RECEIVE 1
2 1 sbin/tinit 10o REPLY 204820
3 1 proc/boot/slogger 10o RECEIVE 1
12292 1 queue/x86/o/mqueue 10o RECEIVE 1
5 1 proc/boot/pci-bios 12o RECEIVE 1
6 1 roc/boot/devb-eide 10o SIGWAITINFO
6 2 roc/boot/devb-eide 21r RECEIVE 1
6 3 roc/boot/devb-eide 21r RECEIVE 4
6 4 roc/boot/devb-eide 10o RECEIVE 10
6 5 roc/boot/devb-eide 10r CONDVAR b0374468
6 6 roc/boot/devb-eide 10o RECEIVE 7
6 7 roc/boot/devb-eide 10o RECEIVE 7
6 8 roc/boot/devb-eide 9o RECEIVE 7
7 1 devc-con 10o RECEIVE 1
8 1 .1/x86/sbin/fs-pkg 10o RECEIVE 1
8 2 .1/x86/sbin/fs-pkg 10o SIGWAITINFO
8 3 .1/x86/sbin/fs-pkg 9o RECEIVE 1
8 4 .1/x86/sbin/fs-pkg 10o RECEIVE 1
8 5 .1/x86/sbin/fs-pkg 9o RECEIVE 1
8 6 .1/x86/sbin/fs-pkg 10o RECEIVE 1
4105 1 to/pipe/x86/o/pipe 10o RECEIVE 1
4105 2 to/pipe/x86/o/pipe 9o RECEIVE 1
4105 3 to/pipe/x86/o/pipe 9o RECEIVE 1
4105 4 to/pipe/x86/o/pipe 9o RECEIVE 1
147466 1 usr/sbin/dumper 10o RECEIVE 1
57355 1 devc-pty 20o RECEIVE 1
90124 1 devc-ser8250 24o RECEIVE 1
122893 1 sbin/devb-fdc 10o SIGWAITINFO
122893 2 sbin/devb-fdc 21r RECEIVE 1
122893 3 sbin/devb-fdc 10o RECEIVE 7
122893 4 sbin/devb-fdc 10o CONDVAR b0374468
122893 5 sbin/devb-fdc 10o RECEIVE 4
122893 6 sbin/devb-fdc 10o RECEIVE 4
118798 1 bin/dhcp.client 10o NANOSLEEP
90127 1 devc-par 10o RECEIVE 1
90127 2 devc-par 9r CONDVAR 804e83c
4628496 1 r/photon/bin/pterm 10r RECEIVE 1
90129 1 sbin/io-net 10o SIGWAITINFO
90129 2 sbin/io-net 9o READY
90129 4 sbin/io-net 21o RECEIVE 4
90129 5 sbin/io-net 10o RECEIVE 1
90129 6 sbin/io-net 17f CONDVAR 805d8d4
90129 7 sbin/io-net 21r RECEIVE 11
90129 8 sbin/io-net 10o RECEIVE 1
90129 9 sbin/io-net 19f CONDVAR 80522ec
90129 10 sbin/io-net 10o RECEIVE 1
90129 12 sbin/io-net 18f CONDVAR 805bdb4
405522 1 usr/photon/bin/pwm 10r RECEIVE
106515 1 oler/x86/o/spooler 10o RECEIVE 1
106515 2 oler/x86/o/spooler 10o SIGWAITINFO
204820 1 /photon/bin/Photon 12r RECEIVE 1
249877 1 ton/bin/fontsleuth 6o RECEIVE 1
4628502 1 bin/sh 10r SIGSUSPEND
241687 1 hoton/bin/phfontFA 12r RECEIVE 1
282648 1 io-graphics 12r REPLY 204820
450585 1 r/photon/bin/shelf 10r RECEIVE 1
450585 2 r/photon/bin/shelf 10r CONDVAR b04f9ea4
299034 1 o/x86/o/devi-hirun 15o RECEIVE 1
299034 2 o/x86/o/devi-hirun 10o REPLY 7
299034 3 o/x86/o/devi-hirun 12o SIGWAITINFO
299034 4 o/x86/o/devi-hirun 15o RECEIVE 1
487451 1 photon/bin/bkgdmgr 10r REPLY 204820
487452 1 hoton/bin/wmswitch 10r RECEIVE 2
487453 1 r/photon/bin/saver 10r REPLY 204820
4161566 1 r/photon/bin/pterm 10r RECEIVE 1
499743 1 ./Xphoton 10r SIGWAITINFO
499744 1 gtwm 10r SIGWAITINFO
4161569 1 bin/sh 10r REPLY 57355
557090 1 usr/sbin/fs-cifs 9r READY
557090 2 usr/sbin/fs-cifs 9r RECEIVE 1
557090 3 usr/sbin/fs-cifs 10r RECEIVE 1
557090 4 usr/sbin/fs-cifs 9r RECEIVE 1
557090 5 usr/sbin/fs-cifs 10r RECEIVE 1
4796451 1 bin/pidin 10r REPLY 1
4554789 1 usr/ntox86/bin/as 9r REPLY 557090







\

cburgess@qnx.com

The -nopipe compiler option appears to have fixed the problem I was having.
Other than that, I have not had any problems so far with fs-cifs. I am just
using it to allow me to edit my source code on a Win98 Notebook that travels
between home and work to develop on two different QNX systems. One system is a
dual-boot with Win95 and QNX and the other system is a pure QNX system with no
Windows.

I am not ready to upgrade to Win2000PE at the moment so will stick with fs-cifs
for the time being. I have a bad attitude towards Windows products and find it
very poor form that you would have to purchase a seperate package from Msoft to
play with Unix systems. This should come with NT or 2000PE by default
especially with the growing popularity of Linux based systems.

When I do eventually upgrade I will probably end up buying the package anyway
and trying out fs-nfs2 but I have to bitch about it a little first. heh heh

Thanks for the help,
FibreBoy


bzycinsky wrote:

I had problems with fs-cifs, I switched to fs-nfs2 and never looked back.
The downside to fs-nfs2 is that you need to purchase, Windows Services for
Unix 2.0 and install it on Window NT or Windows 2000. The connection is alot
more stable.

“Colin Burgess” <> cburgess@qnx.com> > wrote in message
news:96rjm3$qgb$> 1@nntp.qnx.com> …
It looks like there is an error in fs-cifs. as is not getting signals
delivered to it after cc1 exits and closes the pipe.

The workaround for now is to tell qcc not to use pipes, rather to use
tempfiles. To do this, pass the -nopipe option to qcc

FibreBoy <> fibreboy777@hotmail.com> > wrote:
I am having a problem with cc. If qcc gets an error (eg error 33) it
hangs in the shell and ctrl-c will break it but the “as” process
continues
running.

I am new to QNX development.
I am running what I believe to be the latest version of RTP or
Nuetrino. It is difficult for me to tell what version this is since the
names and version of QNX are not making much sense as far as the actual
image and the associated development tools. I downloaded the image that
was posted at QNX on Jan. 18, 2001

For my initial stab at coding I am
mounting a windows 98 shared area using fs-cifs in QNX. This allows me
to edit my
code from a windows environment but perform the compilation on the QNX
system.
It appears that the “as” process is blocking on the “fs-cifs” process
somehow.
I am including the complete listing of pidin that shows one instance of
the
“as” process which is just about pegging my processor usage (in photon
desktop). Any help would be greatly appreciated. Having to reboot the
system
for every compiler error is getting a little cumbersome.

A few years back I was fairly proficient at writing device drivers in
VxWorks but
have been sidetracked writing Windows applications for the last three
years. I
am still a bit “culture-shocked” trying to re-awaken my Unix skills and
experience. Please Help.

pid tid name prio STATE Blocked
1 1 (n/a) 0f READY
1 2 (n/a) 10r RECEIVE 1
1 3 (n/a) 10r RECEIVE 1
1 4 (n/a) 15r RECEIVE 1
1 5 (n/a) 10r RUNNING
1 6 (n/a) 10r RECEIVE 1
1 7 (n/a) 6r NANOSLEEP
1 8 (n/a) 15r RECEIVE 1
2 1 sbin/tinit 10o REPLY 204820
3 1 proc/boot/slogger 10o RECEIVE 1
12292 1 queue/x86/o/mqueue 10o RECEIVE 1
5 1 proc/boot/pci-bios 12o RECEIVE 1
6 1 roc/boot/devb-eide 10o SIGWAITINFO
6 2 roc/boot/devb-eide 21r RECEIVE 1
6 3 roc/boot/devb-eide 21r RECEIVE 4
6 4 roc/boot/devb-eide 10o RECEIVE 10
6 5 roc/boot/devb-eide 10r CONDVAR b0374468
6 6 roc/boot/devb-eide 10o RECEIVE 7
6 7 roc/boot/devb-eide 10o RECEIVE 7
6 8 roc/boot/devb-eide 9o RECEIVE 7
7 1 devc-con 10o RECEIVE 1
8 1 .1/x86/sbin/fs-pkg 10o RECEIVE 1
8 2 .1/x86/sbin/fs-pkg 10o SIGWAITINFO
8 3 .1/x86/sbin/fs-pkg 9o RECEIVE 1
8 4 .1/x86/sbin/fs-pkg 10o RECEIVE 1
8 5 .1/x86/sbin/fs-pkg 9o RECEIVE 1
8 6 .1/x86/sbin/fs-pkg 10o RECEIVE 1
4105 1 to/pipe/x86/o/pipe 10o RECEIVE 1
4105 2 to/pipe/x86/o/pipe 9o RECEIVE 1
4105 3 to/pipe/x86/o/pipe 9o RECEIVE 1
4105 4 to/pipe/x86/o/pipe 9o RECEIVE 1
147466 1 usr/sbin/dumper 10o RECEIVE 1
57355 1 devc-pty 20o RECEIVE 1
90124 1 devc-ser8250 24o RECEIVE 1
122893 1 sbin/devb-fdc 10o SIGWAITINFO
122893 2 sbin/devb-fdc 21r RECEIVE 1
122893 3 sbin/devb-fdc 10o RECEIVE 7
122893 4 sbin/devb-fdc 10o CONDVAR b0374468
122893 5 sbin/devb-fdc 10o RECEIVE 4
122893 6 sbin/devb-fdc 10o RECEIVE 4
118798 1 bin/dhcp.client 10o NANOSLEEP
90127 1 devc-par 10o RECEIVE 1
90127 2 devc-par 9r CONDVAR 804e83c
4628496 1 r/photon/bin/pterm 10r RECEIVE 1
90129 1 sbin/io-net 10o SIGWAITINFO
90129 2 sbin/io-net 9o READY
90129 4 sbin/io-net 21o RECEIVE 4
90129 5 sbin/io-net 10o RECEIVE 1
90129 6 sbin/io-net 17f CONDVAR 805d8d4
90129 7 sbin/io-net 21r RECEIVE 11
90129 8 sbin/io-net 10o RECEIVE 1
90129 9 sbin/io-net 19f CONDVAR 80522ec
90129 10 sbin/io-net 10o RECEIVE 1
90129 12 sbin/io-net 18f CONDVAR 805bdb4
405522 1 usr/photon/bin/pwm 10r RECEIVE
106515 1 oler/x86/o/spooler 10o RECEIVE 1
106515 2 oler/x86/o/spooler 10o SIGWAITINFO
204820 1 /photon/bin/Photon 12r RECEIVE 1
249877 1 ton/bin/fontsleuth 6o RECEIVE 1
4628502 1 bin/sh 10r SIGSUSPEND
241687 1 hoton/bin/phfontFA 12r RECEIVE 1
282648 1 io-graphics 12r REPLY 204820
450585 1 r/photon/bin/shelf 10r RECEIVE 1
450585 2 r/photon/bin/shelf 10r CONDVAR b04f9ea4
299034 1 o/x86/o/devi-hirun 15o RECEIVE 1
299034 2 o/x86/o/devi-hirun 10o REPLY 7
299034 3 o/x86/o/devi-hirun 12o SIGWAITINFO
299034 4 o/x86/o/devi-hirun 15o RECEIVE 1
487451 1 photon/bin/bkgdmgr 10r REPLY 204820
487452 1 hoton/bin/wmswitch 10r RECEIVE 2
487453 1 r/photon/bin/saver 10r REPLY 204820
4161566 1 r/photon/bin/pterm 10r RECEIVE 1
499743 1 ./Xphoton 10r SIGWAITINFO
499744 1 gtwm 10r SIGWAITINFO
4161569 1 bin/sh 10r REPLY 57355
557090 1 usr/sbin/fs-cifs 9r READY
557090 2 usr/sbin/fs-cifs 9r RECEIVE 1
557090 3 usr/sbin/fs-cifs 10r RECEIVE 1
557090 4 usr/sbin/fs-cifs 9r RECEIVE 1
557090 5 usr/sbin/fs-cifs 10r RECEIVE 1
4796451 1 bin/pidin 10r REPLY 1
4554789 1 usr/ntox86/bin/as 9r REPLY 557090







\

cburgess@qnx.com

Well, I happen to think that Bill Gates is the devil incarnate, but your
posting made me recall what Winston Churchill said when his defence
minister expressed shock at his willingness to sign a pact with Stalin;
it was something to the effect “I would sign a pact with the devil
himself
if he would align with me against Hitler”…

As much as I hate to admit it, SMB (aka CIFS) is a better file sharing
protocol than NFS (of course nothing compares to native QNX networking).
Personally, I would stick with fs-cifs if you are going to host your
files
on windoze and compile them from QNX, and use Samba if you want to host
your files on QNX and edit them from windoze. Just my $0.02…

-----Original Message-----
From: FibreBoy [mailto:fibreboy777@hotmail.com]
Posted At: Sunday, February 25, 2001 6:00 PM
Posted To: devtools
Conversation: CC Hang Problem
Subject: Re: CC Hang Problem


The -nopipe compiler option appears to have fixed the problem I was
having.
Other than that, I have not had any problems so far with fs-cifs. I am
just
using it to allow me to edit my source code on a Win98 Notebook that
travels
between home and work to develop on two different QNX systems. One
system is a
dual-boot with Win95 and QNX and the other system is a pure QNX system
with no
Windows.

I am not ready to upgrade to Win2000PE at the moment so will stick with
fs-cifs
for the time being. I have a bad attitude towards Windows products and
find it
very poor form that you would have to purchase a seperate package from
Msoft to
play with Unix systems. This should come with NT or 2000PE by default
especially with the growing popularity of Linux based systems.

When I do eventually upgrade I will probably end up buying the package
anyway
and trying out fs-nfs2 but I have to bitch about it a little first. heh
heh

Thanks for the help,
FibreBoy