fs-cifs and windows98

Hi,
I have a question related to windows98.
i use fs-cifs mount a networks image on windows98 or windows me just like
this:
#fs-cifs //server:192.168.0.119:/tools /win98 my_name 123456
it’s ok.i can “ls” this dir and i can copy files (read and write).
but when i test the trans speed ,i copy a big file(about 100M) from qnx to
win98 or from win98 to qnx,
I found the io-net dead when i copy about 3M bytes(if the os is windows
xp,it would be 20M byte. ).
The same thing happened when i run ftp to trans data to a ftp server on
windows 98.
i have a rtl8139(c?) networks card and I config it like this:
#io-net -d rtl -p tcpip
#ifconfig en0 192.168.0.222

who can tell me why ?
what’s with my config?
thanks,
johnson.

“johnson zhou” <jszhou@yahoo.com> wrote in message
news:al4jff$hgp$1@inn.qnx.com

Hi,
I have a question related to windows98.
i use fs-cifs mount a networks image on windows98 or windows me just like
this:
#fs-cifs //server:192.168.0.119:/tools /win98 my_name 123456
it’s ok.i can “ls” this dir and i can copy files (read and write).
but when i test the trans speed ,i copy a big file(about 100M) from qnx to
win98 or from win98 to qnx,
I found the io-net dead when i copy about 3M bytes(if the os is windows
xp,it would be 20M byte. ).
The same thing happened when i run ftp to trans data to a ftp server on
windows 98.

You said the io-net dead. Does that mean the io-net crashed or
the fs-cifs/ftp were blocking on io-net? Can you provide us
the “pidin” output and, in case the io-net crashed, give us the core file.
(default cores are in /var/dumps/) Thanks.

Weijie

i have a rtl8139(c?) networks card and I config it like this:
#io-net -d rtl -p tcpip
#ifconfig en0 192.168.0.222

who can tell me why ?
what’s with my config?
thanks,
johnson.

Zhang,
Thanks for your answer.
I think perhanps the io-net doesn’t reponse any request.If I “slay
io-net”,and restart it ,copy can continue.
This is the “pidin” output,the left is run normal and the right is in
trouble.The /val/dumps/io-net.core have no change.
You are right,fs-cifs blocked on io-net. But how to do? pls help me.Thanks.

Johnson

