Help - Search - Members - Calendar
Full Version: silent Installation motherboard monitor 5.3.6.0
MSFN Forums > Unattended Windows Discussion & Support > Application Installs

   


Google Internet Forums Unattended CD/DVD Guide
ari
My switches for the silent installation are:

..\mbm5360.exe /VERYSILENT /SP-

it works perfectly, but I can't start the program.
After the installation, reboot and start comes one error, see the image below.

Does anybody have another solution?

Thx for Your help.
mmarable
This is caused by the registry entry for the MBM service having the incorrect path located in it. It's a known problem with MBM.

This thread in thier forum has the details:
http://www.livewiredev.com/bbs/showthread....=&threadid=2821

This should fix the problem and you'll be back up and running in no time.
ari
Thx mmarable,

I have repacked the original setup in a *.msi package. The same is the result.
At the start of the program I get the error again.

I will remove the driver installation and the registry entry from the setup now and create the *.msi package once again.
Perhaps I then can execute the installation and the start of the program without errors. sad.gif

QUOTE (Alex van Kaam - MBM Creator @ 11-09-2002 10:17 AM)
- find the file mbmiodrvr.sys on your system and delete it
- open the registry and delete the key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mbmiodrvr
- REBOOT
- install mbm again and select the right startup mode for the driver as explained above
- REBOOT


The program works perfectly after the non silent installation .
edmoncu
about here, in doing a silent install, MBM popped out a window:

Error
the driver didn't load

i also can't start the program.
i wonder how will i be able to have a workaround with this problem?

I am using MBM 5.3.6.6.

@mmarable: it seems the site is down. sad.gif
edmoncu
i suppose, for now, i'll be using an autoit script. rolleyes.gif
edmoncu
anyway, here's my the MBM autoit script i made:
CODE
AutoItSetOption("WinTitleMatchMode", 1)

Run(@HomeDrive&"\Others\MBM5366.exe")
BlockInput(1)
WinWaitActive("Setup - Motherboard Monitor 5")
ControlClick("Setup - Motherboard Monitor 5", "", "&Next >")
ControlClick("Setup - Motherboard Monitor 5", "", "I &accept the agreement")
ControlClick("Setup - Motherboard Monitor 5", "", "&Next >", "", 8)
ControlClick("Setup - Motherboard Monitor 5", "", "&Install")
WinWaitActive("MBM Configuration Wizard")
ControlClick("MBM Configuration Wizard", "", "Cancel")
WinWaitActive("Setup - Motherboard Monitor 5")
ControlClick("Setup - Motherboard Monitor 5", "", "&No, I will restart the computer later")
ControlClick("Setup - Motherboard Monitor 5", "", "&Finish")
BlockInput(0)
Sleep(5000)

This one worked though, but I just dunno if the previous silent installation (the one mentioned above) screwed MBM, as it produced an error everytime i run MBM.

The error I encountered when launching MBM is still:
Error
the driver didn't load
edmoncu
hmm, autoit scripting seems doesn't look feasible with automating mbm installation.

i realized, mbm installation dialogs differs from one machine to another. it was evident that i made the script to work for an epox ep-8rda3+ motherboard. trying the same script on an jetway v266b, the installation came to a halt during the part where i have to select install. i suppose, the installer script had too much "next" button clicks on the epox than the jetway board.

sad.gif
edmoncu
i tried posting here about the situation. i hope they could provide with a workaround.

hmm, seems i wasnt the only one having this problem.
ZoSTeR
The setup runs MBMIO.EXE /s /32 /1 {sys folder} (or other parameters depending on the user selection during setup) from the temp folder.
The file is deleted after that.

I don't think you can recreate that behavior during silent installation without rebuilding the setup.

You could extract that file and run it manually after MBM5 silent installation.

Parameter examples: (32 or 64 bit systems) 0=Automatic 1=System 2=Boot + %systemroot%\system32
I guess newwink.gif
CODE
MBMIO.EXE /s /32 /0 "c:\windows\system32"
MBMIO.EXE /s /32 /1 "c:\windows\system32"
MBMIO.EXE /s /32 /2 "c:\windows\system32"
MBMIO.EXE /s /64 /0 "c:\windows\system32"
MBMIO.EXE /s /64 /1 "c:\windows\system32"
MBMIO.EXE /s /64 /2 "c:\windows\system32"
edmoncu
woot.gif wow zoster! you gave me the answer! thumbup.gif

anyway, what i did was to create a batch that calls the following (in order):

CODE
start /wait MBM5366.exe /VERYSILENT /SP-
start /wait MBMIO.EXE /s /32 /2 "%systemroot%\system32"
copy mbmiodrvr.sys %systemroot%\system32
start /wait REGEDIT /S registry.reg


as for the registry.reg file, it just contains the registry entries that i ripped from a fresh install of MBM5. it contains this code:
CODE
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mbmiodrvr]
"Version"="32"
"Type"=dword:00000001
"Start"=dword:00000000
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
 62,00,6d,00,69,00,6f,00,64,00,72,00,76,00,72,00,2e,00,73,00,79,00,73,00,00,\
 00
"DisplayName"="mbmiodrvr"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mbmiodrvr\Security]
"Security"=hex:01,00,14,80,90,00,00,00,9c,00,00,00,14,00,00,00,30,00,00,00,02,\
 00,1c,00,01,00,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,\
 00,00,02,00,60,00,04,00,00,00,00,00,14,00,fd,01,02,00,01,01,00,00,00,00,00,\
 05,12,00,00,00,00,00,18,00,ff,01,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,\
 20,02,00,00,00,00,14,00,8d,01,02,00,01,01,00,00,00,00,00,05,0b,00,00,00,00,\
 00,18,00,fd,01,02,00,01,02,00,00,00,00,00,05,20,00,00,00,23,02,00,00,01,01,\
 00,00,00,00,00,05,12,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mbmiodrvr\Enum]
