Problem with dial-up connections

Hi,

I desperately need help: until a few days ago, I could use an internal
softmodem properly. I performed a test with another internal modem,
replacing the old one momentarily, and everything was working fine. But
when I came back to the previous configuration, something went wrong:
now, when I configure a dial-up connection and then try to connect using
it, I get the famous blue screen. This is true for both modems.

Of course, I uninstalled and reinstalled them, checked their drivers,
verified that there were no conflict on COM ports and that the modems
were working properly according to System window in the Settings,
inserted them on another PCI slot on the mainboard, and also tried
different connections to different providers: no way around. Each time I
try to establish a dial-up connection, either I get the blue screen, or
I have an error window telling me that the modem is out of service or
turned off, and the system becomes sluggish.

What should I do in order to fix the issue? TIA.

PS: Configuration: (Asus A7V333 mainboard, AMD Athlon XP 2000+ running
at 1,2 Gzh (voluntary bios setting), 128 Mb of RAM, 20 Gb HD, Rage Pro
Turbo AGP 2X video card, SoftV92 Speakerphone Modem with SoftSP (brand
Origo 2000, Conexant chipset) the oder modem being a Olitec PCI V.92
Ready (conexant chipset too).

In article <44b6a071$0$165$(E-Mail Removed)>, Stegozor
<(E-Mail Removed)> wrote:
>Hi,
>
>I desperately need help: until a few days ago, I could use an internal
>softmodem properly. I performed a test with another internal modem,
>replacing the old one momentarily, and everything was working fine. But
>when I came back to the previous configuration, something went wrong:
>now, when I configure a dial-up connection and then try to connect using
>it, I get the famous blue screen. This is true for both modems.
>
>Of course, I uninstalled and reinstalled them, checked their drivers,
>verified that there were no conflict on COM ports and that the modems
>were working properly according to System window in the Settings,
>inserted them on another PCI slot on the mainboard, and also tried
>different connections to different providers: no way around. Each time I
>try to establish a dial-up connection, either I get the blue screen, or
>I have an error window telling me that the modem is out of service or
>turned off, and the system becomes sluggish.
>
>What should I do in order to fix the issue? TIA.
>
>PS: Configuration: (Asus A7V333 mainboard, AMD Athlon XP 2000+ running
>at 1,2 Gzh (voluntary bios setting), 128 Mb of RAM, 20 Gb HD, Rage Pro
>Turbo AGP 2X video card, SoftV92 Speakerphone Modem with SoftSP (brand
>Origo 2000, Conexant chipset) the oder modem being a Olitec PCI V.92
>Ready (conexant chipset too).

Assuming that the old modem hasn't been damaged, I'd try putting the
old modem back in its old slot and using System Restore to go back to
a time before the problem occurred.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional - Windows Networking
http://mvp.support.microsoft.com

Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm

Steve Winograd [MVP] a écrit :

> Assuming that the old modem hasn't been damaged, I'd try putting the
> old modem back in its old slot and using System Restore to go back to
> a time before the problem occurred.

Okay, I haven't considered this option. Here's what happened: there was
only one restore point available at a time before the problem occurred.
I chose it, the system restore (the first time ever I use it) performed
correctly, and guess what, the old modem is functioning correctly now.
However, Murphy still rules. I don't know why, but I've had difficulties
to install the driver of the video card, I had to try three or four
times, and it finally worked (before it was requesting a CD and
complaining about a missing .dll). Once I installed it, everything
seemed fine, but some software do not work properly now (SeaMonkey, even
after a uninstall/reinstall, doesn't launch). OpenOffice.org complains
about a missing I18NISOLANG1MSC.DLL. I couldn't repair it using the
repair option in the installer, I uninstalled it and right now Firefox
is fetching it.

I suppose there will be other strange problems like these. Could you
please explain the reason? Hell, what happened to this computer? What
should I do to take the control back as much as possible? TIA.

In article <44b6e97d$0$169$(E-Mail Removed)>, Stegozor
<(E-Mail Removed)> wrote:
>>>I desperately need help: until a few days ago, I could use an internal
>>>softmodem properly. I performed a test with another internal modem,
>>>replacing the old one momentarily, and everything was working fine. But
>>>when I came back to the previous configuration, something went wrong:
>>>now, when I configure a dial-up connection and then try to connect using
>>>it, I get the famous blue screen. This is true for both modems.
>>>
>>>Of course, I uninstalled and reinstalled them, checked their drivers,
>>>verified that there were no conflict on COM ports and that the modems
>>>were working properly according to System window in the Settings,
>>>inserted them on another PCI slot on the mainboard, and also tried
>>>different connections to different providers: no way around. Each time I
>>>try to establish a dial-up connection, either I get the blue screen, or
>>>I have an error window telling me that the modem is out of service or
>>>turned off, and the system becomes sluggish.
>>>
>>>What should I do in order to fix the issue? TIA.
>>>
>>>PS: Configuration: (Asus A7V333 mainboard, AMD Athlon XP 2000+ running
>>>at 1,2 Gzh (voluntary bios setting), 128 Mb of RAM, 20 Gb HD, Rage Pro
>>>Turbo AGP 2X video card, SoftV92 Speakerphone Modem with SoftSP (brand
>>>Origo 2000, Conexant chipset) the oder modem being a Olitec PCI V.92
>>>Ready (conexant chipset too).
>>
>>Assuming that the old modem hasn't been damaged, I'd try putting the
>>old modem back in its old slot and using System Restore to go back to
>>a time before the problem occurred.
>
>Okay, I haven't considered this option. Here's what happened: there was
>only one restore point available at a time before the problem occurred.
>I chose it, the system restore (the first time ever I use it) performed
>correctly, and guess what, the old modem is functioning correctly now.

You're welcome.

I recommend creating a System Restore point before making any
significant change to the system, such as installing a program,
device, or driver.

>However, Murphy still rules. I don't know why, but I've had difficulties
>to install the driver of the video card, I had to try three or four
>times, and it finally worked (before it was requesting a CD and
>complaining about a missing .dll). Once I installed it, everything
>seemed fine, but some software do not work properly now (SeaMonkey, even
>after a uninstall/reinstall, doesn't launch). OpenOffice.org complains
>about a missing I18NISOLANG1MSC.DLL. I couldn't repair it using the
>repair option in the installer, I uninstalled it and right now Firefox
>is fetching it.
>
>I suppose there will be other strange problems like these. Could you
>please explain the reason? Hell, what happened to this computer? What
>should I do to take the control back as much as possible? TIA.

I'm sorry, but I don't know what's causing the other problems. I
recommend posting your question in one of these news groups:

microsoft.public.windowsme.general
microsoft.public.windowsme.setup
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional - Windows Networking
http://mvp.support.microsoft.com

Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm

Steve Winograd [MVP] a écrit :

>>> Assuming that the old modem hasn't been damaged, I'd try putting the
>>> old modem back in its old slot and using System Restore to go back to
>>> a time before the problem occurred.
>> Okay, I haven't considered this option. Here's what happened: there was
>> only one restore point available at a time before the problem occurred.
>> I chose it, the system restore (the first time ever I use it) performed
>> correctly, and guess what, the old modem is functioning correctly now.
>
> You're welcome.
>
> I recommend creating a System Restore point before making any
> significant change to the system, such as installing a program,
> device, or driver.

You're right, I'll remember this. Interestingly, I tested the second
modem (Olitec) on another computer, and it works fine, while on the
previous one, each time I go into Settings>system>gestionnaire de
périphériques (in French, it means hardware manager or something
similar) and then I click on the properties button after having
highlighted the modem, I get the blue screen. It displays the following
error code: 0E:0028:000001C0.

I think I made a mistake somewhere when I installed the drivers or maybe
there are corrupt files somewhere. Clamwin will have a look on the HD
too. From time to time, computers are really weird.
Anyway, thank you for the system restore clue, it mostly solved my problem.

Stegozor wrote :-

> I think I made a mistake somewhere when I installed the drivers or maybe
> there are corrupt files somewhere.

> ... each time I go into Settings>system> ..
> ... and then I click on the properties button after
> having highlighted the modem, I get the blue screen.
> It displays the following error code: 0E:0028:000001C0.

First, set a new System Restore Point!!

Boot into Safe Mode and using Device Manager, "Remove" your modem.

Reboot (into Normal Mode) and let WinMe redetect (enumerate) and try to
re-install it again. Any improvement?

If not - and you've got SR to get you back <g> - then re-evaluate the error
report

Mart



"Stegozor" <(E-Mail Removed)> wrote in message
news:44b731ef$0$161$(E-Mail Removed). ..
> Steve Winograd [MVP] a écrit :
>
>>>> Assuming that the old modem hasn't been damaged, I'd try putting the
>>>> old modem back in its old slot and using System Restore to go back to
>>>> a time before the problem occurred.
>>> Okay, I haven't considered this option. Here's what happened: there was
>>> only one restore point available at a time before the problem occurred.
>>> I chose it, the system restore (the first time ever I use it) performed
>>> correctly, and guess what, the old modem is functioning correctly now.
>>
>> You're welcome.
>>
>> I recommend creating a System Restore point before making any
>> significant change to the system, such as installing a program,
>> device, or driver.
>
> You're right, I'll remember this. Interestingly, I tested the second modem
> (Olitec) on another computer, and it works fine, while on the previous
> one, each time I go into Settings>system>gestionnaire de périphériques (in
> French, it means hardware manager or something similar) and then I click
> on the properties button after having highlighted the modem, I get the
> blue screen. It displays the following error code: 0E:0028:000001C0.
>
> I think I made a mistake somewhere when I installed the drivers or maybe
> there are corrupt files somewhere. Clamwin will have a look on the HD too.
> From time to time, computers are really weird.
> Anyway, thank you for the system restore clue, it mostly solved my
> problem.

Mart a écrit :

>> I think I made a mistake somewhere when I installed the drivers or maybe
>> there are corrupt files somewhere.
>
>> ... each time I go into Settings>system> ..
>> ... and then I click on the properties button after
>> having highlighted the modem, I get the blue screen.
>> It displays the following error code: 0E:0028:000001C0.

Well this isn't actually true, I should have been more precise, in fact
I get the blue screen when I choose (Settings, Modems, Diagnosis tab
(translation from French)) the COM port of the Olitec modem (right now
COM 4) and then when I click on complementary information : blue screen,
0E:0028:000001C0.
When I call a provider (tested many), the system becomes sluggish and
unresponsive (the modem never "lifts the receiver", a SMS box shows me
the status of the line), the only solution is to hit the reset button.
Note that the other modem works fine on this PC, and that this Olitec
modem works well on another PC. Drivers up to date (I tried to install
them after the autodetection) and no conflict on COM ports according to
Windows. All windows updates installed. X-Files?

> First, set a new System Restore Point!!

Done.

> Boot into Safe Mode and using Device Manager, "Remove" your modem.

Done too.

> Reboot (into Normal Mode) and let WinMe redetect (enumerate) and try to
> re-install it again. Any improvement?

The modem is redected and reinstalled, but the problem remains.

> If not - and you've got SR to get you back <g> - then re-evaluate the error
> report

I might have to find back the install CD of Windows Me, and to repair or
reinstall the OS, but that's not an emergency, as the system restore
(thanks to Steve Winograd) fixed most issues. Something strange still
remains, though (SeaMonkey impossible to launch, and this Olitec problem).

If you are only seeing 'blue screen' errors with this one modem, then it's
very likely that there is a resource conflict - probably due to 'incorrect'
drivers. Are you sure that you've got the correct and latest WinMe drivers
for that specific modem?

What does Device Manager say - any conflicts? (Thinks .... COM 4? - Not
impossible, but usually 2 or 3 by default) Can you 'manually' over-ride the
auto-detect settings. If a PCI modem, try moving it to a different slot.

Can't think of any further suggestions, but doubt that re/over install of OS
will resolve it especially if this modem is the only item giving 0E:0028:xxx
error reports.

Mart




"Stegozor" <(E-Mail Removed)> wrote in message
news:44b7af6e$0$163$(E-Mail Removed). ..
> Mart a écrit :
>
>>> I think I made a mistake somewhere when I installed the drivers or maybe
>>> there are corrupt files somewhere.
>>
>>> ... each time I go into Settings>system> ..
>>> ... and then I click on the properties button after
>>> having highlighted the modem, I get the blue screen.
>>> It displays the following error code: 0E:0028:000001C0.
>
> Well this isn't actually true, I should have been more precise, in fact I
> get the blue screen when I choose (Settings, Modems, Diagnosis tab
> (translation from French)) the COM port of the Olitec modem (right now COM
> 4) and then when I click on complementary information : blue screen,
> 0E:0028:000001C0.
> When I call a provider (tested many), the system becomes sluggish and
> unresponsive (the modem never "lifts the receiver", a SMS box shows me the
> status of the line), the only solution is to hit the reset button. Note
> that the other modem works fine on this PC, and that this Olitec modem
> works well on another PC. Drivers up to date (I tried to install them
> after the autodetection) and no conflict on COM ports according to
> Windows. All windows updates installed. X-Files?
>
>> First, set a new System Restore Point!!
>
> Done.
>
>> Boot into Safe Mode and using Device Manager, "Remove" your modem.
>
> Done too.
>
>> Reboot (into Normal Mode) and let WinMe redetect (enumerate) and try to
>> re-install it again. Any improvement?
>
> The modem is redected and reinstalled, but the problem remains.
>
>> If not - and you've got SR to get you back <g> - then re-evaluate the
>> error report
>
> I might have to find back the install CD of Windows Me, and to repair or
> reinstall the OS, but that's not an emergency, as the system restore
> (thanks to Steve Winograd) fixed most issues. Something strange still
> remains, though (SeaMonkey impossible to launch, and this Olitec problem).

Mart a écrit :
> If you are only seeing 'blue screen' errors with this one modem, then it's

Both modems had previously worked correctly on this computer. The
problem occured when I replaced the softmodem by the Olitec (in fact, to
check whether given providers were supporting V44 compression). At some
point, while replacing the modems (I never had both connected
physically), I must have done something wrong.

> very likely that there is a resource conflict - probably due to 'incorrect' drivers.

I think so. I double clicked once by mistake on the HSFsetup.exe without
using the proper driver install procedure. Nothing happened, but who
knows...

> Are you sure that you've got the correct and latest WinMe drivers
> for that specific modem?

According to the manufacturer's website, it's the latest driver.

> What does Device Manager say - any conflicts? (Thinks .... COM 4? - Not
> impossible, but usually 2 or 3 by default) Can you 'manually' over-ride the

COM 1: Standard GSM Modem (don't know where it comes from, I don't have
such a modem, it is there since I installed Windows Me)
COM 2: Empty
COM 3: SoftV92 Speakerphone Modem with SoftSP (physically not there,
anyway when I remove it via the Device Manager the result is the same)
COM 4: Initially the OLITEC PCI V92 Ready V2 Data,Fax Modem , now empty
(isn't on the list anymore).
No conflicts according to Device Manager.

> auto-detect settings. If a PCI modem, try moving it to a different slot.

I already placed the modem in another PCI slot. Didn't fix the issue.

> Can't think of any further suggestions, but doubt that re/over install of OS
> will resolve it especially if this modem is the only item giving 0E:0028:xxx
> error reports.

The problem is not very serious anymore. I'll try to use Windows CDs
when I find them, and then I'll post the result here, though this may
take quite a while. BTW, thank you for going to that trouble Mart.

Stegozor wrote :-

> ... BTW, thank you for going to that trouble Mart.

You're welcome - sorry I couldn't help any further

> .... I'll try to use Windows CDs when I find them,

FWIW - As you refer to CD's (plural), I presume they are OEM CD's (not the
single MS retail CD). However, you *may* have (if it's an OEM install and
your OEM has provided them) a complete set of WinMe installation files in
either the \windows\options\CABS folder or the \windows\options\instal
folder.

Mart



"Stegozor" <(E-Mail Removed)> wrote in message
news:44b7c9ad$0$168$(E-Mail Removed). ..
> Mart a écrit :
>> If you are only seeing 'blue screen' errors with this one modem, then
>> it's
>
> Both modems had previously worked correctly on this computer. The problem
> occured when I replaced the softmodem by the Olitec (in fact, to check
> whether given providers were supporting V44 compression). At some point,
> while replacing the modems (I never had both connected physically), I must
> have done something wrong.
>
>> very likely that there is a resource conflict - probably due to
>> 'incorrect' drivers.
>
> I think so. I double clicked once by mistake on the HSFsetup.exe without
> using the proper driver install procedure. Nothing happened, but who
> knows...
>
>> Are you sure that you've got the correct and latest WinMe drivers for
>> that specific modem?
>
> According to the manufacturer's website, it's the latest driver.
>
>> What does Device Manager say - any conflicts? (Thinks .... COM 4? - Not
>> impossible, but usually 2 or 3 by default) Can you 'manually' over-ride
>> the
>
> COM 1: Standard GSM Modem (don't know where it comes from, I don't have
> such a modem, it is there since I installed Windows Me)
> COM 2: Empty
> COM 3: SoftV92 Speakerphone Modem with SoftSP (physically not there,
> anyway when I remove it via the Device Manager the result is the same)
> COM 4: Initially the OLITEC PCI V92 Ready V2 Data,Fax Modem , now empty
> (isn't on the list anymore).
> No conflicts according to Device Manager.
>
>> auto-detect settings. If a PCI modem, try moving it to a different slot.
>
> I already placed the modem in another PCI slot. Didn't fix the issue.
>
>> Can't think of any further suggestions, but doubt that re/over install of
>> OS will resolve it especially if this modem is the only item giving
>> 0E:0028:xxx error reports.
>
> The problem is not very serious anymore. I'll try to use Windows CDs when
> I find them, and then I'll post the result here, though this may take
> quite a while. BTW, thank you for going to that trouble Mart.