mazin

@ embe Why don't you just delete this line from your first RunOnceEX.cmd: rundll32 iernonce.dll,RunOnceExProcess

Diskeeper: Use that button to restart your PC. When the PC is restarted, you'll find the MSI there. How to identify an installer: Check this util by MHz. http://www.msfn.org/board/index.php?showtopic=83388

First: NERO and Office 2003. Good work! I just wonder how INSTALLDIR1 worked as I know it should be INSTALLDIR (without 1). Well, I think it worked just because a MSI usually reads the first 8 characters of a switch. If I remember correctly! Second: MSI installers. Like you did to Office and NERO, you can usually create a MST or just use the INSTALLDIR switch with MSI installers Adding INSTALLDIR switch on the command line directly or inside a SFX makes no difference. I mean it should work either way. Diskeeper 10 is a MSI. You can run the package (v10ProPrem.exe) manually and let the first setup screen wait as it is. Then, look for the MSI file. It should be extracted somewhere like %TEMP% directory or so. I don't know wether there's a CAB file along with the MSI. You have to check for that. You can use that MSI (with CAB, if any) with a custom directory when installing with your UACD. I think TweakUI Powertoy and Deskman Powertoy are similar to Diskeeper 10. Third: FoxIt Reader. My favorite! What I did: - Installed it manually. - Looked for FoxitReader.exe in the installation directory. (I no longer remember where it is!) - I copied FoxitReader.exe (ONLY) to my UACD. I renamed it to PDFRead.exe (This is not obligatory). - A batch script (in my UACD) copied it to %SystemRoot%. - The same batch script runs this code to make it be the default PDF viewer: %SystemRoot%\PDFRead.exe /register That's it! Fourth: Firefox. I'm not a Firefox user! However, I found FirefoxSetup-0.9.exe on my HDD. It's probably left there someday when I was planning to test FireFox. I'm not sure. I extracted FirefoxSetup-0.9.exe to a directory with 7-zip. Inside the directory, there is the config.ini. A wealth of information is in config.ini, not only -ms and -ira! The first block of lines (inside config.ini) and the last block of lines are of special interest to your situation. Fifth: INNO installers. I think INNO installers are, also, dominating a good portion of apps because INNO is free and open source. I hope I'm correct! Well, you asked where to put /GROUP="FolderName". You put it on the command line like this: start /wait %SystemDrive%\Install\MyApp\MyINNO.exe /VERYSILENT /SP- /DIR="C:\Program Files\2-Multimedia\MyAppFolder" /GROUP="FolderName" More INNO discussion by ZoSTeR is here: - Inno Setup complete switch list. - Rebuilding Inno Setups. Sixth: Unattended Installation of Windows. To have a full control on where Windows should be installed, I have these lines in my WINNT.SIF under these sections: [Data] Autopartition = 0 [unattended] UnattendMode = DefaultHide TargetPath=\Windows Filesystem=* Repartition= "No"

Welcome to MSFN! Assumptions: 1- You created InstallRite kits on a working system. 2- A working system means that all services and drivers are loaded. 3- Some of your kits depends on loaded services/drivers. Conclusion: 1- You'd better install your kits when your Desktop is loaded. 2- When Desktop is loaded, it means services/drivers are loaded. 3- Kits will, then, work as expected. Recommendation: Check this topic for proper RUN POINTS where Desktop is loaded.

Well, thanks. But I think it can be run manually on a PC that needs it, am I correct?

First, thank you very much for your time and effort. Your all-in-one NET package saved me alot of time. Is your package made to work only from SVCPACK? Can't I install it from somewhere else? Thanks.

I, totally, agree!

Just last night, I used RougeSpear's package. I installed it from SVCPACK with no workarounds, just by itself.

To bypass the DriverSigning check, add these two lines under [unattended] section in your WINNT.SIF: DriverSigningPolicy = Ignore NonDriverSigningPolicy = Ignore And, yes, nLite has this option, too.

Sua! I just wonder what G.L. is?

Beautiful! I need something like that for my SYSDM.CPL.

I use this: cdr open all I take out a CD and insert another CD. cdr is on the Download page.

@ tiico According to your setuperr.txt, I think the "Help and Support" link on Start Menu does not work, either.

Have you added this tag? Windows Registry Editor Version 5.00 There's nothing special about applying a reg tweak other than this: REGEDIT /S %SystemDrive%\Install\Utils\explorer.reg Well, you can use PaulIA's VBS for the same purpose.

http://www.msfn.org/board/index.php?showtopic=53392

