🚀 go-pugleaf

In article <905622840snz@dsl.co.uk>
   bhk@dsl.co.uk (Brian {Hamilton Kelly}) writes:
> [Note cross-post]
> There have been recent articles reminding one that it is possible to use
> a "packet driver interface" with KA9Q, and hence communicate over, say, a
> LAN.  AIUI, some people use a separate program to dial-up and provide PPP
> connectivity, in order to use other programs such as DOS-Lynx, and use a
> packet driver within KA9Q so that it too can communicate over that link.
>
> I would like to experiment at least with using KA9Q in this fashion, but
> with the slight variation that my "dialer" would be a full-blown TCP/IP
> stack (which presumably must have some relatively standardized API
> mechanism).  I'd either be using KA9Q/2 under OS/2 Warp V4 (using Warp's
> TCP/IP V4.0) or even, just for the hell of it, the standard DOS version
> of KA9Q above the TCP/IP stack which Warp provides in each and every
> DOS-box.
> 
> Has anyone ever tried anything like this?  Is it a matter of finding the
> "right" packet driver (and then, presumably, specifying "encapsulation
> none" when "attach"ing the "device")?  I ask mainly because the
> description (in DISview) of attaching a packet driver gave me the
> impression that it's solely for use with an Ethernet card.

The attach for packet drivers is aimed at network cards, however some
dialers , the ones used in this manner, behave as though they where
network card packet drivrs once dialled in. The only way I can think of
that would allow you to do what you want, would be to use a shim[1] of some 
sort, I know that a shim exists for the win95 stack.

> I remember some few years ago (when I was running OS/2 V2.1, which did
> not come with a built-in TCP/IP stack) experimenting with some packet
> driver and an ODI shim (IIRC).  With this, I was able to dial-up, and
> then allow the shim (which came FOC from a NetWare "taster") to permit
> use of MS-DOS Kermit as a telnet client.  The various TSRs were loaded as
> the DOS-box was created, and it all worked, but I never tried plonking
> KA9Q on top of the crumbling edifice as well!

You probably could have done, this is the way to go I feel, as AFAIK there
is no mechanism within KA9Q to allow it to work through an alternate stack.

> My interest is because I'm finding cFos/2 unstable (I'm using cFos to
> emulate a COM port for KA9Q/2 to use and thus make connection over my
> ISDN line); on some connections, things never progress after the
> equivalent of the "CONNECT" point: in particular, KA9Q's pop-up window
> for the PPP/PAP phase doesn't appear, the thread ceases to receive any
> events from the O/S, and I have to resort to rebooting --- something of a
> rarity with OS/2 :-(

Have you tried cispa /* I think that's what it was called */[2] I never
had any luck getting cFos working but cispa did the job quite nicely.
Although using the shareware version having to reset it every 20 minutes was
a pain.

[1] What is a shim exactly anyway?
[2] *rummage* nope it was ISPA, which comes with instructions for KA9Q

-- 
RobM
       "Trust the computer The computer is your fiend"
       http://www.maghmell.demon.co.uk/dispc/index.html