• %System%\vamsoft.exe [ 115,353 Bytes ]
• %System%\vbsdfe2.dll
• %System%\vbsdfe0.dll
• %System%\amvo0.dll
• %System%\amvo2.dll
• %System%\ckvo0.dll
• %System%\ckvo2.dll
• %System%\jwedsfdo0.dll
• %System%\jwedsfdo2.dll
• %System%\kavo0.dll
• %System%\kavo2.dll
  
  • If you have any of these files in running process from task manger, end the process before removal.
  • Note: if task manager is disabled, Download the following file, Click to Download - Enable Registry.reg
  • Open it with Regedit.exe [%system32\regedit.exe], then it Confirms Add to registry Yes or No, Confirm Yes, then click Ok.
    

• Note: If the registry editor fails to open the threat may have modified the registry to prevent access to the registry editor.
  • Download and run this UnHookExec.inf, and then continue with the removal.
  • Save it to your Windows desktop. Do not run it at this time, download it only.
  • After booting into the Safe Mode or VGA Mode
  • Right-click the UnHookExec.inf file and click Install. [This is a small file. It does not display any notice or boxes when you run it.]

Astrum Antivirus Pro is rogue antispyware program, sucessor of well known VirusTrigger and AntivirusTrigger. Astrum Antivirus Pro is usually downloaded and installed with a help of Trojan Horses, misleading websites, fake online spyware scaners, browser security holes. Once Astrum Antivirus Pro is installed it will generate fake Widows Security Center alerts and pop-ups stating that computer is infected with various spyware and malware. Also Astrum Antivirus Pro can perform system scan and list a lot of threats detected on PC. Moreover it may mark legitimate files as dangerous parasites to scare computer users and trick them into purchasing full version.
We strongly recommend you to remove Astrum Antivirus Pro as soon as possible manually or using -

Type: Rogue Anti-Spyware
Malware Author: Unknown
Threat Level: Critical
Screenshot:


How to remove Astrum Antivirus Pro manually:
It's possible to remove Astrum Antivirus Pro manually , but you have to be very experienced in dealing with registry entries, program files and .dll files.

The files to be deleted:

%UserProfile%c:\Program Files\Astrumsoftware
%UserProfile%c:\Program Files\Astrumsoftware\Astrum.exe
%UserProfile%c:\Program Files\Astrumsoftware\uninst.exe
%UserProfile%%UserProfile%\Application Data\Microsoft\Internet Explorer\Quick Launch\Astrum Antivirus Pro 3.6.lnk
%UserProfile%%UserProfile%\Desktop\Astrum Antivirus Pro 3.6.lnk
%UserProfile%%UserProfile%\Start Menu\Astrum Antivirus Pro 3.6.lnk
%UserProfile%%UserProfile%\Start Menu\Programs\Astrum Antivirus Pro 3.6
%UserProfile%%UserProfile%\Start Menu\Programs\Astrum Antivirus Pro 3.6\Astrum Antivirus Pro 3.6.lnk

Remove registry entries:

%UserProfile%HKEY_CURRENT_USER\Software\Astrumsoft
%UserProfile%HKEY_CLASSES_ROOT\CLSID\{29E762AD-1B6F-3CB6-7F71-866F3E78180B}
%UserProfile%HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\Astrumsoft
%UserProfile%HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Astrumsoft

Please be careful because manual removal of Astrum Antivirus Pro may seriously damage operational system and sensitive data. Also there is a big possibility of incomplete removal, because some files could be hidden and program could re-install itself after you delete files and registry entries. -="-?item=11719-8&.&linkid=mraastap">-.

Windows Vista is an obvious flop. With all the praises that most people gave it when it first hit the market, Microsoft now finds itself trying to win back its customers no thanks to the defects and problems that this erring operating system has caused. And the savior’s name? Windows 7.

Expected to be shown at CES this coming January, rumor has it that Windows 7 will come out in three versions, namely:

• Windows Vista Home Premium Edition => Windows 7 Home Premium Edition
• Windows Vista Business Edition => Windows 7 Professional Edition
• Windows Vista Ultimate Edition => Windows 7 Ultimate Edition

