|
thanks. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Jim Franz Sent: Tuesday, August 12, 2003 10:51 AM To: Midrange Systems Technical Discussion Subject: Re: Warning: Operations Console and Win2K SP4 *DONT* > I doubt that it is a MS problem...., if you read the microsoft link in Larry's post, MS admit's it's their error/feature and relates to any remote server, not just os400. jim ----- Original Message ----- From: "Steve Richter" <srichter@xxxxxxxxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Tuesday, August 12, 2003 10:45 AM Subject: RE: Warning: Operations Console and Win2K SP4 *DONT* > sp4 solved a problem I was having on a w2k pc that runs winfax in automated > mode to send as400 generated faxes. Microsoft is doing a good job lately > with automatic update and service packs to fix problems in windows. > > I would like to know what the problem is with ops console and sp4. I doubt > that it is a MS problem, but either way, IBM should get the problem fixed. > > -Steve > > > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Larry Bolhuis > Sent: Monday, August 11, 2003 3:44 PM > To: Midrange Systems Mailing List > Subject: Warning: Operations Console and Win2K SP4 *DONT* > > > Greetings and salutations to this august body of international intelligence! > > One of my customers running operations console just updated his Win2K > console machine to Service Pack 4. This effectively destroys the ability > to use the machine as the console. There is a hotfix but you must call > to get it. > > For more information see: > http://support.microsoft.com/default.aspx?scid=kb;en-us;824301 > > I would avoid SP4 on any operations console machines for the moment. > > - Larry > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > 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@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > 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@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx 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.