barryf@aix01.aix.rpi.edu (Barry B. Floyd) (05/31/91)
After much fiddling and some help from the folks at FTP, Inc. I think
I have the EXCELAN NDIS/packet driver files arranged in my autoexect.bat
and config.sys files correctly. One individual (not from FTP) shared
his PROTOCOL.INI settings with me, pointing out areas where I might
have problems due to differing hardware (EXCELAN 205t RAM size).
There are two tell tale signs of trouble remaining:
1) I downloaded WATTCP utilities. TCPINFO works fine. PING results in an
error (abnormal termination...). Both run from the DOS prompt. After PING
exits (abnormally) to the DOS prompt and I attempt to run any program,
that program hangs (RAM corrupted?).
2) With a minimal config.sys, autoexec.bat, win.ini I am able to launch
Win QVT Net (repeatedly) without it hanging my system. However, QVT Net
presents me with the following three dialogue boxes (STOP...):
- Packet Driver Error: TYPE_IN_USE (Access Type)
- Can't Access IP handle Interface Type 1
Packet Driver probably not loaded
- Network Initialization Error!
I have checked my intvec settings, membase, ip addr, etc settings in the
QVT.RC file, EXCELAN "hardware" file, PROTOCOL.INI file, etc. I chose
intvec 0x65 for these app's. I no longer load any EXCELAN modules (when
I do WIN QVT Net hangs my system). The same exact setup plus TCP modules
loaded enables me to successfully use all EXCELAN app's (FTP, TELNET, etc.).
Has anyone seen the above dialogue boxes? What did you do to fix the problem?
What is the problem?
barry
ps
config.sys and autoexec.bat drivers/modules load successfully, but possibly
not correctly. I currently suspect "membase" is off, due to the way WATTCP
crashes my system (I sometimes get interesting characters displayed on my
monitor during execution of PING or after abnormal termination of PING).
thanks in advance... I plan to put all necessary files plus a cheat sheet
in a .ZIP file and post it to the relevant ftp sites, in order to save
others the same trouble. Look for XLNSETUP.ZIP if I suceed in configuring
my system.
--
+--------------------------------------------------------------------+
| Barry B. Floyd \\\ barry_floyd@mts.rpi.edu |
| Manager Information Systems - HR \\\ usere9w9@rpitsmts |
+-Rensselaer Polytechnic Institute--------------------troy, ny 12180-+swh@hpcupt1.cup.hp.com (Steve Harrold) (06/03/91)
>>> However, QVT Net presents me with the following dialogue boxes (STOP...): >>> >>> - Packet Driver Error: TYPE_IN_USE (Access Type) >>> >>> - Can't Access IP handle Interface Type 1 >>> Packet Driver probably not loaded >>> >>> - Network Initialization Error! >>> ---------- I, too, have experienced the TYPE_IN_USE set of messages with WinQVT/Net. These messages occur whenever I restart WinQVT after it dies with an Unrecoverable Application Error (UAE). I have been using the 3C501 packet driver from the Clarkson Collection, along with version 1.65 of WinQVT. Russ Clarkson wrote and suggested I use the TERMIN command from the collection to reset the packet driver, but this did not help. I would conclude that the problem lies with the PKTINT program that comes with WinQVT and its inability to reset the interface between the packet driver and WinQVT itself. It would be nice if WinQVT would give you a dialog box when the TYPE_IN_USE condition arises and let you choose to die or to force a reset of whatever it is that is clogging the TCP/IP path. -- --------------------- Steve Harrold swh@cup.hp.com HPG200/11 (408) 447-5580 ---------------------