Anybody have an idea what this is?

Guest · Mar 11, 2002

I must have set-up a logging file without setting limits, but for the life of me I can't remember where. This one has reached 4.5 gigs.

WINDOWS\system32\LogFiles\WMI\trace.log

I'd really like to get rid of this monster, or at least set some limits, but not knowing what's controlling it, I'm afraid to just delete it. Anybody have a suggestion on how I should proceed?

Thanks.
SRS

silverpig · Mar 11, 2002

Set a restore point and then just delete it...

Lyrics. Wasted time between solos.

Toejam31 · Mar 11, 2002

You can access the Trace Logs from Administrative Tools\Performance\Trace Logs. Right-click on Trace Logs and choose Help from the menu to see how the log parameters can be defined.

If you just delete the log file, the next time you boot, the whole thing will start over again. You need to delete the Trace Log you created before deleting the Log File Data.

Toejam31

My Rig: <A HREF="http://www.anandtech.com/mysystemrig.html?rigid=6847" target="_new">Toejam31's Tantalizing Tantric Toy</A>
Second Rig: <A HREF="http://www.anandtech.com/mysystemrig.html?rigid=15942" target="_new">Toey's Dynamite DDR Duron</A>
____________________________________________________________

"Procrastination on your part does not constitute an emergency on my part."

Guest · Mar 11, 2002

Thanks to Toejam31 and Silverpig.

There was nothing set-up in Administrative Tools\Performance\Trace Logs. Nevertheless, as of this morning, the file size had returned to zero. If it grows again, perhaps I'll be able to identify its source. If not, I'll re-post.

Thanks again,
SRS

Toejam31 · Mar 11, 2002

Try setting the Performance Logs and Alerts Service to manual, or even disabling it. That should stop the log from appearing again, unless you manually enable the Service, and create a new log with personally defined parameters.

Toejam31

My Rig: <A HREF="http://www.anandtech.com/mysystemrig.html?rigid=6847" target="_new">Toejam31's Tantalizing Tantric Toy</A>
Second Rig: <A HREF="http://www.anandtech.com/mysystemrig.html?rigid=15942" target="_new">Toey's Dynamite DDR Duron</A>
____________________________________________________________

"Procrastination on your part does not constitute an emergency on my part."

Guest · Mar 12, 2002

Thanks for your follow-up.

"Performance Logs and Alerts" is set to manual and stopped. The system won't allow the file to be deleted. However, I was finally able to look at it and, if it wouldn't be too much trouble, perhaps you could take a look at what I found early in the file (copying more seemed redundant). It seems to me that I need to identify what is causing the file to be generated before the problem becomes susceptible to correction. (I inserted an extra blank line between each entry for ease of review. At this moment, the file is 1.6 gigs.)

Thanks again,
SRS

============

P a c i f i c S t a n d a r d T i m e
P a c i f i c D a y l i g h t T i m e

N T K e r n e l L o g g e r C : \ W I N D O W S \ S y s t e m 3 2 \ L o g F i l e s \ W M I \ t r a c e . l o g

\ W I N D O W S \ s y s t e m 3 2 \ w o w 3 2 . d l l

\ W I N D O W S \ s y s t e m 3 2 \ c r y p t 3 2 . d l l

a p p H e l p . d l l

\ W I N D O W S \ s y s t e m 3 2 \ a p p h e l p . d l l

U S E R E N V . d l l

\ W I N D O W S \ s y s t e m 3 2 \ u s e r e n v . d l l

M S A S N 1 . d l l

\ W I N D O W S \ s y s t e m 3 2 \ m s a s n 1 . d l l

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ W I N D O W S \ S y s t e m 3 2 \ L o g F i l e s \ W M I \ t r a c e . l o g

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ W I N D O W S \ S y s t e m 3 2 \ L o g F i l e s \ W M I \

