Delprat

Just to say... Maybe something to do with NTFS compression ?

There is multiple 7-Zip SFX modules (like for WinRAR) : 7z.SFX ("default" one with a gui asking where to extract) ; 7zCon.SFX (same as the previous, but in console mode : i think this one accepts switches to specify the path to extract, like 7z(a).exe) and 7zS.SFX (for making "setups" : this one accepts the "config.txt" file) When we're talking about extracting setups, specifying a destination is of no use : the setup files should be deleted after use. But to use these files, one obviously needs to know where to find them Here, the big OEM.exe is extracted @ T-12 (via cmdline), during GUI setup ; the setup files should remain on disk until the first GUI boot (for RunOnceEx) : the matter is not "security" against deletion... if the files are not moved/copied elsewhere, they will be deleted by 7zS.SFX (for sure !), and all those RunOnceEx entries added by install.cmd will drive you nowhere... (and may pops errors up !) I do prefer moving instead of copying because source & destination are likely to be on the same partition (7zS.SFX extracts files to %TEMP%\7z.xxx, which is by default on %systemdrive%). The windows MOVE command doesn't work for directory trees (you can move a folder, but not recursively), and the XCOPY command can't do a move operation. I suggested ROBOCOPY as an alternative, but you can use any other tool. btw, the full command should be like that : ROBOCOPY . %systemdrive%\oem /S /E /MOVE /COPY:DSO /A-:RHS /NFL /ETA /XF ROBOCOPY.EXE STARTX.EXE INSTALL.CMD /S /E : like xcopy : folders & subfolders & empty ones /MOVE : moves files & folders instead of copying /COPY:DSO : include data, security attributes & owner info in the operation (not really needed) /A-:RHS : remove attributes read-only, hidden & system (in case of...) /NFL /ETA : reduced output (no file list, only directories), with estimated time of arrival (only for cosmetic purpose -- notice that the window if you follow my "directives", but useful for debugging) /XF ROBOCOPY.EXE STARTX.EXE INSTALL.CMD : exclude these 3 files from moving operation If you read again this thread, you'll get two answers : cmdow & startx. If you make a SFX, you can ResHack the 7z.SFX file to modify the progress dialog (or even remove everything)

Why someone having a legit windows would install a tool which sole purpose is to say "legit" or "not legit" ??? (you were not talking about the tool that allow to download files & updates ; only about the "wga notifications", am i right ?) I can understand if someone using a pirated windows installs it... But here... netsys004, you're using a legit copy, so why did you installed this ??? ??? ??? ???????

You can try this link

