Pccard server

I have been looking up posts on using ethernet cardbus/pcmcia cards with the
pccard server contained in 4.25G. I have the following questions

  1. Hugh says that the 3CXFE575BT is supported, but this card has now been
    replaced by the …575CT, does this card work OK ?

  2. Is the pccard server in 4.25G (which I do not have) the same as the
    down-loadable one ?

  3. Does the D-Link DFE-660TX work with the pccard server as mentioned in a
    previous post ?

I have to resolve these problems in order to purchase some spares for some
mission-critical legacy systems based on Allen Bradley Open Controllers. The
3com cards I originally used (3CCE589ET) are now obsolete. We got hold of a
recent 3CCE589EC but have discovered that it does not work with the pccard
server !

Hope someone can help resolve this problem

Ray Threadgould

Previously, Ray Threadgould wrote in qdn.public.qnx4:

I have been looking up posts on using ethernet cardbus/pcmcia cards with the
pccard server contained in 4.25G. I have the following questions

  1. Hugh says that the 3CXFE575BT is supported, but this card has now been
    replaced by the …575CT, does this card work OK ?

The 575C should be compatible with the 575B, but I have not tested the C
version.

  1. Is the pccard server in 4.25G (which I do not have) the same as the
    down-loadable one ?

No, the 4.25G version has some fixes that are not in the developers corner
version.

  1. Does the D-Link DFE-660TX work with the pccard server as mentioned in a
    previous post ?

The DFE-660 is not supported under QNX4, only under QNX6.

I have to resolve these problems in order to purchase some spares for some
mission-critical legacy systems based on Allen Bradley Open Controllers. The
3com cards I originally used (3CCE589ET) are now obsolete. We got hold of a
recent 3CCE589EC but have discovered that it does not work with the pccard
server !

Hope someone can help resolve this problem

Ray Threadgould

When will I be able to get 4.25G (I am not a beta tester)

Ray

Hugh Brown <hsbrown@qnx.com> wrote in message
news:Voyager.030124095620.29334A@node90.ott.qnx.com

Previously, Ray Threadgould wrote in qdn.public.qnx4:
I have been looking up posts on using ethernet cardbus/pcmcia cards with
the
pccard server contained in 4.25G. I have the following questions

  1. Hugh says that the 3CXFE575BT is supported, but this card has now
    been
    replaced by the …575CT, does this card work OK ?


    The 575C should be compatible with the 575B, but I have not tested the C
    version.

  2. Is the pccard server in 4.25G (which I do not have) the same as the
    down-loadable one ?


    No, the 4.25G version has some fixes that are not in the developers corner
    version.

  3. Does the D-Link DFE-660TX work with the pccard server as mentioned in
    a
    previous post ?


    The DFE-660 is not supported under QNX4, only under QNX6.

I have to resolve these problems in order to purchase some spares for
some
mission-critical legacy systems based on Allen Bradley Open Controllers.
The
3com cards I originally used (3CCE589ET) are now obsolete. We got hold
of a
recent 3CCE589EC but have discovered that it does not work with the
pccard
server !

Hope someone can help resolve this problem

Ray Threadgould
\

Just subscribe here http://qdn.qnx.com/beta/form.html, it’s easy and you’ll
be able to test any beta you submit for.

Denis


“Ray Threadgould” <microcon@globalnet.co.uk> a écrit dans le message de
news: b15g2c$ca8$1@inn.qnx.com

When will I be able to get 4.25G (I am not a beta tester)

Ray

Hugh Brown <> hsbrown@qnx.com> > wrote in message
news:> Voyager.030124095620.29334A@node90.ott.qnx.com> …
Previously, Ray Threadgould wrote in qdn.public.qnx4:
I have been looking up posts on using ethernet cardbus/pcmcia cards
with
the
pccard server contained in 4.25G. I have the following questions

  1. Hugh says that the 3CXFE575BT is supported, but this card has now
    been
    replaced by the …575CT, does this card work OK ?


    The 575C should be compatible with the 575B, but I have not tested the C
    version.

  2. Is the pccard server in 4.25G (which I do not have) the same as the
    down-loadable one ?


    No, the 4.25G version has some fixes that are not in the developers
    corner
    version.

  3. Does the D-Link DFE-660TX work with the pccard server as mentioned
    in
    a
    previous post ?


    The DFE-660 is not supported under QNX4, only under QNX6.

I have to resolve these problems in order to purchase some spares for
some
mission-critical legacy systems based on Allen Bradley Open
Controllers.
The
3com cards I originally used (3CCE589ET) are now obsolete. We got hold
of a
recent 3CCE589EC but have discovered that it does not work with the
pccard
server !

