S
Silverman
I FOUND IT, I FOUND IT, I FOUND IT!!!!
Well, let's say I found it but that doesn't mean in the mnidst
of ALL THE THOUSANDS OF POSTS ABOUT IT that no one else has
found it but I found it and am posting it for those poor dumb
slobs (like me) that have an external modem attached to a
serial / com port and that XP pro keeps "losing".
LEMME ESPLAIN!:
I have typed it up all nice and neat for y'all too!
PROBLEM:
External USR or internal modem is listed as "Not Present" in
XP. Even if the modem is, in fact, installed, turned on, ready
to go; XP will declare (at it's own weird inconsistent
schedule) that the modem is "Not Present" when you go to
Control Panel - Phone and Modem Options - Modems.
NOTE: This is ALL ABOUT A MODEM THAT ALREADY WORKS, HAS BEEN
TESTED, YOU -KNOW- it is fine, it's JUST THAT now and then XP
will say it's "not present" but if you go to ADD NEW HARDWARE
and let it scan, cancel it, do it again, cancel and then find
XP has "miraculously" found your modem again; then continue on
reading this solution.
(If your modem NEVER WORKED, HASN'T EVER BEEN INSTALLED,
DOESN'T EVER GET FOUND BY XP: then this is NOT NOT NOT your
solution.)
The solutions CAN BE:
1. Uninstall and re-install modem drivers.
2. Get updated modem drivers.
3. Make sure modem is turned on.
HOWEVER, most of these won't work and the next day, week,
hour; you will find that Winfax or MS FAX isn't working
because the "Device" is "NOT PRESENT".
STUPID RETARDED DUMB STINKING XP!! - WHAM WHAM! And MS
KNOWS ABOUT THIS BUG TOO!! Have they fixed it yet?!?!?!?
NOOOOOOOOOOOOOO! MAGGOT SUCKING SNOTS! - Okies, I feel
better!
THE SOLUTION IS AS FOLLOWS:
1.
Microsoft has a tool called "Device Console" that you can use
in a batch file to "find" the modem and "wake XP up to it".
FOUND AT:
http://support.microsoft.com/default.aspx?scid=kb;en-us%
3b311272
(Watch the wrap on that address, it should all be one line)
GO GET IT! AND PAY ATTENTION: THE PAGE HAS INFO ABOUT USING
IT. YOU CAN READ ON HERE BUT YOU ALSO MIGHT WANT TO SAVE THAT
PAGE!
What you will download from MS at the above address is a self-
expanding ZIP FILE that has devcon.exe for 32-bit (in the i386
folder and what 99.9999 percent of us need) AND one for 64-bit
(in the ia64 and if you need that then have at it you speed /
power hungry varmint you!).
2.
I extracted, as I said, the 32-bit devcon.exe (found in the
i386 folder) and I put it in C:\Windows\Command.
3.
Make sure your modem is on, connected, you know, how it ALWAYS
IS even when XP says it isn't there sometimes.
Then get to a command prompt and typed in:
devcon rescan
That command makes it find your modem and makes sure it's
listed in Control Panel - Phone and Modem Options - Modems.
Do NOT NOT NOT go any further unless, at this point, your
modem is listed under Modems as attached to a com port. If you
have to, use "devcon rescan" again.
4.
THEN I typed in the following:
devcon find * >C:\test.txt
That command has devcon scan my system, and put whatever
devices it found in a text file on C:\ called "test.txt".
Now I went and opened test.txt up with notepad and I found the
"listing" for my modem. It looked liked this:
SERENUM\USR3020\1&3509B83&0&0000: U.S. Robotics 56K Voice Pro
EXT PnP
It was in the middle of a bunch of goo, but if you know what
modem you have you can find it in there somewhere.
NEXT I found a unique part of it. I found a part that I could
"scan for". I used the "USR3020" part.
What do I mean; "I used the "USR3020" part"?
Well, let's go on to number 5........
5.
I created a batch file to scan my system, put the scan in a
file, then use FIND to scan the file for the USR3020 part, and
if it is NOT THERE (meaning the modem disappeared again thanks
to XP); then devcon puts it back in there and tests again to
make sure.
THE BATCH FILE I USE FOR OUR MODEM AND THAT WE RUN EVERY 4
HOURS IS:
(Use Task Scheduler to run every 4 hours - it runs VERY FAST)
------------Begin Batch
:MODEMSCN
rem FIND.EXE will give errorlevel of 0 when match is found
rem and a 1 when no match is found.
devcon find * >E:\TEMP\DEVCON.TXT
C:\WINDOWS\SYSTEM32\FIND.EXE "USR3020" E:\TEMP\DEVCON.TXT
IF ERRORLEVEL 1 GOTO RESCAN
ERASE E:\TEMP\DEVCON.TXT
GOTO END
:RESCAN
devcon rescan
ERASE E:\TEMP\DEVCON.TXT
GOTO MODEMSCN
:END
------------End Batch
(Did you see where I used the "USR3020" part?)
SO FINALLY IN SHORT: You get devcon from MS, you use it to
scan your system while your modem is working so you can find
out what your modem information is and find some uniquee part
of it (like mine was that unique "USR3020" part) and then you
use that info in a batch file to check now and then and see if
XP has "lost" your modem and if it has; then you use devcon to
SLAP XP IN THE FACE and tell it to put the dang modem BACK!
SIMPLE!!
Okies, it SOUNDS really complicated, but I tried to make it
simple for you.
ALSO SOME TIPS:
A. If you never use your modem but say in the morning; then
set up the batch file to run at 9am once a day and be done
with it.
OR
B. If you only use your modem once in a while / blue moon;
Create the batch file, make a shortcut to it, and hit the
shortcut / run the batch only before you're fixing to use the
modem for faxing or whatever.
C. If you use your modem tons and you want to check it's
availability every few hours then use the Task Scheduler built
into XP. It's wonderful. You can set it to run between xam and
ypm, every Z hours.
BUT IF YOU DO; then make sure you set it to run NO MORE
THAN 1 minute (it's a REALLY FAST PROGRAM so it only needs a
few secs) because if your modem really IS broken, or turned
off; the batch file above will loop forEVER.
I know there is a way to tell a batch file to "go through
a loop only so many times" but I don't know how. If anyone out
there does and wants to pipe up: FEEL FREE!!
This is my best for y'all, hope it helps someone.
AND REMEMBER TO ALWAYS SAY *-THANK YOU VERY MUCH-* to the
EXCELLENT AND WONDERFUL CRITTER, KELLY, WHO *-ALWAYS-* HELPS
OUT HERE!!
Peeps like me pipe up once in a while; SHE IS ALWAYS HERE
HELPING YOU PEEPS OUT!! Be NICE to her, say prayers for her,
buy her CARS and FUR COATS and thingies like that!
Okies, AT LEAST say THANKS to her once in a while!
Well, let's say I found it but that doesn't mean in the mnidst
of ALL THE THOUSANDS OF POSTS ABOUT IT that no one else has
found it but I found it and am posting it for those poor dumb
slobs (like me) that have an external modem attached to a
serial / com port and that XP pro keeps "losing".
LEMME ESPLAIN!:
I have typed it up all nice and neat for y'all too!
PROBLEM:
External USR or internal modem is listed as "Not Present" in
XP. Even if the modem is, in fact, installed, turned on, ready
to go; XP will declare (at it's own weird inconsistent
schedule) that the modem is "Not Present" when you go to
Control Panel - Phone and Modem Options - Modems.
NOTE: This is ALL ABOUT A MODEM THAT ALREADY WORKS, HAS BEEN
TESTED, YOU -KNOW- it is fine, it's JUST THAT now and then XP
will say it's "not present" but if you go to ADD NEW HARDWARE
and let it scan, cancel it, do it again, cancel and then find
XP has "miraculously" found your modem again; then continue on
reading this solution.
(If your modem NEVER WORKED, HASN'T EVER BEEN INSTALLED,
DOESN'T EVER GET FOUND BY XP: then this is NOT NOT NOT your
solution.)
The solutions CAN BE:
1. Uninstall and re-install modem drivers.
2. Get updated modem drivers.
3. Make sure modem is turned on.
HOWEVER, most of these won't work and the next day, week,
hour; you will find that Winfax or MS FAX isn't working
because the "Device" is "NOT PRESENT".
STUPID RETARDED DUMB STINKING XP!! - WHAM WHAM! And MS
KNOWS ABOUT THIS BUG TOO!! Have they fixed it yet?!?!?!?
NOOOOOOOOOOOOOO! MAGGOT SUCKING SNOTS! - Okies, I feel
better!
THE SOLUTION IS AS FOLLOWS:
1.
Microsoft has a tool called "Device Console" that you can use
in a batch file to "find" the modem and "wake XP up to it".
FOUND AT:
http://support.microsoft.com/default.aspx?scid=kb;en-us%
3b311272
(Watch the wrap on that address, it should all be one line)
GO GET IT! AND PAY ATTENTION: THE PAGE HAS INFO ABOUT USING
IT. YOU CAN READ ON HERE BUT YOU ALSO MIGHT WANT TO SAVE THAT
PAGE!
What you will download from MS at the above address is a self-
expanding ZIP FILE that has devcon.exe for 32-bit (in the i386
folder and what 99.9999 percent of us need) AND one for 64-bit
(in the ia64 and if you need that then have at it you speed /
power hungry varmint you!).
2.
I extracted, as I said, the 32-bit devcon.exe (found in the
i386 folder) and I put it in C:\Windows\Command.
3.
Make sure your modem is on, connected, you know, how it ALWAYS
IS even when XP says it isn't there sometimes.
Then get to a command prompt and typed in:
devcon rescan
That command makes it find your modem and makes sure it's
listed in Control Panel - Phone and Modem Options - Modems.
Do NOT NOT NOT go any further unless, at this point, your
modem is listed under Modems as attached to a com port. If you
have to, use "devcon rescan" again.
4.
THEN I typed in the following:
devcon find * >C:\test.txt
That command has devcon scan my system, and put whatever
devices it found in a text file on C:\ called "test.txt".
Now I went and opened test.txt up with notepad and I found the
"listing" for my modem. It looked liked this:
SERENUM\USR3020\1&3509B83&0&0000: U.S. Robotics 56K Voice Pro
EXT PnP
It was in the middle of a bunch of goo, but if you know what
modem you have you can find it in there somewhere.
NEXT I found a unique part of it. I found a part that I could
"scan for". I used the "USR3020" part.
What do I mean; "I used the "USR3020" part"?
Well, let's go on to number 5........
5.
I created a batch file to scan my system, put the scan in a
file, then use FIND to scan the file for the USR3020 part, and
if it is NOT THERE (meaning the modem disappeared again thanks
to XP); then devcon puts it back in there and tests again to
make sure.
THE BATCH FILE I USE FOR OUR MODEM AND THAT WE RUN EVERY 4
HOURS IS:
(Use Task Scheduler to run every 4 hours - it runs VERY FAST)
------------Begin Batch
:MODEMSCN
rem FIND.EXE will give errorlevel of 0 when match is found
rem and a 1 when no match is found.
devcon find * >E:\TEMP\DEVCON.TXT
C:\WINDOWS\SYSTEM32\FIND.EXE "USR3020" E:\TEMP\DEVCON.TXT
IF ERRORLEVEL 1 GOTO RESCAN
ERASE E:\TEMP\DEVCON.TXT
GOTO END
:RESCAN
devcon rescan
ERASE E:\TEMP\DEVCON.TXT
GOTO MODEMSCN
:END
------------End Batch
(Did you see where I used the "USR3020" part?)
SO FINALLY IN SHORT: You get devcon from MS, you use it to
scan your system while your modem is working so you can find
out what your modem information is and find some uniquee part
of it (like mine was that unique "USR3020" part) and then you
use that info in a batch file to check now and then and see if
XP has "lost" your modem and if it has; then you use devcon to
SLAP XP IN THE FACE and tell it to put the dang modem BACK!
SIMPLE!!
Okies, it SOUNDS really complicated, but I tried to make it
simple for you.
ALSO SOME TIPS:
A. If you never use your modem but say in the morning; then
set up the batch file to run at 9am once a day and be done
with it.
OR
B. If you only use your modem once in a while / blue moon;
Create the batch file, make a shortcut to it, and hit the
shortcut / run the batch only before you're fixing to use the
modem for faxing or whatever.
C. If you use your modem tons and you want to check it's
availability every few hours then use the Task Scheduler built
into XP. It's wonderful. You can set it to run between xam and
ypm, every Z hours.
BUT IF YOU DO; then make sure you set it to run NO MORE
THAN 1 minute (it's a REALLY FAST PROGRAM so it only needs a
few secs) because if your modem really IS broken, or turned
off; the batch file above will loop forEVER.
I know there is a way to tell a batch file to "go through
a loop only so many times" but I don't know how. If anyone out
there does and wants to pipe up: FEEL FREE!!
This is my best for y'all, hope it helps someone.
AND REMEMBER TO ALWAYS SAY *-THANK YOU VERY MUCH-* to the
EXCELLENT AND WONDERFUL CRITTER, KELLY, WHO *-ALWAYS-* HELPS
OUT HERE!!
Peeps like me pipe up once in a while; SHE IS ALWAYS HERE
HELPING YOU PEEPS OUT!! Be NICE to her, say prayers for her,
buy her CARS and FUR COATS and thingies like that!
Okies, AT LEAST say THANKS to her once in a while!