Jump to content
IObit Forum
Top Free Driver Updater Tools Best 25 PC Optimization Software Best 22 Antimalware Best 22 Uninstaller Software IObit Coupons & Discount Offers PC Optimizer Mac Boost Advice IObit Coupons A Good Utility Program From IObit IObit Promo Codes IObit Coupon Codes IObit Coupons and Deals FAQs Driver Booster Pro Review

JustDave

Members
  • Posts

    362
  • Joined

Posts posted by JustDave

  1. Ted - Ha! I tell the same joke about Alabama. (My family's from there so it's okay if I tell Alabama jokes. Actually, I have some relatives that prove many of the jokes aren't really too far-fetched at all. :razz: )

  2. I like escalators because an escalator can never break, it can only become stairs. There would never be an "Escalator Temporarily Out of Order" sign, only an "Escalator Temporarily Stairs" sign.

    -Mitch Hedberg

  3. The old prospector came out of his mine to see a cowboy sitting on the porch of his shack next to his dog.

     

    Prospector: Hey now! What're you doing there!

     

    Cowboy: Just talking to your dog.

     

    Prospector: : "Ha. That dog don't talk."

     

    Cowboy: "Hey dog, how's it going?"

     

    Dog: "Doin' all right."

     

    Prospector: (Look of shock!)

     

    Cowboy: "Is this prospector your owner?", pointing to the Prospector.

     

    Dog: "Yep."

     

    Cowboy: "How's he treating you?"

     

    Dog: "Pretty good. I guard the place and feeds me real good and takes me to the lake once a week to play."

     

    Prospector: (Dumbfounded)

     

    Cowboy: "Mind if I talk to your horse?"

     

    Prospector: "Uhhh...the horse don't talk?"

     

    Cowboy: "Hey horse, how's it going?"

     

    Horse: "It's cool."

     

    Prospector: (Jaw hits the dirt!)

     

    Cowboy: "Is this your owner?", pointing to the prospector.

     

    Horse: "Yep."

     

    Cowboy: "How's he treating you?"

     

    Horse: "Darned well, thanks for asking. I work real hard, but he brushes me down often and keeps me in a lean-to to protect me from the weather."

     

    Prospector: (Look of total amazement)

     

    Cowboy: "Mind if I talk to your sheep?"

     

    Prospector: "Hell yes I mind! That damned sheep lies!"

  4. A cowboy walks into a bar and orders a whiskey. When the bartender delivers the drink, the cowboy looks around and said, "Well shoot. This place is empty. Where is everybody?"

     

    The bartender replies, "They've gone to the hanging."

     

    "Hanging? Who are they hanging?" asks the cowboy.

     

    "Brown Paper Pete," the bartender says.

     

    "What kind of a name is that?" the cowboy asks.

     

    "Well," says the bartender, "he wears a brown paper hat,

    brown paper shirt, brown paper trousers, brown paper chaps, and brown paper

    boots."

     

    "I have to admit, that's mighty peculiar." muses the cowboy. "What are they hanging him for?"

     

    "Rustling," says the bartender.

  5. IObit Security 360

     

    OS:Windows XP

    Version:0.4.0.20

    Define Version:1146

    Time Elapsed:08/29/2009 10:48:40 PM

    Objects Scanned:87834

    Threats Found:7

     

    |Name|Type|Description|ID|

    Worm.Dropper, File, C:\WINDOWS\system32\WanPacket.dll, 9-100077

    Backdoor.SpyBouncer, File, C:\WINDOWS\system32\wpcap.dll, 9-78159

    Worm.Dropper, File, E:\program files\WMR11\WanPacket.dll, 9-100077

    Trojan.Dldr, File, E:\program files\Moyea\FLV Downloader\SockHook.dll, 12-1035

    Trojan.Dldr, File, E:\program files\Wondershare\Video to DVD Burner\WS_DVDBurner.dll, 12-1035

    Trojan.Drop.Agent, File, E:\program files\Kodak\Printer\Center\KodakSvc.exe, 12-551

    Dropper.Autoit.PM, File, H:\zUSB Sync Folders\TrueCrypt Vol T\MY PROGRAMS\AutoIt v3\Aut2Exe\AutoItSC.bin, 12-1945

     

    VirusTotal shows all these as being clean.

  6. Another neat little app (for recovery, not prevention) is UnHackMe. My son ended up with a rootkit and an assortment of trojans when his friend's girlfriend "clicked something stupid." I tried all the standard anti-virus and anti-malware apps, online scanners, free rootkit scanners, etc., and nothing would touch it. Likely as not the machine would just freeze. I finally stumbled onto UnHackMe, and it found the rootkit, (hacker defender) cleaned it, then cleaned the trojans. I was so impressed that I bought the roaming version. Free trial.

     

    http://www.greatis.com/unhackme/

  7. Hi solbjerg,

     

    I saw your title, "Dishwashing," and expected some sort of metaphorical essay on the value of the proper rinsing, loading and washing of PCs. Imagine my surprise. :lol:

     

    (I'm buying a new dishwasher myself in the next couple of months so I'll have to come back to your post for a reference.) :wink:

     

     

    Dave

  8. Good idea enoskype. I just upgraded to PD2008 and I never thought to test it against AWC2 Pro 2.7. Sheesh. So I figured I'd go ahead and be the guinea pig for the group.

     

    I removed the PD2008 registry entries from the ignore file, and then ran AWC2 Pro 2.7 through a scan/repair cycle. PD2008 lived through it. I've run several scan/repair cycles since then with no apparent effect on PD2008. Looks like a "fix" was indeed included in the latest release. Pretty cool. Thanks for the suggestion.

  9. Hey! I've been stickied! I've never been stickied before...I'm giddy. :-P Guess I'll have to get on the stick and post a revision to include MacPeter's use of a sand-boxed environment for testing.

     

    Thanks MacPeter. I'm trying to get up to speed with SandBoxie...pretty cool.

  10. Hey! I've been stickied! I've never been stickied before...I'm giddy. :-P Guess I'll have to get on the stick and post a revision to include MacPeter's use of a sand-boxed environment for testing.

     

    Thanks MacPeter. I'm trying to get up to speed with SandBoxie...pretty cool.

  11. If you don't find a an obvious culprit in your troubleshooting take enoskype's advice; Dial-a-fix is a pretty nifty little tool. It solved a Windows update problem for me a couple of months ago, and I fixed a friend's machine with it last week. Basically it re-installs standard Windows apps, re-registers dlls, flushes caches, etc. I was wary about it at first, but I've come to trust it.

  12. Tros - You might want to check the dependencies for the system restore service as well to be sure something else isn't turned off. Have you tried restore in safe mode? Press F8 during the boot process, select safe mode, then select restore when given the option.

     

    Windows update relies on the background intelligent transfer service...see if that's on.

     

    Also...have a look at your event viewer. Start->Run->"eventvwr.msc"->OK. Look for red or yellow splats in the System Tools/Event Viewer/System log.

     

    For what it's worth, I'm with solbjerg in that I don't think AWC actually caused all your problems. I personally have AWC Pro running on three machines, and I've recommended it to ten or twelve people and they installed with with nary a hiccup. AWC did appear to cause some problems on my son's machine, but when I dug into the problem I found he'd made some questionable registry tweaks from one of of those "1337" game tweaking support sites. Once I got the registry back to a known good state I had no more problems. I always suspected that one or more of the funky tweaks he had made probably conflicted one of the tweaks AWC made...sort of tipped the boat don't you know. Mind you, I don't know that for sure, and I'm not saying you've done the same thing, or that it's all your fault, just that AWC may be tripping on up already existing, just-below-the-surface type problems.

  13. Tros - Regarding the system restore failure...did you check to see if the system restore service is still running? Click Start, then Run. Enter "services.msc" (without the "") and click OK. Scroll down until you see System Restore Service. Its Status should be "Started" and its Startup Type should be "Automatic." What does yours show?

  14. solbjerg, samr & enoskype: Thanks guys. It's just that so many people really don't understand the risk they're taking when they run a beta. People really need to think twice about it and then take precautions.

     

    MacPeter: For what it's worth, I wasn't talking about your specific post. I thought you made reasonable points. If a developer is going to release a beta in order to improve the final product, then that developer must be committed to communicating with and working actively with the community in order to make the whole process bearable. Frankly, with all the major issues with 4.01 I'm surprised Newton, or at least someone from IOBit hasn't been more active. But, just because they don't respond doesn't mean your input is useless; the more data they get the better.

     

    I've run 4.01 a couple of times with no problems, but I'm thinking I'm gonna hold off until we hear more about what's going on.

     

    By the way...how do you like Sandboxie? I've been thinking about trying it but just haven't gotten around to it.

  15. solbjerg, samr & enoskype: Thanks guys. It's just that so many people really don't understand the risk they're taking when they run a beta. People really need to think twice about it and then take precautions.

     

    MacPeter: For what it's worth, I wasn't talking about your specific post. I thought you made reasonable points. If a developer is going to release a beta in order to improve the final product, then that developer must be committed to communicating with and working actively with the community in order to make the whole process bearable. Frankly, with all the major issues with 4.01 I'm surprised Newton, or at least someone from IOBit hasn't been more active. But, just because they don't respond doesn't mean your input is useless; the more data they get the better.

     

    I've run 4.01 a couple of times with no problems, but I'm thinking I'm gonna hold off until we hear more about what's going on.

     

    By the way...how do you like Sandboxie? I've been thinking about trying it but just haven't gotten around to it.

  16. A few posts lately have complained that the latest beta of ISD is buggy and causing problems. Gang, beta releases are, by definition, buggy and unstable. The reason a developer releases a beta app in the first place is to get it out of the lab and onto more PCs, exposing it to real world conditions. Putting the program into the hands of normal people is a guaranteed, surefire way to expose the limitations of, and problems with the software. In return, the developer usually wants to know of all problems encountered so he/she can fix and improve the software. If you choose to run beta software, you’re essentially agreeing to risk your data, your time, and your sanity, in order to assist the developer in testing the software. If you’re willing to take that risk, at least take a few extra steps to protect your system. And yes, I learned these the hard way. :neutral:

     

     

    For registry or operating system cleanup/optimization apps…

    1. Create a system restore point. Often an issue inadvertently raised by a beta app will rear its head immediately as, or just after you run the software; a simple restore may set you right.

     

    2. Do a complete backup of the registry. If a system restore alone doesn’t take care of it, that plus a restoration of the registry usually will.

     

    3. Review the items the software proposes to “cleanup” or “optimize.” If you’re not familiar enough with the registry or operating system to really know what you’re looking at you probably shouldn’t be running a beta program in the first place. Better to find and use a known good, known safe application.

     

    4. Create a restore point and a fresh registry backup every time you make significant changes to your system. Yes, it’s tedious, but so is reinstalling Windows.

     

     

    For HDD maintenance/defrag apps…

    1. Create a system restore point and do a complete backup of the registry. Same rationale as above. Depending on the type of damage a system and/or registry restore might get you back up and running.

     

    2. Backup the drive you’ll be working on. As in create an image of the entire drive. That is, unless you really don’t mind losing everything on the drive.

     

    3. Don’t work on your boot drive until you’re certain the software is safe. If the app goes south on a data drive you can often recover at least some of the content. If it takes your boot drive down you can’t do squat. (Actually, if you backed up your drive per step 2 you can completely recover either your boot or data drives, it's just easier to recover the data drive.)

     

    4. Always run in manual mode until your certain the software is safe. You want to be able to explicitly control what the software is doing and when. You definitely don’t want beta software firing up in the middle of the night and automatically defragging all 4 hard drives.

     

    5. Create a fresh disk image whenever recreating new content is more hassle than making another image. Yes, it’s tedious…

×
×
  • Create New...