Archived from groups: microsoft.public.windowsxp.basics (
More info?)
Only with people who lie like you.
--
----------------------------------------------------------
War on the Pachyderms Terrorists
http://www.counterpunch.org/wilson09012004.html
"Wayne G. Dengel" <wgd.roaming@verizon.net> wrote in message news:Zb__c.5428$vI2.2736@trnddc02...
> Sharon:
>
> Thank You for taking the time to reply.
>
> Note Mr. Candy's reply. This newsgroup has some professionals, probably
> many, as are you. Then there is Mr. Candy, far less than professional.
>
> BTW, thanks for explaining the autorun.inf situation. One respondent was
> gracious enough to provide an input that worked for him at one time.
>
> Regards,
> Wayne
>
>
> "Sharon F" <sharonfDEL@ETEmvps.org> wrote in message
> news:eQ68%2348kEHA.2504@TK2MSFTNGP14.phx.gbl...
> > On Mon, 06 Sep 2004 00:49:12 GMT, Wayne G. Dengel wrote:
> >
> > > At the same time, how
> > > come there are many who experience this same problem?? From what you
> say,
> > > suggest, there may be a number of reasons why this error msg appears.
> Thus
> > > maybe not so easy to get rid of short of installing all from scratch.
> > >
> > > The message, as you know, is just that, an annoyance and does not seem
> to
> > > inhibit proper operation. Therefore, there is not just one solution to
> > > wipe out the annoyance?
> >
> > In the threads that I found, the message was not coming directly from
> > Windows.
> >
> > In one instance, it was coming from programs installed into Windows
> (Office
> > programs) that needed attention. Probably a portion of an Office program
> > that was configured to load at startup but could not due to missing files
> > or incomplete settings.
> >
> > Since the message occurs at every startup, this would be a logical area to
> > look at a little closer. Try using Start> Run> MSCONFIG and disable all
> > startup programs. Then restart. If the message is gone, re-enable one
> > startup item. Restart. Repeat until you get the message again. The last
> > item added before the error message appears, is the one that needs
> > repairing/reinstalling.
> >
> > I see from your other post that you have checked for an autorun.inf.
> > Autorun are typically used on CDs and contain an execute command that
> > initiates a setup program. On occasion, an *.inf file is copied to the
> root
> > of C: and cannot autorun. This is not as common now as it once was but it
> > still happens now and then. No need to rename the one that you found for
> > Roxio. You only need to concern yourself with any that are in the root
> > folder of the boot drive.
> >
> > For example, if your system boots from C: (most common), that is where you
> > need to look. Not in the subfolders - just in the loose files that show up
> > when C: is highlighted in Windows Explorer. You may want to set Folder
> > Options to show hidden files just in case there is a hidden autorun.inf
> > file in this location. If found, delete.
> >
> > Another thing to check would be Event Viewer. Start> Run> eventvwr.msc
> will
> > bring up this tool. Check the Application and the System branches for a
> > more detailed message about the startup problem. Double click any item to
> > bring up a window with more details about each event. Perhaps a file name
> > will be mentioned in one of these descriptions that will help you to
> narrow
> > your search for the cause.
> >
> > --
> > Sharon F
> > MS-MVP ~ Windows XP Shell/User
>
>
YI_c.347$Ux5.118@newsfe2-win.ntli.net...
Facebook
Twitter
Instagram