Page 1 of 1
TCPLIB ERROR with WG2.0 and VMWare
Posted: Tue Aug 26, 2008 5:40 pm
by Talonp
Ok any help would be great guys
Running WG2.0 Dos on VMWare and I am getting the following error;
TCPLIB ERROR # 0xA accessing packet driver
CH01=:0/0,MSG : tcplibm.mcv/45
Anyone ever get this ....sorry to bug you guys but my eyes are crossing and not thinking clear hehe so I thought I would ask for help
Thanks again!
Talonp
Posted: Tue Aug 26, 2008 11:39 pm
by Questman
Do you have a packet driver (an appropriate one) installed within the VM DOS?
Posted: Wed Aug 27, 2008 12:45 am
by Talonp
I have the AMD Packet Drivers installed with the command line of
PCNTPK INT=0x60
and it appears to be working. Got the drivers from the link that was in the forums here for Packet Drivers.
Posted: Wed Aug 27, 2008 11:34 am
by VeNoM
That looks like the right syntax for the packet driver for VMWare.
When you issue that command, does it come back with a message saying that it's loaded, and give you the NIC's mac address? That's about the best way to tell if its actually loaded.
Are you using WG's built in ethernet capabilities? Or something like Vircomm's MajorTCP?
BTW, i've had quite a bit of trial and error experience in both WG2, and VMWare (and the two combined). if you run into any odd issues, feel free to PM me.
Posted: Wed Aug 27, 2008 1:12 pm
by Talonp
Yes the packet drivers are loading and getting the message
I am using WG2.0 DOS with MajorTCP/IP v2.22-4 and the AMD Packet Drivers v2.2
Everything seems to be loading fine until it hits that error and boom!
Posted: Wed Aug 27, 2008 2:12 pm
by VeNoM
When you installed WG, at the end of setup it asks you how you're connecting to the network. It lets you pick ethernet slip/ppp/whatever.
What did you select?
if you picked Ethernet, that;s probably your problem. I ran into the same problem when i first setup my board. You have to tell WG that it's not connected to the network, then install MajorTCP/IP and let it handle the network calls.
If you have WG and MajorTCP both trying to access the packet driver directly, one or the other wont be able to access the packet driver. At that point, you'll get the error youre reporting.
I'd imagine that there's a tool you can run that will let you re-setup WG's network connectivity, i dont know what it is though.
Posted: Wed Aug 27, 2008 5:26 pm
by Talonp
Thats the Problem thanks for the help ...now I know what to do to get it running
This was driving me crazy because I did everything the way I always do...but I am adding the MajorTCP/IP this time and I didnt even think about that....see what going without sleep will get you hehe again thanks Venom
Posted: Thu Aug 28, 2008 2:07 am
by VeNoM
No problem!
I set my board up years ago, and took it down due to a hdd failure when i moved.
After about a year i decided to put it up on another hdd. Took me 2 days of pulling my hair out with this exact same problem! I had forgotten how i set it up the first time, and when i went to re-set it up, i fell into the same trap. heh.
Glad its working!