Sign in with
Sign up | Sign in
Your question

Microsoft Fax Console crashing

Last response: in Windows XP
Share
Anonymous
September 8, 2004 1:07:05 AM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

Microsoft Fax Console crashes when I launch it.

Removing it and adding it as a windows component didn't fix anything.

I see there are two versions of it under \WINDOWS\system32

08/29/2002 06:41 AM 130,048 fxsclnt(2).exe
08/04/2004 03:56 AM 143,360 fxsclnt.exe

Here's the pop-up error window:

http://www.post-in-toronto.on.ca/chuck.kahn/hello/246/9...

How do I launch it successfully?
Anonymous
September 8, 2004 9:24:35 AM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

Perhaps you should start at the beginning. List the steps that produced your
problem. Did Fax ever work successfully? How many times did you install Fax
and how? Is your analog fax modem on the Windows XP HCL list?
--
Russ Valentine
[MVP-Outlook]
"Chuck Kahn" <chuck.kahn@post-in-toronto.on.ca> wrote in message
news:3f532227.0409072007.9e1114@posting.google.com...
> Microsoft Fax Console crashes when I launch it.
>
> Removing it and adding it as a windows component didn't fix anything.
>
> I see there are two versions of it under \WINDOWS\system32
>
> 08/29/2002 06:41 AM 130,048 fxsclnt(2).exe
> 08/04/2004 03:56 AM 143,360 fxsclnt.exe
>
> Here's the pop-up error window:
>
> http://www.post-in-toronto.on.ca/chuck.kahn/hello/246/9...
>
> How do I launch it successfully?
Anonymous
September 12, 2004 8:23:21 PM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

"Russ Valentine [MVP-Outlook]" <russval@mvps.org> wrote in message news:<OyFoM4YlEHA.3760@TK2MSFTNGP12.phx.gbl>...
> Perhaps you should start at the beginning. List the steps that produced your
> problem.

The steps that produced the problem were:

1) Installing a new faxmodem.

2) Double clicking the shortcut to "Fax Console" which points to
%SystemRoot%\system32\FxsClnt.exe /new

3) Watching as this error message pops up:
http://www.post-in-toronto.on.ca/chuck.kahn/hello/246/9...

Actually, I can still poke around in the Fax Console if I move the
error pop up out of the way.

The event viewer reports the following:

Faulting application fxsclnt.exe, version 5.2.2600.2180, faulting
module nl_lsp.dll, version 0.0.0.0, fault address 0x00002170.

> Did Fax ever work successfully?

Yes. Last time I used it successfully was 04/21/2004 9:37:17 PM. But
that was another faxmodem.

> How many times did you install Fax and how?

Three times. I installed it once, nine months ago. When it didn't
work last week, I re-installed it. When it still didn't work, I
uninstalled and re-installed it.

Every installation was performed through the Windows Components Wizard
utility.

> Is your analog fax modem on the Windows XP HCL list?

It is listed as "Compatible with Windows XP" at
http://www.microsoft.com/windows/catalog/default.aspx?s...

> "Chuck Kahn" <chuck.kahn@post-in-toronto.on.ca> wrote in message
> news:3f532227.0409072007.9e1114@posting.google.com...
> > Microsoft Fax Console crashes when I launch it.
> >
> > Removing it and adding it as a windows component didn't fix anything.
> >
> > I see there are two versions of it under \WINDOWS\system32
> >
> > 08/29/2002 06:41 AM 130,048 fxsclnt(2).exe
> > 08/04/2004 03:56 AM 143,360 fxsclnt.exe
> >
> > Here's the pop-up error window:
> >
> > http://www.post-in-toronto.on.ca/chuck.kahn/hello/246/9...
> >
> > How do I launch it successfully?
Related resources
Anonymous
September 12, 2004 10:36:09 PM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

Let me make sure I've got this straight. Your old fax modem worked. But then
you installed a new fax modem and then just launched the Fax program?
The logical sequence (to me at least) would have been to uninstall Fax,
install your new modem and make sure it was working with no conflicts, then
reinstall the Fax Service. I would never expect the Fax Service to detect a
new modem and reconfigure itself automatically.
--
Russ Valentine
[MVP-Outlook]
"Chuck Kahn" <chuck.kahn@post-in-toronto.on.ca> wrote in message
news:3f532227.0409121523.4b4396c3@posting.google.com...
> "Russ Valentine [MVP-Outlook]" <russval@mvps.org> wrote in message
> news:<OyFoM4YlEHA.3760@TK2MSFTNGP12.phx.gbl>...
>> Perhaps you should start at the beginning. List the steps that produced
>> your
>> problem.
>
> The steps that produced the problem were:
>
> 1) Installing a new faxmodem.
>
> 2) Double clicking the shortcut to "Fax Console" which points to
> %SystemRoot%\system32\FxsClnt.exe /new
>
> 3) Watching as this error message pops up:
> http://www.post-in-toronto.on.ca/chuck.kahn/hello/246/9...
>
> Actually, I can still poke around in the Fax Console if I move the
> error pop up out of the way.
>
> The event viewer reports the following:
>
> Faulting application fxsclnt.exe, version 5.2.2600.2180, faulting
> module nl_lsp.dll, version 0.0.0.0, fault address 0x00002170.
>
>> Did Fax ever work successfully?
>
> Yes. Last time I used it successfully was 04/21/2004 9:37:17 PM. But
> that was another faxmodem.
>
>> How many times did you install Fax and how?
>
> Three times. I installed it once, nine months ago. When it didn't
> work last week, I re-installed it. When it still didn't work, I
> uninstalled and re-installed it.
>
> Every installation was performed through the Windows Components Wizard
> utility.
>
>> Is your analog fax modem on the Windows XP HCL list?
>
> It is listed as "Compatible with Windows XP" at
> http://www.microsoft.com/windows/catalog/default.aspx?s...
>
>> "Chuck Kahn" <chuck.kahn@post-in-toronto.on.ca> wrote in message
>> news:3f532227.0409072007.9e1114@posting.google.com...
>> > Microsoft Fax Console crashes when I launch it.
>> >
>> > Removing it and adding it as a windows component didn't fix anything.
>> >
>> > I see there are two versions of it under \WINDOWS\system32
>> >
>> > 08/29/2002 06:41 AM 130,048 fxsclnt(2).exe
>> > 08/04/2004 03:56 AM 143,360 fxsclnt.exe
>> >
>> > Here's the pop-up error window:
>> >
>> > http://www.post-in-toronto.on.ca/chuck.kahn/hello/246/9...
>> >
>> > How do I launch it successfully?
Anonymous
September 18, 2004 2:49:37 PM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

"Russ Valentine [MVP-Outlook]" <russval@mvps.org> wrote in message news:<OhCmMFSmEHA.2968@TK2MSFTNGP14.phx.gbl>...
> Let me make sure I've got this straight. Your old fax modem worked. But then
> you installed a new fax modem and then just launched the Fax program?