\ $ M a p A t t r i b u t e V a l u e

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ W I N D O W S \ S y s t e m 3 2 \ C o n f i g \ S E C U R I T Y

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ W I N D O W S \ S y s t e m 3 2 \ C o n f i g \ S E C U R I T Y . L O G

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ W I N D O W S \ S y s t e m 3 2 \ C o n f i g \ S O F T W A R E

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ W I N D O W S \ S y s t e m 3 2 \ C o n f i g \ S O F T W A R E . L O G

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ W I N D O W S \ S y s t e m 3 2 \ C o n f i g \ S Y S T E M

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ W I N D O W S \ S y s t e m 3 2 \ C o n f i g \ S Y S T E M . L O G

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ W I N D O W S \ S y s t e m 3 2 \ C o n f i g \ D E F A U L T

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ W I N D O W S \ S y s t e m 3 2 \ C o n f i g \ D E F A U L T . L O G

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ W I N D O W S \ S y s t e m 3 2 \ C o n f i g \ S A M

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ W I N D O W S \ S y s t e m 3 2 \ C o n f i g \ S A M . L O G

\ $ M a p A t t r i b u t e V a l u e

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ h i b e r f i l . s y s

\ W I N D O W S \ s y s t e m 3 2 \ L o g F i l e s \ W M I \ t r a c e . l o g

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ W I N D O W S \ s y s t e m 3 2 \ w i n 3 2 k . s y s

SyncEvalObject: Object = \_SB.PCI0.LPCB.BAT1._BST

AsyncEvalObject: Object = \_SB.PCI0.LPCB.BAT1._BST

AsyncEvalObject: Object = \_SB.PCI0.LPCB.BAT1._BST

SyncEvalObject: Object = \_SB.PCI0.LPCB.BAT1._BST

SyncEvalObject: Object = \_SB.PCI0.LPCB.ACAD._PSR

AsyncEvalObject: Object = \_SB.PCI0.LPCB.ACAD._PSR

AsyncEvalObject: Object = \_SB.PCI0.LPCB.ACAD._PSR

SyncEvalObject: Object = \_SB.PCI0.LPCB.ACAD._PSR

SyncEvalObject: Object = \_SB.PCI0.LPCB.BAT2._BST

AsyncEvalObject: Object = \_SB.PCI0.LPCB.BAT2._BST

AsyncEvalObject: Object = \_SB.PCI0.LPCB.BAT2._BST

SyncEvalObject: Object = \_SB.PCI0.LPCB.BAT2._BST

SyncEvalObject: Object = \_SB.PCI0.LPCB.ACAD._PSR

AsyncEvalObject: Object = \_SB.PCI0.LPCB.ACAD._PSR

AsyncEvalObject: Object = \_SB.PCI0.LPCB.ACAD._PSR

SyncEvalObject: Object = \_SB.PCI0.LPCB.ACAD._PSR

\ W I N D O W S \ s y s t e m 3 2 \ w i n 3 2 k . s y s

\ W I N D O W S \ s y s t e m 3 2 \ w i n 3 2 k . s y s

\ W I N D O W S \ s y s t e m 3 2 \ n t d l l . d l l

\ W I N D O W S \ s y s t e m 3 2 \ P D B o o t . e x e

\ D E V I C E \ H A R D D I S K V O L U M E 1

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ W I N D O W S \ s y s t e m 3 2

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ W I N D O W S \ S y s t e m 3 2 \ P D B o o t S t a t e

PDBoot.exe

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ W I N D O W S \ b o o t s t a t . d a t

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ W I N D O W S

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ S y s t e m V o l u m e I n f o r m a t i o n \ _ r e s t o r e { 2 2 0 6 E 2 3 B - 9 A F 3 - 4 C 2 1 - B 9 1 7 - E 8 9 3 B 9 7 F 0 F 5 9 } \ _ f i l e l s t . c f g

\ W I N D O W S \ b o o t s t a t . d a t

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ W I N D O W S \ s y s t e m 3 2 \ a u t o c h k . e x e

\ W I N D O W S \ s y s t e m 3 2 \ a u t o c h k . e x e

autochk.exe

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ W I N D O W S \ s y s t e m 3 2 \ a u t o c h k . e x e