"0"="Root\\LEGACY_MBMIODRVR\\0000"
"Count"=dword:00000001
"NextInstance"=dword:00000001


what i am unsure of if copying of the mbmiodrvr.sys is actually needed or might impose some problems if the file will differ from one motherboard to the other. the same goes for invoking the registry file... if its necessary if those two can be skipped.

anyways, this one worked for me. and its cool! welcome.gif

i have also included the mbmio.exe file in RAR compressed format.

i should note also, that just like installing MBM manually, doing this method still requires that windows has to be restarted.
ZoSTeR
From what I can tell from the installer script
CODE
start /wait MBM5366.exe /VERYSILENT /SP-
start /wait MBMIO.EXE /s /32 /2 "%systemroot%\system32"

should suffice.
edmoncu
hi,

i have tried removing the copying of the *.sys file and calling the registry entry... the mbm startup error re-appeared. blushing.gif

checking at %systemroot%\system32 folder, i see no mbmiodrvr.sys there.
checking at the registry, i see the mbmiodrvr key on the sevices, but its lacking some entries. here's a snippet:
CODE
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mbmiodrvr]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mbmiodrvr\Enum]
"0"="Root\\LEGACY_MBMIODRVR\\0000"
"Count"=dword:00000001
"NextInstance"=dword:00000001
edmoncu
darn! huh.gif placing it on an unattended cd and testing on another pc (jet v266b motherboard), produced the same error:

wonder where i missed...

i got no errors during the entire silent installation tho.

will try to re-arrange the order of my batch file to see if it resolves the problem.

CODE
start /wait MBM5366.exe /VERYSILENT /SP-
copy mbmiodrvr.sys %systemroot%\system32
start /wait REGEDIT /S registry.reg
start /wait MBMIO.EXE /s /32 /2 "%systemroot%\system32"


the file was copied successfully on its designated location and the registry entry was registered. confused.gif
edmoncu
bump crazy.gif im getting awfuly confused blink.gif . i dunno how my approach differs from the manual installation. tried using installrite to monitor the installation, but it monitored more than what i thought. wacko.gif
edmoncu
seems i really finally got it to work this time... hopefully...
i revised the previous registry entry:
CODE
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mbmiodrvr]
"Version"="32"
"Type"=dword:00000001
"Start"=dword:00000000
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
 62,00,6d,00,69,00,6f,00,64,00,72,00,76,00,72,00,2e,00,73,00,79,00,73,00,00,\
 00
"DisplayName"="mbmiodrvr"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mbmiodrvr\Security]
"Security"=hex:01,00,14,80,90,00,00,00,9c,00,00,00,14,00,00,00,30,00,00,00,02,\
 00,1c,00,01,00,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,\
 00,00,02,00,60,00,04,00,00,00,00,00,14,00,fd,01,02,00,01,01,00,00,00,00,00,\
 05,12,00,00,00,00,00,18,00,ff,01,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,\
 20,02,00,00,00,00,14,00,8d,01,02,00,01,01,00,00,00,00,00,05,0b,00,00,00,00,\
 00,18,00,fd,01,02,00,01,02,00,00,00,00,00,05,20,00,00,00,23,02,00,00,01,01,\
 00,00,00,00,00,05,12,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mbmiodrvr\Enum]
"0"="Root\\LEGACY_MBMIODRVR\\0000"
"Count"=dword:00000001
"NextInstance"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_MBMIODRVR]
"NextInstance"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_MBMIODRVR\0000]
"Service"="mbmiodrvr"
"Legacy"=dword:00000001
"ConfigFlags"=dword:00000000
"Class"="LegacyDriver"
"ClassGUID"="{8ECC055D-047F-11D1-A537-0000F8753ED1}"
"DeviceDesc"="mbmiodrvr"
"Capabilities"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_MBMIODRVR\0000\Control]
"ActiveService"="mbmiodrvr"


what i am unsure of is the consistency of ClassGUID... though checking the installation behaviour on two PCs (jet v266b and epox 8rda3+), it shows on both computers the same ClassGUID. thumbup.gif
edmoncu
the parameter i used with MBMIO is wrong. (start /wait MBMIO.EXE /s /32 /2 "%systemroot%\system32")

there should be no quotes surrounding the system32 path.

the correct parameter should've been:
start /wait MBMIO.EXE /s /32 /2 %systemroot%\system32

anyways, it seems the registry hack im forcing to install can be skipped. blushing.gif

update: tried this parameter on an unattended winxp cd. this time, it really worked! thumbup.gif woot.gif
Mann
thumbup.gif good work
ari
@edmoncu,

very good work, it works perfectly. also with the new Version 5.3.7.0

thx ari thumbup.gif
Cykasm
At the risk of sounding stupid.
I havent been able to find the "MBMIO.EXE" file in a temp file for the latest Version 5.3.7.0

The one in the rar is for the older version.

Any help would be appreciated.
TheJerk
I'm wondering if anyone might have some insight in regards to having the monitor preconfigured to start monitoring from the next boot (for a specific PC or group of PCs with the same hardware).

I was thinking I might copy the motherboard monitor 5\Data directory from a preconfigured setup. Problem I see with that is the possibility of drive mismatches (for instance, Computer A uses c:\Program Files while Computer B uses d:\Program Files, etc.).
tom_kauf
smile.gif Hi edmoncu,
I also have the same problem with motherboard monitor. Could you please tell me what to fix on my computer? So you created a batch file to run the installation, and the edited the registry. Is that right?

thanks for your help,
tom






Google Internet Forums Unattended CD/DVD Guide

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.