Jump to content

Nero Burning ROM v7 installation


BoardBabe
 Share

Recommended Posts


besides you cannot have a legit copy of it as it will be released on the 13th of october, you can use /a on the msi-file to create an adminstrative installpoint an then just compress the parts of the suite you want into an 7z/rar or whatever to be extracted in your %programfiles% during install.

Link to comment
Share on other sites

dude, wth does that have to do with nero 7?

eirogge, Im sure youve heard of such things as beta testers? well nero uses them also...now im not saying I am one, but I have tested the program only to find out in its beta form I must warn everyone from using it. I dont know how many times I had to reinstall/repair the program...every time I rebooted nero home and burning rom would always have an issue and id have to repair. so for those beta testing, I can only say the best bet is to wait until nero releases it.

Link to comment
Share on other sites

Try NeroSuite.msi (folder Nero 7 Premium) with parameters below.

(Version Nero Premium 7.0.0.0)

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.

Edited by Gerrit.B
Link to comment
Share on other sites

there is a config file...i forget where, do a search for config.* and youll find it...but it looks like quite a few options can be used there, tho i have no idea how to call it because even tho i set some things in there, the installer doesnt automatically pull from it.

Link to comment
Share on other sites

try running the msi with ISSETUPDRIVEN=0. I have no way of testing this nor do I know for a fact, I downloaded the whole huge file and about a day later deleted it for the reasons I stated above, so I have no way of testing anything...I can just give ideas.

Edited by evilvoice
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.


×
×
  • Create New...