|
All, As Windoze 98 will inevitably be causing us all problems, and soon, Here is the latest from IBM on support for it. Lou: It does not specifically address the BOS emulator card problem that you are having (are you shocked?) but it IBM's won't work then chances are your problem is the same. Larry Bolhuis Arbor Solutions, Inc IBM Certified Client Access Wacko lbolhui@ibm.net > APAR# II11274 CLIENT ACCESS SUPPORT FOR WINDOWS 98 > >** Last updated 6/25/98 ** > >Client Access for Windows 95/NT V3R1M3 is supported on >Windows 98. Requirements: in addition to Client Access for >Windows 95/NT V3R1M3, service pack SF48155 or later is >required. > >IBM will accept a service call under the standard Service support. > >Support will not be provided for V3R1M2 or earlier versions >of Client Access for Windows 95/NT on Windows 98. > >Here are the known problems that have been identified using >Client Access for Windows 95/NT in the Windows 98 >environment. > >KNOWN PROBLEMS IN THE TWINAX ENVIRONMENT > >In the Windows 98 twinax environments, there are two >limitations known at this time. >1. Client Access SNA twinax connections cannot be made > with IBM PCMCIA twinax cards. This includes both the > IBM 5250 Emulation PCMCIA Adapter (part number 92G5359), > and the IBM 5250 Express PC Card (part number 88H0260). > >2. Client Access TCP/IP twinax connections cannot be made > with the IBM 5250 Emulation PCMCIA Adapter (part > number 92G5359). The Express card works fine for TCP/IP. > >Development is investigating these limitations and hopes to >provide resolutions in a future service pack. > >KNOWN PROBLEMS USING THE NS ROUTER > >There are two known problems at this time: > >1. When running data transfer over the NS Router Netware > for SAA link type on Windows 98, it hangs. The Novell > server operating system is IntraNetWare 4.11 with > service packs, and SAA version is V2.20.10. > >2. On Windows 98, an NS Router link type of Async in > "direct" mode will either: > > a) not connect > or > b) connect OK, but Client Access functions cannot be > run over the connection. > > CIRCUMVENTION: > This appears to be a problem with the Windows 98 > operating system. Larger frames being received in this > environment are coming back as garbage. We have found > that setting the receive FIFO buffer to low or unchecking > the "Use FIFO buffers" box resolves the problem. The > FIFO buffer settings can be found under the "Advanced > Port Settings." To access these settings, > a) Select the "Link Profile" tab on the properties page > for the link. > b) Click on the "Port Settings" button next to the > "Direct Cable on:" prompt. > c) Select the "Advanced" button. > d) You can then modify the "FIFO buffers" information > - Uncheck the "Use FIFO buffers" checkbox > OR > - Leave "Use FIFO buffers" checked and set the > "Receive Buffer" to Low Lou Schmaus wrote: > > Has anyone loaded Win98 on a PC with Client Access or Neftsoft yet? One > our our customers(who was probably waiting outside the CompUSA at 8 AM > yesterday), loaded it on his PC, and now can't connect to the AS/400. He > is using twinax emulation, and the BOS Native Plus Stealth card. He > get's the generic "something is wrong, maybe the configuration" error > from the Netsoft router. > > I tried both Client Access for Win95(V3R1M1, which he had been using > previously with no problems), and Netsoft(ver 3.11, latest one I think). > Netsoft tech support was unaware of any incompatibility, but they also > said that they had not yet completed their testing with WIN98. > > Boy, I hope this isn't going to be a huge problem. We still have quite a > few customers who connect their PC's via twinax. I'd hate to have to > tell them that every time they buy a new PC, we have to reformat the > drive and install Win95. > > Thanks in advance, > > -- > Lou Schmaus > Creative Computer Associates, Inc. > Parlin, NJ 08859 > lschmaus@home.com > > -- > The opinions expressed here are not necessarily those > of my employer, unless it is billable. > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@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 > +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@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.