\ S y s t e m R o o t \ S y s t e m 3 2 \ n t d l l . d l l

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ W I N D O W S \ P r e f e t c h \ A U T O C H K . E X E - 2 F 8 C 5 9 C 3 . p f

\ W I N D O W S \ P r e f e t c h \ A U T O C H K . E X E - 2 F 8 C 5 9 C 3 . p f

\ D E V I C E \ H A R D D I S K V O L U M E 1

\ D E V I C E \ H A R D D I S K V O L U M E 1

\ D E V I C E \ H A R D D I S K V O L U M E 1 \ W I N D O W S \

\ D E V I C E \ H A R D D I S K V O L U M E 1 \ W I N D O W S \ S Y S T E M 3 2 \

\ D E V I C E \ H A R D D I S K V O L U M E 1 \ W I N D O W S \ S Y S T E M 3 2 \ N T D L L . D L L

\ D E V I C E \ H A R D D I S K V O L U M E 1 \ W I N D O W S \ S Y S T E M 3 2 \ A U T O C H K . E X E

\ W I N D O W S \ s y s t e m 3 2 \ a u t o c h k . e x e

\ W I N D O W S \ s y s t e m 3 2 \ a u t o c h k . e x e

\ W I N D O W S \ s y s t e m 3 2 \ a u t o c h k . e x e

\ D E V I C E \ H A R D D I S K V O L U M E 1

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ W I N D O W S \ s y s t e m 3 2

\ D e v i c e \ H a r d d i s k 0 \ D P ( 1 ) 0 - 0 + 2

\ D e v i c e \ H a r d d i s k 0 \ D P ( 1 ) 0 - 0 + 2

\ D e v i c e \ H a r d d i s k V o l u m e 1

autochk.ex

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ W I N D O W S \ b o o t s t a t . d a t

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ W I N D O W S \ S y s t e m 3 2 \ s f c f i l e s . d l l

\ W I N D O W S \ s y s t e m 3 2 \ s f c f i l e s . d l l

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ W I N D O W S \ s y s t e m 3 2

\ W I N D O W S \ s y s t e m 3 2 \ a d v a p i 3 2 . d l l

c o m d l g 3 2 . d l l

\ W I N D O W S \ s y s t e m 3 2 \ c o m d l g 3 2 . d l l

\ W I N D O W S \ s y s t e m 3 2 \ g d i 3 2 . d l l

i m a g e h l p . d l l

\ W I N D O W S \ s y s t e m 3 2 \ i m a g e h l p . d l l

k e r n e l 3 2 . d l l

\ W I N D O W S \ s y s t e m 3 2 \ k e r n e l 3 2 . d l l

\ W I N D O W S \ s y s t e m 3 2 \ l z 3 2 . d l l

\ W I N D O W S \ s y s t e m 3 2 \ o l e 3 2 . d l l

o l e t h k 3 2 . d l l

\ W I N D O W S \ s y s t e m 3 2 \ o l e a u t 3 2 . d l l

o l e c l i 3 2 . d l l

\ W I N D O W S \ s y s t e m 3 2 \ o l e c l i 3 2 . d l l

o l e c n v 3 2 . d l l

\ W I N D O W S \ s y s t e m 3 2 \ o l e c n v 3 2 . d l l

o l e s v r 3 2 . d l l

\ D e v i c e \ H a r d d i s k V o l u m e 1

\ W I N D O W S \ s y s t e m 3 2 \ o l e s v r 3 2 . d l l

o l e t h k 3 2 . d l l

\ W I N D O W S \ s y s t e m 3 2 \ o l e t h k 3 2 . d l l

\ W I N D O W S \ s y s t e m 3 2 \ s f c f i l e s . d l l

\ W I N D O W S \ s y s t e m 3 2 \ s h e l l 3 2 . d l l

\ W I N D O W S \ s y s t e m 3 2 \ w i n i n e t . d l l

Toejam31 · Mar 13, 2002

This could be a logging issue with the Windows Management Instrumentation service ... at least, that's how it appears to me from the information you've posted.

The computer might be trying to collect performance data through this service, instead of from the Registry.

