The "Freeola Customer Forum" forum, which includes Retro Game Reviews, has been archived and is now read-only. You cannot post here or create a new thread or review on this forum.
The PC spec is:
700MHz Duron
128Mb Ram
20Gb HDD
Windows ME
Motorola SM56 PCI soft modem
I have taken the log file from the modem. Here is a small (in comparison) bit of it.
06-03-2003 17:53:20.36 - Modem type: Motorola SM56 PCI Speakerphone Modem
06-03-2003 17:53:20.36 - Modem inf path: MOTORO~1.INF
06-03-2003 17:53:20.36 - Modem inf section: Modem11
06-03-2003 17:53:20.39 - 115200,N,8,1
06-03-2003 17:53:20.39 - 57600,N,8,1
06-03-2003 17:53:20.39 - Initializing modem.
06-03-2003 17:53:20.39 - Send: AT
06-03-2003 17:53:21.15 - Recv: AT
06-03-2003 17:53:21.26 - Recv:
06-03-2003 17:53:21.26 - Interpreted response: Ok
06-03-2003 17:53:21.26 - Send: AT&F&D2&C1V1S0=0E0+a8e=1,1
06-03-2003 17:53:21.29 - Recv: AT&F&D2&C1V1S0=0E0+a8e=1,1
06-03-2003 17:53:21.56 - Recv:
06-03-2003 17:53:21.56 - Interpreted response: Ok
06-03-2003 17:53:21.56 - Send: ATS7=60T0L0M1N7%C1Q3*LS1X4
06-03-2003 17:53:21.94 - Recv:
06-03-2003 17:53:21.94 - Interpreted response: Ok
06-03-2003 17:53:21.94 - Dialing.
06-03-2003 17:53:21.94 - Send: ATDT;
06-03-2003 17:53:25.29 - Recv:
06-03-2003 17:53:25.29 - Interpreted response: Ok
06-03-2003 17:53:25.30 - Dialing.
06-03-2003 17:53:25.30 - Send: ATDT###########
06-03-2003 17:53:49.72 - Recv:
06-03-2003 17:53:49.72 - Interpreted response: Connect
06-03-2003 17:53:49.72 - Connection established at 46666bps.
06-03-2003 17:53:49.72 - Error-control on.
06-03-2003 17:53:49.72 - Data compression on.
06-03-2003 17:55:56.56 - Hanging up the modem.
06-03-2003 17:55:56.56 - Hardware hangup by lowering DTR.
06-03-2003 17:55:57.77 - WARNING: The modem did not respond to lowering DTR. Trying software hangup...
06-03-2003 17:55:57.77 - Send: +++
06-03-2003 17:55:58.93 - Recv:
06-03-2003 17:55:58.93 - Interpreted response: Ok
06-03-2003 17:55:58.93 - Send: ATH
06-03-2003 17:56:00.93 - ERROR: Unable to send command to the device.
06-03-2003 17:56:00.93 - Hardware hangup by lowering DTR.
06-03-2003 17:56:03.33 - ERROR: Unable to send command to the device.
06-03-2003 17:56:04.34 - Session Statistics:
06-03-2003 17:56:04.34 - Reads : 1480 bytes
06-03-2003 17:56:04.34 - Writes: 2005 bytes
06-03-2003 17:56:04.34 - Motorola SM56 PCI Speakerphone Modem closed.
ATI1 - 000
ATI2 - OK
ATI3 - Release 4.10 AD04 Build 80.5
ATI4 - OK
ATI5 - LAST DISCONNECT: NONE
ATI6 - 44
ATI7 - Motorola SM56 PCI Speakerphone Modem
AT+FCLASS=? - 0,1,8
The particular bit that caught my attention although I dont know what it means is the "hardware hang up by lowering DTR".
I tried everything I could think of on this one. Im thinking it might actually be a hardware fault, although it did work once upon a time. However the woman wwho owns the PC, had some sort of trouble with it that from what I gather ended up with an engineer coming out and replacing the mouse. Theres all that I can think of. Somebody please help!
Firstly, uninstall the modem from the PC (make sure all drivers are deleted, etc). Reinstall the modem and see if anything is different.
You may want to check which internet protocols you have installed. You'll want TCP/IP, possibly IPX/SPX depending on what you use your comp for.
Check the microsoft website and the modem vendors site for any known issues or compatability problems. Tech forums/FAQ's normally hold a lot of useful info.
Whilst you're at the manufacturers site, download the latest drivers/patches for that particular modem, and install them too.
If all this fails, apply a precise jolt to the side of the modem/case, possibly with a boot or shoe of some kind...
The PC spec is:
700MHz Duron
128Mb Ram
20Gb HDD
Windows ME
Motorola SM56 PCI soft modem
I have taken the log file from the modem. Here is a small (in comparison) bit of it.
06-03-2003 17:53:20.36 - Modem type: Motorola SM56 PCI Speakerphone Modem
06-03-2003 17:53:20.36 - Modem inf path: MOTORO~1.INF
06-03-2003 17:53:20.36 - Modem inf section: Modem11
06-03-2003 17:53:20.39 - 115200,N,8,1
06-03-2003 17:53:20.39 - 57600,N,8,1
06-03-2003 17:53:20.39 - Initializing modem.
06-03-2003 17:53:20.39 - Send: AT
06-03-2003 17:53:21.15 - Recv: AT
06-03-2003 17:53:21.26 - Recv:
06-03-2003 17:53:21.26 - Interpreted response: Ok
06-03-2003 17:53:21.26 - Send: AT&F&D2&C1V1S0=0E0+a8e=1,1
06-03-2003 17:53:21.29 - Recv: AT&F&D2&C1V1S0=0E0+a8e=1,1
06-03-2003 17:53:21.56 - Recv:
06-03-2003 17:53:21.56 - Interpreted response: Ok
06-03-2003 17:53:21.56 - Send: ATS7=60T0L0M1N7%C1Q3*LS1X4
06-03-2003 17:53:21.94 - Recv:
06-03-2003 17:53:21.94 - Interpreted response: Ok
06-03-2003 17:53:21.94 - Dialing.
06-03-2003 17:53:21.94 - Send: ATDT;
06-03-2003 17:53:25.29 - Recv:
06-03-2003 17:53:25.29 - Interpreted response: Ok
06-03-2003 17:53:25.30 - Dialing.
06-03-2003 17:53:25.30 - Send: ATDT###########
06-03-2003 17:53:49.72 - Recv:
06-03-2003 17:53:49.72 - Interpreted response: Connect
06-03-2003 17:53:49.72 - Connection established at 46666bps.
06-03-2003 17:53:49.72 - Error-control on.
06-03-2003 17:53:49.72 - Data compression on.
06-03-2003 17:55:56.56 - Hanging up the modem.
06-03-2003 17:55:56.56 - Hardware hangup by lowering DTR.
06-03-2003 17:55:57.77 - WARNING: The modem did not respond to lowering DTR. Trying software hangup...
06-03-2003 17:55:57.77 - Send: +++
06-03-2003 17:55:58.93 - Recv:
06-03-2003 17:55:58.93 - Interpreted response: Ok
06-03-2003 17:55:58.93 - Send: ATH
06-03-2003 17:56:00.93 - ERROR: Unable to send command to the device.
06-03-2003 17:56:00.93 - Hardware hangup by lowering DTR.
06-03-2003 17:56:03.33 - ERROR: Unable to send command to the device.
06-03-2003 17:56:04.34 - Session Statistics:
06-03-2003 17:56:04.34 - Reads : 1480 bytes
06-03-2003 17:56:04.34 - Writes: 2005 bytes
06-03-2003 17:56:04.34 - Motorola SM56 PCI Speakerphone Modem closed.
ATI1 - 000
ATI2 - OK
ATI3 - Release 4.10 AD04 Build 80.5
ATI4 - OK
ATI5 - LAST DISCONNECT: NONE
ATI6 - 44
ATI7 - Motorola SM56 PCI Speakerphone Modem
AT+FCLASS=? - 0,1,8
The particular bit that caught my attention although I dont know what it means is the "hardware hang up by lowering DTR".
I tried everything I could think of on this one. Im thinking it might actually be a hardware fault, although it did work once upon a time. However the woman wwho owns the PC, had some sort of trouble with it that from what I gather ended up with an engineer coming out and replacing the mouse. Theres all that I can think of. Somebody please help!