Hope someone can help resolve this problem

Ray Threadgould


\

Hugh I need your help to explain DFE-660 nework card matter.
Is or isn’t D-Link DFE 660 TX supported by QNX 4?

You told:
“The DFE-660 is not supported under QNX4, only under QNX6.”

I have installed QNX 4.25 patch G release on Toshiba Satellite 2410-303
model.
D-Link DFE-660TX pccrad works fine for me with this notebook.

As a proof I attached output from several system commands.

sin ver

PROGRAM NAME VERSION DATE
/boot/sys/Proc32 Proc 4.25O Aug 19 2002
/boot/sys/Proc32 Slib16 4.23G Oct 04 1996
/boot/sys/Slib32 Slib32 4.24B Aug 12 1997
/bin/Fsys Fsys32 4.24Y Apr 23 2002
/bin/Fsys Floppy 4.24B Aug 19 1997
/bin/Fsys.eide eide 4.25G Apr 15 2002
//1/bin/Dev32 Dev32 4.23G Oct 04 1996
//1/bin/Pipe Pipe 4.23A Feb 26 1996
//1/bin/Dev32.ansi Dev32.ansi 4.23H Nov 21 1996
//1/bin/Dev32.par Dev32.par 4.25A Jan 08 2001
//1/bin/Dev32.pty Dev32.pty 4.23G Oct 04 1996
//1/bin/Fsys.eide eide 4.25G Apr 15 2002
//1/bin/Iso9660fsys Iso9660fsys 4.23D Mar 20 2000
//1/bin/pccard PcCard 4.25A May 09 2002
//1/bin/Net Net 4.25E Apr 24 2002
//1/bin/Net.tulip Net.tulip 4.25Q Aug 30 1999
//1/bin/Dosfsys Dosfsys 4.23E Jan 21 1997

ps -a

PID PGRP SID PRI STATE BLK SIZE COMMAND
1 1 0 30f READY 262066K /boot/sys/Proc32 -l 1
2 2 0 10r RECV 0 108K /boot/sys/Slib32
4 4 0 10r RECV 0 218508K /bin/Fsys
5 5 0 22r RECV 0 72964K /bin/Fsys.eide
fsys -Ndsk0 -n0=hd0. -n5=cd0. eide -a1f0 -i14
8 8 0 0r READY 40K (idle)
16 7 0 24f RECV 0 392K Dev
21 7 0 10r RECV 0 32K Pipe
25 7 0 20r RECV 0 472K Dev.ansi -Q -n9
29 7 0 9o RECV 0 148K Dev.par
30 16 0 20r RECV 0 316K Dev.pty -n16
34 32 0 22r RECV 0 72964K /bin/Fsys.eide
fsys -Ndsk1 -n0=hd1. -n5=cd1. eide -a170 -i15
36 4 0 10o RECV 0 36364K /bin/Fsys.floppy -a3f0 -i6
37 7 0 10o RECV 0 56K /bin/Iso9660fsys /cd1.0
40 7 0 20o RECV 0 20K nameloc
41 7 0 20o REPLY 0 16K nameloc
44 7 0 10o WAIT -1 28K tinit -t /dev/con1
45 7 0 10o RECV 0 20K tinit -T /dev/con2 /dev/con3 /dev/con4
/dev/con5 /dev/con6 /dev/con7 /dev/con8 /dev/con9
46 46 1 10o WAIT -1 44K -sh
57 56 1 20o RECV 0 120K pccard -v
66 46 1 23r RECV 0 240K Net
77 46 1 20r RECV 0 260K Net.tulip -c21143 -I0 -l1
1979 46 1 10o REPLY 1 24K ps
1494 46 1 10o RECV 0 120K Dosfsys

pc-pin

Sock Func Type Flags PID Base Size IRQ
1 Empty ----MF---------- None
1 Empty ----MF---------- None
2 0 Network C—I-±-----SAW None 0x1000 256 11
0x10100000 4096
2 Empty ----MF---------- None

pc-pin cis

