 |
Modemsite's Forum56 - The Modem Board Main | profile | register | search | help | Ad-free Login |
| Forums | USR | Want to override some USR V.90 feature so can hibernate | Watch |
| Author | Topic |
| kjavds Tl Posts: 53 USA | Posted - 3/26/2002 7:29:19 AM     I installed a PCI card data/fax/voice WinModem (V.90 56k) by US Robotics, model 3594, and ever since then my System refuses to allow hibernation. I attribute this to the additional features which this modem may have, such as auto-answer and speakerphone. When I try to force hibernation with software, I get something like "A program has attempted to change the system power state but it was vetoed by another system component". This would be OK if I knew of a way to get the system to SHUT down after so long idle, but I don't see that possibility under Windows ME. Correct me if I'm wrong. [I experimented with the shareware utility SwitchOff but it is not operating correctly, yet]. If this were a Macintosh I would FIND a way to get INTO the modem script and DISABLE auto-answer and PERHAPS that would correct the problem. But I don't know where to begin with .INF files or .vxd files or WHATEVER is in use here! Ati3 gives "US Robotics Modem Win Int RS Rev 4.11.015" The drivers I installed with this unit came on a floppy and all the files are circa August 2000. When I ask Windows ME to search for a better driver there is no better on my System. I do not believe that looking for a newer driver is the solution, though I could be wrong. I would think that ALL the latest drivers would also force the system to stay up for auto-answer. Anyone have any ideas? Thank you!!
|
| charles Tl Posts: 5879 USA | Posted - 3/26/2002 9:13:20 AM http://www.usr.com/support/s-modem/s-modem-oem-downloads.asp#3594 The driver above is showing Ver version 4.11.015.8 The inf file is showing S0=0 which auto-answer is off by default.Post a modem log please.Might check if there is any software like fax..ect that might have changed the default setting.Click ctrl,alt,delete and see what is running in the background. |
| charles Tl Posts: 5879 USA | Posted - 3/26/2002 9:26:33 AM You might try going to the device manager,hight the modem,properties,and put a check in disable in this hardware profile.Try hibernation again. |
| kjavds Tl Posts: 53 USA | Posted - 3/26/2002 3:28:53 PM Thank you for your kind replies! First off, if I disable that modem from the configuration, hibernation is STILL barred until I ALSO uncheck the box marked "Exists in all configurations"! Ok?? Secondly, no suspicious background processes are running and that is not the problem because I can hibernate while my OTHER (Conexant generic) modem is the only one enabled as I suspected. Here is the modem log and yes S0=0! The S10=250 was intentional and my doing. It's for my Call-Wait Box. 03-26-2002 18:06:10.03 - U.S. Robotics 56K Voice Win Int in use. That is all of the connection portion of the log. -Ken Edited by - kjavds on 3/28/02 5:01:43 AM |
| kjavds Tl Posts: 53 USA | Posted - 3/26/2002 3:38:49 PM See my post under chit chat for description of GREAT difficulties I had that day posting the above (but all is working AOK now for some reason). -Ken Edited by - kjavds on 3/28/02 5:03:32 AM |
| Bob Starnes Tl Posts: 4360 USA | Posted - 3/26/2002 10:19:48 PM It's quite simple to just copy and paste a portion of the modem log rather that selecting the entire text.
|
| kjavds Tl Posts: 53 USA | Posted - 3/28/2002 5:20:30 AM Just on the off chance that the revision 08 part of the driver was critical, I went to the site Charles mentioned in his post and downloaded the driver that it says was for device #3594A and expanded it to a floppy as instructed. Now, EVEN THOUGH the download was specifically named "3594A_Me_082200" so SHOULD be for Windows Millenium, it APPEARRED to be packed with a driver for Windows98! And when I told my system to look on that floppy for a better driver, it said my existing one was best, and the one it found on the floppy specifically showed "Win 98" in the title! AND, it was revision 03! Howdya like them apples?!!
|
| Troubled_user Tl Posts: 263 USA | Posted - 3/28/2002 8:59:23 PM Factoring in that this is a USR product, I'm not surprised |
| charles Tl Posts: 5879 USA | Posted - 3/29/2002 1:32:37 AM ; 98WdmDva.inf needs to be included for installation of WDM Parent Device 08/22/2000, 4.11.015.3 I think the Me drivers need this file to install this is why the 98 is in the drivers.Also check the driver date of the drivers you have install now.Try removeing the S10=250 in modem string reboot and try hibernation again. NOTE: If you set S10 = 255, the modem will not hang up when carrier is lost. Dropping DTR hangs up the modem. This possibility is country-dependent. I know you have 250 but maybe the modem is not hanging up.
Edited by - charles on 3/29/02 2:04:55 AM |
| kjavds Tl Posts: 53 USA | Posted - 3/29/2002 2:51:58 PM Thanks again Charles, as that sounds like sage advice. Now, I had been holding off installing that downloaded driver because 1) it was dated the SAME as my existing driver, 2) it clearly had "for Win 98" in its TITLE even though the download was just-as-CLEARLY labelled for WinME, 3) Windows insisted that my already-installed driver was likely a "closer match", 4) I wasn't sure I could ever revert to my existing driver, 5) the new downloaded driver was marked only Rev.3 (ie 4.11.015.3) instead of Rev.8. But since the new d/l driver included that 98wdmdva (both a Security Catalog AND a .INF) and no such files were to found elsewhere on my system, I thought I would painstakingly make a copy of ALL my existing driver files (total 21 files) for safe revert and go ahead and FORCE installation. I have now done that.. and the 98wdmdva files WERE NOT EVEN INSTALLED ANYWHERE, but MAY hav been referred to during installation. Soon I will be able to post here whether any of this had any beneficial results, or even if the modem now still works (I am connecting here now w/another). Thank you for sticking with this dilemma. Pls be patient.
|
| kjavds Tl Posts: 53 USA | Posted - 3/29/2002 3:41:55 PM OK, it still doesn't allow hibernate. But just as soon as I disable it in the hardware config AND uncheck the "Exists in all profiles" box AND reboot, hibernation capability RESUMES! It's just as I first stated. (Help!) As for whether that new driver is even functional, I didn't bother crawling behind my computer to plug the phone into it to test, since the hibernate problem persists. I will restore my old driver if and when I again want use of that modem. Thanks again for sticking with this. You'll notice I cleaned up my other posts some. Do post here again if more information surfaces!!!!
|
| kjavds Tl Posts: 53 USA | Posted - 3/29/2002 5:27:42 PM If nothing else this makes for a captivating probe! CHARLES: What you said about removing the S10=250... naturally, when I went to the alternate (downloaded) driver, that EXTRA Setting was not yet explicitly included, and as I reported, still no success. That answers that. A funny occurrence! When I tried to revert to my prior driver by using the floppy I had earlier been supplied (duh! yeah I was stupid thinking I shoud SAVE those files!?)... well when I tried to Update (back) to that original driver that came with the device, Windows warned me that THAT driver was not specifically formulated for this exact device! ..and that I should stick with what I have! GO FIGURE!!! Since I haven't achieved my goal with EITHER driver, it's academic what I do next. Oh well!
|
| kjavds Tl Posts: 53 USA | Posted - 3/30/2002 2:55:40 AM It occurs to me now that MAYBE this modem is not even the model 3594 that I presumed it to be. Here soon I'll dig it out of the chassis and get my eyeglasses on and read the fine print labels on the card itself. I had only presumed it to be the 3594 because that was the label on the driver floppy that the supplier 'tossed in' with the item. This modem only cost $25. Am I right in surmising that is cheap for a USR Voice/Fax/Data? Maybe this is from a 'lot' that had a problem and was dumped onto the market cheap. I bought it thru 'BilSystem.com'. All conjecture!
|
| kjavds Tl Posts: 53 USA | Posted - 3/30/2002 3:26:57 AM Confirmed now -- it's definitely a model 3594A
|
| charles Tl Posts: 5879 USA | Posted - 3/30/2002 10:11:33 AM If you need to determine which device prevents your system (WinME) from hibernation support look for file nohiber.txt in the Windows directory. In the dialog that shows why it failed, a particular device will be listed. Details about the failure can be found in the Susfail.txt log file located in the Windows directory. When you put your computer in Hibernate mode, Windows Millennium Edition (Me) writes a file called Vmmhiber.w9x to the hard disk drive. The Vmmhiber.w9x file contains information on current system processes and information in memory at the time the system is instructed to hibernate. This file is located at X:\%WinDir%\ (where X: is the drive that contains the Windows directory) and is a hidden file. I think that the modem drivers on your USR modem are not hibernation compatible. |
| kjavds Tl Posts: 53 USA | Posted - 3/30/2002 2:51:21 PM Unbelievable! The problem is gone! Unbelievable! Star Office 5.2 is this incredble SUPER SUBSYSTEM (oxymoron there) from Sun Microsystems that's free for download (77MB) or $40 for the retail package. It does EVERYTHING! (Word, Image, Drawing, Spread, DB, Browser, email, FAX, FTP, News, calendar, navigation etc). Well it comes with the ability to integrate modules from the System TRAY into it's OWN taskbar and run full-screen say, and look like a complete GUI in and of itself. Yet it also comes with a little utility, SOINTGR.EXE which can be used to enable or disable this feature for maybe troubleshooting, ie if conflicts arise. Now I didn't suspect this as being the culprit (duh), yet I had OCCASION to disable it for troubleshooting a microphone problem (but that problem turned out to be something ELSE), so I reenabled Star Office integration with its little utilty. Later I came along and reenabled the USR to evoke and then look for this silly nohiber.txt file (which otherwise had since been cycled out I guess.. but susfail.txt was present). This APPARENTLY switched the ORDER in which these background tasks were loaded at startup -- SOINTGR and 3C1807PD ... AND THAT DID THE TRICK! EVERYTHING IS GROOVY! I'M USING THE USR Modem TO POST HERE, STAR OFFICE INTEGRATION IS WELL, THE MIKE WORKS.. AND HIBERNATION IS SUPPORTED! ahA!
|
Click Here To Close Thread, Administrators & Moderators Only.
Show All Forums |