pid tid name prio STATE Blocked pid tid name
prio STATE Blocked
1 1 procnto 0f READY 1 1 procnto
0f READY
1 2 procnto 15r RECEIVE 1 1 2 procnto
15r RECEIVE 1
1 3 procnto 63r RECEIVE 1 1 3 procnto
63r RECEIVE 1
1 4 procnto 10r RECEIVE 1 1 4 procnto
12r RECEIVE 1
1 5 procnto 15r RECEIVE 1 1 5 procnto
15r RECEIVE 1
1 6 procnto 10r RECEIVE 1 1 6 procnto
10r RECEIVE 1
1 7 procnto 15r RECEIVE 1 1 7 procnto
15r RECEIVE 1
1 8 procnto 10r RECEIVE 1 1 8 procnto
10r RECEIVE 1
1 9 procnto 6r NANOSLEEP 1 9 procnto
6r NANOSLEEP
1 10 procnto 10r RUNNING 1 10 procnto
10r RUNNING
1 11 procnto 10r RECEIVE 1 1 11 procnto
10r RECEIVE 1
1 12 procnto 15r RECEIVE 1 1 12 procnto
15r RECEIVE 1
2 1 sbin/tinit 10o REPLY 196626 2 1
sbin/tinit 10o REPLY 196626
3 1 proc/boot/slogger 21o RECEIVE 1 3 1
proc/boot/slogger 21o RECEIVE 1
12292 1 sbin/mqueue 10o RECEIVE 1 12292 1
sbin/mqueue 10o RECEIVE 1
5 1 proc/boot/pci-bios 10o RECEIVE 1 5 1
proc/boot/pci-bios 10o RECEIVE 1
6 1 roc/boot/devb-eide 10o SIGWAITINFO 6 1
roc/boot/devb-eide 10o SIGWAITINFO
6 2 roc/boot/devb-eide 21r RECEIVE 1 6 2
roc/boot/devb-eide 21r RECEIVE 1
6 3 roc/boot/devb-eide 10o RECEIVE 7 6 3
roc/boot/devb-eide 10o RECEIVE 7
6 4 roc/boot/devb-eide 10r CONDVAR b0378fec 6 4
roc/boot/devb-eide 10r CONDVAR b0378fec
6 5 roc/boot/devb-eide 10o RECEIVE 4 6 5
roc/boot/devb-eide 10o RECEIVE 4
6 6 roc/boot/devb-eide 10o RECEIVE 4 6 6
roc/boot/devb-eide 10o RECEIVE 4
6 8 roc/boot/devb-eide 10o RECEIVE 4 6 8
roc/boot/devb-eide 10o RECEIVE 4
7 1 /x86/sbin/devc-con 10o RECEIVE 1 7 1
/x86/sbin/devc-con 10o RECEIVE 1
8 1 .2/x86/sbin/fs-pkg 10o RECEIVE 1 8 1
…2/x86/sbin/fs-pkg 10o RECEIVE 1
8 2 .2/x86/sbin/fs-pkg 10o SIGWAITINFO 8 2
…2/x86/sbin/fs-pkg 10o SIGWAITINFO
8 3 .2/x86/sbin/fs-pkg 10o RECEIVE 1 8 3
…2/x86/sbin/fs-pkg 10o RECEIVE 1
8 4 .2/x86/sbin/fs-pkg 10o RECEIVE 1 8 4
…2/x86/sbin/fs-pkg 10o RECEIVE 1
8 5 .2/x86/sbin/fs-pkg 10o RECEIVE 1 8 5
…2/x86/sbin/fs-pkg 10o RECEIVE 1
8 6 .2/x86/sbin/fs-pkg 10o RECEIVE 1 8 6
…2/x86/sbin/fs-pkg 10o RECEIVE 1
4105 1 sbin/pipe 10o RECEIVE 1 4105 1
sbin/pipe 10o RECEIVE 1
4105 2 sbin/pipe 10o RECEIVE 1 4105 2
sbin/pipe 10o RECEIVE 1
4105 4 sbin/pipe 10o RECEIVE 1 4105 4
sbin/pipe 10o RECEIVE 1
4105 5 sbin/pipe 10o RECEIVE 1 4105 5
sbin/pipe 10o RECEIVE 1
122890 1 usr/sbin/random 10o SIGWAITINFO 122890 1
usr/sbin/random 10o SIGWAITINFO
122890 2 usr/sbin/random 10o RECEIVE 1 122890 2
usr/sbin/random 10o RECEIVE 1
122890 3 usr/sbin/random 10o NANOSLEEP 122890 3
usr/sbin/random 10o NANOSLEEP
45067 1 sbin/devc-pty 10o RECEIVE 1 45067 1
sbin/devc-pty 10o RECEIVE 1
999436 1 sbin/io-net 10r SIGWAITINFO 999436 1
sbin/io-net 10r SIGWAITINFO
999436 2 sbin/io-net 10r RECEIVE 1 999436 2
sbin/io-net 10r RECEIVE 1
999436 3 sbin/io-net 10r RECEIVE 1 999436 3
sbin/io-net 10r RECEIVE 1
999436 4 sbin/io-net 10r RECEIVE 1 999436 4
sbin/io-net 10r RECEIVE 1
999436 5 sbin/io-net 21r RECEIVE 5 999436 5
sbin/io-net 21r RECEIVE 5
999436 6 sbin/io-net 10r RECEIVE 9 999436 6
sbin/io-net 20r RECEIVE 9
110605 1 sbin/devb-fdc 10o SIGWAITINFO 110605 1
sbin/devb-fdc 10o SIGWAITINFO
110605 2 sbin/devb-fdc 21r INTR 110605 2
sbin/devb-fdc 21r INTR
110605 3 sbin/devb-fdc 10o RECEIVE 7 110605 3
sbin/devb-fdc 10o RECEIVE 7
110605 4 sbin/devb-fdc 10o CONDVAR b0378fec 110605 4
sbin/devb-fdc 10o CONDVAR b0378fec
110605 5 sbin/devb-fdc 10o RECEIVE 4 110605 5
sbin/devb-fdc 10o RECEIVE 4
110605 6 sbin/devb-fdc 10o RECEIVE 4 110605 6
sbin/devb-fdc 10o RECEIVE 4
110605 7 sbin/devb-fdc 10o RECEIVE 4 110605 7
sbin/devb-fdc 10o RECEIVE 4
94222 1 sbin/devc-ser8250 24o RECEIVE 1 94222 1
sbin/devc-ser8250 24o RECEIVE 1
135183 1 usr/sbin/dumper 10o RECEIVE 1 135183 1
usr/sbin/dumper 10o RECEIVE 1
520208 1 r/photon/bin/pterm 10r RECEIVE 1 520208 1
r/photon/bin/pterm 10r RECEIVE 1
401425 1 usr/photon/bin/pwm 10r RECEIVE 1 401425 1
usr/photon/bin/pwm 10r RECEIVE 1
196626 1 /photon/bin/Photon 10r RECEIVE 1 196626 1
/photon/bin/Photon 10r RECEIVE 1
241683 2 ton/bin/fontsleuth 6o RECEIVE 1 241683 2
ton/bin/fontsleuth 6o RECEIVE 1
241683 3 ton/bin/fontsleuth 6o RECEIVE 1 241683 3
ton/bin/fontsleuth 6o RECEIVE 1
241683 4 ton/bin/fontsleuth 6o RECEIVE 1 241683 4
ton/bin/fontsleuth 6o RECEIVE 1
241683 5 ton/bin/fontsleuth 6o RECEIVE 1 241683 5
ton/bin/fontsleuth 6o RECEIVE 1
520212 1 bin/sh 10r SIGSUSPEND 520212 1 bin/sh
10r SIGSUSPEND
233493 1 hoton/bin/phfontFA 10r RECEIVE 1 233493 1
hoton/bin/phfontFA 12r RECEIVE 1
274454 1 on/bin/io-graphics 12r REPLY 196626 274454 1
on/bin/io-graphics 12r REPLY 196626
446487 1 r/photon/bin/shelf 10r RECEIVE 1 446487 1
r/photon/bin/shelf 10r RECEIVE 1
446487 2 r/photon/bin/shelf 10r CONDVAR b049aacc 446487 2
r/photon/bin/shelf 10r CONDVAR b049aacc
290840 1 ton/bin/devi-hirun 15o RECEIVE 1 290840 1
ton/bin/devi-hirun 15o RECEIVE 1
290840 2 ton/bin/devi-hirun 10o REPLY 7 290840 2
ton/bin/devi-hirun 10o REPLY 7
290840 3 ton/bin/devi-hirun 12o SIGWAITINFO 290840 3
ton/bin/devi-hirun 12o SIGWAITINFO
483353 1 photon/bin/bkgdmgr 10r RECEIVE 1 483353 1
photon/bin/bkgdmgr 10r RECEIVE 1
483354 1 hoton/bin/wmswitch 10r RECEIVE 2 483354 1
hoton/bin/wmswitch 10r RECEIVE 2
483355 1 r/photon/bin/saver 10r RECEIVE 1 483355 1
r/photon/bin/saver 10r RECEIVE 1
1011740 1 usr/sbin/fs-cifs 10r RECEIVE 1 1011740 1
usr/sbin/fs-cifs 15r RECEIVE 1
1011740 2 usr/sbin/fs-cifs 10r READY 1011740 2
usr/sbin/fs-cifs 10r REPLY 999436?!
1011740 3 usr/sbin/fs-cifs 10r RECEIVE 1 1011740 3
usr/sbin/fs-cifs 10r RECEIVE 1
483357 1 /X11R6/bin/Xphoton 10r SIGWAITINFO 1011740 4
usr/sbin/fs-cifs 10r RECEIVE 1
561182 1 r/photon/bin/pterm 10r RECEIVE 1 1011740 5
usr/sbin/fs-cifs 10r RECEIVE 1
561183 1 bin/sh 10r REPLY 45067 483357 1
/X11R6/bin/Xphoton 10r SIGWAITINFO
1073184 1 bin/pidin 10r REPLY 1 561182 1
r/photon/bin/pterm 10r RECEIVE 1
712737 1 usr/photon/bin/ped 10r REPLY 196626 561183 1 bin/sh
10r REPLY 45067
593954 1 usr/photon/bin/pfm 10r REPLY 196626 1105952 1
bin/pidin 10r REPLY 1
593954 2 usr/photon/bin/pfm 10r REPLY 1011740 712737 1
usr/photon/bin/ped 10r REPLY 196626
725027 1 r/photon/bin/pterm 10r RECEIVE 1 593954 1
usr/photon/bin/pfm 10r REPLY 196626
725028 1 bin/sh 10r REPLY 45067 593954 2
usr/photon/bin/pfm 10r REPLY 1011740
892965 1 usr/photon/bin/pfm 10r REPLY 196626 725027 1
r/photon/bin/pterm 10r RECEIVE 1
725028 1 bin/sh
10r REPLY 45067