To turn WMI error logging on or off:
Open the WMI Control.
In the console tree, right-click WMI Control, and then click Properties.
Click the Logging tab.
Under Logging level, click Disabled to turn logging off. Click either Errors only or Verbose to turn it on.

To open the WMI Control console, click Start, click Run, type wmimgmt.msc, and click OK.

Note: "Errors only" reports errors that occur within WMI. "Verbose" reports all actions and errors, which could explain the size of the log file once the system is started and running.

According to Microsoft, Verbose logging can negatively impact system performance, so you should only use it when you need extensive information about error events.

I hope this solves the problem. If not ... post again. We'll try something else.

Toejam31

My Rig: <A HREF="http://www.anandtech.com/mysystemrig.html?rigid=6847" target="_new">Toejam31's Tantalizing Tantric Toy</A>
Second Rig: <A HREF="http://www.anandtech.com/mysystemrig.html?rigid=15942" target="_new">Toey's Dynamite DDR Duron</A>
____________________________________________________________

"Procrastination on your part does not constitute an emergency on my part."

Guest · Mar 14, 2002

Well, I gotta admit I'm confused. Of course, that's nothing new to me -- it happens as one gets older and I'm getting used to it.

I went back as you suggested and checked WMI error logging through wmimgmt.msc. The logging level is set to "Errors only" and "Log file attributes / Maximum size (bytes)" is set to 65536. Even more interesting, however, is that the "Location" is set to C:\WINDOWS\system32\WBEM\Logs\. The trace.log file we're talking about is in another folder altogether (C:\WINDOWS\system32\LogFiles\WMI, which at the moment is 487,808 KB). What do you think?

SRS

Toejam31 · Mar 14, 2002

I understand the confusion.

I'm also old enough to understand inadequacy! :tongue:

Bear with me, please ... let's try another tactic.

First, go to the Help menu and type in Logman. Look at the three Full-Text Search Matches that will be located at the bottom of the Search Results Window.

You'll not only see Logman, but some other elements, such as the Command-line reference A-Z, and new command-line tools.

This is entirely to give you some extra information about Logman, which in WinXP, is the Performance Counter and Event Trace Log Manager and Scheduler.

After perusing this information , open up the Command Prompt located at Start\Programs\Accessories\Command Prompt.

At the C:\Documents and Settings\User Name, type Logman /?

Hopefully, you'll find enough information in this window to successfully stop and delete the trace log.

Mind if I cross my fingers this time 'round?

Toejam31

My Rig: <A HREF="http://www.anandtech.com/mysystemrig.html?rigid=6847" target="_new">Toejam31's Tantalizing Tantric Toy</A>
Second Rig: <A HREF="http://www.anandtech.com/mysystemrig.html?rigid=15942" target="_new">Toey's Dynamite DDR Duron</A>
____________________________________________________________

"Procrastination on your part does not constitute an emergency on my part."

Guest · Mar 14, 2002

ABSOLUTELY! Cross your fingers -- I need all the help I can get, and I'll get back to you.

Thanks,
SRS

Guest · Mar 16, 2002

Reporting my latest efforts:

1. I downloaded the Exctrlst tool and disabled reporting. I then rebooted and found that the TRACE.LOG file was still being created and grew rapidly.

2. I ran LOGMAN and got back the following report:

Provider GUID
------------------------------------------------------------
DNS Trace {1540ff4c-3fd7-4bba-9938-1d1bf31573a7}

Spooler Trace Control {94a984ef-f525-4bf1-be3c-ef374056a592}

COM+ Services {53201895-60E8-4fb0-9643-3F80762D658F}

NTLM Security Protocol{C92CF544-91B3-4dc0-8E11-C580339A0BF8}

Windows Kernel Trace {9e814aad-3204-11d2-9a82-006008a86939}

Local Security Authority (LSA) {cc85922f-db41-11d2-9244-006008269001}

Active Directory: Kerberos {bba3add2-c229-4cdb-ae2b-57eb6966b0c4}

ACPI Driver Trace Provider {dab01d4d-2d48-477d-b1c3-daad0ce6f06b}

3. I found the following in the TRACE.LOG file:

