My QNX v4.25 distribution is patch C, it installs on my laptop with vmware cleanly. But when I try to apply patches D~G - the pkginstall SIGSEGVs. This is the first trouble…
The second one is - I have no TCP/IP connectivity from the guest to the host and from the guest to the real network and back.
I see VMnet0 as auto-bridged, there are no properties for that connection;
VMnet1 as host-only, 192.168.225.0, DHCP enabled;
VMnet8 as NAT, 192.168.150.0, DHCP enabled;
Since I need to reach the outer world and back from QNX guest - I must not use NAT, right?
My XP host is 192.168.0.2 obtained from DHCP (gw == dns == 192.168.0.1).
What should I set in the QNX? Any free address from the real network?
Currently if I set ifconfig en1 192.168.0.111 - there is no even a ping to 192.168.0.2 or any other non-guest IP. When pinging the same subnet IP - 100% loss, when trying to ping other subnets - “No route to host” errors are here…
Please comment.
Where to start from, what to read first, any help is wellcome!
My QNX v4.25 distribution is patch C, it installs on my laptop with vmware
cleanly. But when I try to apply patches D~G - the pkginstall SIGSEGVs.
This is the first trouble…
I’m fairly confident it’s not VMware.
Me too, since this is the only programm that does so…
What should I set in the QNX? Any free address from the real network?
Use dhcp.client in QNX, it will get the ip address from the dhcp server
(along with all the gw and dns info)
I was never able to use dhcp.client in TCP/IP v4.25C successfully. Even in the true-QNX environment.
Currently if I set ifconfig en1 192.168.0.111 - there is no even a ping to
192.168.0.2 or any other non-guest IP. When pinging the same subnet IP -
100% loss, when trying to ping other subnets - “No route to host” errors
are here…
What does netinfo -l says after the ping.
Be right back…
Maybe something went wrong with the install (i’ve seen it happen even in non
VMWare environment)
No, I did not notice anything suspitious during the install…
I’m stupid enough to not understand where the VMnet1 adapter is located - whether it is in the virtual machine or it is in the host machine.
If it’s in the guest machine - what is it’s host’s counterpart? It takes two to tango… Where it’s virtual “twisted-pair cable” goes? It must be plugged somewhere - that’s what I expect.
What does netinfo -l says after the ping.
Total Number Of Net Driver Slots: 2
Driver Slot 0: Driver Pid 40 Logical Net 1 Network Card: Ethernet/
NE2100 Ethernet Controller
Vendor ID … 0x1022
Device ID … 0x0
Revision … 0x0
Physical Node ID … 000C29 11B302
Media Rate … 10Mb/s
Mtu … 1514
I/O Port Range … 0x1080 → 0x109F
Hardware Interrupt … 10
Total Packets Txd OK … 0
Total Packets Txd Bad … 0
Tx Collision Errors … 0
Tx Collision Errors (aborted) … 0
Carrier Sense Lost on Tx … 0
FIFO Underruns During Tx … 0
Tx deferred … 0
Out of Window Collisions … 0
Total Packets Rxd OK … 0
Total Rx Errors … 24
FIFO Overruns During Rx … 0
Alignment errors … 0
CRC errors … 0
Driver Slot 1: Unused
All I can see is that RX errors counter increases…
My QNX v4.25 distribution is patch C, it installs on my laptop with vmware
cleanly. But when I try to apply patches D~G - the pkginstall SIGSEGVs.
This is the first trouble…
I’m fairly confident it’s not VMware.
The second one is - I have no TCP/IP connectivity from the guest to the
host and from the guest to the real network and back.
I see VMnet0 as auto-bridged, there are no properties for that connection;
VMnet1 as host-only, 192.168.225.0, DHCP enabled;
VMnet8 as NAT, 192.168.150.0, DHCP enabled;
Since I need to reach the outer world and back from QNX guest - I must not
use NAT, right?
My XP host is 192.168.0.2 obtained from DHCP (gw == dns == 192.168.0.1).
What should I set in the QNX? Any free address from the real network?
Use dhcp.client in QNX, it will get the ip address from the dhcp server
(along with all the gw and dns info)
Currently if I set ifconfig en1 192.168.0.111 - there is no even a ping to
192.168.0.2 or any other non-guest IP. When pinging the same subnet IP -
100% loss, when trying to ping other subnets - “No route to host” errors
are here…
What does netinfo -l says after the ping.
Please comment.
Where to start from, what to read first, any help is wellcome!
Maybe something went wrong with the install (i’ve seen it happen even in non
VMWare environment)
Desperatelly I installed win98 into a virtual machine just to see if I will be able to connect to it.
It (win98) worked fine and I now understand both - how does it work and why everyone is surprized that I have any problems with vmware at all…
Seems I did everything with QNX v4.25C in vmware right. Now I think that I must try to update it to patch G and TCP/IP v425D (at least) or try using TCP/IP v5.0
I wonder how other people manage even to use FLEET under vmware!
Desperatelly I installed win98 into a virtual machine just to see if I will be able to connect to it.
It (win98) worked fine and I now understand both - how does it work and why everyone is surprized that I have any problems with vmware at all…
Seems I did everything with QNX v4.25C in vmware right. Now I think that I must try to update it to patch G and TCP/IP v425D (at least) or try using TCP/IP v5.0
I wonder how other people manage even to use FLEET under vmware!
Desperatelly I installed win98 into a virtual machine just to see if I
will be able to connect to it.
It (win98) worked fine and I now understand both - how does it work and
why everyone is surprized that I have any problems with vmware at all…
Seems I did everything with QNX v4.25C in vmware right. Now I think that
I must try to update it to patch G and TCP/IP v425D (at least) or try
using TCP/IP v5.0
I wonder how other people manage even to use FLEET under vmware!
It worked for me!
I was pleasantly surprised.
Now if there was a way to use a floppy with it with
a QNX4 filesystem on the floppy…
One way would be to use it via FLEET, but that’s not
ideal.
Every time I try scanning the archives with pkginstall it blows at 0005:000566B9.
However, all the contents of the distribution CD is accessible and can be [un]installed according to the licenses available. The SIGSEGV happens if I try scanning the *.tarx on the HDD or the self-composed CDROM. (I had to copy phinstall and pkginstall to /bin to be able to run them without the original distribution CDROM. When I replace the CD in the drive - the old listing gets stuck in the file selection dialog of pkginstall, no matter what I do.)
Tony.
BTW The original distribution CDROM has some strange file system on it - the correct form of the file names is seen only from within QNX, if I try reading it in windoze (any version) I see trunkated names…
If I write a CDROM with Joliet - I can’t read the proper file names with Fsys v4.24T and Iso9660fsys v4.23B.
How to write a CDROM so it can be read with QNX v4.25 patch level C?
BTW The original distribution CDROM has some strange file system on it -
the correct form of the file names is seen only from within QNX, if I
try reading it in windoze (any version) I see trunkated names…
If I write a CDROM with Joliet - I can’t read the proper file names with
Fsys v4.24T and Iso9660fsys v4.23B.
Iso9660fsys supports Joliet from version 4.23C onwards (so previous
versions will revert back to the ISO9660 volume descriptor on the CD;
actually given that Windows can’t see longer names I assume it is
actually RRIP). [A CD can have multiple directory hierarchies on it:
ISO9660, RIP, and Joliet, so an OS can pick the one it understands]
Note also that QNX4 readdir message enforces a 48-character filename
limit on all filesystems (which affects FAT32 Fatfsys and Joliet
Iso9660fsys, requiring them to truncate filenames for ls, but should be
display-only, they can still be opened with the full name; this was
added to Iso9660fsys version 4.23D).
I’m stupid enough to not understand where the VMnet1 adapter is located -
whether it is in the virtual machine or it is in the host machine.
VMnet1 and 8 are only use if you NAT, they represent each side of the
gateway. VMnet1 is connected to the VM and VMnet8 is connected to the
physical network, both are virtual NIC.
If you used bridge network, VMNet0 is use and it’s a virtual NIC, but it’s
directly connected to the physical network, just like if there was a small
hub inside your PC
If it’s in the guest machine - what is it’s host’s counterpart? It takes
two to tango… Where it’s virtual “twisted-pair cable” goes? It must be
plugged somewhere - that’s what I expect.
Desperatelly I installed win98 into a virtual machine just to see if I
will be able to connect to it.
It (win98) worked fine and I now understand both - how does it work and
why everyone is surprized that I have any problems with vmware at all…
Seems I did everything with QNX v4.25C in vmware right. Now I think that I
must try to update it to patch G and TCP/IP v425D (at least) or try using
TCP/IP v5.0
I wonder how other people manage even to use FLEET under vmware!
If you use bridge networking, it’s totaly transparent.
Seems the networking problems were caused by TCP/IP v4.25C - I made a bruteforce update (got everything to tar.gz on my regular system and unpacked it into a virtual machine) to TCP/IP v4.25D - now it works…
Every time I try scanning the archives with pkginstall it blows at 0005:000566B9.
I was stupid enough not to notice that during the copying the filenames of *.tarx got “_” instead of “.” and “-” - after I renamed all the files correctly - pkginstall works fine.
Sorry for interrupting you!