The old fax modem worked, but it was seven years old, and it didn't
have voice modem capabilities. So I upgraded.

I installed the new fax modem for it's voice capabilities, and as I
use Fax Console infrequently (once every 7-9 months), I never thought
to uninstall it.

> The logical sequence (to me at least) would have been to uninstall Fax,
> install your new modem and make sure it was working with no conflicts, then
> reinstall the Fax Service. I would never expect the Fax Service to detect a
> new modem and reconfigure itself automatically.

How do I make sure that the new modem is working with no conflicts? I
can launch Hypterminal and type ATDT followed by a 10-digit number and
the modem dials the number. Does that establish a lack of conflicts?

When I look under the modem's Advanced Port Settings, the COM Port
Number drop down menu has COM8 selected and COM1 through COM7 report
that they are "in use." Is that an indication of a conflict?

I have revised my expections from:

a) expecting fax console to detect a new modem and reconfiguring
itself automatically.

to:

b) expecting fax console to work after being re-installed.

to:

c) expecting fax console to work after being uninstalled and
re-installed.

None of these expectations have been met. I need some new
expectations to work with.
Anonymous
September 18, 2004 5:08:43 PM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

I would simply make sure your new modem is an analog fax modem with class 1
or 2 fax capabilities, is on the Windows XP HCL list and that it appears in
Device Manager with no conflicts. An IRQ conflict in MSCONFIG may not be
relevant.
Then I would install XP Fax.
--
Russ Valentine
[MVP-Outlook]
"Chuck Kahn" <chuck.kahn@post-in-toronto.on.ca> wrote in message
news:3f532227.0409180949.73d8bd58@posting.google.com...
> "Russ Valentine [MVP-Outlook]" <russval@mvps.org> wrote in message
> news:<OhCmMFSmEHA.2968@TK2MSFTNGP14.phx.gbl>...
>> Let me make sure I've got this straight. Your old fax modem worked. But
>> then
>> you installed a new fax modem and then just launched the Fax program?
>
> The old fax modem worked, but it was seven years old, and it didn't
> have voice modem capabilities. So I upgraded.
>
> I installed the new fax modem for it's voice capabilities, and as I
> use Fax Console infrequently (once every 7-9 months), I never thought
> to uninstall it.
>
>> The logical sequence (to me at least) would have been to uninstall Fax,
>> install your new modem and make sure it was working with no conflicts,
>> then
>> reinstall the Fax Service. I would never expect the Fax Service to detect
>> a
>> new modem and reconfigure itself automatically.
>
> How do I make sure that the new modem is working with no conflicts? I
> can launch Hypterminal and type ATDT followed by a 10-digit number and
> the modem dials the number. Does that establish a lack of conflicts?
>
> When I look under the modem's Advanced Port Settings, the COM Port
> Number drop down menu has COM8 selected and COM1 through COM7 report
> that they are "in use." Is that an indication of a conflict?
>
> I have revised my expections from:
>
> a) expecting fax console to detect a new modem and reconfiguring
> itself automatically.
>
> to:
>
> b) expecting fax console to work after being re-installed.
>
> to:
>
> c) expecting fax console to work after being uninstalled and
> re-installed.
>
> None of these expectations have been met. I need some new
> expectations to work with.
Anonymous
September 19, 2004 10:36:51 PM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

chuck.kahn@post-in-toronto.on.ca (Chuck Kahn) wrote in message news:<3f532227.0409190722.4f6614de@posting.google.com>...
> Could it be some corrupt log that Fax Console is choking on?

I found the Console's logs under:

\Documents and Settings\All Users\Application Data\Microsoft\Windows
NT\MSFax\ActivityLog

There were three files:

| InboxLOG.txt
| OutboxLOG.txt
| schema.ini

In order to delete them, I had to stop the Fax Service. Relaunching
Fax Console after deletion still resulted in "Faulting application
fxsclnt.exe, version 5.2.2600.2180, faulting module nl_lsp.dll,
version 0.0.0.0, fault address 0x00002170."

So corrupt logs aren't the issue.
Anonymous
September 19, 2004 10:49:46 PM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

chuck.kahn@post-in-toronto.on.ca (Chuck Kahn) wrote in message news:<3f532227.0409190722.4f6614de@posting.google.com>...
> It encountered a problem and needs to close. The problem hasn't
> changed.

Also interesting: if I stop the Print Spooler service and then launch
the Fax Console, a warning message comes up saying "A connection to
the fax printer cannot be made", to which I click "OK"; then the Fax
Console just sits there, not crashing. Then I relaunch the Print
Spooler service. Still no crash from Fax Console. Then, if I either
exit and relaunch Fax Console, or if I don't exit and select Configure
Fax from the Tools menu, Fax Console crashes with the same "Faulting
application fxsclnt.exe, version 5.2.2600.2180, faulting module
nl_lsp.dll, version 0.0.0.0, fault address 0x00002170."
Anonymous
September 19, 2004 11:21:53 PM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

chuck.kahn@post-in-toronto.on.ca (Chuck Kahn) wrote in message news:<3f532227.0409121523.4b4396c3@posting.google.com>...
> The event viewer reports the following:
>
> Faulting application fxsclnt.exe, version 5.2.2600.2180, faulting
> module nl_lsp.dll, version 0.0.0.0, fault address 0x00002170.

Uninstalling Net Limiter Beta (where the nl_lsp.dll came from) fixed the problem.

Thanks to RunOrDie of DALnet's #windows95 channel for the advice!
Anonymous
September 20, 2004 1:24:02 AM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

I wasn't asking about corrupt logs. I was asking you for the contents of
faxsetup.log.

--
Russ Valentine
[MVP-Outlook]
"Chuck Kahn" <chuck.kahn@post-in-toronto.on.ca> wrote in message
news:3f532227.0409191736.66f2e727@posting.google.com...
> chuck.kahn@post-in-toronto.on.ca (Chuck Kahn) wrote in message
> news:<3f532227.0409190722.4f6614de@posting.google.com>...
>> Could it be some corrupt log that Fax Console is choking on?
>
> I found the Console's logs under:
>
> \Documents and Settings\All Users\Application Data\Microsoft\Windows
> NT\MSFax\ActivityLog
>
> There were three files:
>
> | InboxLOG.txt
> | OutboxLOG.txt
> | schema.ini
>
> In order to delete them, I had to stop the Fax Service. Relaunching
> Fax Console after deletion still resulted in "Faulting application
> fxsclnt.exe, version 5.2.2600.2180, faulting module nl_lsp.dll,
> version 0.0.0.0, fault address 0x00002170."
>
> So corrupt logs aren't the issue.
Anonymous
September 20, 2004 10:28:14 AM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

