Just wondering about something...I purchased a modem only a few months before XP came out and it is not 'signed' by M$.

I Downloaded the XP driver for it off their site but it still will not work, I've spent many hours trying to fix it, but the best I can make it do is get to 'verifying user name and password' when I try to connect to the internet. It just seems to hang...

Any ideas?

Oh, one more thing, its XP Home edition, if that makes any difference.

Thanks :)

Just because drivers are not signed by M$ doesn't mean they wont work. If you know the make and model (and chipset maybe too) then try and download an updated driver from the maker's website or from other web resources. Post the details here and we can all help and identify where to get them from.

Thanks for the advice Paul.
One question: what is the 'chipset'?

The modem in question is a Swann Speed Demon 56k V.90 (see-through red colour)

I've been to their Website and followed all the appropriate installation instructions for the modem & the drivers but I've never been able to make it work.

Actually the only time its ever worked is when I first bought it and couldnt make it work so I took it to a local technician who somehow fixed it, how I'm not sure...

Thoughts? Thanks.

The chipset is the modem's brain and the "same modem" marketed by one or many different firms may use parts from different chipset manufacturers. Your modem appears to come in two of such flavours with an Ambient or a Rockwell chipset; the drivers for one are most unlikely to work for the other one.

http://www.swann.com.au/s-techsupportinf1.php#speeddemon

You must also ensure that you have the correct drivers for the OS in question.

Pardon my ignorance, but what exactly is my next step here...?

