RE: Client Access & 4.4

["Crabtree, Jerry" <Jerry.Crabtree@xxxxxxxxxxxxxxxx>]

We have Client Express running on Windows NT and 98.  I found that in our
case it was better to remove Client Access 95/NT prior to loading Express.



-----Original Message-----
From: Bruce Collick [mailto:bruce.collick@aretech-is.com]
Sent: Monday, July 31, 2000 4:52 PM
To: MIDRANGE-L@midrange.com
Subject: Re: Client Access & 4.4


Pardon the interruption, but this topic seems to be too timely to be true!
It just so happens that we are trying to install Client Access Express on a
PC in our shop, and it BSOD'd (blue screen of death) the PC. It was so bad
the darn thing had to be re-imaged! We currently run Client Access with no
problems on Windows NT. We also are running V4R4 on the 400 side. The guy
who was trying to install it says he was at the restart when it kept
crashing. Is there an uninstall for Client Access? He thinks there was a
conflict with the two versions.
Thanks
Bruce

>>> matwell@interboro.k12.pa.us 07/29/00 09:28AM >>>
Richard, do you mean on a pc?   Or on a AS/400?   If it's a pc, we don't 
have any pc's like that, and our AS/400 the dear 170 that it is, well, I'm 
not sure, but I think it's really only one cpu there too.   And Terminal 
Server, I definitely am not using.    That I'm positive about.  Now that 
you have my curiosity aroused about the multiple CPU's I'm going to have to 
check for that too!

At 12:45 PM 7/25/00 -0500, you wrote:
>Date: Tue, 25 Jul 2000 10:05:54 -0600
>From: "Richard Jackson" <richardjackson@richardjackson.net>
>Subject: RE: Client Access & V4.4
>
>Also remember, if you are running CA on any machine with multiple CPUs,
>Express can use all of the CPUs and XD1 can use only one CPU.  This might
>not seem important unless you are running terminal server.
>
>Express was a redesign of XD1 largely to solve number-of-CPUs problems on
>the client side and VLIC workspace space and invocation stack handling
>problems on the 400 side.

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