RE: Client Access Express and Windows 95

Janet,

Since CA Express doesn't support the network print function, I assume you
really mean that you're using NetServer on the /400 to do this - is that
correct?  If that's the case, then Client Access is likely irrelevant to the
problem, and anyone suggesting you use something else is not really
contributing to your solution.

What's the number of the tech document on the MS site that describes this
issue?  It's possible our network guys here have a copy, if I can tell them
which specific problem it is.

Dave Shaw
Spartan International, Inc.
Spartanburg, SC

-----Original Message-----
From: jcrowley@ifasys.com [mailto:jcrowley@ifasys.com]

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