|
We also have this happen when we use Norton Utilities. We run MSCONFIG on the command line, select the start tab and uncheck the selection for Client Access start incoming rc. This stops it from running each time you boot your pc. -----Original Message----- From: Jay Peasley [SMTP:jpeasley@ncats.net] Sent: Monday, November 20, 2000 12:07 PM To: MIDRANGE-L@midrange.com Subject: Re: Norton Utilities and Incoming Remote Command Server We had a similar experience a few years ago with an IBM PC and someone using the registry cleaner in Norton Utilities. I don't remember the exact details, other than it really hosed CA/95-NT. Our resolution was to NOT use the registry cleaner in Norton Utilities. The Windoze RegClean does a fine job and it does not mess up Client Access. Jay ----- Original Message ----- From: "Joe Giusto" <JGiusto@patuxent.com> To: <midrange-l@midrange.com> Sent: Monday, November 20, 2000 11:12 AM Subject: Norton Utilities and Incoming Remote Command Server > we have IBM AS400 Client Access on both windows 98 and windows 95. the > problem is that when we run the windows repair utility in Norton Utilities, > it turns on Client Access Incoming Remote Command Server and sets it to come > on every time the computer is booted up. > > This causes the PC to lock up after a short time of running. I have been > able to go into the registry afterwards and delete registry entries to > prevent starting of the IRC Server, however, this is not a solution that we > want to give out to the users as it is very dangerous to be messing around > in the registry. We need a proactive solution to keep this event from > happening in the first place. > > If any of you have had this problem, can you suggest a way around it? > > I have sent a request to Norton Technical Support, but I am betting that I > can get an answer from this list much quicker. > > Thank you very much for any assistance that you can provide. > > Joe Giusto II > Patuxent Publishing Company > 10750 Little Patuxent Parkway > Columbia, MD 21044 > mailto:JGiusto@patuxent.com <mailto:jgiusto@patuxent.com> > http://www.lifegoeson.com <http://lifegoeson.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 +--- +--- | 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 +---
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.