Jump to content

lexxdark

Member
  • Posts

    10
  • Joined

  • Last visited

  • Donations

    $0.00 
  • Country

    Romania

About lexxdark

lexxdark's Achievements

0

Reputation

  1. google for autoit download and compile the scripts into exes NOTE: look in the scripts for what are they running
  2. I thought that the help was refering for any kind of enviroment variable... but from what I see I'm wrong
  3. odd... that if you run help for you'll find this So the above is a paste or a copy by what you see? From what i see there you have this mistake... Second as a debug option run the RunOnceEx.cmd file in a running enviroment (ie not an installing one) and after check the RunOnceEx regsitry keys that are expanded ok. Try pasting them in the command prompt and see if you get errors. Also check not to have copy pause move or other direct commands in the registry (you may have them in a .cmd file but not in the registry, since in the registry it can only run programs aka exe files or cmd files...)
  4. As I said here are the scripts. Enjoy Ok so i used RunOnceEx.cmd from cd (check here http://unattended.msfn.org/unattended.xp/view/web/59/ ) First of all you'll need the attached files, place them in \install\codec (create the folders on the root of the cd). Also place the Ace mega codecs installer in the same dir. the RunOnceEx.cmd code REG ADD %KEY%\031 /VE /D "Ace Mega Codecs Pack 6.03" /f REG ADD %KEY%\031 /V 1 /D "%CDROM%\install\codec\ACE6.0.3Pro.exe /LOADINF=\"%systemdrive%\ace1.inf\" /VERYSILENT /SUPPRESSMSGBOXES " /f REG ADD %KEY%\031 /V 2 /D "%CDROM%\install\codec\ACE6.0.3Pro.exe /LOADINF=\"%systemdrive%\ace2.inf\" /VERYSILENT /SUPPRESSMSGBOXES " /f REG ADD %KEY%\031 /V 3 /D "REG DELETE HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run /v \"QuickTime Task\" /f" /f rem Now we create ace1.inf and ace2.inf so that the installer can use them after the reboot rem Also we set the install dir in them;) copy %CDROM%\install\codec\common.inf %systemdrive%\ace1.inf rem Install Dir echo %ProgramFiles%\ACE Mega CoDecS Pack >> %systemdrive%\ace1.inf copy %systemdrive%\ace1.inf %systemdrive%\ace2.inf type %CDROM%\install\codec\comp1.inf >> %systemdrive%\ace1.inf type %CDROM%\install\codec\comp2.inf >> %systemdrive%\ace2.inf also make sure you add this to the cleanup.cmd (or wherever you make your cleanup after all the installs are done) del /q %systemdrive%\ace1.inf del /q %systemdrive%\ace2.inf PS this last two dels have to be in a cmd or bat file (not in the runonceex registry) common.inf comp1.inf comp2.inf
  5. Well i started looking at this thread: http://www.msfn.org/board/index.php?showto...ega+codecs+pack for installing Ace Mega unattended but as somebody noticed there this way not everything gets installed. Looking into the problem one would notice that the components line (in the generated inf file) ends abruptly with an comma wich would suggest something should follow and that there are only codecs there, no bsplayer, filters or utilities. So I created a second inf file with no codecs and in that file I obtained only filters (entries like filters\blah_blah). Long story short the /SAVEINF AND the /LOADINF file truncates that line and not all components are installed... Further you can make the file shorter by specifing just the top entry and not all entries (ie only codecs instead of an entry for each codec). I attach two inf files with wich you can make a full install without media player classic, antivir, Real Media filters (not codecs), Flash filters, Quick time filters. I removed the later beacuase the installer would ask me for firefox's install dir. Oh there are two files beacause the /LOADINF also truncates the line you should run in your scripts (don't forget to modify the install path in them) start /wait ACE6.0.3Pro.exe /LOADINF=part1.inf /VERYSILENT /SUPPRESSMSGBOXES start /wait ACE6.0.3Pro.exe /LOADINF=part2.inf /VERYSILENT /SUPPRESSMSGBOXES PS if you want bsplayer out just delete "bsplayer," from the first inf file. Also I'll post a bit later some scripts for RunOnceEx.cmd which will install ace mega in the default Program Files dir part1.inf part2.inf
  6. Well an autoit script can do just about anything the problem with autoit scripts is that they are limited to a single installer (ie you can't use the same autoit script for let's say adobe acrobat 7 and office), usualy it's limited even to the version of the installer (not the same for adobe 6 and 7; just an example the autoit scripts might be compatible) The safest bet here is to try and search for a parameter for each install for the destination folder beacause autoit scripts tend to break on a version change...
  7. The sticky threads reamain in front of all other threads no matter what, the threads to which I was refering are on top of all other threads under Application install Here are the links if you don't see them... http://www.msfn.org/board/index.php?showtopic=20502 http://www.msfn.org/board/index.php?showtopic=20197 http://www.msfn.org/board/index.php?showtopic=12657 Good luck
  8. I think you are referring to the sticky posts which are the first on this forum....
  9. Looking a bit more into it i found that some reg keys are the cause of office asking for the cd (HKCU\Software\Microsoft\Office). If i export the hole reg from the user who installed office and import it for the new user office stops asking for the cd for the new user... Next question how do i insert that reg key for the default user (from my knowledge any user created gets it base directory from Default User folder in Documents and settings)
  10. Well I created an Administrative Installation Point for office, patched it SP2 and post SP2, and used the advanced installation method. The problem arises after I create a new user and start any office app with the new user. When office loads it asks me for the cd. Pressing a cancel would pass by that but this will make the office app forget what it was loading (ie a document passed as a parameter) and on the next start it will act the same. Now a simple guess would be that this would be avoided using the cache, but from what I read on other posts the cache isn't built with the advanced install. A bigger problem is that it doesn't even accept the Administrative Installation point as a source and I don't belive I can use the original cd as a soruce (since it's not even SP1). So what are my solutions. 1 for fixing the current install (what would be needed from the original install user, aka administrator user) 2 fix the problem on the cd I don't necesseraly want the cache (if i'll need the cache for an update i'll update the install dvd) Thanks


×
×
  • Create New...