"Russ Valentine [MVP-Outlook]" <russval@mvps.org> wrote in message news:<uaRgmjrnEHA.3324@TK2MSFTNGP15.phx.gbl>...
> I wasn't asking about corrupt logs. I was asking you for the contents of
> faxsetup.log.

Your faxsetup.log question hadn't reached google groups when I wrote
that.

I can see that there are 12655 lines in my faxsetup.log, the most
recent entry is this:

[09/20/04 08:40:09] [0x1160] [ ] FaxOcmSetupProc (fax - (null))
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] FaxOcmSetup proc called with
function 'OC_CLEANUP'
[09/20/04 08:40:09] [0x1160] [ ] prv_OnCleanup
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] Term Unattended module
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
[09/20/04 08:40:09] [0x1160] [ ] Term Service Module
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
[09/20/04 08:40:09] [0x1160] [ ] Term Registry Module
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
[09/20/04 08:40:09] [0x1160] [ ] Term Print Module
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
[09/20/04 08:40:09] [0x1160] [ ] Term MAPI Module
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] } (TRUE)
[09/20/04 08:40:09] [0x1160] [ ] Term File Module
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
[09/20/04 08:40:09] [0x1160] [ ] Term Util module
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
[09/20/04 08:40:09] [0x1160] [ ] Term State module
[09/20/04 08:40:09] [0x1160] [ ] {
[09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
[09/20/04 08:40:09] [0x1160] [ ] fxocDbg_Term
[09/20/04 08:40:09] [0x1160] [ ] {

I don't know how to interpret this.

Anyway, I can launch Fax Console without it crashing, but printing to
fax no longer works (as it did in April) if I make a cover page with
the "Send Fax Wizard." (Back in January, I couldn't queue up more
than 3 fax numbers at a time, so I had to keep re-typing my cover page
info. See "The Fax service print monitor has failed to submit the
fax." <17776f61.0401041810.1847fca1@posting.google.com> )

Here are the steps I'm going through:

1) Open document in Word.

2) File | Print -- choose the printer named "Fax"; click "OK"

3) "Send Fax Wizard" comes up; click "Next"; under "Recipient
Information" click "Address Book"; entry in Address Book is chosen
with a fax number; click "Next"; skipping the Cover Page for this
exercise, "Next"; on "Schedule" dialog, chose "Now" and "Normal"
priority, "Next"; on "Completing the Send Fax Wizard" dialog, clicked
on "Finish";

4) Then it starts dialing and I click cancel since this is just a
test. If I choose a Cover Page in step 3, dialing does not happen,
and no error message or event viewer item comes up to indicate what
went wrong.
Anonymous
September 20, 2004 9:44:24 PM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