Am I to use the Ambient or Rockwell chipset? (Over the years I'm sure to have tryed both of these...)

Should I Email their tech support?

"You must also ensure that you have the correct drivers for the OS in question."

It is WinXP Home. Do you mean all drivers or just modem drivers?


Confused.

It is WinXP Home. Do you mean all drivers or just modem drivers?
In this case modem drivers - but generally speaking all drivers are specific for one or a range of OSes.

Am I to use the Ambient or Rockwell chipset?
If you can work out which one your modem uses that is the one to use. Otherwise a bit of trial and error - but it is wise to remove all traces of the previous drivers before installing new ones. Either from Add/Remove programs if there is an entry there or from Device Manager in Safe Mode.

Ok, I followed the instructions on the Swann website to the letter, when I reboot computer after connecting the modem it recognizes the chipset as 'Ambient'.

The modem connected to my ISP at 4.8bps...too slow even for IE to reach its homepage.

Kinda want to get this working, my 33.6k modem aint much fun either!! :p


Thought maybe this might help you to discern the problem:

Modem Log:


01-24-2005 21:27:00.310 - File: C:\WINDOWS\System32\tapisrv.dll, Version 5.1.2600
01-24-2005 21:27:00.310 - File: C:\WINDOWS\System32\unimdm.tsp, Version 5.1.2600
01-24-2005 21:27:00.310 - File: C:\WINDOWS\System32\unimdmat.dll, Version 5.1.2600
01-24-2005 21:27:00.310 - File: C:\WINDOWS\System32\uniplat.dll, Version 5.1.2600
01-24-2005 21:27:00.310 - File: C:\WINDOWS\System32\drivers\modem.sys, Version 5.1.2600
01-24-2005 21:27:00.310 - File: C:\WINDOWS\System32\modemui.dll, Version 5.1.2600
01-24-2005 21:27:00.310 - File: C:\WINDOWS\System32\mdminst.dll, Version 5.1.2600
01-24-2005 21:27:00.310 - Modem type: Swann Speed Demon
01-24-2005 21:27:00.310 - Modem inf path: mdmsde2k.inf
01-24-2005 21:27:00.310 - Modem inf section: Gen56kExt
01-24-2005 21:27:00.310 - Matching hardware ID: serenum\amb3100
01-24-2005 21:27:00.326 - 115200,8,N,1, ctsfl=1, rtsctl=2
01-24-2005 21:27:00.326 - Initializing modem.
01-24-2005 21:27:00.341 - Send: ATZ<cr>
01-24-2005 21:27:00.420 - Recv: <cr><lf>OK<cr><lf>
01-24-2005 21:27:00.420 - Interpreted response: OK
01-24-2005 21:27:00.435 - Send: AT&FE0V1W2&D2&C1S0=0-C0<cr>
01-24-2005 21:27:00.435 - Recv: AT&FE0V1W2&D2&C1S0=0-C0<cr>
01-24-2005 21:27:00.435 - Command Echo
01-24-2005 21:27:00.529 - Recv: <cr><lf>OK<cr><lf>
01-24-2005 21:27:00.529 - Interpreted response: OK
01-24-2005 21:27:00.545 - Send: ATS7=60\T0L1M1\N3-J1%C1"H3\Q3B0N1X4<cr>
01-24-2005 21:27:00.623 - Recv: <cr><lf>OK<cr><lf>
01-24-2005 21:27:00.623 - Interpreted response: OK
01-24-2005 21:27:00.623 - Waiting for a call.
01-24-2005 21:27:00.638 - Send: at+vcid=1<cr>
01-24-2005 21:27:00.685 - Recv: <cr><lf>OK<cr><lf>
01-24-2005 21:27:00.685 - Interpreted response: OK
01-24-2005 21:27:00.701 - Send: ATS0=0<cr>
01-24-2005 21:27:00.748 - Recv: <cr><lf>OK<cr><lf>
01-24-2005 21:27:00.748 - Interpreted response: OK
01-24-2005 21:27:00.748 - 921600,8,N,1, ctsfl=1, rtsctl=2
01-24-2005 21:27:00.748 - Initializing modem.
01-24-2005 21:27:00.763 - Send: ATZ<cr>
01-24-2005 21:27:00.841 - Recv: <cr><lf>OK<cr><lf>
01-24-2005 21:27:00.841 - Interpreted response: OK
01-24-2005 21:27:00.857 - Send: AT&FE0V1W2&D2&C1S0=0-C0<cr>
01-24-2005 21:27:00.857 - Recv: AT&FE0V1W2&D2&C1S0=0-C0<cr>
01-24-2005 21:27:00.857 - Command Echo
01-24-2005 21:27:00.951 - Recv: <cr><lf>OK<cr><lf>
01-24-2005 21:27:00.951 - Interpreted response: OK
01-24-2005 21:27:00.966 - Send: ATS7=60\T0L1M1\N3-J1%C1"H3\Q3B0N1X4<cr>
01-24-2005 21:27:01.045 - Recv: <cr><lf>OK<cr><lf>
01-24-2005 21:27:01.045 - Interpreted response: OK
01-24-2005 21:27:01.045 - Dialing.
01-24-2005 21:27:01.060 - Send: ATDT##########<cr>
01-24-2005 21:27:35.029 - Recv: <cr>
01-24-2005 21:27:35.029 - Interpreted response: Informative
01-24-2005 21:27:35.029 - Recv: <lf>
01-24-2005 21:27:35.029 - Interpreted response: Informative
01-24-2005 21:27:35.029 - Recv: CONNECT 4800
01-24-2005 21:27:35.029 - Interpreted response: Connect
01-24-2005 21:27:35.029 - Connection established at 4800bps.
01-24-2005 21:27:35.029 - Error-control off or unknown.
01-24-2005 21:27:35.029 - Data compression off or unknown.
01-24-2005 21:28:05.027 - Read: Total: 7766, Per/Sec: 256, Written: Total: 11266, Per/Sec: 372
01-24-2005 21:28:41.121 - Hanging up the modem.
01-24-2005 21:28:41.121 - Hardware hangup by lowering DTR.
01-24-2005 21:28:42.214 - Detected CD dropped from lowering DTR
01-24-2005 21:28:42.214 - Recv: <cr><lf>OK<cr><lf>
01-24-2005 21:28:42.214 - Interpreted response: OK
01-24-2005 21:28:42.230 - Send: ATH<cr>
01-24-2005 21:28:42.292 - Recv: <cr><lf>OK<cr><lf>
01-24-2005 21:28:42.292 - Interpreted response: OK
01-24-2005 21:28:42.308 - 115200,8,N,1, ctsfl=1, rtsctl=2
01-24-2005 21:28:42.308 - Initializing modem.
01-24-2005 21:28:42.324 - Send: ATZ<cr>
01-24-2005 21:28:42.402 - Recv: <cr><lf>OK<cr><lf>
01-24-2005 21:28:42.402 - Interpreted response: OK
01-24-2005 21:28:42.417 - Send: AT&FE0V1W2&D2&C1S0=0-C0<cr>
01-24-2005 21:28:42.417 - Recv: AT&FE0V1W2&D2&C1S0=0-C0<cr>
01-24-2005 21:28:42.417 - Command Echo
01-24-2005 21:28:42.496 - Recv: <cr><lf>OK<cr><lf>
01-24-2005 21:28:42.496 - Interpreted response: OK
01-24-2005 21:28:42.511 - Send: ATS7=60\T0L1M1\N3-J1%C1"H3\Q3B0N1X4<cr>
01-24-2005 21:28:42.589 - Recv: <cr><lf>OK<cr><lf>
01-24-2005 21:28:42.589 - Interpreted response: OK
01-24-2005 21:28:42.589 - Waiting for a call.
01-24-2005 21:28:42.605 - Send: at+vcid=1<cr>
01-24-2005 21:28:42.652 - Recv: <cr><lf>OK<cr><lf>
01-24-2005 21:28:42.652 - Interpreted response: OK
01-24-2005 21:28:42.667 - Send: ATS0=0<cr>
01-24-2005 21:28:42.714 - Recv: <cr><lf>OK<cr><lf>
01-24-2005 21:28:42.714 - Interpreted response: OK
01-24-2005 21:28:42.714 - Session Statistics:
01-24-2005 21:28:42.714 - Reads : 54 bytes
01-24-2005 21:28:42.714 - Writes: 81 bytes

Well it seems that you can dialup and then have difficulty handshaking with the modem at the other end such that it will only attempt to verify the connection or connect at a very slow speed.

I just wonder if you have a bad telecom line. Do everything you can to create a single phone line from the modem to the wall jack (possibly a new telephone cable) and with good connections. Depress one phone number to get rid of the dial tone and see if you can hear any crackles. Even if there is nothing audible, get the telecom company to test the line.

You could try decreasing the FIFO buffer settings (Control Panel -- Phone and Modems -- Modems -- Properties -- Advanced -- Advanced Port Settings) though usually this only has marginal effects if it works at all - the idea is to slow down the "chatter" between the two modems such that they understand each other at the first attempt and don't have to keep re-sending the same data.

The only other way to eliminate the phone line as the cause would be to try the modem at a house with a known good connection.

Thanks for replying Paul, I've had the modem in question working on this phoneline before(at 56k speeds), when the technician installed it and did a number of other things to my computer.
I've also been using my 33.6k modem on the same phoneline and exact same kind of set up as what im trying to do with the 56k modem.
Also I've had broadband on this phoneline (which worked perfectly), if that matters...

Theres no crackles or anything on the line and I had it tested a few months ago when getting broadband(no longer have it) and Telstra(Aus phone company) said the line was fine.

The FIFO settings you mentioned...do you mean 'data connection preferences' or 'hardware settings'? or something else entirely?


Thanks

I was talking about the Transmit and Receive FIFO buffers, which is the software that helps control the UART chip as the "hub of the com port".

The different OSes have the setting in different places. I gave the route for WinXP but post back if it is a different OS and it shouldnt be too hard to point you in the right direction.

Hmm thats what got me puzzled....it is WinXP (Home).

I followed the steps you gave me to get to those advanced settings but all that was there was those 2 others I mentioned in the above post...

Could the problem be that the modem that does work (33.6k) is always plugged into COM 2 whereas the 56k is plugged into COM 1?
Although this wouldnt explain how it connected at 4.8bps...

hmmm!

How many modems are installed? That could be the cause of conflicts and/or ghosts whether physically attached or not.

2 Modems installed. The 33.6k is a Rockwell DPF PnP made by Conexant.

So what your saying is to uninstall the 33.6k before trying to install the 56k?


:)

I'm not saying that you can never have more than one modem attaced but in a situation where there are problem issues it often helps to simplify matters. Yes you can uninstall the modem and you can also disable its hardware profile.

Personally I would uninstall all references to any modems (while booted into safe mode) and physically detach both of them. Then boot up and close down. Then install whichever modem you prefer. If that works well but you then have problems if or when you install the second modem - you have your diagnosis.

Ok gonna try that Paul, thanks, I only want the 1 modem installed (56k).

Will see if it works

Followed your instructions: Got 'Error 777' when dialing...

Perhaps this could be some sort of incompatibilty with the ISP and my modem...?
When I had it working ages ago it was with a different ISP.

When I had it working ages ago it was with a different ISP.

Possibly that's relevant - you could always check with them if it is mandatory to use any specific protocols (eg v90) but I would double-check all the cabling and try a new piece of telephone extension cable (which would have new and hopefully more snugly-fitting jacks on it). It's also not beyond the realms of possibility that the modem is just plain faulty and I have seen the same sort of problem result from lightening strikes in the area.

Hmm, I'm going to Email the ISP, Swann and a local tech guy, I'm also going to get the modem checked out.

Thanks for your help Paul, you really know your stuff.


Cheers~~