Socket : 2 - Function : 0
Link Target : ‘CIS’
Manufacturer ID : 0x149 0x231
PC Card function : Network LAN Adapter
POST : 0x1
Tuple 0x22 link=2 : 01 02
Tuple 0x22 link=5 : 02 80 96 98 00
Tuple 0x22 link=5 : 02 00 e1 f5 05
Tuple 0x22 link=2 : 03 01
Card tuple version : 5.00
Manufacturer : D-Link
Name of Product : DFE-660
Add’nl info (lot #) : CardBus Ethernet
Add’nl info (programming): 10/100
Tuple 0x04 link=6 : 03 01 2a 00 00 00
Tuple 0x07 link=6 : 11 00 80 00 00 00
Tuple 0x07 link=6 : 02 00 80 00 00 00
Tuple 0x07 link=6 : 07 00 00 02 00 00
Tuple 0x05 link=10 : 41 39 01 b5 1e 02 b0 fc
: fe 84
Link Target : ‘CIS’
Manufacturer ID : 0x149 0x231
PC Card function : Network LAN Adapter
POST : 0x1
Tuple 0x22 link=2 : 01 02
Tuple 0x22 link=5 : 02 80 96 98 00
Tuple 0x22 link=5 : 02 00 e1 f5 05
Tuple 0x22 link=2 : 03 01
Card tuple version : 5.00
Manufacturer : D-Link
Name of Product : DFE-660
Add’nl info (lot #) : CardBus Ethernet
Add’nl info (programming): 10/100
Tuple 0x04 link=6 : 03 01 2a 00 00 00
Tuple 0x07 link=6 : 11 00 80 00 00 00
Tuple 0x07 link=6 : 02 00 80 00 00 00
Tuple 0x07 link=6 : 07 00 00 02 00 00
Tuple 0x05 link=10 : 41 39 01 b5 1e 02 b0 fc
: fe 84

I made a couple of tests in QNX Network (copy files, etc…) without
any problems. Broadcast by TCP/IP protocol to the Windows host
machines also works fine (ping command).

netmap

Logical Lan Physical TX Count Last TX Fail Time

1 1 0050BA 7D61D5 ; 0
1 2 t0 ; 0
3 1 002018 5877B1 ; 1492

sin net

Nid Machine Cpu Fpu Speed Memory Hard Flop Other Display Flags
1 PCI 1586 1587 39146 267.8M 1.4M VGA
Color -3+±—8P
3 PCI 586 587 28657 33.1M 13415M 1.4M TCP VGA
Color -3+±—8P


67803 301M 13415M

alive

Node Status
1: Up 3: Up


I think that D-Link DFE 660 network card is only supported
by computers equiped with new PCMCIA/PC Card controllers.
Moreover Toshiba BIOS has possibility to change controller
type. To work with D-Link card I switched my PC Card
controller to “CardBus/16-bit” mode.


Regards,
Jacek

Previously, Jacek Rudnicki wrote in qdn.public.qnx4:

Hugh I need your help to explain DFE-660 nework card matter.
Is or isn’t D-Link DFE 660 TX supported by QNX 4?

You are lucky that the tulip driver works with your adapter. We have
only modified the Net.ether905 driver to work with CardBus adapters.
We could not afford the time to modify all of the QNX4 drivers to
work with PCCards.

Thanks for the information.

You told:
“The DFE-660 is not supported under QNX4, only under QNX6.”

I have installed QNX 4.25 patch G release on Toshiba Satellite 2410-303
model.
D-Link DFE-660TX pccrad works fine for me with this notebook.

As a proof I attached output from several system commands.

sin ver

PROGRAM NAME VERSION DATE
/boot/sys/Proc32 Proc 4.25O Aug 19 2002
/boot/sys/Proc32 Slib16 4.23G Oct 04 1996
/boot/sys/Slib32 Slib32 4.24B Aug 12 1997
/bin/Fsys Fsys32 4.24Y Apr 23 2002
/bin/Fsys Floppy 4.24B Aug 19 1997
/bin/Fsys.eide eide 4.25G Apr 15 2002
//1/bin/Dev32 Dev32 4.23G Oct 04 1996
//1/bin/Pipe Pipe 4.23A Feb 26 1996
//1/bin/Dev32.ansi Dev32.ansi 4.23H Nov 21 1996
//1/bin/Dev32.par Dev32.par 4.25A Jan 08 2001
//1/bin/Dev32.pty Dev32.pty 4.23G Oct 04 1996
//1/bin/Fsys.eide eide 4.25G Apr 15 2002
//1/bin/Iso9660fsys Iso9660fsys 4.23D Mar 20 2000
//1/bin/pccard PcCard 4.25A May 09 2002
//1/bin/Net Net 4.25E Apr 24 2002
//1/bin/Net.tulip Net.tulip 4.25Q Aug 30 1999
//1/bin/Dosfsys Dosfsys 4.23E Jan 21 1997

ps -a

PID PGRP SID PRI STATE BLK SIZE COMMAND
1 1 0 30f READY 262066K /boot/sys/Proc32 -l 1
2 2 0 10r RECV 0 108K /boot/sys/Slib32
4 4 0 10r RECV 0 218508K /bin/Fsys
5 5 0 22r RECV 0 72964K /bin/Fsys.eide
fsys -Ndsk0 -n0=hd0. -n5=cd0. eide -a1f0 -i14
8 8 0 0r READY 40K (idle)
16 7 0 24f RECV 0 392K Dev
21 7 0 10r RECV 0 32K Pipe
25 7 0 20r RECV 0 472K Dev.ansi -Q -n9
29 7 0 9o RECV 0 148K Dev.par
30 16 0 20r RECV 0 316K Dev.pty -n16
34 32 0 22r RECV 0 72964K /bin/Fsys.eide
fsys -Ndsk1 -n0=hd1. -n5=cd1. eide -a170 -i15
36 4 0 10o RECV 0 36364K /bin/Fsys.floppy -a3f0 -i6
37 7 0 10o RECV 0 56K /bin/Iso9660fsys /cd1.0
40 7 0 20o RECV 0 20K nameloc
41 7 0 20o REPLY 0 16K nameloc
44 7 0 10o WAIT -1 28K tinit -t /dev/con1
45 7 0 10o RECV 0 20K tinit -T /dev/con2 /dev/con3 /dev/con4
/dev/con5 /dev/con6 /dev/con7 /dev/con8 /dev/con9
46 46 1 10o WAIT -1 44K -sh
57 56 1 20o RECV 0 120K pccard -v
66 46 1 23r RECV 0 240K Net
77 46 1 20r RECV 0 260K Net.tulip -c21143 -I0 -l1
1979 46 1 10o REPLY 1 24K ps
1494 46 1 10o RECV 0 120K Dosfsys

pc-pin

Sock Func Type Flags PID Base Size IRQ
1 Empty ----MF---------- None
1 Empty ----MF---------- None
2 0 Network C—I-±-----SAW None 0x1000 256 11
0x10100000 4096
2 Empty ----MF---------- None

pc-pin cis

Socket : 2 - Function : 0
Link Target : ‘CIS’
Manufacturer ID : 0x149 0x231
PC Card function : Network LAN Adapter
POST : 0x1
Tuple 0x22 link=2 : 01 02
Tuple 0x22 link=5 : 02 80 96 98 00
Tuple 0x22 link=5 : 02 00 e1 f5 05
Tuple 0x22 link=2 : 03 01
Card tuple version : 5.00
Manufacturer : D-Link
Name of Product : DFE-660
Add’nl info (lot #) : CardBus Ethernet
Add’nl info (programming): 10/100
Tuple 0x04 link=6 : 03 01 2a 00 00 00
Tuple 0x07 link=6 : 11 00 80 00 00 00
Tuple 0x07 link=6 : 02 00 80 00 00 00
Tuple 0x07 link=6 : 07 00 00 02 00 00
Tuple 0x05 link=10 : 41 39 01 b5 1e 02 b0 fc
: fe 84
Link Target : ‘CIS’
Manufacturer ID : 0x149 0x231
PC Card function : Network LAN Adapter
POST : 0x1
Tuple 0x22 link=2 : 01 02
Tuple 0x22 link=5 : 02 80 96 98 00
Tuple 0x22 link=5 : 02 00 e1 f5 05
Tuple 0x22 link=2 : 03 01
Card tuple version : 5.00
Manufacturer : D-Link
Name of Product : DFE-660
Add’nl info (lot #) : CardBus Ethernet
Add’nl info (programming): 10/100
Tuple 0x04 link=6 : 03 01 2a 00 00 00
Tuple 0x07 link=6 : 11 00 80 00 00 00
Tuple 0x07 link=6 : 02 00 80 00 00 00
Tuple 0x07 link=6 : 07 00 00 02 00 00
Tuple 0x05 link=10 : 41 39 01 b5 1e 02 b0 fc
: fe 84

I made a couple of tests in QNX Network (copy files, etc…) without
any problems. Broadcast by TCP/IP protocol to the Windows host
machines also works fine (ping command).

netmap

Logical Lan Physical TX Count Last TX Fail Time

1 1 0050BA 7D61D5 ; 0
1 2 t0 ; 0
3 1 002018 5877B1 ; 1492

sin net

Nid Machine Cpu Fpu Speed Memory Hard Flop Other Display Flags
1 PCI 1586 1587 39146 267.8M 1.4M VGA
Color -3+±—8P
3 PCI 586 587 28657 33.1M 13415M 1.4M TCP VGA
Color -3+±—8P


67803 301M 13415M

alive

Node Status
1: Up 3: Up


I think that D-Link DFE 660 network card is only supported
by computers equiped with new PCMCIA/PC Card controllers.
Moreover Toshiba BIOS has possibility to change controller
type. To work with D-Link card I switched my PC Card
controller to “CardBus/16-bit” mode.


Regards,
Jacek