A.G.Bishop@massey.ac.nz (A.G. Bishop) (11/07/90)
Part #1 ======= Is anybody running WinQVT/Net on a WD8003E card successfully? I obtained the WNQVTNET.ZIP file from Simtel but there was no sign of the DRIVERS.ARC file mentioned in the doc. I may, therefore, have missed something. Having obtained the clarkson WD8003E.COM packet driver, I tried simply adding it to my present setup (loading it then PktInt just before a batch Pause then Win /s) - a reboot ensued. I eventually wound up booting from a floppy to get a config.sys that loaded only HIMEM.SYS and an autoexec.bat that sets up a path, loads the packet driver and PKTINT.COM and starts WIN /S. You guessed it, I still get a lock up when I start WinQVT/Net. I use WD8003E 0x80 0x5 0x280 0xD000 (I took the 80H from the description of PKTINT, the int=5 and I/O=280 are correct and I believe the driver sets the RAM base address (though I did get an "suggested address already in use" message with C800 which surprises me as that is what I normally use ) ). Part #2 ======= I normally use my ethernet card to run PC-NFS, currently I exit windows, run NCSA telnet then reboot when I want to log in to the server under Unix. I would love to be able to run 4 or 5 Unix sessions on different servers in windows without even having to exit Windows (plus a background ftp). The problem (apart from not going, see above) is how will I go using the one ethernet card for two lots of IP traffic (PC-NFS & WinQVT)? I understand that I cannot have two stacks using the same protocol on the same ethernet card. How about it? Must be lots of people out there using Windows on PC-NFS who would like to be able to do this. Thanks in advance, Tony -- The opinions, policies and biases | A.G.Bishop@massey.ac.nz inflicted upon the Gentle Reader | Palmerston North, herein are owned by me. | New Zealand
rodrigol@ulrik.uio.no (Rodrigo Lopez) (11/08/90)
> Anyone running WinQvt/Net on a wd8003e and Pc-Nfs succesfully ?
Well, I got the thing running yesterday. Not without a lot of problems
and being forced to do things I don't like. Let me summarize:
1. I did not change my config.sys at all. The packet driver provided
with pc-nfs is the one I use to boot-up.
2. As you, I also use INT 5 on my card.
3. After boot-up but before you start windows type the following:
wd8003e 0x60 5 0x280 0xd000
pktint
4. Now run windows (Win/s or Win/3).
5. Use the notepad to edit QVT_TCP.RC and make sure "pc_ip","netmask","domain",
"packet_vector=60", and "packet_class=0" are in the first seccion. On
the second
seccion define you "default" set-up. Then, on the third seccion, where
you define
your hosts, I had to add:
"gateway=1"
"nameserver=1"
for every host entry.
6. Run WinQvt/nett and if you get the host list up on the screen you are
in
buisness. Now try to open a session to the first host. It may be you
have to
press RETURN to wake up the system.
This works but only for the first host. I cannot make a connection to
any
of my other hosts unless I modify QVT_TCP.RC and "isolate" the gateway
and the
nameserver specifically to it. I don't know why, but at least I've got
the "thing"
working.
If anybody out there is kind enough to explain why this work (when in
theory it
should'nt) please, please post a followup.leoh@hardy.hdw.csd.harris.com (Leo Hinds) (11/09/90)
In article <1990Nov7.035509.23197@massey.ac.nz> A.G.Bishop@massey.ac.nz (A.G. Bishop) writes: >======= >Is anybody running WinQVT/Net on a WD8003E card successfully? No, I tried on an interlan card with mixed success (would start up, but die) >I obtained the WNQVTNET.ZIP file from Simtel but there was no sign of >the DRIVERS.ARC file mentioned in the doc. I may, therefore, have >missed something. The .doc file talks about the clarkson packet drivers AND it tells you WHERE to FTP them from. Arguably they could be made available on cica as well, but why duplicate? >Having obtained the clarkson WD8003E.COM packet driver, I tried >simply adding it to my present setup (loading it then PktInt just >before a batch Pause then Win /s) - a reboot ensued. >I use WD8003E 0x80 0x5 0x280 0xD000 The readme file with the packet drivers says that if you plan to use windows, there is a special flag (-w) required before any of the hex info you supply. (WD8003E -w 0x80 0x5 0x280 0xD000) >(I took the 80H from the description of PKTINT, the int=5 and I/O=280 >are correct and I believe the driver sets the RAM base address WinQVT/net says (in the readme file (lines 115-117) NOT TO USE 80h as that is what is used by pkinit. It is up to you to select another software interrupt that is currently not used by anything else. On my machine, 60h works well. On the interlan card, the driver DOES NOT sate the base address of the card. The card needs to be configured correctly first, then the pertinent info is passed to the packet driver so that it know exactly where to "talk". The WD8003E card may be different - I don't know. >The problem (apart from not going, see above) is how will I go using >the one ethernet card for two lots of IP traffic (PC-NFS & WinQVT)? >I understand that I cannot have two stacks using the same protocol on >the same ethernet card. >How about it? Must be lots of people out there using Windows on >PC-NFS who would like to be able to do this. I too would like to do that, but as you point out to entities running tcp/ip do not work ... so as far as I know, we are stuck. If someone knows of a way, PLEASE let me know ... thanks leoh@hdw.csd.harris.com Leo Hinds (305)973-5229 Gfx ... gfx ... :-) whfg orpnhfr V "ebg"grq zl fvtangher svyr lbh guvax V nz n creireg ?!!!!!!? ... znlor arkg gvzr