N T K e r n e l L o g g e r C : \ W I N D O W S \ S y s t e m 3 2 \ L o g F i l e s \ W M I \ t r a c e . l o g

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ W I N D O W S \ S y s t e m 3 2 \ L o g F i l e s \ W M I \ t r a c e . l o g

\ D e v i c e \ N e t B T _ T c p i p _ { 8 1 1 E 9 E 3 9 - 9 9 1 2 - 4 A 0 2 - 9 C 8 0 - A 8 6 4 8 F E 1 3 C F 6 } ]?

4. Assuming that the "NT Kernel Logger" was creating the file, I unsuccessfully attempted to find a relevant entry in "Administrative Tools."

If I'm correct and the TRACE.LOG file is being created by the NT Kernel Logger, I assume I can limit the file's size if I can find the control for that logger. Any ideas?

Thanks,
SRS

Guest · Mar 16, 2002

The system won't permit me to delete the file, but please see my reply post of this date to Toejam31 for an update.

Thanks,
SRS

Guest · Mar 20, 2002

Hi,

I had the same problem... one question: did you use bootvis, the tool to speed up the loading process off XP?

That #$$$%^&(*( program was the cause of my trace.log file!

BHard

Toejam31 · Mar 20, 2002

Woohoo ... BHard got it in one ... that's it!

I checked out the BootVis tool, and that's the correct file path for the trace.log.

When you used the utility, the parameters must have gotten changed from the default, and now it is running at every boot, and attempting to optimize the boot files on the hard drive while the GUI is running.

It didn't do diddly-squat for my system bootup time ... in fact, it caused the system to boot slower than before. It added about five seconds from a cold boot, even after it wasn't running. Typical, crappy MS programming.

I suggest you delete it, and then you should be able to remove the file.

If you can't remember where it is located, either double-click the self-extracting .exe and take note of the installation folder, or just search for bootvis.exe. You should delete the other files in the folder, too, such as the Trace*.bin.

Toejam31

My Rig: <A HREF="http://www.anandtech.com/mysystemrig.html?rigid=6847" target="_new">Toejam31's Tantalizing Tantric Toy</A>
Second Rig: <A HREF="http://www.anandtech.com/mysystemrig.html?rigid=15942" target="_new">Toey's Dynamite DDR Duron</A>
____________________________________________________________

"Procrastination on your part does not constitute an emergency on my part."

Guest · Mar 30, 2002

EXTREME apologies. I've been gone for 10 days and couldn't reply sooner.

You guys are terrific! I'm sure you hit the nail on the head. I attempted to use BOOTVIS.EXE quite some time ago, but it wouldn't work. It kept saying that I had no hard drive, or something similar. Anyway, I deleted the file.

As I remember, no directory was ever created. I was just instructed to place the app in my root directory. When it didn't work, I deleted the file.

I did a search and BOOTVIS.EXE doesn't show up anywhere. But, "TRACE_BOOT_1_1.BIN" shows up in my "C:\Documents and Settings\Admin" directory, created 1/22/2000. Is that the file you're suggesting I delete?

Thanks again for being so helpful! Please post back with confirmation that I should delete "TRACE_BOOT_1_1.BIN" and I'll report the result on re-boot.

SRS

Toejam31 · Mar 30, 2002

Yes, I'd definitely delete the file.

You might also wish to download a program to clean the Registry of any extraneous keys that may be associated with the program, such as <A HREF="http://www.vtoy.fi/jv16/shtml/regcleaner.shtml" target="_new">RegCleaner</A>, which is my preference for this kind of utility.

Toejam31

My Rig: <A HREF="http://www.anandtech.com/mysystemrig.html?rigid=6847" target="_new">Toejam31's Tantalizing Tantric Toy</A>
Second Rig: <A HREF="http://www.anandtech.com/mysystemrig.html?rigid=15942" target="_new">Toey's Dynamite DDR Duron</A>
____________________________________________________________

"Procrastination on your part does not constitute an emergency on my part."

Guest · Mar 30, 2002

Oh, well. I really thought we had it licked. Nope.

