|
I didn't install any service packs, just straight off the CA disk that came with V4R5. -----Original Message----- From: Jim Franz [mailto:franz400@triad.rr.com] Sent: Tuesday, October 02, 2001 8:33 AM To: midrange-l@midrange.com Subject: Re: Client Access & XP > When I had a beta version of XP, I used CAE45. It worked just fine for me. Mike - with or without the V4R5 "Refresh" after Aug 28? We are doing tn5250, printing & file transfer, both local lan and WAN and some internet VPN (Cisco vpn). jim ----- Original Message ----- From: "Wills, Mike N. (TC)" <MNWills@taylorcorp.com> To: <midrange-l@midrange.com> Sent: Tuesday, October 02, 2001 9:01 AM Subject: RE: Client Access & XP > When I had a beta version of XP, I used CAE45. It worked just fine for me. > > -----Original Message----- > From: Jim Franz [mailto:franz400@triad.rr.com] > Sent: Monday, October 01, 2001 9:37 PM > To: MIDRANGE-L@midrange.com > Subject: Client Access & XP > > > This is a multi-part message in MIME format. > -- > [ Picked text/plain from multipart/alternative ] > Any comments/concerns about CA/Express and Win XP? > The CA site > http://www-1.ibm.com/servers/eserver/iseries/clientaccess/caiixe1.htm > has a doc from June about future support in the V5R1 client only, then in > the > aug 28 announcement, the following stmnt : > Client Access Family for Windows (5769-XW1) customers running OS/400 V4R5 > and have software subscription can acquire and use the V5R1 versions of the > following products by ordering the Client Access Family for Windows refresh. > Anyone loaded the refresh yet? > I assume this means only the V5R1 client, talking to a V4R5 system with the > "refresh". > Also, in the June stmnt, said "XP Professional Edition". Does this mean the > "XP Home Edition" may be a problem? (and before you ask why anyone would buy > the home edition-so many computers will come preloaded-it's going to > happen). > jim franz > -- > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.