Each time you post, you post with a different story. I'm having a hard time
keeping track. It appears that the Fax Console is no longer crashing. Is
that right?
If so, and if you can send faxes, then the faxsetup.log is no longer in
play.
Please bring us up to date on what the current problem is and what happened
to the earlier problems.
--
Russ Valentine
[MVP-Outlook]
"Chuck Kahn" <chuck.kahn@post-in-toronto.on.ca> wrote in message
news:3f532227.0409200528.40da6b09@posting.google.com...
> "Russ Valentine [MVP-Outlook]" <russval@mvps.org> wrote in message
> news:<uaRgmjrnEHA.3324@TK2MSFTNGP15.phx.gbl>...
>> I wasn't asking about corrupt logs. I was asking you for the contents of
>> faxsetup.log.
>
> Your faxsetup.log question hadn't reached google groups when I wrote
> that.
>
> I can see that there are 12655 lines in my faxsetup.log, the most
> recent entry is this:
>
> [09/20/04 08:40:09] [0x1160] [ ] FaxOcmSetupProc (fax - (null))
> [09/20/04 08:40:09] [0x1160] [ ] {
> [09/20/04 08:40:09] [0x1160] [ ] FaxOcmSetup proc called with
> function 'OC_CLEANUP'
> [09/20/04 08:40:09] [0x1160] [ ] prv_OnCleanup
> [09/20/04 08:40:09] [0x1160] [ ] {
> [09/20/04 08:40:09] [0x1160] [ ] Term Unattended module
> [09/20/04 08:40:09] [0x1160] [ ] {
> [09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
> [09/20/04 08:40:09] [0x1160] [ ] Term Service Module
> [09/20/04 08:40:09] [0x1160] [ ] {
> [09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
> [09/20/04 08:40:09] [0x1160] [ ] Term Registry Module
> [09/20/04 08:40:09] [0x1160] [ ] {
> [09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
> [09/20/04 08:40:09] [0x1160] [ ] Term Print Module
> [09/20/04 08:40:09] [0x1160] [ ] {
> [09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
> [09/20/04 08:40:09] [0x1160] [ ] Term MAPI Module
> [09/20/04 08:40:09] [0x1160] [ ] {
> [09/20/04 08:40:09] [0x1160] [ ] } (TRUE)
> [09/20/04 08:40:09] [0x1160] [ ] Term File Module
> [09/20/04 08:40:09] [0x1160] [ ] {
> [09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
> [09/20/04 08:40:09] [0x1160] [ ] Term Util module
> [09/20/04 08:40:09] [0x1160] [ ] {
> [09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
> [09/20/04 08:40:09] [0x1160] [ ] Term State module
> [09/20/04 08:40:09] [0x1160] [ ] {
> [09/20/04 08:40:09] [0x1160] [ ] } (ERROR_SUCCESS)
> [09/20/04 08:40:09] [0x1160] [ ] fxocDbg_Term
> [09/20/04 08:40:09] [0x1160] [ ] {
>
> I don't know how to interpret this.
>
> Anyway, I can launch Fax Console without it crashing, but printing to
> fax no longer works (as it did in April) if I make a cover page with
> the "Send Fax Wizard." (Back in January, I couldn't queue up more
> than 3 fax numbers at a time, so I had to keep re-typing my cover page
> info. See "The Fax service print monitor has failed to submit the
> fax." <17776f61.0401041810.1847fca1@posting.google.com> )
>
> Here are the steps I'm going through:
>
> 1) Open document in Word.
>
> 2) File | Print -- choose the printer named "Fax"; click "OK"
>
> 3) "Send Fax Wizard" comes up; click "Next"; under "Recipient
> Information" click "Address Book"; entry in Address Book is chosen
> with a fax number; click "Next"; skipping the Cover Page for this
> exercise, "Next"; on "Schedule" dialog, chose "Now" and "Normal"
> priority, "Next"; on "Completing the Send Fax Wizard" dialog, clicked
> on "Finish";
>
> 4) Then it starts dialing and I click cancel since this is just a
> test. If I choose a Cover Page in step 3, dialing does not happen,
> and no error message or event viewer item comes up to indicate what
> went wrong.
Anonymous
September 21, 2004 10:09:43 AM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

"Russ Valentine [MVP-Outlook]" <russval@mvps.org> wrote in message news:<uD3liN2nEHA.556@tk2msftngp13.phx.gbl>...
> Each time you post, you post with a different story. I'm having a hard time
> keeping track. It appears that the Fax Console is no longer crashing. Is that right?
> If so, and if you can send faxes, then the faxsetup.log is no longer in play.
> Please bring us up to date on what the current problem is and what happened
> to the earlier problems.

Earlier problem of Fax Console crashing was solved by uninstalling Net
Limiter Beta (that's where the offending .dll originated)

New problems:

1) If I select cover page during the Send Fax Wizard, no fax gets
sent.

2) If I select multiple fax recipients during the Send Fax Wizard, no
fax gets sent. (Actually an old problem I've had since my January 4,
2004 post to microsoft.public.windowsxp.print_fax "The Fax service
print monitor has failed to submit the fax.")

The only way a fax gets successfully sent with the Send Fax Wizard is
to send to one recipient with no cover page.
Anonymous
September 21, 2004 6:03:09 PM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

Never seen anything like it reported.
Are your cover pages in the correct location? Do they open correctly in the
Cover Page editor? The Help files will clue you in on all this.
--
Russ Valentine
[MVP-Outlook]
"Chuck Kahn" <chuck.kahn@post-in-toronto.on.ca> wrote in message
news:3f532227.0409210509.13b175@posting.google.com...
> "Russ Valentine [MVP-Outlook]" <russval@mvps.org> wrote in message
> news:<uD3liN2nEHA.556@tk2msftngp13.phx.gbl>...
>> Each time you post, you post with a different story. I'm having a hard
>> time
>> keeping track. It appears that the Fax Console is no longer crashing. Is
>> that right?
>> If so, and if you can send faxes, then the faxsetup.log is no longer in
>> play.
>> Please bring us up to date on what the current problem is and what
>> happened
>> to the earlier problems.
>
> Earlier problem of Fax Console crashing was solved by uninstalling Net
> Limiter Beta (that's where the offending .dll originated)
>
> New problems:
>
> 1) If I select cover page during the Send Fax Wizard, no fax gets
> sent.
>
> 2) If I select multiple fax recipients during the Send Fax Wizard, no
> fax gets sent. (Actually an old problem I've had since my January 4,
> 2004 post to microsoft.public.windowsxp.print_fax "The Fax service
> print monitor has failed to submit the fax.")
>
> The only way a fax gets successfully sent with the Send Fax Wizard is
> to send to one recipient with no cover page.
Anonymous
February 14, 2005 4:49:03 PM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

Got the same problem here with a brand new Gateway with SP2 preinstalled.
When I try to install Fax Component get error message 0x8 unable to find some
files and the Fax component install fails. Contacted Gateway. They have
nothing to say on the matter. I guess this one will be on the docket for a
fix at Microsoft on SP 33.

Mike


"Chuck Kahn" wrote:

> Microsoft Fax Console crashes when I launch it.
>
> Removing it and adding it as a windows component didn't fix anything.
>
> I see there are two versions of it under \WINDOWS\system32
>
> 08/29/2002 06:41 AM 130,048 fxsclnt(2).exe
> 08/04/2004 03:56 AM 143,360 fxsclnt.exe
>
> Here's the pop-up error window:
>
> http://www.post-in-toronto.on.ca/chuck.kahn/hello/246/9...
>
> How do I launch it successfully?
>
Anonymous
February 14, 2005 7:58:50 PM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

Did Gateway at least tell you (or have you been able to figure out on your
own) where the Windows XP installation files are for your system?
When the installation routine is unable to find the necessary installation
files (even when directed to the appropriate i386 Folder) it usually means
that the installation files are compressed or in another location. This is
often the case when the files are pre-copied by a manufacturer on the hard
drive. I suspect this will be an issue Gateway must solve.
--
Russ Valentine
[MVP-Outlook]
"MichaelM" <MichaelM@discussions.microsoft.com> wrote in message
news:47898505-A6B1-4DF7-A57F-C497F0468501@microsoft.com...
> Got the same problem here with a brand new Gateway with SP2 preinstalled.
> When I try to install Fax Component get error message 0x8 unable to find
> some
> files and the Fax component install fails. Contacted Gateway. They have
> nothing to say on the matter. I guess this one will be on the docket for a
> fix at Microsoft on SP 33.
>
> Mike
>
>
> "Chuck Kahn" wrote:
>
>> Microsoft Fax Console crashes when I launch it.
>>
>> Removing it and adding it as a windows component didn't fix anything.
>>
>> I see there are two versions of it under \WINDOWS\system32
>>
>> 08/29/2002 06:41 AM 130,048 fxsclnt(2).exe
>> 08/04/2004 03:56 AM 143,360 fxsclnt.exe
>>
>> Here's the pop-up error window:
>>
>> http://www.post-in-toronto.on.ca/chuck.kahn/hello/246/9...
>>
>> How do I launch it successfully?
>>
Anonymous
February 15, 2005 11:25:02 AM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

I figured out a month ago that the Windows XP installation files are on a
seperate D: partition on my hard drive. The only file I see mentioned in the
fax install log is fxsmon.dll. When it is called there is a failure to add a
Printer Monitor and failure to create a printer monitor. Both of these are
fatal errors and shutdown the install. The fxsmon.dll is in my i386
directory, but in a compressed form. I also have noted that there are two
other errors at the beginning of the log, dealing with failure to create
short-cuts.

Gateway has been of no help at all in the matter. They want me to do a
restore back to day one or recovery, and wipe out a month of work on my part.
No deal since I know that will not work. I tried to install Fax the second
day I had the computer and it didn't work. I certainly don't need Fax that
bad anyway.

I guess I have learned my lesson this time. Don't buy any computer that has
anything but the operating system installed and the original CD or DVD to go
with it.

Thanks,
Mike


"Russ Valentine [MVP-Outlook]" wrote:

> Did Gateway at least tell you (or have you been able to figure out on your
> own) where the Windows XP installation files are for your system?
> When the installation routine is unable to find the necessary installation
> files (even when directed to the appropriate i386 Folder) it usually means
> that the installation files are compressed or in another location. This is
> often the case when the files are pre-copied by a manufacturer on the hard
> drive. I suspect this will be an issue Gateway must solve.
> --
> Russ Valentine
> [MVP-Outlook]
> "MichaelM" <MichaelM@discussions.microsoft.com> wrote in message
> news:47898505-A6B1-4DF7-A57F-C497F0468501@microsoft.com...
> > Got the same problem here with a brand new Gateway with SP2 preinstalled.
> > When I try to install Fax Component get error message 0x8 unable to find
> > some
> > files and the Fax component install fails. Contacted Gateway. They have
> > nothing to say on the matter. I guess this one will be on the docket for a
> > fix at Microsoft on SP 33.
> >
> > Mike
> >
> >
> > "Chuck Kahn" wrote:
> >
> >> Microsoft Fax Console crashes when I launch it.
> >>
> >> Removing it and adding it as a windows component didn't fix anything.
> >>
> >> I see there are two versions of it under \WINDOWS\system32
> >>
> >> 08/29/2002 06:41 AM 130,048 fxsclnt(2).exe
> >> 08/04/2004 03:56 AM 143,360 fxsclnt.exe
> >>
> >> Here's the pop-up error window:
> >>
> >> http://www.post-in-toronto.on.ca/chuck.kahn/hello/246/9...
> >>
> >> How do I launch it successfully?
> >>
>
>
>
Anonymous
February 15, 2005 5:23:03 PM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

This is often the case when the files are pre-copied by a manufacturer on
the hard drive. If you do a search for the files that the installation
routine claims are missing (fxsapi.dll and fxcfgwz.dll) you won't find them,
but you will find fxsapi.dl_ and fxcfgwz.dl_. These are compressed DLL files
and will need to be decompressed. Double click on them and you will get a
prompt for the file to use to open them. Click on BROWSE. and select Win32
Cabinet Self-Extractor, which is in the system folder. With any luck it will
uncompress them all and make them visible as DLL files. The install routine
still may not find these files. If so, then you must manually direct the
installation routine to the i386 folder that contains these extracted files.
--
Russ Valentine
[MVP-Outlook]
"MichaelM" <MichaelM@discussions.microsoft.com> wrote in message
news:8C23777B-4AB8-4468-BAA2-383A688019D4@microsoft.com...
>I figured out a month ago that the Windows XP installation files are on a
> seperate D: partition on my hard drive. The only file I see mentioned in
> the
> fax install log is fxsmon.dll. When it is called there is a failure to add
> a
> Printer Monitor and failure to create a printer monitor. Both of these are
> fatal errors and shutdown the install. The fxsmon.dll is in my i386
> directory, but in a compressed form. I also have noted that there are two
> other errors at the beginning of the log, dealing with failure to create
> short-cuts.
>
> Gateway has been of no help at all in the matter. They want me to do a
> restore back to day one or recovery, and wipe out a month of work on my
> part.
> No deal since I know that will not work. I tried to install Fax the second
> day I had the computer and it didn't work. I certainly don't need Fax that
> bad anyway.
>
> I guess I have learned my lesson this time. Don't buy any computer that
> has
> anything but the operating system installed and the original CD or DVD to
> go
> with it.
>
> Thanks,
> Mike
>
>
> "Russ Valentine [MVP-Outlook]" wrote:
>
>> Did Gateway at least tell you (or have you been able to figure out on
>> your
>> own) where the Windows XP installation files are for your system?
>> When the installation routine is unable to find the necessary
>> installation
>> files (even when directed to the appropriate i386 Folder) it usually
>> means
>> that the installation files are compressed or in another location. This
>> is
>> often the case when the files are pre-copied by a manufacturer on the
>> hard
>> drive. I suspect this will be an issue Gateway must solve.
>> --
>> Russ Valentine
>> [MVP-Outlook]
>> "MichaelM" <MichaelM@discussions.microsoft.com> wrote in message
>> news:47898505-A6B1-4DF7-A57F-C497F0468501@microsoft.com...
>> > Got the same problem here with a brand new Gateway with SP2
>> > preinstalled.
>> > When I try to install Fax Component get error message 0x8 unable to
>> > find
>> > some
>> > files and the Fax component install fails. Contacted Gateway. They have
>> > nothing to say on the matter. I guess this one will be on the docket
>> > for a
>> > fix at Microsoft on SP 33.
>> >
>> > Mike
>> >
>> >
>> > "Chuck Kahn" wrote:
>> >
>> >> Microsoft Fax Console crashes when I launch it.
>> >>
>> >> Removing it and adding it as a windows component didn't fix anything.
>> >>
>> >> I see there are two versions of it under \WINDOWS\system32
>> >>
>> >> 08/29/2002 06:41 AM 130,048 fxsclnt(2).exe
>> >> 08/04/2004 03:56 AM 143,360 fxsclnt.exe
>> >>
>> >> Here's the pop-up error window:
>> >>
>> >> http://www.post-in-toronto.on.ca/chuck.kahn/hello/246/9...
>> >>
>> >> How do I launch it successfully?
>> >>
>>
>>
>>
Anonymous
February 16, 2005 7:37:04 AM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

Russ, I don't find "Win32 cabinet self-extractor" on my computer anywhere. I
don't understand what the problem with the files being compressed is for the
installation. I have always compressed dlls and exes for distribution and
part of the setup is to decompress the files to the locations they need to
be. Surely the installer for Fax is smart enough to do this.

"Russ Valentine [MVP-Outlook]" wrote:

> This is often the case when the files are pre-copied by a manufacturer on
> the hard drive. If you do a search for the files that the installation
> routine claims are missing (fxsapi.dll and fxcfgwz.dll) you won't find them,
> but you will find fxsapi.dl_ and fxcfgwz.dl_. These are compressed DLL files
> and will need to be decompressed. Double click on them and you will get a
> prompt for the file to use to open them. Click on BROWSE. and select Win32
> Cabinet Self-Extractor, which is in the system folder. With any luck it will
> uncompress them all and make them visible as DLL files. The install routine
> still may not find these files. If so, then you must manually direct the
> installation routine to the i386 folder that contains these extracted files.
> --
> Russ Valentine
> [MVP-Outlook]
> "MichaelM" <MichaelM@discussions.microsoft.com> wrote in message
> news:8C23777B-4AB8-4468-BAA2-383A688019D4@microsoft.com...
> >I figured out a month ago that the Windows XP installation files are on a
> > seperate D: partition on my hard drive. The only file I see mentioned in
> > the
> > fax install log is fxsmon.dll. When it is called there is a failure to add
> > a
> > Printer Monitor and failure to create a printer monitor. Both of these are
> > fatal errors and shutdown the install. The fxsmon.dll is in my i386
> > directory, but in a compressed form. I also have noted that there are two
> > other errors at the beginning of the log, dealing with failure to create
> > short-cuts.
> >
> > Gateway has been of no help at all in the matter. They want me to do a
> > restore back to day one or recovery, and wipe out a month of work on my
> > part.
> > No deal since I know that will not work. I tried to install Fax the second
> > day I had the computer and it didn't work. I certainly don't need Fax that
> > bad anyway.
> >
> > I guess I have learned my lesson this time. Don't buy any computer that
> > has
> > anything but the operating system installed and the original CD or DVD to
> > go
> > with it.
> >
> > Thanks,
> > Mike
> >
> >
> > "Russ Valentine [MVP-Outlook]" wrote:
> >
> >> Did Gateway at least tell you (or have you been able to figure out on
> >> your
> >> own) where the Windows XP installation files are for your system?
> >> When the installation routine is unable to find the necessary
> >> installation
> >> files (even when directed to the appropriate i386 Folder) it usually
> >> means
> >> that the installation files are compressed or in another location. This
> >> is
> >> often the case when the files are pre-copied by a manufacturer on the
> >> hard
> >> drive. I suspect this will be an issue Gateway must solve.
> >> --
> >> Russ Valentine
> >> [MVP-Outlook]
> >> "MichaelM" <MichaelM@discussions.microsoft.com> wrote in message
> >> news:47898505-A6B1-4DF7-A57F-C497F0468501@microsoft.com...
> >> > Got the same problem here with a brand new Gateway with SP2
> >> > preinstalled.
> >> > When I try to install Fax Component get error message 0x8 unable to
> >> > find
> >> > some
> >> > files and the Fax component install fails. Contacted Gateway. They have
> >> > nothing to say on the matter. I guess this one will be on the docket
> >> > for a
> >> > fix at Microsoft on SP 33.
> >> >
> >> > Mike
> >> >
> >> >
> >> > "Chuck Kahn" wrote:
> >> >
> >> >> Microsoft Fax Console crashes when I launch it.
> >> >>
> >> >> Removing it and adding it as a windows component didn't fix anything.
> >> >>
> >> >> I see there are two versions of it under \WINDOWS\system32
> >> >>
> >> >> 08/29/2002 06:41 AM 130,048 fxsclnt(2).exe
> >> >> 08/04/2004 03:56 AM 143,360 fxsclnt.exe
> >> >>
> >> >> Here's the pop-up error window:
> >> >>
> >> >> http://www.post-in-toronto.on.ca/chuck.kahn/hello/246/9...
> >> >>
> >> >> How do I launch it successfully?
> >> >>
> >>
> >>
> >>
>
>
>
Anonymous
February 16, 2005 9:09:36 PM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

Sadly, it is not and many users have had to resort to this method. If your
version of Windows XP no longer has the self extractor, you'll have to
resort to the manual method:
https://mvp.support.microsoft.com/default.aspx?scid=kb;en-us;310435
--
Russ Valentine
[MVP-Outlook]
"MichaelM" <MichaelM@discussions.microsoft.com> wrote in message
news:B4420CE2-FEF2-4FE6-B44E-F8B5F46DD65F@microsoft.com...
> Russ, I don't find "Win32 cabinet self-extractor" on my computer anywhere.
> I
> don't understand what the problem with the files being compressed is for
> the
> installation. I have always compressed dlls and exes for distribution and
> part of the setup is to decompress the files to the locations they need to
> be. Surely the installer for Fax is smart enough to do this.
>
> "Russ Valentine [MVP-Outlook]" wrote:
>
>> This is often the case when the files are pre-copied by a manufacturer on
>> the hard drive. If you do a search for the files that the installation
>> routine claims are missing (fxsapi.dll and fxcfgwz.dll) you won't find
>> them,
>> but you will find fxsapi.dl_ and fxcfgwz.dl_. These are compressed DLL
>> files
>> and will need to be decompressed. Double click on them and you will get a
>> prompt for the file to use to open them. Click on BROWSE. and select
>> Win32
>> Cabinet Self-Extractor, which is in the system folder. With any luck it
>> will
>> uncompress them all and make them visible as DLL files. The install
>> routine
>> still may not find these files. If so, then you must manually direct the
>> installation routine to the i386 folder that contains these extracted
>> files.
>> --
>> Russ Valentine
>> [MVP-Outlook]
>> "MichaelM" <MichaelM@discussions.microsoft.com> wrote in message
>> news:8C23777B-4AB8-4468-BAA2-383A688019D4@microsoft.com...
>> >I figured out a month ago that the Windows XP installation files are on
>> >a
>> > seperate D: partition on my hard drive. The only file I see mentioned
>> > in
>> > the
>> > fax install log is fxsmon.dll. When it is called there is a failure to
>> > add
>> > a
>> > Printer Monitor and failure to create a printer monitor. Both of these
>> > are
>> > fatal errors and shutdown the install. The fxsmon.dll is in my i386
>> > directory, but in a compressed form. I also have noted that there are
>> > two
>> > other errors at the beginning of the log, dealing with failure to
>> > create
>> > short-cuts.
>> >
>> > Gateway has been of no help at all in the matter. They want me to do a
>> > restore back to day one or recovery, and wipe out a month of work on my
>> > part.
>> > No deal since I know that will not work. I tried to install Fax the
>> > second
>> > day I had the computer and it didn't work. I certainly don't need Fax
>> > that
>> > bad anyway.
>> >
>> > I guess I have learned my lesson this time. Don't buy any computer that
>> > has
>> > anything but the operating system installed and the original CD or DVD
>> > to
>> > go
>> > with it.
>> >
>> > Thanks,
>> > Mike
>> >
>> >
>> > "Russ Valentine [MVP-Outlook]" wrote:
>> >
>> >> Did Gateway at least tell you (or have you been able to figure out on
>> >> your
>> >> own) where the Windows XP installation files are for your system?
>> >> When the installation routine is unable to find the necessary
>> >> installation
>> >> files (even when directed to the appropriate i386 Folder) it usually
>> >> means
>> >> that the installation files are compressed or in another location.
>> >> This
>> >> is
>> >> often the case when the files are pre-copied by a manufacturer on the
>> >> hard
>> >> drive. I suspect this will be an issue Gateway must solve.
>> >> --
>> >> Russ Valentine
>> >> [MVP-Outlook]
>> >> "MichaelM" <MichaelM@discussions.microsoft.com> wrote in message
>> >> news:47898505-A6B1-4DF7-A57F-C497F0468501@microsoft.com...
>> >> > Got the same problem here with a brand new Gateway with SP2
>> >> > preinstalled.
>> >> > When I try to install Fax Component get error message 0x8 unable to
>> >> > find
>> >> > some
>> >> > files and the Fax component install fails. Contacted Gateway. They
>> >> > have
>> >> > nothing to say on the matter. I guess this one will be on the docket
>> >> > for a
>> >> > fix at Microsoft on SP 33.
>> >> >
>> >> > Mike
>> >> >
>> >> >
>> >> > "Chuck Kahn" wrote:
>> >> >
>> >> >> Microsoft Fax Console crashes when I launch it.
>> >> >>
>> >> >> Removing it and adding it as a windows component didn't fix
>> >> >> anything.
>> >> >>
>> >> >> I see there are two versions of it under \WINDOWS\system32
>> >> >>
>> >> >> 08/29/2002 06:41 AM 130,048 fxsclnt(2).exe
>> >> >> 08/04/2004 03:56 AM 143,360 fxsclnt.exe
>> >> >>
>> >> >> Here's the pop-up error window:
>> >> >>
>> >> >> http://www.post-in-toronto.on.ca/chuck.kahn/hello/246/9...
>> >> >>
>> >> >> How do I launch it successfully?
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>
Anonymous
February 17, 2005 12:17:25 AM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

He probably won't be able to access the KB article from the MVP site, this
URL should work better:

http://support.microsoft.com/kb/310435
Description and Explanation of a Cabinet File

Hal
--
Hal Hostetler, CPBE -- hhh@kvoa.com
Senior Engineer/MIS -- MS MVP-S/U -- WA7BGX
http://www.kvoa.com -- "When News breaks, we fix it!"
KVOA Television, Tucson, AZ. NBC Channel 4
Still Cadillacin' - www.badnewsbluesband.com

"Russ Valentine [MVP-Outlook]" <russval@mvps.org> wrote in message
news:ugZ%23WyHFFHA.464@TK2MSFTNGP09.phx.gbl...
> Sadly, it is not and many users have had to resort to this method. If your
> version of Windows XP no longer has the self extractor, you'll have to
> resort to the manual method:
> https://mvp.support.microsoft.com/default.aspx?scid=kb;en-us;310435
> --
> Russ Valentine
> [MVP-Outlook]
> "MichaelM" <MichaelM@discussions.microsoft.com> wrote in message
> news:B4420CE2-FEF2-4FE6-B44E-F8B5F46DD65F@microsoft.com...
> > Russ, I don't find "Win32 cabinet self-extractor" on my computer
anywhere.
> > I
> > don't understand what the problem with the files being compressed is for
> > the
> > installation. I have always compressed dlls and exes for distribution
and
> > part of the setup is to decompress the files to the locations they need
to
> > be. Surely the installer for Fax is smart enough to do this.
> >
> > "Russ Valentine [MVP-Outlook]" wrote:
> >
> >> This is often the case when the files are pre-copied by a manufacturer
on
> >> the hard drive. If you do a search for the files that the installation
> >> routine claims are missing (fxsapi.dll and fxcfgwz.dll) you won't find
> >> them,
> >> but you will find fxsapi.dl_ and fxcfgwz.dl_. These are compressed DLL
> >> files
> >> and will need to be decompressed. Double click on them and you will get
a
> >> prompt for the file to use to open them. Click on BROWSE. and select
> >> Win32
> >> Cabinet Self-Extractor, which is in the system folder. With any luck it
> >> will
> >> uncompress them all and make them visible as DLL files. The install
> >> routine
> >> still may not find these files. If so, then you must manually direct
the
> >> installation routine to the i386 folder that contains these extracted
> >> files.
> >> --
> >> Russ Valentine
> >> [MVP-Outlook]
> >> "MichaelM" <MichaelM@discussions.microsoft.com> wrote in message
> >> news:8C23777B-4AB8-4468-BAA2-383A688019D4@microsoft.com...
> >> >I figured out a month ago that the Windows XP installation files are
on
> >> >a
> >> > seperate D: partition on my hard drive. The only file I see mentioned
> >> > in
> >> > the
> >> > fax install log is fxsmon.dll. When it is called there is a failure
to
> >> > add
> >> > a
> >> > Printer Monitor and failure to create a printer monitor. Both of
these
> >> > are
> >> > fatal errors and shutdown the install. The fxsmon.dll is in my i386
> >> > directory, but in a compressed form. I also have noted that there are
> >> > two
> >> > other errors at the beginning of the log, dealing with failure to
> >> > create
> >> > short-cuts.
> >> >
> >> > Gateway has been of no help at all in the matter. They want me to do
a
> >> > restore back to day one or recovery, and wipe out a month of work on
my
> >> > part.
> >> > No deal since I know that will not work. I tried to install Fax the
> >> > second
> >> > day I had the computer and it didn't work. I certainly don't need Fax
> >> > that
> >> > bad anyway.
> >> >
> >> > I guess I have learned my lesson this time. Don't buy any computer
that
> >> > has
> >> > anything but the operating system installed and the original CD or
DVD
> >> > to
> >> > go
> >> > with it.
> >> >
> >> > Thanks,
> >> > Mike
> >> >
> >> >
> >> > "Russ Valentine [MVP-Outlook]" wrote:
> >> >
> >> >> Did Gateway at least tell you (or have you been able to figure out
on
> >> >> your
> >> >> own) where the Windows XP installation files are for your system?
> >> >> When the installation routine is unable to find the necessary
> >> >> installation
> >> >> files (even when directed to the appropriate i386 Folder) it usually
> >> >> means
> >> >> that the installation files are compressed or in another location.
> >> >> This
> >> >> is
> >> >> often the case when the files are pre-copied by a manufacturer on
the
> >> >> hard
> >> >> drive. I suspect this will be an issue Gateway must solve.
> >> >> --
> >> >> Russ Valentine
> >> >> [MVP-Outlook]
> >> >> "MichaelM" <MichaelM@discussions.microsoft.com> wrote in message
> >> >> news:47898505-A6B1-4DF7-A57F-C497F0468501@microsoft.com...
> >> >> > Got the same problem here with a brand new Gateway with SP2
> >> >> > preinstalled.
> >> >> > When I try to install Fax Component get error message 0x8 unable
to
> >> >> > find
> >> >> > some
> >> >> > files and the Fax component install fails. Contacted Gateway. They
> >> >> > have
> >> >> > nothing to say on the matter. I guess this one will be on the
docket
> >> >> > for a
> >> >> > fix at Microsoft on SP 33.
> >> >> >
> >> >> > Mike
> >> >> >
> >> >> >
> >> >> > "Chuck Kahn" wrote:
> >> >> >
> >> >> >> Microsoft Fax Console crashes when I launch it.
> >> >> >>
> >> >> >> Removing it and adding it as a windows component didn't fix
> >> >> >> anything.
> >> >> >>
> >> >> >> I see there are two versions of it under \WINDOWS\system32
> >> >> >>
> >> >> >> 08/29/2002 06:41 AM 130,048 fxsclnt(2).exe
> >> >> >> 08/04/2004 03:56 AM 143,360 fxsclnt.exe
> >> >> >>
> >> >> >> Here's the pop-up error window:
> >> >> >>
> >> >> >>
http://www.post-in-toronto.on.ca/chuck.kahn/hello/246/9...
> >> >> >>
> >> >> >> How do I launch it successfully?
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
Anonymous
February 17, 2005 7:43:03 AM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

Right. Thanks.
--
Russ Valentine
[MVP-Outlook]
"Hal Hostetler [MVP S/U]" <hhh@kvoa.com> wrote in message
news:%23MIUXeKFFHA.1408@TK2MSFTNGP10.phx.gbl...
> He probably won't be able to access the KB article from the MVP site, this
> URL should work better:
>
> http://support.microsoft.com/kb/310435
> Description and Explanation of a Cabinet File
>
> Hal
> --
> Hal Hostetler, CPBE -- hhh@kvoa.com
> Senior Engineer/MIS -- MS MVP-S/U -- WA7BGX
> http://www.kvoa.com -- "When News breaks, we fix it!"
> KVOA Television, Tucson, AZ. NBC Channel 4
> Still Cadillacin' - www.badnewsbluesband.com
>
> "Russ Valentine [MVP-Outlook]" <russval@mvps.org> wrote in message
> news:ugZ%23WyHFFHA.464@TK2MSFTNGP09.phx.gbl...
>> Sadly, it is not and many users have had to resort to this method. If
>> your
>> version of Windows XP no longer has the self extractor, you'll have to
>> resort to the manual method:
>> https://mvp.support.microsoft.com/default.aspx?scid=kb;en-us;310435
>> --
>> Russ Valentine
>> [MVP-Outlook]
>> "MichaelM" <MichaelM@discussions.microsoft.com> wrote in message
>> news:B4420CE2-FEF2-4FE6-B44E-F8B5F46DD65F@microsoft.com...
>> > Russ, I don't find "Win32 cabinet self-extractor" on my computer
> anywhere.
>> > I
>> > don't understand what the problem with the files being compressed is
>> > for
>> > the
>> > installation. I have always compressed dlls and exes for distribution
> and
>> > part of the setup is to decompress the files to the locations they need
> to
>> > be. Surely the installer for Fax is smart enough to do this.
>> >
>> > "Russ Valentine [MVP-Outlook]" wrote:
>> >
>> >> This is often the case when the files are pre-copied by a manufacturer
> on
>> >> the hard drive. If you do a search for the files that the installation
>> >> routine claims are missing (fxsapi.dll and fxcfgwz.dll) you won't find
>> >> them,
>> >> but you will find fxsapi.dl_ and fxcfgwz.dl_. These are compressed DLL
>> >> files
>> >> and will need to be decompressed. Double click on them and you will
>> >> get
> a
>> >> prompt for the file to use to open them. Click on BROWSE. and select
>> >> Win32
>> >> Cabinet Self-Extractor, which is in the system folder. With any luck
>> >> it
>> >> will
>> >> uncompress them all and make them visible as DLL files. The install
>> >> routine
>> >> still may not find these files. If so, then you must manually direct
> the
>> >> installation routine to the i386 folder that contains these extracted
>> >> files.
>> >> --
>> >> Russ Valentine
>> >> [MVP-Outlook]
>> >> "MichaelM" <MichaelM@discussions.microsoft.com> wrote in message
>> >> news:8C23777B-4AB8-4468-BAA2-383A688019D4@microsoft.com...
>> >> >I figured out a month ago that the Windows XP installation files are
> on
>> >> >a
>> >> > seperate D: partition on my hard drive. The only file I see
>> >> > mentioned
>> >> > in
>> >> > the
>> >> > fax install log is fxsmon.dll. When it is called there is a failure
> to
>> >> > add
>> >> > a
>> >> > Printer Monitor and failure to create a printer monitor. Both of
> these
>> >> > are
>> >> > fatal errors and shutdown the install. The fxsmon.dll is in my i386
>> >> > directory, but in a compressed form. I also have noted that there
>> >> > are
>> >> > two
>> >> > other errors at the beginning of the log, dealing with failure to
>> >> > create
>> >> > short-cuts.
>> >> >
>> >> > Gateway has been of no help at all in the matter. They want me to do
> a
>> >> > restore back to day one or recovery, and wipe out a month of work on
> my
>> >> > part.
>> >> > No deal since I know that will not work. I tried to install Fax the
>> >> > second
>> >> > day I had the computer and it didn't work. I certainly don't need
>> >> > Fax
>> >> > that
>> >> > bad anyway.
>> >> >
>> >> > I guess I have learned my lesson this time. Don't buy any computer
> that
>> >> > has
>> >> > anything but the operating system installed and the original CD or
> DVD
>> >> > to
>> >> > go
>> >> > with it.
>> >> >
>> >> > Thanks,
>> >> > Mike
>> >> >
>> >> >
>> >> > "Russ Valentine [MVP-Outlook]" wrote:
>> >> >
>> >> >> Did Gateway at least tell you (or have you been able to figure out
> on
>> >> >> your
>> >> >> own) where the Windows XP installation files are for your system?
>> >> >> When the installation routine is unable to find the necessary
>> >> >> installation
>> >> >> files (even when directed to the appropriate i386 Folder) it
>> >> >> usually
>> >> >> means
>> >> >> that the installation files are compressed or in another location.
>> >> >> This
>> >> >> is
>> >> >> often the case when the files are pre-copied by a manufacturer on
> the
>> >> >> hard
>> >> >> drive. I suspect this will be an issue Gateway must solve.
>> >> >> --
>> >> >> Russ Valentine
>> >> >> [MVP-Outlook]
>> >> >> "MichaelM" <MichaelM@discussions.microsoft.com> wrote in message
>> >> >> news:47898505-A6B1-4DF7-A57F-C497F0468501@microsoft.com...
>> >> >> > Got the same problem here with a brand new Gateway with SP2
>> >> >> > preinstalled.
>> >> >> > When I try to install Fax Component get error message 0x8 unable
> to
>> >> >> > find
>> >> >> > some
>> >> >> > files and the Fax component install fails. Contacted Gateway.
>> >> >> > They
>> >> >> > have
>> >> >> > nothing to say on the matter. I guess this one will be on the
> docket
>> >> >> > for a
>> >> >> > fix at Microsoft on SP 33.
>> >> >> >
>> >> >> > Mike
>> >> >> >
>> >> >> >
>> >> >> > "Chuck Kahn" wrote:
>> >> >> >
>> >> >> >> Microsoft Fax Console crashes when I launch it.
>> >> >> >>
>> >> >> >> Removing it and adding it as a windows component didn't fix
>> >> >> >> anything.
>> >> >> >>
>> >> >> >> I see there are two versions of it under \WINDOWS\system32
>> >> >> >>
>> >> >> >> 08/29/2002 06:41 AM 130,048 fxsclnt(2).exe
>> >> >> >> 08/04/2004 03:56 AM 143,360 fxsclnt.exe
>> >> >> >>
>> >> >> >> Here's the pop-up error window:
>> >> >> >>
>> >> >> >>
> http://www.post-in-toronto.on.ca/chuck.kahn/hello/246/9...
>> >> >> >>
>> >> >> >> How do I launch it successfully?
>> >> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>
>
!