🚀 go-pugleaf

In <50cneu$2a9o@news-s01.ny.us.ibm.net>, vilez@ibm.net writes:
>In <DwvrF0.BoH@matilda.vut.edu.au>, johnr@warp.vut.edu.au writes:
>>I hope I can get some help with the following problem.
>>
>>I'm trying to install Warp Connect Blue.  The installation procedure
>>installs the OS fine and seems to install the networking component
>>correctly as well (just TCP/IP 3.0 off the parallel port), but when the
>>system automatically reboots I get the following trap
>>
>>==================================================================
>>
>>Exception in device driver: PROTMAN$
>[snip]
>>The system is stopped. Record all of the above information and
>>contact your service representative.
>>
>>==================================================================
>>
>>If I remove the PROTMAN.OS2 line, Warp boots - but then I can't
>>connect to my ISP.
>>
>[snip]
>
>No final answers but,
> If installing Warp Connect over Warp with Bonus Pak TCP/IP,
> you need to remove TCP/IP 2.x first.
>
> Check LANTRAN.LOG.  There might be something useful here.
>
> Replace PROTMAN.OS2 with a known good copy.
>
> Check PROTOCOL.INI for "bad" or incorrect entries.
>
> CHKDSK
>
> 
>I suggest:
>  Remove TCP/IP 2.x
>  Check/edit CONFIG.SYS
>  Install Warp Connect w/o networking 
>  When up and running, then install Networking.
>    (dbl.-check that parallel support is installing)
>
>Hope some of these ideas gets you results.
>
>Mark Vilez

I was trying to install Warp Connect on a bare system - no TCP/IP 2.0.
One of your suggestions did work.  I installed the base OS first and then
the networking.

Thanks also to John Summerfield for pointing out that updates to MPTS and
TCPIP are available.

John
_________
John Roumeliotis                   |  finger for PGP public key
Computer and Mathematical Sciences |  E-Mail: johnr@matilda.vut.edu.au
Victoria University of Technology  |  WWW:    http://dingo.vut.edu.au/~johnr