I deleted the file, ran REGCLEANER (great app, by the way), and re-booted. NaDa! There was the file.

FYI, I ran "tracelog -stop 'NT Kernel Logger'" and it did the trick, but only for the current session. On re-boot, there was that "trace.log" growing away as usual.

I still think you're right, that the problem may be connected with that program I tried back in January, but that there's something else I need to do to get rid of whatever it set on the system. If that's the case, I assume REGCLEANER wasn't able to identify the entry on automatic, and I wasn't able to identify it visually. Any ideas will be most welcome.

Thanks,
SRS

Guest · Mar 30, 2002

As indicated in my earlier post, I still think you were right, that it was BOOTVIS that may have caused my problem. Unfortunately, it appears that I need to do something more than just delete the executable and the apparently related file I found after reading your post.

Was there something else you did, by any chance, back when you had the problem? Any idea would be greatly appreciated.

Thanks,
SRS

Toejam31 · Mar 31, 2002

At this point, unless BHard has another idea, I think you have four options left to you:

1.) Boot into Safe Mode, and delete the entire
C:\Windows\System32\LogFiles folder, which was created when BootVis was installed and run. Clean installations of WinXP don't have this folder by default.

2.) Check these Registry keys for any files that might show that the program is loading from the Registry during startup:

Run REGEDIT.EXE at the Start\Run-Command Line.

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run

There are several other "Run" (RunOnce, Run Services, etc.) keys in the same area. Make sure that there is no reference to the file you wish to remove in any of them.

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run

HKEY_USERS\.DEFAULT\Software\Microsoft|Windows\CurrentVersion\Run

Note: If you are worried about damaging the Registry, you can always highlight any key before you edit it, and choose to export the entire branch. This option is available from the Registry Editor Toolbar in one of the drop-down menu's. Give the key a name, and save it somewhere safe. Later, if it appears that the changes caused a problem, double-click the exported key, and it will reinstall back into the Registry, completely intact, just as it was.

Exporting a key will not remove it from the Registry. This is only a copy.

3.) Reinstalling the latest version of BootVis, running it, and changing the parameters this time around so that the Trace Log doesn't get created anew with each boot.

<A HREF="http://www.windows-help.net/WindowsXP/tune-19.html" target="_new">BootVis Help</A>

<A HREF="http://www.microsoft.com/hwdev/platform/performance/fastboot/default.asp" target="_new">BootVis Download</A>

4.) Formatting the partition and reinstalling the operating system.

Toejam31

My Rig: <A HREF="http://www.anandtech.com/mysystemrig.html?rigid=6847" target="_new">Toejam31's Tantalizing Tantric Toy</A>
Second Rig: <A HREF="http://www.anandtech.com/mysystemrig.html?rigid=15942" target="_new">Toey's Dynamite DDR Duron</A>
____________________________________________________________

"Procrastination on your part does not constitute an emergency on my part."

Guest · Apr 6, 2002

Thanks, Toejam31. As soon as I can find the time, I'll follow your suggestions. As an interim solution, I created a DOS batch file which I run to stop the logging for each session.

Thanks again,
SRS

P.S. By the way, I wonder if you might know how to get into the place where the system stores the command lines for the drop-down selections displayed when you right-click a file in Windows Explorer. I switched to the corporate edition of McAfee, which doesn't provide a program name so that I can automate scanning files downloaded via GetRight, etc. I'm thinking that, if I can identify the command line used by the selection intended to run a scan on a particular file, group of files or folder, I can use it in the relevant field in the download manager and other such apps which provide a similar facility. Please let me know how I can get a look at this command line, if you know, when you have an opportunity.

Thanks again for all your help!

Anybody have an idea what this is?

Guest

Guest

Splendid

Distinguished

Guest

Guest

Distinguished

Guest

Guest

Distinguished

Guest

Guest

Distinguished

Guest

Guest

Guest

Guest

Guest

Guest

Guest

Guest

Distinguished

Guest

Guest

Distinguished

Guest

Guest

Guest

Guest

Distinguished

Guest

Guest

Share this page