Win2k and Modem Help

This is a discussion about Win2k and Modem Help in the Windows Hardware category; For the life of me I can not get my Creative Labs Modem Blaster DI5601-1 to work. The modem works fine in Win98 but whenever I boot into Win2k I have problems. Whenever I try to dial I get an error saying, Error Could Not Open Port.

Windows Hardware 9627 This topic was started by , . Last reply by ,


data/avatar/default/avatar31.webp

2 Posts
Location -
Joined 2000-08-09
For the life of me I can not get my Creative Labs Modem Blaster DI5601-1 to work. The modem works fine in Win98 but whenever I boot into Win2k I have problems. Whenever I try to dial I get an error saying, "Error Could Not Open Port".
 
I have tried setting the jumpers on the modem to non PNP mode and that didn't work either. Win2k detects the modem fine when I set it to PNP mode and installs it without a hitch, but I still can't get it to dial.
 
I am using Win2K build 2195. If anyone can help I would appreciate it. Thanks.

Participate in our website and join the conversation

You already have an account on our website? To log in, use the link provided below.
Login
Create a new user account. Registration is free and takes only a few seconds.
Register
This subject has been archived. New comments and votes cannot be submitted.
Aug 9
Created
Aug 9
Last Response
0
Likes
2 minutes
Read Time
User User
Users

Responses to this topic


data/avatar/default/avatar31.webp

2 Posts
Location -
Joined 2000-08-09
OP
Here is a log of my last attempt:
 
08-08-2000 14:37:32.893 - File: D:\WINNT\System32\unimdm.tsp, Version 5.0.2175 - Retail
08-08-2000 14:37:32.893 - File: D:\WINNT\System32\unimdmat.dll, Version 5.0.2134 - Retail
08-08-2000 14:37:32.893 - File: D:\WINNT\System32\uniplat.dll, Version 5.0.2151 - Retail
08-08-2000 14:37:32.903 - File: D:\WINNT\System32\drivers\modem.sys, Version 5.0.2134 - Retail
08-08-2000 14:37:32.903 - File: D:\WINNT\System32\modemui.dll, Version 5.0.2146 - Retail
08-08-2000 14:37:32.903 - Modem type: Creative Modem Blaster Flash56 DI5601-1
08-08-2000 14:37:32.903 - Modem inf path: oem0.inf
08-08-2000 14:37:32.903 - Modem inf section: Install
08-08-2000 14:37:32.913 - 115200,8,N,1, ctsfl=1, rtsctl=2
08-08-2000 14:37:32.913 - Initializing modem.
08-08-2000 14:37:32.923 - Send: ATZ<cr>
08-08-2000 14:37:32.923 - Recv: ATZ<cr>
08-08-2000 14:37:32.923 - Command Echo
08-08-2000 14:37:33.033 - Recv: <cr><lf>OK<cr><lf>
08-08-2000 14:37:33.033 - Interpreted response: OK
08-08-2000 14:37:33.043 - Send: AT&FE1V1S0=0&C1&D2+MR=2;+DR=1;+ER=1W2<cr>
08-08-2000 14:37:33.073 - Recv: AT&FE1V1S0=0&C1&D2+MR=2;+DR=1;+ER=1W2<cr>
08-08-2000 14:37:33.073 - Command Echo
08-08-2000 14:37:33.073 - Recv: <cr><lf>ERROR<cr><lf>
08-08-2000 14:37:33.073 - Interpreted response: Error
08-08-2000 14:37:33.083 - Session Statistics:
08-08-2000 14:37:33.083 - Reads : 57 bytes
08-08-2000 14:37:33.083 - Writes: 42 bytes

data/avatar/default/avatar08.webp

112 Posts
Location -
Joined 2000-05-11
This could be caused by a common Windows 2000 issue. It happens because when windows 2000 boots, windows 2000 detects again all COM ports.
 
If you install a modem, and then you turn it off, next time you start windows 2000 won't find you modem, and so, it won't attatch it to a COM port.
 
This can be fixed by just turning on your modem before you boot windows 2000.
 
If you have no success...well, good luck then!