OS/2 Networking under VMWare 2.0 beta?
Kendall Bennett
I am running the VMWare beta 2.0 build 444 release, and I now have OS/2
properly installed in the VM, have upgraded it to FP12 and have
installed the VMWare tools (ie: GRADD driver). The problem is that I
can't seem to get the networking components (NetBUI and NetBIOS)
working. The AMD PCNet family adapter driver is loading just fine, so I
have full TCP/IP access. However I don't have any networking that allows
me to connect to our Windows NT file servers (or my Win2K host system
drives). To get that going I need to use NetBUI.
When I boot the system, I get the following:
---- cut here ----
AMD PCNet Family Ethernet Adapter
NDIS v2.0.1 MAC Driver, Version 3.00
DriverName ......... PCNTND$
Station Address ... 00.50.56.A0.02.57
Driver Configuration.
IOAddress ......... 0x1000
Interrupt ......... 9
DMA ............... 0
Rx Buffers ........ 4
Tx Buffers ........ 4
SYS1201: The device driver C:\IBMCOM\PROTOCOL\NETBUI.OS2 specified in
the DEVICE statement
on line 109 of the CONFIG.SYS file was not installed. Line 109 is
ignored.
Press Enter to continue...
NET3406: An error occurred while opening network device driver NET1 =
NETBUI$.
SYS1719: The file C:\IBMLAN\NETPROG\NETWKSTA.200 specified in the IFS
statement
on line 111 of the CONFIG.SYS file does not contain a valid device
driver or file system driver. Line 111 is ignored.
Press Enter to continue...
SYS1201: The device driver C:\IBMCOM\PROTOCOL\NETBIOS.OS2 specified in
the DEVICE statement
on line 112 of the CONFIG.SYS file was not installed. Line 112 is
ignored.
Press Enter to continue...
SYS1201: The device driver C:\IBMCOM\PROTOCOL\LANVDD.OS2 specified in
the DEVICE statement
on line 122 of the CONFIG.SYS file was not installed. Line 122 is
ignored.
Press Enter to continue...
---- cut here ----
Obviously the trail of errors are all caused because the NETBUI.OS2
driver failed to load at the beginning of the sequence. Originally when
I installed OS/2 the AMD PCNet driver was *after* the NetBUI/NetBIOS
drivers in the CONFIG.SYS and I got this error, so I moved it before
those thinking it was a device driver ordering problem. However that did
not work either.
So, any ideas what is causing this, and how I can work around it? I have
OS/2 installed and working fine in a real partition on the same system
(Intel EtherExpress 100 mini PCI adapter in my docking station). However
I realise that probably does not mean much since OS/2 is running in a
virtual machine with different hardware to the stuff in my real machine
(ie: all virtual devices ;-).
I really want to get this going, since if I can get OS/2 running under
Windows 2000 nicely, then I can avoid having to reboot my system in
order to do builds of our OS/2 products!
Regards,
Peter Flass
>
> Hi Guys,
>
> I am running the VMWare beta 2.0 build 444 release, and I now have OS/2
> properly installed in the VM, have upgraded it to FP12 and have
> installed the VMWare tools (ie: GRADD driver). The problem is that I
> can't seem to get the networking components (NetBUI and NetBIOS)
> working.
VMWare now supports OS/2? When did this happen??
Marty
to NETBIOS over TCPIP. It forgot to update something in the net.cfg
file in mptn\etc (IIRC). Also, isn't it NETB*E*UI instead of NETBUI?
Make sure those files exist as it has named them. I'll check more when
I get home.
- Marty
Kendall Bennett
I am not trying to run NetBEUI over TCP/IP, just regular Windows
networking. Hence it is something more basic than trying to get it
running over TCP/IP.
Regards,
Kendall Bennett
> VMWare now supports OS/2? When did this happen??
They have a new 2.0 beta release that supports OS/2. Seems to work quite
well ;-)
Regards,
Marty
>
> ---- cut here ----
> AMD PCNet Family Ethernet Adapter
> NDIS v2.0.1 MAC Driver, Version 3.00
> DriverName ......... PCNTND$
> Station Address ... 00.50.56.A0.02.57
> Driver Configuration.
> IOAddress ......... 0x1000
> Interrupt ......... 9
> DMA ............... 0
> Rx Buffers ........ 4
> Tx Buffers ........ 4
> SYS1201: The device driver C:\IBMCOM\PROTOCOL\NETBUI.OS2 specified in
> the DEVICE statement
> on line 109 of the CONFIG.SYS file was not installed. Line 109 is
> ignored.
That's because there's no such file. The file is named NETBEUI.OS2 in that
directory. Did you mistype this or did it actually say this?
> NET3406: An error occurred while opening network device driver NET1 =
> NETBUI$.
Same here. It should be NETBEUI$. Everything after this point is just the
avalanche of errors resulting from this. ;-)
Also check that it is correct in your \ibmcom\protocol.ini.
- Marty
Brad Barclay
> I am not trying to run NetBEUI over TCP/IP, just regular Windows
> networking. Hence it is something more basic than trying to get it
> running over TCP/IP.
Regular Windows Networking *is* NetBIOS over TCP/IP, aka NetBEUI.
Brad BARCLAY
Marty
Nope. It's normally straight NetBEUI. NetBIOS over TCP/IP uses TCP/IP as its
carrier. In other words, to access a machine's share you don't use
//machinename/sharename (unless machinename can be resolved by your TCP/IP
nameserver), you'd use //ip/sharename. Believe me, I had it set up one way
and changed it over because the latter worked better. I think in Kendall's
case, the problem was a misspelling of the device driver name (unless he
reproduced the error message here incorrectly).
Paul Ratcliffe
>Kendall Bennett wrote:
>
>> I am not trying to run NetBEUI over TCP/IP, just regular Windows
>> networking. Hence it is something more basic than trying to get it
>> running over TCP/IP.
>
> Regular Windows Networking *is* NetBIOS over TCP/IP, aka NetBEUI.
No. Regular Windows networking is NetBios, aka NETBEUI.
Netbios over TCP/IP is also known as TCPBEUI.
Kendall Bennett
> > SYS1201: The device driver C:\IBMCOM\PROTOCOL\NETBUI.OS2 specified in
> > the DEVICE statement
> > on line 109 of the CONFIG.SYS file was not installed. Line 109 is
> > ignored.
>
> That's because there's no such file. The file is named NETBEUI.OS2 in that
> directory. Did you mistype this or did it actually say this?
Unfortunately I mispelt the name of the file (I just checked). I wish it
was that simple ;-(. I was not able to get a screen capture easily, so I
had to type in the error messages by hand ;-).
BTW, it appears that this is a known problem with VMWare at the moment
running the OS/2 client, and they are looking into the problem in order
to solve it.
Regards,