2010-09-23, 04:21 PM
^ I don't think that should be related if all you did was uncheck the "Allow the computer to turn off the device to save power" thing. But if it had to be connected somehow, it'd probably be some script, which I wouldn't know what it did anyways.
At any rate, if it really WAS connected to that DNS failure, checking back on the box should make it go away. (but that's probably not the route you want to go, since Eosian is right; it's a dumb thing to do)
Wait, how is that different from just inputting "ping -t 192.168.X.X" into cmd without a .bat file?
(sorry I don't mean to thread jack or anything)
At any rate, if it really WAS connected to that DNS failure, checking back on the box should make it go away. (but that's probably not the route you want to go, since Eosian is right; it's a dumb thing to do)
Cancambo Wrote:Figure out the router's IP address. I am not sure how you do this for W7, but on XP you go to Run and type in cmd. Then in the command prompt, type 'ipconfig' and your router's IP should be the same as the default gateway. It should be 192.168.X.X. Then create a the .bat file by opening notepad and put in "ping -t 192.168.X.X" (replace the X's, of course). Then instead of saving it as a .txt file, save it as a .bat file. Double clicking on this .bat will then start the pinger that will constantly ping your router. This creates a constant connection between your PC and your router, and it uses of very minute amoutns of memory to do so, at least that's how I understand it.
Wait, how is that different from just inputting "ping -t 192.168.X.X" into cmd without a .bat file?
(sorry I don't mean to thread jack or anything)