MSI switches

[Ctwizzy]

Ok there are a few applications on my uADVD which drive me up the wall.

To name them they are:

Alcohol 120%

Daemon Tools

Virtual Machine

all 3 use an msi to install, and all 3 done this way will throw a reboot in 60 seconds no matter what(all testing is done in VM2004):

appname.msi /qb REBOOT=Suppress
appname.msi /qb REBOOT=ReallySuppress
appname.msi /qb /noreboot

I am in the process of trying it this way:

msiexec /i /passive /noreboot appname.msi

But im not confident it wont try and reboot again.

can anyone shed some light onto what im doing wrong?

Thanks!

[S0mE0nesMiNd1]

Both hof these have been mentioned countless times - use the forum search function.

[Ctwizzy]

Youd think I havnt spent time searching huh. I think ive read every post on all 3. Most people use the switches I listed above without issues.

Anyways to update.

msiexec /i "pathtoProgram.msi" /qb /norestart

Also forces a shutdown.

So now I have no clue, if anyone can help in anyways please let me know.

[S0mE0nesMiNd1]

Like I said, these have been discussed on numerous occassions. The problem is, you are obviously not reading the topics and expect them to be in the first post. It might involve more than just running a switch, perhaps extracting the main executable file. Either way, like I said, these have been done and are quite popular.

And just for arguments Sake - I retieved my Alcohol 120% Switch that works fine, and it *DID* involve extracting the main executable file.

/qn Reboot=Suppress

No msiexec is needed, nor do I think these are ever used in switchs.

[Ctwizzy]

how about you dont lecture me about not reading posts and go ahead and read my first post again.

You know what ill quote it for you.

all 3 use an msi to install, and all 3 done this way will throw a reboot in 60 seconds no matter what(all testing is done in VM2004):

appname.msi /qb REBOOT=Suppress
appname.msi /qb REBOOT=ReallySuppress
appname.msi /qb /noreboot

So you said to use REBOOT=Suppress... seeing as I have yet to test this ill get right on that.

On a further note DaemonTools is an .exe, now how do you think I got the msi?

Typing in msiexec in cmd I get this:

Windows ® Installer. V 3.01.4000.1823

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options

</package | /i> <Product.msi>

  Installs or configures a product

/a <Product.msi>

  Administrative install - Installs a product on the network

/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]

  Advertises a product - m to all users, u to current user

</uninstall | /x> <Product.msi | ProductCode>

  Uninstalls the product

Display Options

/quiet

  Quiet mode, no user interaction

/passive

  Unattended mode - progress bar only

/q[n|b|r|f]

  Sets user interface level

  n - No UI

  b - Basic UI

  r - Reduced UI

  f - Full UI (default)

/help

  Help information

Restart Options

/norestart

  Do not restart after the installation is complete

/promptrestart

  Prompts the user for restart if necessary

/forcerestart

  Always restart the computer after installation

Logging Options

/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>

  i - Status messages

  w - Nonfatal warnings

  e - All error messages

  a - Start up of actions

  r - Action-specific records

  u - User requests

  c - Initial UI parameters

  m - Out-of-memory or fatal exit information

  o - Out-of-disk-space messages

  p - Terminal properties

  v - Verbose output

  x - Extra debugging information

  + - Append to existing log file

  ! - Flush each line to the log

  * - Log all information, except for v and x options

/log <LogFile>

  Equivalent of /l* <LogFile>

Update Options

/update <Update1.msp>[;Update2.msp]

  Applies update(s)

/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi | ProductCode>

  Remove update(s) for a product

Repair Options

/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>

  Repairs a product

  p - only if file is missing

  o - if file is missing or an older version is installed (default)

  e - if file is missing or an equal or older version is installed

  d - if file is missing or a different version is installed

  c - if file is missing or checksum does not match the calculated value

  a - forces all files to be reinstalled

  u - all required user-specific registry entries (default)

  m - all required computer-specific registry entries (default)

  s - all existing shortcuts (default)

  v - runs from source and recaches local package

Setting Public Properties

[PROPERTY=PropertyValue]

Consult the Windows ® Installer SDK for additional documentation on the

command line syntax.

Copyright © Microsoft Corporation. All rights reserved.

Portions of this software are based in part on the work of the Independent JPEG Group.

So anyways, as I said most people the "/qb Reboot=Suppress" works normally. But I cant seem to find a way where it wont force a restart. Is there anyway I can do this another way?

Thanks

[Ctwizzy]

Am I the only one who has had this problem?

[1chaoticadult]

Am I the only one who has had this problem?

<{POST_SNAPBACK}>

Probably... Not quite sure though. Daemon Tools creates an msi file when you run the setup program. While setup is still running, look in your temp directory.

[Ctwizzy]

I use the msi file, but no matter what switches I use I get the forced restart. Ive tried /norestart, REBOOT=Suppress and REBOOT=ReallySuppress with no luck. Im using 3.47.0

I have the same issue with Virtual PC and Alcohol, and Daemon. I abandoned using alcohol on my cd due to this problem, but now Alcohol gives me the same thing.

I dont know if this is just a VM thing or what.

Would appreciate any help anyone could give as these last 2 apps are what are holding my cd back from being ready to use.

[InTheWayBoy]

This is what I use for Daemon Tools and I get no issues:

Setup.msi /passive /norestart

[staples]

There may also be a custom action to cause the reboot. Use orca to look for a item in the custom action table that has the word restart or reboot. sometime the people who right msi want to assure it reboots.

[Ctwizzy]

@InTheWayBoy do you use WPI? and what version of DaemonTools?

@Staples, sorry Im not sure how to do this. Ill google, but if you get the chance could you explain it a little. And if you mean in the installer, wouldnt everyone be having this problem then?

[InTheWayBoy]

3.47.0

Lastest version essentially...I run that previous post on the MSI for Daemon Tools, then I have this extra utility called DAEMount (Which is pretty handy I might add!) that installs after Daemon Tools. The setup program from DAEMount runs the application immediately after installation, so I also have a taskkill command...nothing works until reboot, but then I have a virtual CD upon reboot. I further enhance it by removing the tray icon using a simple registry file...here's the whole WPI chain:

WPI:

prog[pn]=['Daemon Tools']
uid[pn]=['DAEMON']
desc[pn]=['Virtual CD Emulator']
ordr[pn]=[60]
cmd1[pn]=['C:\\DoctorPC\\WPI\\Install\\DTools\\Setup.msi /passive /norestart']
cmd2[pn]=['C:\\DoctorPC\\WPI\\Install\\DTools\\DAEMount.exe']
cmd3[pn]=['taskkill /F /IM daemount.exe']
rega[pn]=['C:\\DoctorPC\\WPI\\Install\\DTools\\Startup.reg']
cat[pn]=['Utilities']
pn++

Startup.reg:

REGEDIT4

[-HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run]
"DAEMON Tools-1033"="\"C:\\Program Files\\D-Tools\\daemon.exe\"  -lang 1033"

Don't seem to have any issues with it...good luck!

[Ctwizzy]

Is it the virtual machine or is it just me having huge bad luck?

Thanks for your help.