Jump to content

edmoncu

Member
  • Posts

    360
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Hong Kong

Everything posted by edmoncu

  1. just a followup to office2k3 shrink, it would also be possible to compress the shrinked ofc2k3 installer via 7zip or winrar to an sfx archive and have it silently decompressed before the installation starts. i've done it with ofc2k3, shrinked it with officeshrink of buckeyeXP, the installer went down to 180+mb. compressed it to sfx with winrar. it went down further to 64mb.
  2. you could look at the first page of this thread. i dunno though if it covers the non-important or recommended updates.
  3. as much as possible, driver locations (even the chipset drivers) has to be broken down into specific folder... (for gart, memory controller, ide, sound, etc). then specify each under OemPnpDriversPath path. although its kinda painstaking, you'd better off doing this method when declaring drivers.
  4. even when ran at cmdlines.txt (or from a cmd file), all the M$ updates didnt created temp folders like that in the root of the systemdrive.
  5. mine installed via svcpack.inf like so: "Q832483.exe /C:""dahotfix.exe /q /n"" /q:a" here's the entire svcpack.inf i have: [Version] Signature="$Windows NT$" MajorVersion=5 MinorVersion=1 BuildNumber=2600 [SetupData] CatalogSubDir="\i386\Update" [ProductCatalogsToInstall] [SetupHotfixesToRun] JS56NEN.exe /Q:A /R:N "Q832483.exe /C:""dahotfix.exe /q /n"" /q:a" KB823182.exe /Q /N /Z /O KB824105.exe /Q /N /Z /O KB824141.exe /Q /N /Z /O KB825119.exe /Q /N /Z /O KB826939.exe /Q /N /Z /O KB828035.exe /Q /N /Z /O KB828741.exe /Q /N /Z /O Q832894.exe /Q:A /R:N Q831167.exe /Q:A /R:N KB833407.exe /Q /N /Z /O KB835732.exe /Q /N /Z /O KB837001.exe /Q /N /Z /O KB837009.exe /Q:A /R:N KB840374.exe /Q /N /Z /O WMP9MM2.exe Q828026.exe /Q /N /Z /O qchain.exe DX9NTopk.exe
  6. hmm, interesting. this has been a long time stumper... i suppose, this guide will enlighten us further hopes that this method is still highly usable.
  7. jedi, you must set a specific order. its all outlined here
  8. tried unattendedly installing nod32 trial and imon has been enabled even without any registry editing.
  9. talking about placing hotfixes somewhere else, i am unsure if this had been asked before, but would it be possible to use environment variables (like %systemdrive%) within svcpack.inf (or dosnet.inf) in specifying the location of the updates? i am planning on placing the hotfixes on the hard disk instead of em being accessed from the cd... so as to have a faster install times.
  10. hi, can i call this file (using the same /qn parameters) via "msiexec -i" method? it was okay calling an *.MSI via msiexec, i wonder if the same applies to the Winamp.MSP file. i need this msiexec approach because i am running an autoit script when calling the *.MSI file. within autoit, i can't directly call an MSI file, im afraid the same might be true with MSP files. i tried running msiexec -i winamp.msp thru the RUN dialog in windows but i got this error: This installation package could not be opened Contact the application vendor to verify that this is a valid Windows Installer package. i am now trying (but im unsure if i used the right parameters) this commandline: msiexec -p winamp.msp /qn i wonder if this is correct.
  11. kinda off topic question, but at this stage, is it effective to execute runonceex.cmd here? since it just contains registry entries.
  12. hi, can i use this approach with the one discussed in this thread? thanks.
  13. you could try doing this approach at installing the patched uxtheme.dll
  14. i suppose, you're using a trimmed down version of MS Office. Probably you've missed someting along when creating the unnattend.mst file.
  15. k, done it. thanks for the info hmm, with the thread you gave me, it made me more curious to try that approach.
  16. i realized, it worked. but it did not decompressed at the HDD\Drivers folder as i expected, rather, it decompressed the files at the HDD\windows folder. i suppose, i should apply some advanced SFX rules with the drivers.exe file.
  17. tried it on my winnt.sif. placed the following code in it: [GuiUnattended] AdminPassword=* EncryptedAdminPassword=NO OEMSkipRegional=1 TimeZone=215 OemSkipWelcome=1 DetachedProgram="%systemdrive%\drivers\drivers.exe" Arguments="/S" but it didn't worked as mentioned. btw, my cd (G:\$OEM$\$1\Drivers) contained the drivers.exe RAR-SFX compressed archive. i wonder what part have i missed or its just winrar sfx doesn't work in this scenario?
  18. wow, cool tips! i was wondering, if ever i am to decide to password protect the SFX archive, would it be possible to include a commandline parameter when decompressing it from a batch file (or an automation tool like AutoIt)? thanks!
  19. oops im sorry, what i meant was, can i control where the extracted files are placed when running unattendedly a rar-sfx compressed archive?
  20. i was wondering, i dunno how unattended RAR-SFX archives behave though, but will it extract to the folder where the file's located at or it will extract on the default active directory (if there's one existing)? i had this sample *.CMD file that's being called under RunOnceEx.cmd cd %WINDIR%\Resources\Themes start /wait %WINDIR%\Resources\Themes\ChaNinja.exe /s cd %SYSTEMDRIVE%\Others\dotnetfx start /wait %SYSTEMDRIVE%\Others\dotnetfx\dotnetfx.exe /s cd %SYSTEMDRIVE%\Others\acroread start /wait %SYSTEMDRIVE%\Others\acroread\acroread.exe /s cd %SYSTEMDRIVE%\Others\alcohol start /wait %SYSTEMDRIVE%\Others\alcohol\alcohol.exe /s cd %SYSTEMDRIVE%\Others\diskeeper start /wait %SYSTEMDRIVE%\Others\diskeeper\diskeeper.exe /s cd %SYSTEMDRIVE%\Others\Powerdvd start /wait %SYSTEMDRIVE%\Others\Powerdvd\powerdvd.exe /s cd %SYSTEMDRIVE%\Others\Ofc2k3 start /wait %SYSTEMDRIVE%\Others\Ofc2k3\ofc2k3.exe /s cd %SYSTEMDRIVE%\Others\Nod32 start /wait %SYSTEMDRIVE%\Others\Nod32\nod32.exe /s all the exe files called unattendedly are rar-sfx compressed. i was wondering, about the behavior of rar-sfx archives, would it be safe if i remove the cd commands?
  21. oh nevermind, i got it to work... what i did was to extract the dotnetfx file via winrar and from the extracted files, i located at the msi file called netfx.msi and applied a parameter /qn REBOOT=Suppress. here's how it looked like: netfx.msi /qn REBOOT=Suppress" /F edited: oops, i was late at replying. thanks anyways.
  22. Hi all, I hope you could help me with this, as I've searched thru the forum, I found out that the parameters used to silently install DotNet Framework 1.1 is by using the parameter /q:a /r:n However, this one doesnt work for me. It stops at the License Agreement portion of the setup. I wonder if I got the switches correct or have forgotten something. Thanks.
  23. im sorry guys if im slow to follow, does this simply mean i can have my $OEM$\drivers compressed and be extracted before the detecting hardware phase starts?
  24. i had the same problem running this on a real pc when doing an unattended install, this time, the file involved is a quicktime file (or codec).
  25. i had the same problem every once in a while during that part of the silent install. either under vmware or under vpc. its yet to be confirmed if the same will occur on a real pc..
×
×
  • Create New...