BitDefender Pro 7.2 acting up

entropyentropy Yah-Der-Hey (Wisconsin)
edited August 2004 in Science & Tech
Sometimes when I leave my comp for awhile, when I come back, the Management Console is stuck in they SysTray, and the only thing i can do it close it and restart the program. I've never witnessed it getting itself stuck as of yet. However, when I try to do a manual scan, it seems like it locks up. Gets a few files in then just ... stops scanning apparently. The Settings button in the Virus Scan menu just shows me a blank dialogue box. Folks over at Softwin tell me to run a program called sysdump.exe, but it seems to be giving a LOT of extravagant information (IP, traffic, network details, programs, reg keys etc) and it locks up when scanning for Roxio 7 due to the fact that I have removed a few parts of the program that I didn't want. So has anyone else had these problems? If so, how'd you fix it? Thanks in advance

Comments

  • Straight_ManStraight_Man Geeky, in my own way Naples, FL Icrontian
    edited August 2004
    Roxio can do strange things to a system, and can use .dll files for multiple modules. So, if you pull .dll files when you pull modules, and have Roxio stuff in systray to make it quick load, and it is part broken, you can get Windows locks. I hate to say this, but try uninstalling ROXIO. If that works, then just pull the .exe calls fro what you do not want to load and use, leave the .dll files there. I've also seen ROXIO replace system files.... In the underlayers of XP there is a program called sfc.exe. Stick your XP CD in, open a command console, run it-- it will stick the .dlls back in a dllcache folder, and XP can recover them as needed.

    Probably along the way a .dll ot two or three got replaced, mashed, erased, etc. I hate Roxio for that sticking thier custom .dlls in system directory. Most real good apps, if there is a system .dll with same name, will store thier custom apps in thier PROGRAM INSTALL directory. Then the system can use its .dlls and the app can call its .dlls.

    When cleaning a box or manually uninstalling things, unless you know the .dll deps, leave the .dlls you are not sure of, ok??? Some of the ones the uninstaller "thinks" are good to go might NOT be good to go-- they might need to be kept. Second, when I see semi-random flakes, I use Registry Mechanic 3.0 (paid for) to clean up orphan registry entries left by manual file Wiping uninstalls.

    Clean up orphan calls and run sfc.exe from a command prompt to get base system files made available again for XP's autorecovery stuff, then try a registry reboot. Then uninstall what you most recently installed, or roll back to a restore point before the install. Once the system stops flaking, then roll back forward by reinstalling your apps, and if you get flakes, look for updates. BitDefender has some recently updated versions for Windows, so does Roxio.com for Roxio stuff.

    In short form explanation, sfc.exe does this:

    It looks at the OS install CD, reads sig info. Then it reads info from files, and compares. If a .dll gets corrupted( seen by bad signature and\or checksum compare), it gets put back from original OS install CD. Its a manually started "semi-automatic" way to roll back just your system files. When it is done, it will just "disappear." Keep hitting retry if it yells, unless it still locks after ten repeats without moving forward in progress bar, then if you get that kind of repeat hang look at CD and do some scratch or thumbprint removal if needed. Windows 98 called it the System File Checker-- AFAIK, XP calls it the System Verification Tool in the System Information applet's tools menu, but it still does call sfc.exe. So I call it the System File Checker even today.
Sign In or Register to comment.