Windows 7 Serial Modem - A long shot

moss

moss

moss

Soldato
Joined
1 Nov 2002
Posts
6,487
Location
South Shields
Has any used a serial modem with Windows 7 Pro x86?
We have some Wavecom Fastrack 20 GSM modems (http://www.fouriersystems.com/files/download_center/wavecom_GSM_Modem.pdf) which are used for redundancy purposes should the main lines fail. It would only ever send a few text commands, so they are still a reasonable backup comms method.

At the minute they are connected to Windows XP machines however we have recently upgraded most of the desktop infrastructure to Windows 7.

Using the standard 56k modem drivers built into XP, they connect without problem. Again using the standard 56k modem drivers, Windows 7 detects the modem and can query it fine. On one Win7 PC it will connect then automatically disconnects. On another it wont actually connect, the log shows its failing at the point when it sends the 'user initialization commands' which I have configured. These are correct as they are copied directly from the XP machines. I have also put the Sim card into a USB modem and it connected using the same commands.

Code: 
06-30-2011 15:15:02.735 - Sending user initialization commands.
06-30-2011 15:15:02.745 - Send: AT+CGDCONT=1,"IP","xxx.gov.uk"<cr>
06-30-2011 15:15:02.752 - Recv: <cr><lf>ERROR<cr><lf>

I know its a long shot as few companies/people are likely to be using these now. Anyone shed any light on this?
 
Last edited:
hey the old AT command set, long time no see baby! I have had a couple of issues with serial comms on windows 7, have you checked the setup in BIOS it seemed well picky...if not, more info the better mate!
 
Nothing in the BIOS that would make any difference.
The error reported by Windows 7 is:
Error 692: There was a hardware failure in the modem (or other connecting device).
The log shows it fails at the extra initialization commands. If I remove them I get an:
Error 777: The connection attempt failed because the modem on the remote computer is out of order.

Windows 7 is using the same serial port config as the XP machines:
Port Speed: 115200
Flow Control: Hardware
Data Bits: 8
Parity: None
Stop Bits: 1

Using PAP unencrypted passwords.

We could simply buy USB modems but in the places these are used serial ones are much better option.
 
I'm guessing you've tried all the usual suspects like cables etc. first? Serial comms appears to be mightily screwed in Win 7 after a quick google with many older solutions failing under 7 after working fine on XP
 
I've tried other cables/modems, it looks like we'll end up using USB modems, they arent ideal though.
Thanks for the help, if I do find a resolution i'll post it.
 
Sorry I can't be more specific...lot of stuff to go through in that pdf, I'll take a looksy when I get a chance...
 
Tried a brand new slightly different modem (Fastrack Xtend FXT009) which also has a USB interface. It failed at exactly the same point on both the USB and serial interfaces (using the USB drives downloaded from the manufacturers site). This would usually point to the extra initialization commands being wrong or some issue with the sim/connection, but it works fine it XP using the same commands.
 
I couldnt see why you should, they are being sent directly to Orange. I'm running the Sierra control suite and can perform all other diagnostic/comm tasks through serial without problems. I'll check with the provider on Monday to see if any other commands are needed for Win 7 clients.
 
I've got an orange USB dongle setup this way on my work laptop to connect via DUN and it's fine on Windows 7. It is setup in exactly the same was it was on XP.

The init string looks correct. Daft question - did you cut/paste it across or type it in?
 
You must log in or register to reply here.
Back
Top Bottom