“Weijie Zhang” <wzhang@qnx.com> дÈëÏûÏ¢ÐÂÎÅ:al86ad$ho0$1@nntp.qnx.com

“johnson zhou” <> jszhou@yahoo.com> > wrote in message
news:al4jff$hgp$> 1@inn.qnx.com> …
Hi,
I have a question related to windows98.
i use fs-cifs mount a networks image on windows98 or windows me just
like
this:
#fs-cifs //server:192.168.0.119:/tools /win98 my_name 123456
it’s ok.i can “ls” this dir and i can copy files (read and write).
but when i test the trans speed ,i copy a big file(about 100M) from qnx
to
win98 or from win98 to qnx,
I found the io-net dead when i copy about 3M bytes(if the os is windows
xp,it would be 20M byte. ).
The same thing happened when i run ftp to trans data to a ftp server on
windows 98.

You said the io-net dead. Does that mean the io-net crashed or
the fs-cifs/ftp were blocking on io-net? Can you provide us
the “pidin” output and, in case the io-net crashed, give us the core file.
(default cores are in /var/dumps/) Thanks.

Weijie

i have a rtl8139(c?) networks card and I config it like this:
#io-net -d rtl -p tcpip
#ifconfig en0 192.168.0.222

who can tell me why ?
what’s with my config?
thanks,
johnson.

