Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!pilchuck!jewell
From: jewell@Data-IO.COM (Cal Jewell)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Another Problem with WinQVT/Net
Summary: Looks like we have the same situation
Message-ID: <1717@pilchuck.Data-IO.COM>
Date: 4 Mar 91 18:57:07 GMT
References: <1716@pilchuck.Data-IO.COM> <2477@travis.csd.harris.com>
Sender: news@Data-IO.COM
Distribution: na
Organization: Data I/O Corporation; Redmond, WA
Lines: 68

In article <2477@travis.csd.harris.com> leoh@hardy.hdw.csd.harris.com (Leo Hinds) writes:
>In article <1716@pilchuck.Data-IO.COM> jewell@Data-IO.COM (Cal Jewell) writes:
>>As soon as I logout, I get an "Unrecoverable Application Error"
>
>I get these without logging out of the telnet session ... just idle time will 
>do it for me ...

Interesting. I can let my telnet window sit idle for hours and
nothing will happpen. (WinQVT/NET won't crash. Everything seems
to run fine.

>>and the current application (WinQVT/Net) is terminated. Then, while
>>still in the same Windows session, if I restart WinQVT/Net, I get 
>>the following error as soon as I launch QVT/Net:
>>    Packet Driver Error: TYPE_IN_USE (Access Type)
>>
>>    Can't Access IP handle interface type 1
>>    Packet Driver probably not loaded.
>>
>>    Network Initialization Error!
>
>What is happening is that the previous winqvt/net session IS NOT 
>relinquishing the network, therefore when the new instance starts up, it 
>can't access the network.  

I kind of figured something like this was happening. But I didn't
know enough about packet drivers and networks to properly word
my guess.

>
>Exiting windows & re-entering will not clear it up either.  

Yep, same thing here. 

Also, somebody e-mailed me and asked if I was using the 
-w switch for the packet driver. I wasn't, but when I do use 
the -w switch for the packet driver (3c501.com) I experience
the same problems when I don't use the -w switch. At this point
it doesn't seems like the -w swicth is part of the problem.

>
>I am guessing that PKTINT.COM (that is part of winqvt/net) is "told" that 
>someone has accessed the network, but is not told (by the crashing winqvt/net) 
>that it is free again.

That sounds like it fits our situation. It would be nice if the
QPC Software Folks (the WinQVT/NET folks) could modify their 
software to detect this situation (a crashed WinQVT/NET session).

>
>Net result ... a re-boot is required (at least in my case).

Yep, I have to use the same 'fix.' Looks like I will be going
back to the older version of WinQVT/NET. (And this really 
pisses me off. I payed to be registered and what do I get, 
a newer version of software that won't work properly on the
same hardware and network setup that the older version of 
software had no problems with. Actually, I'm not pissed off,
just a little upset.)

Hope the QPC software folks are listening. Anybody
know of if they are reachable by e-mail or if they
can be reached on a BBS. (At this point, I'm willing to
pay for the phone call; I just want to get their software
working.)

>
>leoh@hdw.csd.harris.com         	Leo Hinds       	(305)973-5229