XP's Fax Conxole remains open...

[Guest]

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

...after faxing a document, so it attempts to answer the phone each time
it rings, which is not what I want.

I notice that the program <fxssvc.exe> remains an active process running
in the background and I find no way to delete it unless going through
the Task Mgr and manually doing so. Is there a way to even prevent the
auto-answer from remaining active? I have it set to "manual."

I use DSL for my internet and only use the modem for faxes, so the only
time it is called up is by XP's fax console as I attempt to fax a
document. I also have my modem's current and latest version so
upgrading doesn't seem to be a possible solution. The only question
remaining is if this could be due to a firewall issue. I use ZoneLabs'
Zone Alarm Pro and wouldn't even begin to know what to look for that
would keep the app in memory...

Any suggestions?
--
Paul R
-------------------------------
For email reply, please remove 195

 

[Guest]

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

Why not just disable autoreception? The Help files will tell you how.
--
Russ Valentine
[MVP-Outlook]
"Paul R" <195prosete@195earthlink.com> wrote in message
news:gA16d.4569$Ki1.2405@newsread2.news.atl.earthlink.net...
> ..after faxing a document, so it attempts to answer the phone each time it
> rings, which is not what I want.
>
> I notice that the program <fxssvc.exe> remains an active process running
> in the background and I find no way to delete it unless going through the
> Task Mgr and manually doing so. Is there a way to even prevent the
> auto-answer from remaining active? I have it set to "manual."
>
> I use DSL for my internet and only use the modem for faxes, so the only
> time it is called up is by XP's fax console as I attempt to fax a
> document. I also have my modem's current and latest version so upgrading
> doesn't seem to be a possible solution. The only question remaining is if
> this could be due to a firewall issue. I use ZoneLabs' Zone Alarm Pro and
> wouldn't even begin to know what to look for that would keep the app in
> memory...
>
> Any suggestions?
> --
> Paul R
> -------------------------------
> For email reply, please remove 195

 

[Guest]

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

Russ Valentine [MVP-Outlook] wrote:
> Why not just disable autoreception? The Help files will tell you how.


Simple and intuitive, isn't it? But actually, the reason I don't simply
disable it is because doing so prevents the entire fax progam from
functioning when I call it to fax a document. The initial fax wizard
screen just freezes and stops responding when I call it on if I have it
disabled. There doesn't seem to be a middle ground here, aparently,
like any 3rd party software might offer.

--
Paul R
-------------------------------
For email reply, please remove 195

 

[Guest]

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

Well that's certainly not by design. Something is wrong with your
installation. I can easily disable receptions and still send faxes.
Any error messages that would permit troubleshooting? Is your modem on the
Windows XP HCL list?

--
Russ Valentine
[MVP-Outlook]
"Paul R" <195prosete@195earthlink.com> wrote in message
news:1mR6d.7886$Ki1.5875@newsread2.news.atl.earthlink.net...
> Russ Valentine [MVP-Outlook] wrote:
>> Why not just disable autoreception? The Help files will tell you how.
>
>
> Simple and intuitive, isn't it? But actually, the reason I don't simply
> disable it is because doing so prevents the entire fax progam from
> functioning when I call it to fax a document. The initial fax wizard
> screen just freezes and stops responding when I call it on if I have it
> disabled. There doesn't seem to be a middle ground here, aparently, like
> any 3rd party software might offer.
>
> --
> Paul R
> -------------------------------
> For email reply, please remove 195

 

[Guest]

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

Russ Valentine [MVP-Outlook] wrote:
> Well that's certainly not by design. Something is wrong with your
> installation. I can easily disable receptions and still send faxes.

Well, my installation was one of those out-of-the-box HP systems that
came with Win XP Home Edition. The Fax Console is the one that comes
with XP and accessed thru Programs/Accessories/Communication/Fax. All I
did was run the Fax Wizard that sets up the console and subsequent
faxes. So, I guess I'm not sure which part of the installation might
have gone wrong, as per your thinking...

> Any error messages that would permit troubleshooting? Is your modem on the
> Windows XP HCL list?

No error messages, it just freezes up when the "Send" wizard comes up
(if I have auto-reception "disabled"). My Agere 56K PCI Soft Modem is on
the Win 2000 HCL.

Paul R.
----------------------------
For email reply, please remove 195

 

[Guest]

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

