🚀 go-pugleaf

tsr@clark.net (Tay Systems Research) wrote:

>We're looking to replace an old Novell NACS/NASI comm. server with a
>present day solution, one that's preferably Windows-based (ie. no DOS
>TSR's required, drivers are all Windows .DLL based) and works over NetWare
>3.12. 

>For those of you who have deployed a comm. server solution on your
>environment, what are your experiences and recommendations?  This will
>serve primarily as a dial-out (I doubt if there will be any dial-in)
>through system, for access to online systems and hosts (ie. BBS, etc.) via
>28.8K modems, and using Procomm Plus for Windows.  

>I understand that the two components needed are separated; software and
>hardware.  For the former, is INT14 the way to go?

We use a Netware Connect 1.0 box (486SX-33 w/ Digiboard PC8Xem, 8MB
RAM, and 120 MB HD).  If you are only concerned about dial-out and
never see the possiblity of dialing in via PPP, I'd find a copy of
Newtare Connect 1.0

Novell released a free NASI redirector for Windows (winncs) which does
not require INT 14 to access a Netware Connect modem from a
workstation.  winncs allows any Windows application to access a
Netware Connect modem .  The only requirement is that your
workstations must have 8MB of RAM (6 works but not recommended).

We use our Netware Connect box for dialing out under Procomm,
Terminal, Trumpet Winsock for dial-up PPP internet access, and procomm
for DOS.