|
Jure, The problem I'm having with Client Access Enhanced for Win 3.1 is that I get PROGMAN errors when I go into something else after EXITING client Access. If they leave it running, it's no problem. One problem I had on some computers was that TCP/IP would not install properly - It put the ETHERNET__II frame type after 802.3 which is the frame my Novell is running on. If you can't PING the 400 from within windows, I suggest checking the frame types. Paul Jure Erznoznik wrote: > I've got a VERY CONSISTENT problem with Client Access Enhanced for > Win > 3.1. As far as I can tell, I am at the latest patch levels but the > following errors occur on every workstation with 100% reproducability: > > >---------------------------------------------------------------------------------------------------- > > I have also problem with Client access Enhanced for Win 3.1. The > biggest problem is that simply on some PCs I can't use PC5250 that > came with Client Access Enhanced, (Personal Communication V4.1), while > the old 5250 emulation from Client Access for Windows works. Is there > any PTF's for CA Enhanced for Win ?Jure. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.