Has anyone successfully used Dev.net with Qnx4 32 bit devices to Qnx2
over the arcnet interface. I have a version that works with 16bit
devices.
Padraig Furlong
“Padraig Furlong” <Padraig.Furlong@rte.ie> wrote in message
news:3C874851.9FEF073D@rte.ie…
Has anyone successfully used Dev.net with Qnx4 32 bit devices to Qnx2
over the arcnet interface. I have a version that works with 16bit
devices.
I don’t remember if we ever got a Dev32.net. However, are you aware that
you can run Dev16 as well as Dev32? You can then use Dev32 for all your
“standard” devices, and run Dev16 with a different prefix to handle Dev.net.
Regards,
Bert Menkveld
Engineer
Corman Technologies Inc.
Bert,
I had thought of that, Dev.net has no argument to specify the name for Dev16 -
Defaults to Dev32 where Dev32 controls /dev
Padraig
Bert Menkveld wrote:
“Padraig Furlong” <> Padraig.Furlong@rte.ie> > wrote in message
news:> 3C874851.9FEF073D@rte.ie> …
Has anyone successfully used Dev.net with Qnx4 32 bit devices to Qnx2
over the arcnet interface. I have a version that works with 16bit
devices.I don’t remember if we ever got a Dev32.net. However, are you aware that
you can run Dev16 as well as Dev32? You can then use Dev32 for all your
“standard” devices, and run Dev16 with a different prefix to handle Dev.net.Regards,
Bert Menkveld
Engineer
Corman Technologies Inc.
I vaguely recall setting up Dev32.net and having something very bad
happen. I ended up going back to Dev16.net. This was some time ago,
so I’m not all that sure of what happened.
Previously, Bert Menkveld wrote in qdn.public.qnx2:
“Padraig Furlong” <> Padraig.Furlong@rte.ie> > wrote in message
news:> 3C874851.9FEF073D@rte.ie> …
Has anyone successfully used Dev.net with Qnx4 32 bit devices to Qnx2
over the arcnet interface. I have a version that works with 16bit
devices.I don’t remember if we ever got a Dev32.net. However, are you aware that
you can run Dev16 as well as Dev32? You can then use Dev32 for all your
“standard” devices, and run Dev16 with a different prefix to handle Dev.net.Regards,
Bert Menkveld
Engineer
Corman Technologies Inc.
\
–
Mitchell Schoenbrun --------- maschoen@pobox.com
“Padraig Furlong” <Padraig.Furlong@rte.ie> wrote in message
news:3C88EF68.AFCA9F4E@rte.ie…
Bert,
I had thought of that, Dev.net has no argument to specify the name for
Dev16 -
Defaults to Dev32 where Dev32 controls /dev
Hmmm, I had forgotten that (it has been a while since I’ve looked at this
stuff…). I just had a look at our setup, and the solution we used is
quite simple: we only run Dev16, and use all the 16-bit versions of the Dev
drivers.
If you have some drivers that only come in 32-bit flavours, you could always
run Dev32 as a second Dev with a non-default prefix.
Or, you could beg QNX to see if they’ll fix Dev32.net. Maybe they’ll give
you the source and you can make the changes for the rest of us… 
Regards,
Bert Menkveld
Padraig
Bert Menkveld wrote:
“Padraig Furlong” <> Padraig.Furlong@rte.ie> > wrote in message
news:> 3C874851.9FEF073D@rte.ie> …
Has anyone successfully used Dev.net with Qnx4 32 bit devices to Qnx2
over the arcnet interface. I have a version that works with 16bit
devices.I don’t remember if we ever got a Dev32.net. However, are you aware
that
you can run Dev16 as well as Dev32? You can then use Dev32 for all your
“standard” devices, and run Dev16 with a different prefix to handle
Dev.net.Regards,
Bert Menkveld
Engineer
Corman Technologies Inc.
Hi,
I found a solution. Start the 16 bit device manager as
Dev16 -N/d16 &
use spatch on Dev.net
spatch /bin/Dev.net
change address ABD to 0x31 and ABE to 0x36
save
This changes the default device directory to /d16
run Dev16 -c8 -n9 &
the Qnx2 system is on node 9. The qnx4 system is on node 41
This creates the following entriesin /d16
net1
net2
net3
net4
net5
net6
net7
net8
On qnx2 run netdev -c8 -n41 &
qtalk operates between the two PCs
Many thanks for your help. I have attached the modified Dev.net called
RteDev.net in RteDev.net.tar.F. Extract using the qnx ‘install’ or ‘melt
<RteDev.net.tar.F | pax -rv’
Padraig Furlong
Bert Menkveld wrote:
“Padraig Furlong” <> Padraig.Furlong@rte.ie> > wrote in message
news:> 3C88EF68.AFCA9F4E@rte.ie> …
Bert,
I had thought of that, Dev.net has no argument to specify the name for
Dev16 -
Defaults to Dev32 where Dev32 controls /devHmmm, I had forgotten that (it has been a while since I’ve looked at this
stuff…). I just had a look at our setup, and the solution we used is
quite simple: we only run Dev16, and use all the 16-bit versions of the Dev
drivers.If you have some drivers that only come in 32-bit flavours, you could always
run Dev32 as a second Dev with a non-default prefix.Or, you could beg QNX to see if they’ll fix Dev32.net. Maybe they’ll give
you the source and you can make the changes for the rest of us… >Regards,
Bert Menkveld
PadraigBert Menkveld wrote:
“Padraig Furlong” <> Padraig.Furlong@rte.ie> > wrote in message
news:> 3C874851.9FEF073D@rte.ie> …
Has anyone successfully used Dev.net with Qnx4 32 bit devices to Qnx2
over the arcnet interface. I have a version that works with 16bit
devices.I don’t remember if we ever got a Dev32.net. However, are you aware
that
you can run Dev16 as well as Dev32? You can then use Dev32 for all your
“standard” devices, and run Dev16 with a different prefix to handle
Dev.net.Regards,
Bert Menkveld
Engineer
Corman Technologies Inc.
Now that is a truly pragmatic solution – definitely in the spirit of QNX 2!
Why use all those fancy compilers when all you really need is spatch?
Thanks for sharing your innovative fix with the rest of us.
Regards,
Bert Menkveld
Engineer
Corman Technologies Inc.
“Padraig Furlong” <Padraig.Furlong@rte.ie> wrote in message
news:3CA9977F.AA1BC261@rte.ie…
Hi,
I found a solution. Start the 16 bit device manager as
Dev16 -N/d16 &use spatch on Dev.net
spatch /bin/Dev.net
change address ABD to 0x31 and ABE to 0x36
save
This changes the default device directory to /d16run Dev16 -c8 -n9 &
the Qnx2 system is on node 9. The qnx4 system is on node 41
This creates the following entriesin /d16
net1
net2
net3
net4
net5
net6
net7
net8On qnx2 run netdev -c8 -n41 &
qtalk operates between the two PCs
Many thanks for your help. I have attached the modified Dev.net called
RteDev.net in RteDev.net.tar.F. Extract using the qnx ‘install’ or ‘melt
RteDev.net.tar.F | pax -rv’
Padraig Furlong