prathapml Posted November 27, 2004 Posted November 27, 2004 Oh well! I've no idea why it won't work at your end. Are you sure you have the latest MSI engine? (use XPSP2 to use the latest - MSI 3.0)Is your diskeeper licensed, And are you sure you have the newer package of diskeeper 9 ? (because the older version that some people got from P2P networks were not properly packaged)If you own diskeeper, then get it from here.
durex Posted November 27, 2004 Author Posted November 27, 2004 Im running XPSP2, so that cant be the case.Ive tried this on multiple MSI files Diskeeper 8 and Adobe 6.02 and get the same results.If this is a parameter for all msi packages, why isnt it shown as one when I run msiexec?Thanks again prathapml
prathapml Posted November 27, 2004 Posted November 27, 2004 If this is a parameter for all msi packages, why isnt it shown as one when I run msiexec?Dunno....There's some things that just never get revealed.Now as for the MSI property, just try one last thing. MS-Office 2003 (and MSO XP) support that property as well. Just check out if the property is valid when you use it with that package. That should certainly work on all machines, since Office comes with all required files self-contained. If that doesn't work either, then we can work out what's wrong. But if the property works with MS-Office, but doesn't work with AcroRead/diskeeper/etc. then you know that it is a *REAL* strange situation . Most MSI-based installers of small utilities do not utilise such advanced properties, but fact is that the bigger companies do give a lot of attention to their installers - so that is why apps like diskeeper does support INSTALLlocation.Well, if nothing else works out on the MSI properties front - cheers to your VBscript.
durex Posted November 27, 2004 Author Posted November 27, 2004 Sure enough... Tried it with MSOfficeXP and it works like a charm. Now, im not sure if it makes a difference, but the Admin extract thing included a setup.exe (instead of .msi)... so I used this with the installlocation and again... worked like a charm! Man Id love to figure this out for these other programs as well...
durex Posted December 16, 2004 Author Posted December 16, 2004 Just an update for anyone who cares...The only reason why I created this VBScript is because I wanted to install into a folder other than the default. I finally found that while the suggestions prathapml was giving me were in the right direction, the parameter to define the installation path was incorrect...Launch the Diskeeper installer, search for the msi file it creates than runsetup.msi INSTALLDIR=C:\Blah\diskeeper /qnso its INSTALLDIR... not INSTALLLOCATIONthx for the help on this prathapml!
WotC Posted March 20, 2005 Posted March 20, 2005 @prathapml: Do you have the reg entry for disabling auto-update at hand? Can't find it right now... And is there a way to set e.g. Screensaver mode to all drives using registry entries?
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now