RE: Client Access Express and Windows 2000?

Was glad to see this post and can't remember if I saw any solutions yet.  We
may be migrating some folks on Win 95 to C/A Express in the future.  On the
other side... We installed CA Express on Win 2000 PC's and it seems to be
running fine EXCEPT... How do I get rid of the little pop up signon screen
that comes up every time I connect to an AS/400.  I defined the default user
and did NOT check the little box that says "pop up every time".  I recall
this as a problem in early versions of C/A but was fine as of CA V3R2.

Lastly...  DO NOT accidentally install C/A for 95/98 on a Win 2000 PC.
Locks it up solid and is a real b*#tch to put back together.  And one more
thing... Why did they call it C/A Express??  My first inclination was that
IBM created a "lite" version just by the silly name they gave it (like
Outlook Express).  Of course it is just as fully functional as C/A for 95/98
from what I can tell and maybe the "Express" just means it goes "really
fast"!

-----Original Message-----
From: jcrowley@ifasys.com [mailto:jcrowley@ifasys.com]
Sent: Monday, August 28, 2000 2:26 PM
To: MIDRANGE-L@midrange.com
Subject: Client Access Express and Windows 95


We have just started implementing Client Access Express on some of our PCs,
and
I've been frustrated because some, but not all, of the Win95 PCs I've
installed
CA Express on absolutely cannot print workstation output to an AS/400
network
printer. I get a SPOOL32 error, the printer disappears, the machine
sometimes
locks up, but amazingly the printer and the printout reappear when the
system is
rebooted.

Today I finally decided to do some research on this at the Microsoft
website,
and, guess what? This is a documented Win95 bug that appears whenever you
have a
Win95 machine with the service pack loaded. There is a fix apparently, but
Microsoft doesn't make it downloadable (at least nowhere I can find) because
it
isn't fully regression-tested (or somesuch) and they want you to get the fix
only if you're really in need of it. Oh, and by the way, the problem is
solved
in Win98.

The documentation implies the problem is with a specific DLL, but when I
pulled
a newer version of the DLL from a newer PC, the problem was not resolved, so
there must be some other pieces parts to the resolution.

I am not going to buy Win98 licenses for these PCs at this time -- I'd have
to
buy more memory as well even if I were so inclined -- so my options are to
stick
with CA 95/NT or try to track down someone at Microsoft who can provide me
with
the supposed fix. I can't find any way to obtain the fix without contacting
Microsoft Technical Support, which probably involves a fee of some sort.

So, before I jump through Microsoft hoops, is there anyone out there who
actually got and installed the fix, and does it work?

Janet Elam Crowley
Systems Analyst
IFA Systems
Boise, Idaho






+---
| 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
+---