Hi,

I've just installed gentoo 1.4, updated the kernel to 2.4.22 and installed the hcfpcimodem drivers.

Using minicom I can dial out so quite pleased there (thats more than I can do in Windows 2K with that modem, unless using AOL software)

I'm using the initialisation string and dialling prefixes from the AOL software as I know they work. The Modem is an Aztech MDMP3858V-WE, which uses the Conexant HCF chip.

Init String: AT&F&C1&D2S95=1^M
Dial Prefix: ATD

I've installed penggy without a hitch, but launching it doesn't seem to DO anything. It doesn't pick up the line, it just sits there.

Any ideas as to what I should do next?

I'm assuming the ^M is written exactly as seen (hold shift, press 6 and m), and not using some escaped sequence?

The AOL software uses ^M as a dialling suffix - I guess I need to check if it works with a normal carriage return (or is it a line feed, or new line?) in minicom.

I could always try to get the modem working in Windows 2K and use a proper ISP, but I would say that I'm pretty proficient with Windows and Drivers... and I can't make it work (despite trying several different drivers), which is why I use AOL (since it does work with their software).

Thanks to all in advance,
Ben.

^M is a Carriage Return character and may be present if the file you read it from was created under Windows. Try just removing the ^M. If that doesn't work then CTRL+M may.

Thanks... that makes a bit more sense.

The ^M is actually in the initialisation string as shown in the AOL options.

Within minicom, using that initialisiation string, and then using:
ATD0123456789 (carraige return, or presumably, ^M)
dials 0123456789.

It then seems to report no carrier if I hang up, so I think the modem configuration is ok.

I guess the problem is either penggy or it's configuration. Anybody have any ideas how to troubleshoot or what to try?

Thanks.

Ben

Ok... fixed the dodgy modem in wondows thing now.

I'm posting this from lynx whilst performing an using a proper ISP.

Cheers,
Ben

there you go ben, you did get there after all.

Yeah... and I've just a whole load more time working out why my computer now can't access my modem in windows... after spending several hours last night getting it to work.

Something that the freeserve connection kit does to the computer (I think maybe DUN 1.4 is installed in there somewhere as well) stops the thing from working. So thats gone now, apparently that will "greatly reduce my ability to connect to anytime", seems to opposite to me...

Why can't these bloody ISPs just use standard protocols with standard software to access standard features. Maybe I don't hate Linux... :-)