If you really care about saving as much space as possible, you should have no compressed file inside your big OEM.7z. I saw "dotnet1.exe" & "dotnet2.exe" in your first post. Try to expand them, and pack both folders together. You'll get something smaller than the two SFXes. (and when used, you get twice less disk swapping) Also, you can get better compression ratio using complicated command lines. Example : 7za.exe a ArchiveName.7z -r -t7z -mx=9 -ms=on -m0=BCJ2 -m1=LZMA:d24:fb273:a2:lc7:mf=bt3 -m2=LZMA:d19:fb273:a2:lc0:lp2:mf=bt3 -m3=LZMA:d19:fb273:a2:lc0:lp2:mf=bt3 -mb0:1 -mb0s1:2 -mb0s2:3 * This one takes 2x more time to complete than the default "max" compression level, but gives smaller archive. (decompression speed is not affected) Last but not least, 7za.exe is 3x bigger than 7z SFX module. That's only a few hundreds kilobytes, but using a SFX can make things "easier" : one big OEM.exe can auto-unpack via cmdlines.txt and add runonce entries. The directory : [ %CDROOT% ] \--- [ $OEM$ ] | OEM.exe | cmdlines.txt cmdlines.txt : [Commands] "OEM.exe" OEM.exe root directory : OEM\ | startx.exe | robocopy.exe | install.cmd |--> dx9\ |--> dotnet1\ |--> dotnet2\ ... config.txt (for making OEM.exe SFX) RunProgram line should be : RunProgram="startx.exe /wait /b install.cmd" (this way install.cmd will run hidden in background) and install.cmd should be like that (take care, i don't know it by heart) : @echo off rem first move directories to %systemdrive%\OEM so 7z will not find them and not delete them rem (check the robocopy command, i'm not sure it moves the subdirs) robocopy /MOVE *.* %systemdrive%\oem rem now add commands for runonce : REG ADD %KEY%\005 /VE /D "Microsoft DirectX 9c" /f REG ADD %KEY%\005 /V 1 /D "%systemdrive%\oem\DX9\dxsetup.exe /silent" /f REG ADD %KEY%\005 /V 2 /D "rd /s /q %systemdrive%\oem\DX9" /f REG ADD %KEY%\010 /VE /D "Microsoft .NET Runtimes" /f REG ADD %KEY%\010 /V 1 /D "msiexec /i %systemdrive%\oem\dotnet1\netfx.msi /qb-" /f REG ADD %KEY%\010 /V 2 /D "rd /s /q %systemdrive%\oem\dotnet1" /f REG ADD %KEY%\010 /V 3 /D "msiexec /i %systemdrive%\oem\dotnet2\netfx.msi /qb-" /f REG ADD %KEY%\010 /V 4 /D "rd /s /q %systemdrive%\oem\dotnet2" /f rem now, a defrag is really needed :rolleyes: REG ADD %KEY%\z99 /VE /D "Defrag & reboot..." /f REG ADD %KEY%\z99 /V 1 /D "rd /s /q %systemdrive%\oem" /f REG ADD %KEY%\z99 /V 2 /D "defrag %systemdrive% -f" /f REG ADD %KEY%\z99 /V 3 /D "shutdown.exe /r /t 10" /f note that i delete each folder right after each install : very useful when installing things like sun java 1.5 or open office 2 (their install folders are huge) you can go further : i use always the same "install.cmd" that guess wich commands must be ran (it checks if there's an msi, an innosetup, etc... add creates reg keys according to folder names), so i only need to add/remove/update folders and repack. (and some installers can run at T-12, : no need for reg keys, only a "start /wait blablabla.exe" & "rd /s /q blabladir" ; before the robocopy command) i hope you'll find that useful (and not too messy )

RegShot before and RegShot after completing it maybe ?

what ? whaaaaa...(lots of 'a')...aaaaaat ? Yes, and i'm thinking that this "silent installer" is also a waste : look, it extracts installation files from an ISO file to a virtual hard disk, then install to the same virtual hard disk, then removes the installation files from the virtual hard disk... while keeping the files uncompressed in the ISO makes it install from the ISO to the virtual hard disk. In one word : K.I.S.S. Ps: uh, i forgot to say that 'joe' may not exist IRL

yes, and if the SFX is used without the script outside a VM, the extraction is made before the installer aborts => time lost. If the files are not packed, the script is no longer needed, and no time will be lost by an extraction process. "msiexec /i vmwaretools.msi /passive" in a cmd... Not that big of a deal too... (or replace /passive with your prefered switch : /qb- /qn /qr /quiet /anything...) I were saying that burning an ISO with VMwareTools is a lost of space on the disc : why put on it something useful only in a VM ??? (plus it needs to bother with a script to check if.... ) If you add VMwT only in ISO inteded for VMs, the script check is unuseful... (and the size of an ISO is not as important as the size of a CD : VMware accept 2GB... it is possible to keep VMwT unpacked) i hope you understand my opinion better this way

The good reason is, in two words : speed and size. Without the script, the check is made after unpacking the SFX. The other solution is to keep the files uncompressed : when testing in a VM, the ISO size doesn't matter so much. And there's IMHO no point in burning a disc with VMwareTools eating space

In fact, i never disable autorun. And i mounted "windows.iso" (not in a VM) to extract the tools... Now, the main question is : why some people are making scripts to check if it's needed to install VMwT ??? ++

Anyway, they don't install outside a VMware virtual machine...

that's obvious : with no modifications, Server 2003 doesn't uses themes. Instead of comparing XP/2003 "out of the box", we should copy XP settings on 2003 and 2003 settings on XP... Then differences will be very small. But that's not important : better kernel or not, 2003 and XP does'nt focuses on the same goals

maybe i had a special version of 7-zip that disallow it... more that one month ago... there were some updates... OMG, i feeded the troll

two ar' both little and big and both in the middle and on the outside... r'u blind ?... (Open your Eyes from the same artist...) or maybe you did suppose 't was some sort of "coincidence" ?...

You don't look weird with your 250KB saved when you're adding tons of KBxxxxxx... Why nLite keeps YAHOO.BMP : turn the "H" 90° right (or left), it becomes an "=", put it in place of the point, that transforms in a coma, that moves after the "A", then scramble a bit the extension to make it "PBM", which is the short for "problem". Now, write what you have, and you'll get toto's head when he tweaks his OS... ++

Get it here We dream of ways to break these iron bars We dream of black nights without moon or stars We dream of tunnels and of sleeping guards We dream of blackouts in the prison yards Heaven sent reply, however small Evidence of life, beyond this wall Born and bred in this machine Wardens dread to see us dream We dream of jailers throwing down their arms We dream of open gates and no alarms Thrice - The Earth Will Shake ++ (edit: not mine, but nice -- even if the barcode doesn't match the numbers)

Translation updated Since there were only two lines to translate, i made an 4173rn471v3 1337 v3r510n ++ nlaom_lng_fr_3r.7z

Perhaps the matter is Explorer.exe itself which is looking if that "Shell" regkey is exactly "Explorer.exe" before running in shell-mode... Why are you trying that ??? You can make a low-rights user...

I did never know if it works in winnt.sif, if you're sure that's a better way. What ? What ? WHAAAAT ? That's impossible ! It must work ! It worked on my old 386 SX with MS-DOS 5.00 about 15 years ago /me is hopefully living in a piece of countryside lost in the middle of nowhere and there's no shop selling edible french flag miles and miles around... Why not trying the full line i gave you, with "cmd" in front : C:\WINDOWS\System32\cmd.exe /C @ECHO something>C:\TAGNAME.TAG ...and you're trying to make a full-featured all-in-one dvd... OMG! There's lot of work for you if you're making this sort of omission You're welcome !Hummm... Take care, it's not tested ... ... ... But that's a good idea to make a new guide (title suggestion : the best way to lose time) ++

That's not what i were thinking about. It may work for some app, but not all, 'coz it's @ T-39... not a good time to install apps ! First of all, the blue line is "false" : winnt.sif can obviously run something from the CD/DVD BUT you must know the drive letter and "harcode" it in the sif file. Very bad practice to avoid at all costs... You want to make an all-in-one dvd : this is done by splitting install source of each OS into separated "boot folder" and "setup folder" You want to install a "personalized software selection" (or "tweaks" such as 2003 to workstation), or not, for each OS : this is done by splitting "boot folder" for each OS and editing detachedprogram= line in winnt.sif : DetachedProgram=C:\WINDOWS\System32\cmd.exe /C @ECHO something>C:\TAGNAME.TAG You'll need to change the red part, and make it unique in each boot folder. examples : W51SP1.TAG = XP SP1 W51SP2S.TAG = XP SP2 + software W52DCW.TAG = 2003 data center to workstation W52DCWS.TAG = 2003 data center to workstation + software Do not forget the .TAG. Let's name the root of your AIO-DVD "X:\", and suppose that your programs (or tweaks, or whatever) will be in "X:\Programs\" (that's the folder name i used many times : it's 8 letters and it works very well both under NT-based and 9x-based). In this foler, you'll create an "Install.cmd" file that will install applications by testing the presence of a tag file. Example : Now, create RunOnce.cmd : compress it : makecab /D CompressionMemory=21 /D CompressionType=LZX RunOnce.cmd you'll get a RunOnce.cm_ file : copy it in each setup folder then edit setup files as i said in my first post : DosNet.inf [Files] : d1,RunOnce.cmd TxtSetup.sif [sourceDisksFiles] : RunOnce.cmd = 1,,,,,,,1,0,0 This way, RunOnce.cm_ will be unpacked to C:\Windows\RunOnce.cmd in each install, and it will launch Install.cmd from the DVD. The last thing to do is to call that RunOnce.cmd. So edit winnt.sif in each boot folder, and add two lines in [GuiRunOnce] (Install.cmd is CALL'ed from RunOnce.cmd, it's unsafe to delete RunOnce.cmd from Install.cmd, so do it here) : C:\WINDOWS\RunOnce.cmd C:\WINDOWS\System32\cmd.exe /C del /f /q C:\WINDOWS\RunOnce.cmd That's all, your programs will install at first gui boot, depending on the tag file. Modifications are possible to install @ T-13 : right after creating RunOnce.cmd, copy it uncompressed to setup folders\SVCPACK ; edit every svcpack.inf (cabbed in svcpack.in_) to launch it (add a line in [setupHotfixesToRun]) ; and do not add the first line in [GuiRunOnce], only the second. ++

look carefully : there are 3 methods of install. There's one where drivers are unpacked via presetup.cmd, which ran before setup.exe and another where drivers are unpacked via detachedprogram (this is based on v5, i didn't tested v6)

Yes And i should start with english :VERY BAD : proverb: "not possable" is not french (well, it's also not english, but that's not the question) BETTER : proverb : "not possable" is not french (nor english, but that's not the question) i think yes : my method allows "two boot options" since it's based on two diffent winnt.sif ! There's two methods : winnt.sif on a floppy (not the case here ) ; or different boot folders. But it's no longer required (as in your method) to split the setup folder : seeing andregcasal ENORMOUS AIO DVD project, i'm pretty sure that minimizing the number of setup folders will clarify & simplify things. André, you can include the TAGs via DetachedProgram, you can even use the same RunOnce.cmd for every NT-based OS. (that's Bezalel idea, i just picked it up on the fly) And to make things more flexible, the RunOnce.cmd slipstreamed in i386 can be a single-or-two-lines call to another CMD on the DVD that would take care of the real installation, depending on the tag set by winnt.sif (and, in this case, also the cleanup ; it make "RANTAG" and RunOnceBoth.cmd useless : if you said before that you're making a so huge project, i wouldn't have proposed this solution). kof94 : Does your solution allows the same depth of customization with the same ease of use ? (in other words, i think there's no point in splitting the source when there's no need to and when it adds no feature) One line to change in each winnt.sif that is specific to the OS ; and one file to slipstream in the setup folder which is the same for all ! (and one ring to rule them all, thanks Bezalel ) (and the slipstream can be done via dosnet & txtsetup for a "1st-gui-boot-install-like-runonceex" ; or in svcpack for a T-13 install, or even both ; only drawback is : no application add-ons) Well, 3 posts, and 3 ways to go. Did someone understood what i say ? (or may i write a tutorial ?) In fact all of this only 'coz winnt.sif is unable to call a file on the source disc... PS: andré : kof94 spoken about CDimage, which saves space for you

i explain a bit more my p.o.v. : I don't think repacking the 7z DP in a single 7z will saves enough space to say "it's useful". (They're already less than 210 MB 7-zipped !) Keeping the drivers in a "windows usable form" (that is : not 7z) is, of course, useful. But afaik BTS's DPs keeps them uncompressed (1090 MB), not cabbed (450 MB) and i bet that dropping a .cab on the HD is not enough for windows (look for the add new hardware wizard : it doesn't look for .inf inside .cab, thus .inf must be outside the .cab, which requires editing EACH .inf...) Maybe i'm wrong on that : i don't use DP 'coz i have only CD-burner, not DVD You changed first post again without notice ! But my answer remains "no" : boot files are in place, so there's no need to boot the CD.

Hi (again) » Text-mode Setup 1. massstorage drivers mainly, you can add massstorage drivers only (search on the forum, there's a thread) 3. yes 4. no » GUI-mode Setup 0. you can repack all packs in one PackedDriverPacks.7z and then edit drivers.cmd. Is it useful ? I don't think so... You'll need to extract the drivers on the HDD if you don't want to put the CD in each time ; and you'll need to extract the drivers on the CD (or use .cabs) else windows won't even find them on the CD ++

dosnet.inf [files] section only lists the files on the CD ; the "d1" specifies the disk id. txtsetup.sif [sourceDisksFiles] section is waaaaayyy more complicated, it list the files, their source location (if not i386, it's the first 1, which match a line in [i-don't-remember]), their destination directory (the second "1", which match a line in [WinntDirectories]), their destination file name, and some special values that i don't understand correctly... I use that as a black box proverb: "not possable" is not french (well, it's also not english, but that's not the question ) Winnt.sif has a "DetachedProgram=" feature, that launch a program at T-39 : in one install it can launch a .cmd that will create that tag file you spoken about (INSTTAG) ; in the other install it will be omitted. When RunOnce.cmd is launched (first line of [GuiRunOnce] i presume), it looks for INSTTAG, if it exist it installs the progs, then it creates another tag, RANTAG (regardless of INSTAG presence). When RunOnceBoth.cmd is launched (second line of [GuiRunOnce] i presume), it looks for RANTAG, if it exists, it deletes INSTTAG, RunOnce.cmd and RunOnceBoth.cmd Again, it seems complicated... The only advantage is that having a single source is easier to update About the creation of the installers, the addon method gets more complicated : your addons needs to look for INSTTAG presence, and this will complicate things (you'll need to remove the RunOnce.cmd and keep only RunOnceBoth.cmd, and add a cmd file in each addon). If you want to use the method i described, i urge you to prefer installers (best suited for RunOnce©) : they can be SFX, SFX switchless, or any other (MSI files, original setups, etc...). Note that the RunOnce.cmd file i'm talking about should not look like the one described in the unattended guide : it's only a list of commands to run. Example : @echo off REM checks for INSTTAG : If not exist C:\INSTTAG goto :end for %%i in (D E F G H ... X Y Z) do set CDROM=%%i: start /wait %CDROM%\Installers_directory\OneProg\setup.exe /silent start /wait %CDROM%\Installers_directory\AnotherProg\install.exe /s start /wait msiexec /i %CDROM%\Installers_directory\MSIProg\msifile.msi /passive start /wait %CDROM%\Installers_directory\OneWinRARSFXinstaller\setup.exe ... :end REM creates RANTAG : echo something>C:\RANTAG explanation : in the unattend guide, Runonce.cmd is ran @ T-12 from cmdlines.txt and creates registry entries to be processed at firt gui boot ; in my method RunOnce.cmd is ran @ first gui boot by Winnt.sif [GuiRunOnce]... PS: example of RunOnceBoth.cmd : @echo off :deb REM checks for RANTAG if exists C:\RANTAG goto :finishhim REM waits about 5 seconds : ping -n 5 127.0.0.1>nul goto deb :finishhim del /f /q c:\RANTAG del /f /q c:\INSTTAG del /f /q %Windir%\RunOnce.cmd del /f /q %Windir%\RunOnceBoth.cmd ++ edit: to create INSTTAG via DetachedProgram= : DetachedProgram="c:\windows\system32\cmd.exe /c ""@echo something > c:\INSSTAG"""