My two cents... Q4- What is the diference between using .bat or .cmd? Don´t they do the same thing? A4- BAT files work under DOS, Win9x, and WinNT systems. --- CMD files, by default, do not work under DOS or Win9x systems. --- Under winxp, they do the same. Q5- To add comments (only for information inside the file) on .bat or .cmd, i just use :: ? A5- There are many methods to comment a line in a BAT or CMD file. --- The most popular methods are :: (double colons) and REM. Q8- Is there a way to Enable Quick Launch on windows install? A8- I apply this reg file from SVCPACK (T-13) to enable QL for all user accounts.

Yes! User Name must match.

I updated the first post and added a section for creating a SFX. HTH

First post updated with a new look!

You don't have to worry about that. DLLs in our example (BRU) are built for use with their related EXE. Since they are (EXE & DLLs) in one folder, the app should work correctly. This parameter tells the SFX where to install the files: Path=Bulk Rename Utility! When a path stated this way, a folder in %ProgramFiles% called "Bulk Rename Utility" is created. And if a folder with the same name already pre-exists in %ProgramFiles%, it will be overwritten by the parameter: Overwrite=1 The parameter "Silent=1" tells the SFX not to show any setup windows during installation. Of course, the parameter "Setup=BRUtweak.cmd" tells the SFX what file to launch after extracting the package.

Q1. HKLM uninstall reg keys, is there any reason to have to use REG ADD, rather than simply REG IMPORT (or regedit /s) uninstall.reg? A1. Yes, there's a reason. Here it is: REG ADD %KEY% /v DisplayIcon /d "%SystemDrive%\Program Files\Bulk Rename Utility\Bulk Rename Utility.exe" Since I use REG ADD, the path will be written to the Registry this way: "DisplayIcon"="C:\\Program Files\\Bulk Rename Utility\\Bulk Rename Utility.exe" If my %SystemDrive% is D:, the path will be written to the Registry this way: "DisplayIcon"="D:\\Program Files\\Bulk Rename Utility\\Bulk Rename Utility.exe" So, whatever my %SystemDrive% is, it will be translated correctly using REG ADD. This is apparently useful when I install this package on a computer without knowing its %SystemDrive% in advance. But, if you want to use an absolute path, then you can use REGEDIT /S uninstall.reg instead. Knowing your %SystemDrive% is always C:, your uninstall.reg should appear like this: On the other hand, if you are satisfied with the default uninstall icon (see the attached pic), then you can exclude the "DisplayIcon" line. This way, you won't need to use REG ADD. You can, then, use a reg file instead. Well! You probably noticed that I used: REG ADD %KEY% /v UninstallString /d BRUunins.cmd! Since I created BRUunins.cmd in %SystemRoot% (see block 3 in BRUtweak.cmd), then its location is known to the system. %SystemRoot% is a pre-defined path. Hence, I didn't have to use: REG ADD %KEY% /v UninstallString /d %SystemRoot%\BRUunins.cmd! But, if you create BRUunins.cmd in a non-defined path, then you'll need to use REG ADD again. Q2. This prog doesn't come with uninstaller, so you have to write your own cmd? A2. Yes! Q3. How about the dlls, would it be necessary to unregister them? A3. I think you're referring to BRU_XP.dll and pcre.dll! Well! In your package, if you register a DLL during installation, then you have to unregister it during the uninstallation process. A DLL does not register by itself. So, if you haven't registered it by yourself, you don't have to unregister it. Otherwise, you'll get the message "The specified module could not be found". Q4. What are the 3 shortcuts in SFX arguments? A4. Those are shortcuts to Bulk Rename Utility.exe, Bulk Rename Utility.chm, and Readme.rtf! They are created in "%UserProfile%\Start Menu\Programs\Bulk Rename Utility". Example: Shortcut=P, "Readme.rtf", "Bulk Rename Utility", "Info about BRU", "Read Me" Where to put a shortcut = P (=%UserProfile%\Start Menu\Programs) Which file to create a shortcut to = "Readme.rtf" What folder under P to put the shortcut in = "Bulk Rename Utility" What description to give to the shortcut = "Info about BRU" What name to be given to your shortcut = "Read Me" Eventually, this will create: "%UserProfile%\Start Menu\Programs\Bulk Rename Utility\Read Me.lnk" Q5. What steps do I have to take to make the SFX in WinRAR? A5. To be answered, later. First post updated! Stay tuned.

Yes! Do you have any suggestions for this one?

I spent an hour creating this.

LDID %1% does not work correctly after reboot because the CD-ROM drive is assigned a different letter. This is one of my INFs that works correctly for RunOnceEX under WIN98SE. It should work correctly, too, under WINME and WINXP. CDROM=I: is appended to this INF with the help of a batch file that scans for the CD-ROM drive letter.

I think you haven't used ROEX the correct way. Please make another attempt using the following outlines. Don't use your Progs.reg!