I'm having issues with the command line options of MBAM version 1.38. They do not seem to work for me, or more likely, I don't understand how they are supposed to work. I am running Windows XP sp3 in a VMWare Workstation v6.5.2 virtual machine. I'm am trying to create a batch file (.bat) that will run Mbam.exe in silent mode, and perform a full scan and then put the log file in c:\temp. Here is mybatch file...
@echo off
cls
echo.
echo Scan in progress...
C:\Progra~1\Malwar~1\mbam.exe /fullauto /runupdate /fullscan /logtofolder c:\temp
If Errorlevel 700 echo Error occurred using the command line. Parameters may be incorrect.
If Errorlevel 701 echo The database was empty. Please reinstall the application.
If Errorlevel 702 echo Error occurred expanding variables. Contact support.
:
:
rem I Cut out the other error tests for this message
:
:
If Errorlevel 339 echo Component 'comctl32.ocx' not correctly registered echo file is missing or invalid.
echo.
echo Scan complete!
echo.
pause
The program seems to run for about 2 to 3 minutes and finishes, but a full scan on this system - using the GUI - takes 8 minutes. So I'm assuming that when I run it from the command line, it's really running a Quick Scan. Also, there is no log file to be found anywhere on the hard drive when run from the command line. I added all the listed error codes to the batch file to see if they could tell me anything, but I get no errors. What am I doing wrong?
Also, if it does find malware, how do I know what becomes of it? Are there other error codes that can be used to find what the scan did with malware it finds? Thanks!
#1
Posted 19 June 2009 - 04:38 PM
#2
Posted 19 June 2009 - 06:46 PM
Unfortunately MBAM does not allow multiple command lines at the same time except for a few switches.
So it reads your first switch and then ignores the other switches.
So it reads your first switch and then ignores the other switches.
#3
Posted 19 June 2009 - 07:07 PM
First of all, we do not handle ErrorLevels (yet). We actually just started developing code for that. Secondly, error 339 will not be reported because the process terminates unexpectedly.
#4
Posted 19 June 2009 - 07:28 PM
RubbeR DuckY, on Jun 19 2009, 08:07 PM, said:
First of all, we do not handle ErrorLevels (yet). We actually just started developing code for that. Secondly, error 339 will not be reported because the process terminates unexpectedly.
Thanks for the information on errorlevels. Is it possible to perform a full scan in silent mode? If so, what would be the command?
#5
Posted 19 June 2009 - 08:02 PM
You can use /fullscan or /fullscanterminate. Other command line parameters (for corporate use) are available upon purchase.
#6
Posted 03 May 2010 - 02:56 PM
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users
Sign In
Create Account

Back to top