\

Hi,
I know allmost the same problem while copying files on NT boxes except
that AFAIR I never saw io-net died, but fs-cifs very often!!! I stopped
to use fs-cifs.
Just one question: Are you using 6.1 or 6.2?

regards,
Alain.


johnson zhou a écrit:

Hi,
I have a question related to windows98.
i use fs-cifs mount a networks image on windows98 or windows me just like
this:
#fs-cifs //server:192.168.0.119:/tools /win98 my_name 123456
it’s ok.i can “ls” this dir and i can copy files (read and write).
but when i test the trans speed ,i copy a big file(about 100M) from qnx to
win98 or from win98 to qnx,
I found the io-net dead when i copy about 3M bytes(if the os is windows
xp,it would be 20M byte. ).
The same thing happened when i run ftp to trans data to a ftp server on
windows 98.
i have a rtl8139(c?) networks card and I config it like this:
#io-net -d rtl -p tcpip
#ifconfig en0 192.168.0.222

who can tell me why ?
what’s with my config?
thanks,
johnson.

\

Hi
I’m sure the io-net died because I “slay io-net” and restart it the copy
can continue.
I’m using 6.1.
thanks for your help!
regards
Johnson

“Alain Bonnefoy” <alain.bonnefoy@icbt.com>
???:3D7C3570.6090004@icbt.com

Hi,
I know allmost the same problem while copying files on NT boxes except
that AFAIR I never saw io-net died, but fs-cifs very often!!! I stopped
to use fs-cifs.
Just one question: Are you using 6.1 or 6.2?

regards,
Alain.


johnson zhou a écrit:

Hi,
I have a question related to windows98.
i use fs-cifs mount a networks image on windows98 or windows me just like
this:
#fs-cifs //server:192.168.0.119:/tools /win98 my_name 123456
it’s ok.i can “ls” this dir and i can copy files (read and write).
but when i test the trans speed ,i copy a big file(about 100M) from qnx
to
win98 or from win98 to qnx,
I found the io-net dead when i copy about 3M bytes(if the os is windows
xp,it would be 20M byte. ).
The same thing happened when i run ftp to trans data to a ftp server on
windows 98.
i have a rtl8139(c?) networks card and I config it like this:
#io-net -d rtl -p tcpip
#ifconfig en0 192.168.0.222

who can tell me why ?
what’s with my config?
thanks,
johnson.


\