Why you may ask? For one, operating systems cater to all levels. But one thing noticeably missing is the very basic version of the OS. We saw that in Windows Vista but it seems that it only caused a lot of problems rather than results. In fact, don’t be surprised if you see an upgrade version which allows current Windows XP users to upgrade straight to Windows 7 to avoid the issues with Vista.

But that remains to be seen. Microsoft has a lot of work to do to cover up the mess that Windows Vista caused. Many users reverted to Windows XP but do bear in mind that Windows XP is no longer available in the market.

Windows 7 has been programmed to use lesser resources. This should be welcome news to all Windows OS users. This was one of the issues with Windows Vista and apparently Microsoft has learned its lesson. Will Windows 7 click? Expect reviews and feedbacks once it hits the market in 2009.

Source

The Red Hat Package Manager (RPM) allows the easy installation and removal of software packages—typically, precompiled software. A package consists of an archive of files and other metadata.

It is wonderfully easy to use, and several graphical interfaces have been built around it to make it even easier. Several Linux distributions (distros) and various third parties use this tool to distribute and package their software. In fact, almost all of the software mentioned in this book is available in RPM form. The reason you’ll go through the process of compiling software yourself in other chapters is so that you can customize the software to your system, as such customizations might not be readily possible in an RPM.

An RPM file is a package that contains files needed for the software to function correctly. These files can be configuration files, binaries, and even pre- and postscripts to run while installing the software. However, adhering to the open source principle, the various commercial and noncommercial Linux distros are obliged to make the source code for most GNU binaries available. (Those who don’t make it available by default are obliged to give it to you if you ask for it.) Some Linux vendors stick to this principle more than others. Several Linux vendors, therefore, make the source code for their binaries available in RPM form. For instance, Fedora and SuSE also make source code available as an RPM, and it is becoming increasingly common to download and compile source code in this fashion.

The RPM tool performs the installation and uninstallation of RPMs. The tool also maintains a central database of what RPMs you have installed, where they are installed, when they were installed, and other information about the package.

In general, software that comes in the form of an RPM is less work to install and maintain than software that needs to be compiled. The trade-off is that by using an RPM, you accept the default parameters supplied in the RPM. In most cases, these defaults are acceptable. However, if you need to be more intimately aware of what is going on with a piece of software, you may find that by compiling the source yourself, you will learn more about what software components and options exist and how they work together.

Assuming that all you want to do is install a simple package, RPM is perfect. There are several great resources for RPM packages, including the following:
• http://rpm.pbone.net
• http://ftp.redhat.com
• http://mirrors.kernel.org
• http://freshrpms.net

Of course, if you are interested in more details about RPM itself, you can visit the RPM web site at www.rpm.org. RPM comes with Fedora, OpenSuSE, Mandrake, and countless other Red Hat derivatives, and, most surprising of all, the Red Hat version of Linux! If you aren’t sure if RPM comes with your distribution, check with your vendor.

The primary functions of the RPM are
• Querying, installing, and uninstalling software
• Maintaining a database that stores various items of information about the packages
• Packaging other software into an RPM form

Frequently used RPM options
--install. This installs a new package.

--upgrade. This upgrades or installs the package currently installed to a newer version.

--erase. Removes or erases an installed package.

--query. This is the option used for querying.

--force. This is the sledgehammer of installation. Typically, you use it when you’re knowingly installing an odd or unusual configuration and RPM’s safeguards are trying to keep you from doing so. The –force option tells RPM to forego any sanity checks and just do it, even if it thinks you’re trying to fit a square peg into a round hole. Be careful with this option.

-h. Prints hash marks to indicate progress during an installation. Use with the -v option for a pretty display.

--percent. Prints the percentage completed to indicate progress. It is handy if you’re running RPM from another program, such as a Perl script, and you want to know the status of the install.
-nodeps. If RPM is complaining about missing dependency files, but you want the installation to happen anyway, passing this option at the command line will cause RPM to not perform any dependency checks.

-q. Queries the RPM system for information.

--test. This option does not perform a real installation; it just checks to see whether an installation would succeed. If it anticipates problems, it displays what they’ll be.

-V. Verifies RPMs or files on the system.

-v. Tells RPM to be verbose about its actions.

Source of Information : McGraw Hill Osborne Media Linux Administration A Beginners Guide Fifth Edition