The Win 2000 HCL list would not be in play here.
Unfortunately, Windows XP Fax has proven to be incompatible with many common
modems and drivers, particularly older ones, even if the manufacturers claim
they are "compatible" with Windows XP. Modem incompatibility is not apparent
during installation or the initial setup. It only becomes apparent when you
first try to send or receive a fax. The Fax Service will dial or will answer
an incoming fax but then fail with any of a number of unhelpful error
messages such as "Line is busy," "There is no answer," or "Reception error."
There will be nothing in Event Viewer to give a clue as to where the problem
might lie.

These errors have been nearly impossible to track down. To do so requires
enabling both PSS and debug logging of fax transmissions, both of which
require fairly extensive registry changes. For the time being, the best
advice is to attempt to use XP Fax only if you have a modem that is listed
on the Windows XP Hardware Compatibility List and using the latest drivers.

--
Russ Valentine
[MVP-Outlook]
"Paul R" <195prosete@195earthlink.com> wrote in message
news:chg8d.3136$Vm1.2096@newsread3.news.atl.earthlink.net...
> Russ Valentine [MVP-Outlook] wrote:
>> Well that's certainly not by design. Something is wrong with your
>> installation. I can easily disable receptions and still send faxes.
>
> Well, my installation was one of those out-of-the-box HP systems that came
> with Win XP Home Edition. The Fax Console is the one that comes with XP
> and accessed thru Programs/Accessories/Communication/Fax. All I did was
> run the Fax Wizard that sets up the console and subsequent faxes. So, I
> guess I'm not sure which part of the installation might have gone wrong,
> as per your thinking...
>
>> Any error messages that would permit troubleshooting? Is your modem on
>> the Windows XP HCL list?
>
> No error messages, it just freezes up when the "Send" wizard comes up (if
> I have auto-reception "disabled"). My Agere 56K PCI Soft Modem is on the
> Win 2000 HCL.
>
> Paul R.
> ----------------------------
> For email reply, please remove 195

 

[Guest]

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

Russ Valentine [MVP-Outlook] wrote:
> The Win 2000 HCL list would not be in play here.

Actually, I erred and looked it up incorrectly, ending only with the
2000 HCL. Further checking led to the XP HCL which lists my modem
version as one "designed for XP." Whatever that means...I also checked
and found I have the most current driver.

> Unfortunately, Windows XP Fax has proven to be incompatible with many common
> modems and drivers, particularly older ones, even if the manufacturers claim
> they are "compatible" with Windows XP. Modem incompatibility is not apparent
> during installation or the initial setup. It only becomes apparent when you
> first try to send or receive a fax. The Fax Service will dial or will answer
> an incoming fax but then fail with any of a number of unhelpful error
> messages such as "Line is busy," "There is no answer," or "Reception error."
> There will be nothing in Event Viewer to give a clue as to where the problem
> might lie.
>
> These errors have been nearly impossible to track down. To do so requires
> enabling both PSS and debug logging of fax transmissions, both of which
> require fairly extensive registry changes. For the time being, the best
> advice is to attempt to use XP Fax only if you have a modem that is listed
> on the Windows XP Hardware Compatibility List and using the latest drivers.
>


--
Paul R
-------------------------------
For email reply, please remove 195

 

[Guest]

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

Russ has and can send you the Registry change information required to enable
PSS and Debug logging if you feel like experimenting.

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

"Paul R" <195prosete@195earthlink.com> wrote in message
news:Nzn8d.3838$gs1.2179@newsread2.news.atl.earthlink.net...
> Russ Valentine [MVP-Outlook] wrote:
> > The Win 2000 HCL list would not be in play here.
>
> Actually, I erred and looked it up incorrectly, ending only with the
> 2000 HCL. Further checking led to the XP HCL which lists my modem
> version as one "designed for XP." Whatever that means...I also checked
> and found I have the most current driver.
>
> > Unfortunately, Windows XP Fax has proven to be incompatible with many
common
> > modems and drivers, particularly older ones, even if the manufacturers
claim
> > they are "compatible" with Windows XP. Modem incompatibility is not
apparent
> > during installation or the initial setup. It only becomes apparent when
you
> > first try to send or receive a fax. The Fax Service will dial or will
answer
> > an incoming fax but then fail with any of a number of unhelpful error
> > messages such as "Line is busy," "There is no answer," or "Reception
error."
> > There will be nothing in Event Viewer to give a clue as to where the
problem
> > might lie.
> >
> > These errors have been nearly impossible to track down. To do so
requires
> > enabling both PSS and debug logging of fax transmissions, both of which
> > require fairly extensive registry changes. For the time being, the best
> > advice is to attempt to use XP Fax only if you have a modem that is
listed
> > on the Windows XP Hardware Compatibility List and using the latest
drivers.
> >
>
>
> --
> Paul R
> -------------------------------
> For email reply, please remove 195