I have a Rockwell RC56D2 Serial PnP, V.90 K56Flex, Voice Speakerphon
modem.
After a registry meltdown of my Windows XP Professional, I had t
reinstall windows
Everything is working fine, except sending faxes, using MSFAX.
experience this as pretty odd since it was working fine with m
former windows installation, using the same OS

The behaviour

After connecting to the other fax, the connection is dropped after 3
seconds, although I set the timer for making a connection to 18
seconds
After that, I got the message
"an error occurred sending the fax

This is what the modemlog says

01-24-2006 23:54:47.828 - File: C:\WINXP\system32\tapisrv.dll, Versio
5.1.2600
01-24-2006 23:54:47.828 - File: C:\WINXP\system32\unimdm.tsp, Versio
5.1.2600
01-24-2006 23:54:47.828 - File: C:\WINXP\system32\unimdmat.dll
Version 5.1.2600
01-24-2006 23:54:47.828 - File: C:\WINXP\system32\uniplat.dll, Versio
5.1.2600
01-24-2006 23:54:47.828 - File: C:\WINXP\system32\drivers\modem.sys
Version 5.1.2600
01-24-2006 23:54:47.828 - File: C:\WINXP\system32\modemui.dll, Versio
5.1.2600
01-24-2006 23:54:47.828 - File: C:\WINXP\system32\mdminst.dll, Versio
5.1.2600
01-24-2006 23:54:47.828 - Modem type: Rockwell RC56D2 Serial PnP
V.90,K56Flex,Voice,Speakerphon
01-24-2006 23:54:47.828 - Modem inf path: oem11.in
01-24-2006 23:54:47.828 - Modem inf section: MDMES2
01-24-2006 23:54:47.828 - Matching hardware ID: *rss029
01-24-2006 23:54:47.828 - Opening Mode
01-24-2006 23:54:47.828 - 115200,8,N,1, ctsfl=1, rtsctl=
01-24-2006 23:54:47.828 - Initializing modem
01-24-2006 23:54:47.828 - TSP(0000): Monitorin
01-24-2006 23:54:47.828 - TSP(0000): Monitorin
01-24-2006 23:54:47.828 - TSP(0000): Making Cal
01-24-2006 23:54:47.843 - Send: AT<cr
01-24-2006 23:54:47.843 - Recv
<cr><lf>OK<cr><lf
01-24-2006 23:54:47.843 - Interpreted response: O
01-24-2006 23:54:47.859 - Send
AT&FE0V1&C1&D2S95=45S0=0<cr
01-24-2006 23:54:47.859 - Recv
<cr><lf>OK<cr><lf
01-24-2006 23:54:47.859 - Interpreted response: O
01-24-2006 23:54:47.875 - Send
ATS7=180S30=0L1M1\N3%C3&K3BN1X4<cr
01-24-2006 23:54:47.875 - Recv
<cr><lf>OK<cr><lf
01-24-2006 23:54:47.875 - Interpreted response: O
01-24-2006 23:54:47.875 - Waiting for a call
01-24-2006 23:54:47.890 - Send: at#cid=1<cr
01-24-2006 23:54:47.890 - Recv
<cr><lf>OK<cr><lf
01-24-2006 23:54:47.890 - Interpreted response: O
01-24-2006 23:54:47.906 - Send: ATS0=0<cr
01-24-2006 23:54:47.906 - Recv
<cr><lf>OK<cr><lf
01-24-2006 23:54:47.906 - Interpreted response: O
01-24-2006 23:54:47.906 - Passthrough O
01-24-2006 23:54:47.906 - TSP Completing Async Operation(0x00010038
Status 0x0000000
01-24-2006 23:54:47.906 - TSP(0000): LINEEVENT
LINECALLSTATE_CONNECTE
01-24-2006 23:55:03.218 - TSP(0000): Dropping Cal
01-24-2006 23:55:03.218 - Passthrough Of
01-24-2006 23:55:03.218 - 115200,8,N,1, ctsfl=1, rtsctl=
01-24-2006 23:55:03.218 - Initializing modem
01-24-2006 23:55:03.234 - Send: AT<cr
01-24-2006 23:55:03.234 - Recv
<cr><lf>OK<cr><lf
01-24-2006 23:55:03.234 - Interpreted response: O
01-24-2006 23:55:03.250 - Send
AT&FE0V1&C1&D2S95=45S0=0<cr
01-24-2006 23:55:03.250 - Recv
<cr><lf>OK<cr><lf
01-24-2006 23:55:03.250 - Interpreted response: O
01-24-2006 23:55:03.265 - Send
ATS7=180S30=0L1M1\N3%C3&K3BN1X4<cr
01-24-2006 23:55:03.265 - Recv
<cr><lf>OK<cr><lf
01-24-2006 23:55:03.265 - Interpreted response: O
01-24-2006 23:55:03.265 - Waiting for a call
01-24-2006 23:55:03.281 - Send: at#cid=1<cr
01-24-2006 23:55:03.281 - Recv
<cr><lf>OK<cr><lf
01-24-2006 23:55:03.281 - Interpreted response: O
01-24-2006 23:55:03.296 - Send: ATS0=0<cr
01-24-2006 23:55:03.296 - Recv
<cr><lf>OK<cr><lf
01-24-2006 23:55:03.296 - Interpreted response: O
01-24-2006 23:55:03.296 - TSP(0000): LINEEVENT
LINECALLSTATE_DISCONNECTED(0x1
01-24-2006 23:55:03.296 - TSP(0000): LINEEVENT: LINECALLSTATE_IDL
01-24-2006 23:55:03.296 - TSP Completing Async Operation(0x000100e3
Status 0x0000000
01-24-2006 23:55:03.296 - TSP(0000): Closing Cal
01-24-2006 23:55:03.296 - Session Statistics
01-24-2006 23:55:03.296 - Reads : 30 byte
01-24-2006 23:55:03.296 - Writes: 76 bytes

A dialup connection is working fine, as well as my telebanking
program, using the same modem.

I already dig through google and the knowledge base of MS, but could
not find a helpful clue yet.

WinXp Prof, SP2, all updates
Office 2000, all updates

Any help will be apreciated,

Leon

"Leon" <no@spam.invalid> wrote in message
news:Z%SBf.213307$pW2.176235@fe04.news.easynews.co m...
Have you downloaded and correctly installed the latest inf file for your
modem and motherboard chipset? I see the system is using a supplied inf
(using OEM11.inf) but what exact brand and model is the modem? I have an
internal ISA modem with the same chipset and features from the look of
things but there are many manufacturers of modems using this chipset. The
biggies are/were Askey and GVC back then around 98 ~ 2000 ish.

Paul

The oem11 thing is the same I was wondering..
The funny part is, as I install the good driver (install driver
having disk and point to the folder where there is only one in
file)
it changes, I already had it to oem9.inf
oem19.in
oem20.in
oem11.in
and now it stated oem39.inf (after (again) installing the good .in
file)..
(see logfile

(i used right mouseclick on right .inf file, then pressed install, an
after that I pointed the 'update driver process' from the modem to th
right folder where the good .inf file is...

nevertheless still the same problem!

01-26-2006 21:57:17.578 - File: C:\WINXP\system32\tapisrv.dll, Versio
5.1.2600
01-26-2006 21:57:17.578 - File: C:\WINXP\system32\unimdm.tsp, Versio
5.1.2600
01-26-2006 21:57:17.578 - File: C:\WINXP\system32\unimdmat.dll
Version 5.1.2600
01-26-2006 21:57:17.578 - File: C:\WINXP\system32\uniplat.dll, Versio
5.1.2600
01-26-2006 21:57:17.593 - File: C:\WINXP\system32\drivers\modem.sys
Version 5.1.2600
01-26-2006 21:57:17.593 - File: C:\WINXP\system32\modemui.dll, Versio
5.1.2600
01-26-2006 21:57:17.593 - File: C:\WINXP\system32\mdminst.dll, Versio
5.1.2600
01-26-2006 21:57:17.593 - Modem type: Rockwell RC56D2 Serial PnP
V.90,K56Flex,Voice,Speakerphon
01-26-2006 21:57:17.593 - Modem inf path: oem39.in
01-26-2006 21:57:17.593 - Modem inf section: MDMES2
01-26-2006 21:57:17.593 - Matching hardware ID: *rss029
01-26-2006 21:57:17.593 - 115200,8,N,1, ctsfl=1, rtsctl=
01-26-2006 21:57:17.593 - Initializing modem
01-26-2006 21:57:17.609 - Send: AT<cr
01-26-2006 21:57:17.609 - Recv
<cr><lf>OK<cr><lf
01-26-2006 21:57:17.609 - Interpreted response: O
01-26-2006 21:57:17.609 - Send
AT&FE0V1&C1&D2S95=45S0=0<cr
01-26-2006 21:57:17.625 - Recv
<cr><lf>OK<cr><lf
01-26-2006 21:57:17.625 - Interpreted response: O
01-26-2006 21:57:17.640 - Send
ATS7=180S30=0L1M1\N3%C3&K3BN1X4<cr
01-26-2006 21:57:17.640 - Recv
<cr><lf>OK<cr><lf
01-26-2006 21:57:17.640 - Interpreted response: O
01-26-2006 21:57:17.640 - Waiting for a call
01-26-2006 21:57:17.656 - Send: at#cid=1<cr
01-26-2006 21:57:17.656 - Recv
<cr><lf>OK<cr><lf
01-26-2006 21:57:17.656 - Interpreted response: O
01-26-2006 21:57:17.671 - Send: ATS0=0<cr
01-26-2006 21:57:17.671 - Recv
<cr><lf>OK<cr><lf
01-26-2006 21:57:17.671 - Interpreted response: O
01-26-2006 21:57:17.671 - Passthrough O
01-26-2006 21:58:17.437 - Passthrough Of
01-26-2006 21:58:17.437 - 115200,8,N,1, ctsfl=1, rtsctl=
01-26-2006 21:58:17.437 - Initializing modem
01-26-2006 21:58:17.437 - Send: AT<cr
01-26-2006 21:58:17.437 - Recv
<cr><lf>OK<cr><lf
01-26-2006 21:58:17.437 - Interpreted response: O
01-26-2006 21:58:17.453 - Send
AT&FE0V1&C1&D2S95=45S0=0<cr
01-26-2006 21:58:17.468 - Recv
<cr><lf>OK<cr><lf
01-26-2006 21:58:17.468 - Interpreted response: O
01-26-2006 21:58:17.468 - Send
ATS7=180S30=0L1M1\N3%C3&K3BN1X4<cr
01-26-2006 21:58:17.484 - Recv
<cr><lf>OK<cr><lf
01-26-2006 21:58:17.484 - Interpreted response: O
01-26-2006 21:58:17.484 - Waiting for a call
01-26-2006 21:58:17.484 - Send: at#cid=1<cr
01-26-2006 21:58:17.500 - Recv
<cr><lf>OK<cr><lf
01-26-2006 21:58:17.500 - Interpreted response: O
01-26-2006 21:58:17.500 - Send: ATS0=0<cr
01-26-2006 21:58:17.500 - Recv
<cr><lf>OK<cr><lf
01-26-2006 21:58:17.500 - Interpreted response: O
01-26-2006 21:58:17.500 - Session Statistics
01-26-2006 21:58:17.500 - Reads : 30 byte
01-26-2006 21:58:17.500 - Writes: 76 byte

It appears that I can receive faxes, but not send them: then th
connections keeps dropping after 27 seconds (after the handshake, an
just before start sending pages....

I googled like crazy, but could not find any answers yet..

:retard:

Leo

"Leon" <no@spam.invalid> wrote in message
news:kTdCf.283927$gj3.37643@fe02.news.easynews.com ...
modem (and motherboards chipset) then the fact that windows turns your inf
into an OEMxx.inf is normal. Where did you get the latest inf from? The way
around the OEMx.inf situation is just to copy your inf into the Windows/inf
folder and let it be installed from there.

Paul

I downloaded the driver from driverguide.com (the same as I was usin
before)

I also tried the supplied driver, but that one is/was for nt4 (sinc
the modem itself is a couple of years old). I reinstalled the drive
I was using before on my XP installation

I suspect that one of the windows update(s) or office update(s) ar
causing the problem... (essentially, those are the only things tha
are different from my former installation)

Is it possible that one of the office applications is causing th
trouble with the fax, i.e., that one of those components are tryin
to monitor for incoming faxes as well (beside the ms fax itself of
course)

I noticed that before sending the fax, al lot of lights are blinkin
for a (very) short time on the modem.
It might also be the case that some of the at commands in the ini
strings for de rockwell modem changed (but which and how to chang
them....

Is a fax behaving different from a 'normal' dialup connection or mode
session for telebanking

Leo

"Leon" <no@spam.invalid> wrote in message
news:k2rCf.324116$Es3.233841@fe03.news.easynews.co m...
worked fine previously this is unlikely to be the problem - it always pays
to check its the latest).

out one of them and if it works fine with another software package then it
would tend to point to your software package. I presume that you've checked
all your phone line connections/cables etc If ordinary dialup is working
fine then the cable or phone line are unlikely to be a problem however.

coding changes to faxing software should take account of existing compatible
hardware.
the modem speaker while the fastest possible connection is established, the
protocols used for data transmission are very different between dialup to
the internet and fax transmission.
Paul

Well, the problem is solved, i.e., a 'workaround

I stopped using MS fax, which refuses to send a fax and keeping th
connection

No I installed a trial of Mighty Fax which works (as well as with th
build in drivers as with the drivers installed on XP...

The MS fax can be removed!! :evil:

Thanks for all replies