Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Computer Learning -- Ignore unavailable to you. Want to Upgrade?

To: Martin E. Frankel who wrote (27840)	6/22/2002 1:59:50 PM
From: B.K.Myers	Read Replies (1) \| Respond to of 110655

Marty, Try using Find (Start / Find / Files and Folders...). Enter a "?." in the "Named:" box and "browse" to the "C:\WINNT\" folder for the "Look in:" location then click on "Find Now". "?" is a wild card that represents a single character. If any files or folders are found, that will be the file (of folder) that is not being backed up. You might also try running Scandisk to see if there are any files or folders on your hard drive with errors. I suspect that this is not a serious error and probably shouldn't be a serious concern. B.K.

To: Martin E. Frankel who wrote (27840)	6/22/2002 2:10:20 PM
From: mr.mark	Read Replies (1) \| Respond to of 110655

hi marty from what i can see, and from my limited experience with this.... i believe the log is pointing directly to the files that are causing the error and not being backed up Error: C:\WINNT\Tasks\Symantec NetDetect.job has been modified since it was backed up. Error: C:\WINNT\system32\wbem\Logs\wbemcore.log has been modified since it was backed up. here's just a short snip from my wbemcore.log file... really exciting stuff <w> "(Mon Jun 17 09:38:07 2002) : Core physically unloaded! (Mon Jun 17 11:08:32 2002) : Core physically unloaded! (Mon Jun 17 11:27:01 2002) : Core physically unloaded! (Mon Jun 17 12:56:49 2002) : Core physically unloaded! (Mon Jun 17 13:12:02 2002) : Core physically unloaded! (Mon Jun 17 13:30:30 2002) : Core physically unloaded! (Tue Jun 18 16:09:44 2002) : Core physically unloaded! (Tue Jun 18 16:33:40 2002) : Core physically unloaded! (Tue Jun 18 16:52:08 2002) : Core physically unloaded! (Thu Jun 20 08:15:27 2002) : Core physically unloaded! (Thu Jun 20 13:26:14 2002) : Core physically unloaded! (Thu Jun 20 13:44:42 2002) : Core physically unloaded! (Thu Jun 20 19:57:36 2002) : Core physically unloaded! (Thu Jun 20 21:50:57 2002) : Core physically unloaded! (Thu Jun 20 22:09:24 2002) : Core physically unloaded!" imo, these two files will have no impact on your back up's ability to restore your system. they look like such non files to me. why not peruse the symantec support site knowledge base for info on the NetDetect.job error, and what exactly that file is about. i do have a NetDetectController.DLL in my symantec liveupdate folder. regarding liveupdate's automatic setting, if it's not doing it anyway, i would advise unselecting the auto update function. that could change the job report, maybe. i do disk imaging now for full system back ups, using powerquest's driveimage program. i never get error messages and i image a 4 gb partition in 3 minutes. amazingly, i can restore individual files or folders from that image, OR the entire partition. it's awesome, imo. but i used to back up my files, folders and partitions using iomega media, specifically jaz disks, and i would always end up with a list of files that were not able to be backed up. seems like many of them were log files and files that were open during the back up routine, thus unable to be backed up. to tell you the truth, i never sweated it. i lived with it, but when i came upon a back up routine that did it all in such short order and so thoroughly (driveimage), i abandoned the iomega plan. re, "BTW, NAV snared a SIRCAM worm this morning during download from the e-mail server".... just imagine the fun you could be having right now if you were going, how did matt phrase that? "virus free au natural". <g3> hope some of this helps, marty. i'm basically casting about here, trying to offer random thoughts. i'd like to hear what you discover, if anything, about those two files. i really bet there is info to be had on the symantec support site. good luck :) mark