Faxsetup Log File

In C:\Windows I have a Notepad File called faxsetup.log

This File is added to at every StartUp and is now over 2 Mb

I do no thave a Fax Machine and the Windows Fax Services Component is not
Installed

So - what created this File originally and what is causing it to grow all
the time?

Is there some Service Running which I can stop?

Thanks

I'm not sure this is much help. But, I have the same file in c:\windows and
itis modified every month or two when I boot up. And, it's size is only 150K.
Since it's a log file, you could probably delete it and it will be recreated
the next time it's called for. At least, you could rename it before deleting
in case you need to bring it back to life.

Les

"Lesley" wrote:

In C:\Windows I have a Notepad File called faxsetup.log

This File is added to at every StartUp and is now over 2 Mb

I do no thave a Fax Machine and the Windows Fax Services Component is not
Installed

So - what created this File originally and what is causing it to grow all
the time?

Is there some Service Running which I can stop?

Thanks

Thanks for the Reply

I have Re-named it to Faxsetup old and it has Re-created itself - it is now
only 100Kb but still continues to grow

Since I don't have the Windows Fax Services Installed I can't think what is
adding to it all the time

"SonomaAirporter" wrote:

I'm not sure this is much help. But, I have the same file in c:\windows and
itis modified every month or two when I boot up. And, it's size is only 150K.
Since it's a log file, you could probably delete it and it will be recreated
the next time it's called for. At least, you could rename it before deleting
in case you need to bring it back to life.

Les

"Lesley" wrote:

In C:\Windows I have a Notepad File called faxsetup.log

This File is added to at every StartUp and is now over 2 Mb

I do no thave a Fax Machine and the Windows Fax Services Component is not
Installed

So - what created this File originally and what is causing it to grow all
the time?

Is there some Service Running which I can stop?

Thanks

Thanks for the info

I found FxsOCM.inf but it is a Notepad File, are you suggesting I Edit this?

If so what do I change to what?

Thanks

"... et al." wrote:

Lesley wrote:

In C:\Windows I have a Notepad File called faxsetup.log

This File is added to at every StartUp and is now over 2 Mb

I do no thave a Fax Machine and the Windows Fax Services Component is not
Installed

So - what created this File originally and what is causing it to grow all
the time?

Is there some Service Running which I can stop?

When does this log update? For me it gets appended/recreated
(every time?) when i explicitly run an update for the WinXP OS.
I guess that for people that have ms 'Automatic Update' service
running it will happen at, say, unpredictable occasions.


Looking in the [FaxSetup.log] log i see strings like "OC Manager
version: 0x50000, FaxOcm Expected Version: 0x50000, seems OK" and
"fxocDbg_Term"

Optional Component = OC
OC Manager = OCM

No file with name 'FaxOcm' in it does exist on my machine, but
files [FxsOCM.inf] and [FxsOCM.dll] does. If you look at the
'Original File name' for [FxsOCM.dll] (description 'Fax Optional
Component Installer') it turns out to be ... [FaxOCM.dll].

[FxsOCM.inf] lets you specify the debug logging-level from the
default more verbose down to no logging (even if it claims the
log, [FaxSetup.log], is written to %Temp% and not %WinDir% where
it actually is located). Even if choosing no logging the
[FaxSetup.log] file will still be touched/recreated when an
update is done, but it will not grow any more.


--
All names have been changed to confuse the innocent.

Please followup in the newsgroup.
E-mail address is invalid due to spam-control.

Lesley wrote:

In C:\Windows I have a Notepad File called faxsetup.log

This File is added to at every StartUp and is now over 2 Mb

I do no thave a Fax Machine and the Windows Fax Services Component is not
Installed

So - what created this File originally and what is causing it to grow all
the time?

Is there some Service Running which I can stop?

When does this log update? For me it gets appended/recreated
(every time?) when i explicitly run an update for the WinXP OS.
I guess that for people that have ms 'Automatic Update' service
running it will happen at, say, unpredictable occasions.


Looking in the [FaxSetup.log] log i see strings like "OC Manager
version: 0x50000, FaxOcm Expected Version: 0x50000, seems OK" and
"fxocDbg_Term"

Optional Component = OC
OC Manager = OCM

No file with name 'FaxOcm' in it does exist on my machine, but
files [FxsOCM.inf] and [FxsOCM.dll] does. If you look at the
'Original File name' for [FxsOCM.dll] (description 'Fax Optional
Component Installer') it turns out to be ... [FaxOCM.dll].

[FxsOCM.inf] lets you specify the debug logging-level from the
default more verbose down to no logging (even if it claims the
log, [FaxSetup.log], is written to %Temp% and not %WinDir% where
it actually is located). Even if choosing no logging the
[FaxSetup.log] file will still be touched/recreated when an
update is done, but it will not grow any more.


--
All names have been changed to confuse the innocent.

Please followup in the newsgroup.
E-mail address is invalid due to spam-control.

Lesley wrote:

Thanks for the info

I found FxsOCM.inf but it is a Notepad File, are you suggesting I Edit this?

If so what do I change to what?

Thanks

If you feel unsure it's easiest to just move or rename the
[FaxSetup.log] file and then a couple of days later, when that
didn't cause any problems, delete it.

But if you decide to edit the [FxsOCM.inf] file, the info for
that is in the file itself .. like this:
; DebugLevel can be one of the following:
; 0 - no debug output
; 1 - see errors only
; 2 - see errors & warnings
; 3 - see all the debug output

Then a few lines further down is the actual entry to edit:
DebugLevel = 3

Personally i have changed that line to:
DebugLevel = 2

After i did that my [FaxSetup.log] file stays empty.


"... et al." wrote:


[FxsOCM.inf] lets you specify the debug logging-level from the
default more verbose down to no logging (even if it claims the
log, [FaxSetup.log], is written to %Temp% and not %WinDir% where
it actually is located). Even if choosing no logging the
[FaxSetup.log] file will still be touched/recreated when an
update is done, but it will not grow any more.


--
"26, 27, 28, 29, i'm gonna make your face look just like mine
Five, four, three, two, one, Cassius Clay you'd better run"

Please followup in the newsgroup.
E-mail address is invalid due to spam-control.

Thanks

I will Edit it as you suggest



"... et al." wrote:

Lesley wrote:

Thanks for the info

I found FxsOCM.inf but it is a Notepad File, are you suggesting I Edit this?

If so what do I change to what?

Thanks

If you feel unsure it's easiest to just move or rename the
[FaxSetup.log] file and then a couple of days later, when that
didn't cause any problems, delete it.

But if you decide to edit the [FxsOCM.inf] file, the info for
that is in the file itself .. like this:
; DebugLevel can be one of the following:
; 0 - no debug output
; 1 - see errors only
; 2 - see errors & warnings
; 3 - see all the debug output

Then a few lines further down is the actual entry to edit:
DebugLevel = 3

Personally i have changed that line to:
DebugLevel = 2

After i did that my [FaxSetup.log] file stays empty.


"... et al." wrote:


[FxsOCM.inf] lets you specify the debug logging-level from the
default more verbose down to no logging (even if it claims the
log, [FaxSetup.log], is written to %Temp% and not %WinDir% where
it actually is located). Even if choosing no logging the
[FaxSetup.log] file will still be touched/recreated when an
update is done, but it will not grow any more.


--
"26, 27, 28, 29, i'm gonna make your face look just like mine
Five, four, three, two, one, Cassius Clay you'd better run"

Please followup in the newsgroup.
E-mail address is invalid due to spam-control.