Martin H

You're welcome, mate MSFN member keytotime has made a guide for making 7z SFX installers : http://www.msfn.org/board/7-Zip-Switchless...ler-t39048.html Then you just follow that, but with these changes : Do not download the '7zs.sfx' module from that guide, but instead use the modified module from the page i linked to earlier(7zsd.sfx). Change '7zs.sfx' to '7zsd.sfx' in the command-line example used in the guide. Do not download 'msistub.exe', since the modified module can run msi installers directly from the 'RunProgram' parameter. You can use the parameter GUIMode="2" to completely hide the exraction dialog normally shown when a 7z SFX installer is run. If you run a batchfile from the 'RunProgram' parameter, then add 'hidcon:' infront of the batchfiles name to completely hide the command-promt window, like e.g. : RunProgram="hidcon:setup.cmd" Instead of just : RunProgram="setup.cmd" For other advanced options, then check the parameter reference listed on : http://7zsfx.solta.ru/en/

7-Zip features two SFX modules; a standard module and one for installers. The 7-Zip file manager i.e. the GUI of 7-Zip, only allows you to configure the standard SFX module and the commands that you are trying to add, is commands specifically for the installer SFX module. Also, it's only the standard module which is included in the 7-Zip installer and the installer SFX module is available as a seperate download on the 7-Zip homepage. However, there are a modified and more advanced version available on this page : http://7zsfx.solta.ru/en/

You are most welcome, mate Unfortunetly i cannot help you with your "Cryptographic Service" issue, as i do not know the answer to that...

If you're removing cat files, then don't... When disabling SFC then the non-driver cat files are redundant, but the driver cat files are needed to avoid popups whenever you're installing hardware which makes use of those specific drivers...

...Just run the installer and retrieve the msi from %temp%

To disable SFC(WFP), then either sfc_os.dll/sfc.dll is patched to disable SFC(with or without needing a reg-entry), or sfcfiles.dll is wiped clean so SFC is enabled, but no files is protected/backed-up. nLite currently patches sfc_os.dll/sfc.dll from '83 F8 9D 75 07 8B C6' to 'B8 9D FF FF FF 90 90' I haven't checked if nLite also modifies other files additionally(sfcfiles.dll), but the above is all that's needed to fully disable SFC. Then nLite also sets this reg-entry : [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "SFCDisable"=dword:FFFFFF9D ...But that reg-entry is useless in our case, as it only needs to be applied when patching sfc_os.dll/sfc.dll from '83 F8 9D 75 07 8B C6' to '83 F8 9D 75 07 90 90' and not in the better(full) way which nLite does.

To fully disable auto-updating, then just use the msi install switch : 'AUTOUPDATECHECK=0'. When using 'AUTOUPDATECHECK=0', then the java update schedular isn't placed into the Run reg key anymore and hence, auto-updating is fully disabled. However, there's a bug in the control-panel, so that it still looks like auto-updating is enabled, but it is in fact absolutely disabled... I personally do not use the ADDLOCAL switch, as i think that the JRE package is way to bloated allready as it is : Here's the config.txt which i use for my 7z switchless silent installer(I use Opera, so i don't need to enable support for any extra browser plugins, as Opera is smart enough to communicate directly with the Java runtime) : ;!@Install@!UTF-8! RunProgram="3ca9116.msi /qn SYSTRAY=0 AUTOUPDATECHECK=0" GUIMode="2" ;!@InstallEnd@!

The MSFN guide states that they need to be in 8.3 format, but however, i have read someone here stating that it dosen't matter, but personally, then i would follow the MSFN guide's advice just in case... Btw, the above is for when you're placing the updates manually into '\I386\svcpack\' and not when you're running a batchfile with a 'for' loop and the '/integrate' switch on the updates, since in that case, then it dosen't matter what they are called... I would personally recommend that you do not manually place the updates into '\I386\svcpack\', as that's not the best way to do it, but instead i would recommend that you check out TommyP's HFSLIP. If you don't want to use HFSLIP, then i would recommend nLite and as the final solution, using a batchfile with the '/integrate' switch.

The following reg-file will disable autorun on optical drives and leave auto-insert-notification unaltered : Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer] "NoDriveTypeAutoRun"=dword:000000B5 However, if you have disabled auto-insert-notification, then you'll need to re-enable it : Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Cdrom] "Autorun"=dword:00000001 Complete reg-file with both reg-tweaks follows here, but if you haven't yourself disabled auto-insert-notification, then only the first reg-file is needed, as auto-insert-notification is enabled by default : Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer] "NoDriveTypeAutoRun"=dword:000000B5 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Cdrom] "Autorun"=dword:00000001

I enable blank password for the built-in admin account and then i add a user with admin rights and enable blank password for that account also, and then i set autologon to my admin rights user account and leave the autologon-count at 0(unlimited). No i haden't thought about that i must admit(your cmd code), but indeed some good thinking there on your part Still, it would be prefferable to get it to work without such hacks Anyway, since it dosen't seem like there is anyone out there that is able to help us with this, then i am thinking about throwing the towel in the ring and simply begin using passwords from now on. My reasoning for preffering to not do this, is simply that my PC is 100% single user only, and so enabling passwords in such a scenario dosen't really make much sence IMHO, but oh well, what can you do Thanks for your help, my friend

@jaclaz Thank you very much for your help, mate

Thank you so much Tomcat76, it's very much appreciated

Hi jaclaz and thanks for your reply I'm affraid i have allready deleted the bad batchfile, when i pasted it into a new one that worked, so i can't do that unfortunetly, but it was a good idea, though, so thanks mate Also, the batchfile where actually only consisting of that one line i pasted, and it where located in a folder with 'AcronisTrueImage.msi' and 'msistub.exe'... I originally made the batchfile by doing these exact steps, so i can't see that there is room for any errors on my side : 1. Right-clicked in the folder with 'AcronisTrueImage.msi' and 'msistub.exe' and selected 'New > Text Document'. 2. Changed the default name to 'setup.cmd' and pressed return and answered 'Yes' to the warning about changing the file-extension away from '.txt'. 3. Right-clicked on 'setup.cmd' and selected 'Edit', so it opened up empty in notepad.exe. 4. Typed the command-line and pressed 'Ctrl+S' to save it and closed the batch-file. Btw, i posted that it worked in WinXP, but that was actually wrong(sorry about that), as i was just sure that the problem was comming from Win2K, as i had just changed to it and had never had this problem before with other batchfiles on WinXP, but to make sure, then i ghosted my system partition back to WinXP and then tried the batchfile from there and it also there had the exact same problem... Anyway, atleast i don't have the problem anymore... I just kick myself, for being so stupid as to delete the original bad batchfile, so that i cannot try out jaclaz's good advice...

I have just recently changed from WinXP to Win2K and now i have a big problem that i do not understand ? I have a batchfile which installs a program silently, but when i doubleclick on the batchfile, then it just blinks, and when i then add a pause command to see the error report, then i can see that it won't run because there has been inserted some strange symbol at the start of the batchfile. It works fine in WinXP and when i open the batchfile in Win2K in notepad.exe, then there isn't that strange symbol. I would really be gratefull if someone could tell me whats the cause and maybe solution for this. Here is the copy/pasted output of the batchfile when it fails : D:\Backup\Programs\Acronis_True_Image_Home_v9.0.3677>n++msistub.exe AcronisTrueI mage.msi /qn PIDKEY=XXXXX-XXXXX-XXXXX-XXXXX /norestart 'n++msistub.exe' is not recognized as an internal or external command, operable program or batch file. Btw, it didn't looked like that originally in the cmd prompt, but more like a strange symbol of some sort, but after i had saved the output into a txt file, then when i now open the txt file to post the contents into this post, then the symbol has been changed by notepad.exe to that n++ Thanks in advance. Edit : When i then copy/paste the contents of the batchfile into a new batchfile that i make in Win2K, then that new batchfile also will not run. Edit2 : Hmm, very weird, but i have gotten it fixed now thankfully First i copy/pasted it over to another batchfile and that didn't work. then i tried the exact same thing again to a third batchfile and then it finally worked and didn't showed that strange behaviur anymore ??? So, i don't have an issue anymore, but still, if someone knows what was causing this strange phenomina, then i would be very interessted in hearing it...

Thank you very much Tomcat76 CU, Martin.

Hi Arie, and many thanks for your help Yes, you are of cource perfectly right in that, but however my problem where that my boot image file where named boot.img instead of the needed boot.bin. PS: Actually i also wanted to thank you for something else, as it was by reading some of your posts where you mentioned HFSLIP, that got me to check it out, so i just wanted to say many thank's for that, mate Hi tommyp, and many thanks for your help Firstly, i apologize for asking about the "i have read the instructions" part, as i of course should have searched about it before posting... Then, i have now reverted to using a completely clean source in the SOURCE folder now and then placed my patched 'SFC.DL_' file in '\REPLACE\I386\' folder and it's copied over and overwriting the old one perfectly, but however, i do not get any prompts about the catalog files whatsoever ? Also, from looking at the source, then it seems to me that this is also normal, as the prompting about catalog files should only happen in other cases, like e.g when using the unofficial SP5(W2K) or having the patched dll in the FDVFILES folder etc. Am i completely wrong here ? :DELCATS IF "%DELCATS%"=="0" GOTO :START IF "%DELCATS%"=="1" GOTO :START IF EXIST FDVFILES\SFC* SET SFCFIX=1 IF EXIST "%ALTSRCDIRS%FIX\SFC*" SET SFCFIX=1 IF EXIST "%ALTSRCDIRS%HFEXPERT\APPREPLACEMENT\SFC*" SET SFCFIX=1 IF EXIST HF\w2ksp5* SET SFCFIX=1 IF NOT DEFINED SFCFIX GOTO :START Hi Tomcat76, and many thanks for your help Yeah, it's offical - i'm a complete moron My boot image where called boot.img and not boot.bin and i haden't even noticed the difference, even though i read the code! Also, i apologize to you, for not having read the instructions and code more propperly before asking about it here... Again, many thanks to all of you guys for your kind help, it's very much appreciated CU, Martin.

Sorry, in my previous post then i forgot to say what i had actually done to mimick nLite's behaviur... Instead of using a batch file and a reg file, then i just made a reg file which handled everything. Btw, the 'sfcdisable' reg-entry' is just because i am disabling SFC(WFP) with a pached SFC.DL_ in my \I386\ folder, and it has nothing to do with my current issue... I haven't even comed to the part where i am adding tweaks to my CD, since i can't even get this freakin' autologon thing working ...Never thought that doing things manually would be so difficult, i must confess Again, if someone can help, then i would be very gratefull WINNT.SIF : [GuiUnattended] [...] EncryptedAdminPassword="No" AutoLogon="Yes" AdminPassword=* [...] cmdlines.txt : [COMMANDS] "regedit /s setup.reg" setup.reg : Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "DefaultUserName"="Martin Hertz" "DefaultPassword"="" "AutoAdminLogon"="1" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce] "command1"="cmd /c net user Administrator /passwordreq:no" "command2"="cmd /c net user \"Martin Hertz\" /add /passwordreq:no" "command3"="cmd /c net localgroup Administrators \"Martin Hertz\" /add" "command4"="cmd /c net accounts /maxpwage:unlimited" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "SFCDisable"=dword:FFFFFF9D I can see why this won't work(as the account i'm trying to log into, isn't even made yet, at that time), but from looking at the NLIE.INF which i posted some posts above, then i believe that this is exactly what nLite is doing ???

Well, i have just finished testing an ISO of what i believe that nLite is doing and it didn't work. It showed a logon-screen with my name pre-entered and an error box stating that something was wrong with either the password or username or something. I can also see why that is, since that account hasen't even been made yet, and so i just changed to the built-in admin account and logged in and then my RunOnce commands where executed and my user account created, but still no autologon at the next reboot... This is really annoying to not have a clue about how to fix this issue... Anyway, again if anyone can help me out here, then i would be most gratefull

Firstly, i just wanted to say many thanks to TommyP and Tomcat76 and whoever else has contributed, for making/maintaining this awesome tool I have only just started using it a couple of days ago, but am allready just absolutely loving it, so nice work guys Anyway, i have a couple of newbie questions, so if anyone would kindly help me out alittle with this, then i would be very gratefull... OK, the first thing is the automatic ISO creation. I have read the instructions on the HFSLIP homesite and also looked at the cmd syntax of HFSLIP, and so i placed cdimage.exe + boot.img into the HFTOOLS folder, but however, no ISO is made in the HFTOOLS folder ? I then just in case for testing tried to also place bbie.exe into HFTOOLS folder(even though i can see from the cmd syntax that it's not needed when having boot.img there, but nonetheless...) but still no success... Second, then i have a patched SFC.DL_ file(i'm using Win2K) in my 'SOURCE\I386\' folder, but HFSLIP dosen't ask me if i want to remove catalog files or not ? Third, then i would like to make a feature request about if you would please consider adding sections for also bypassing the return prompts(pause commands) and the 'i have read the instructions' input line, into the HFANSWER.ini file, so that we don't have to go into the cmd syntax of HFSLIP and make these changes directly ourselves anymore. That was it, and again, many thank's for HFSLIP and for all your efforts

...Just wanted to say that i have just finished running 2 VMware sessions with the above mentioned change, one with autologon=yes in winnt.sif and one without, and they both don't work i.e. they don't enable autologon for the admin rights user account. So, the only conclusion to draw then, must be that the solution lies in nLite running the cmd commands for making the admin rights user account from the built-in admin account at T-0(RunOnce), and not at T-12(cmdlines.txt) as i do. However, i'm pretty tired now, so i'm first going to test it out tomorrow evening though...

Hi dll32 Yes, i'm sure, as i have always configured auto-logon to be enabled in nLite and i have also always defined blank passwords for both the built-in admin account and the admin rights user account. Anyway, i have now checked my previous nLite ISO, to see what nLite is doing behind the scenes... OK, this is for a config with one admin rights user account in addition to the built-in admin account and with both of them having blank passwords and set to never expire(in nLite that is) : Relevant part from '\I386\WINNT.SIF' : [GuiUnattended] EncryptedAdminPassword="No" AutoLogon="Yes" AdminPassword=* Relevant part from '\I386\NLITE.INF' : ('NLITE.IN_' uncabbed) HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon","AutoAdminLogon",0x00000000,1 HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon","DefaultUserName",0x00000000,"Martin Hertz" HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon","DefaultPassword",0x00000000,"" [...] HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce","nlite_post_00",0x00000000,"nhelper net1 accounts /maxpwage:unlimited" HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce","nlite_post_01",0x00000000,"nhelper net1 user """"Administrator"""" /passwordreq:no" HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce","nlite_post_02",0x00000000,"nhelper net1 user """"Martin Hertz"""" /add /passwordreq:no" HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce","nlite_post_03",0x00000000,"nhelper net1 localgroup """"Administrators"""" """"Martin Hertz"""" /add" Ahh, i think i'm beginning to see the big picture now, or atleast i hope so From this(and the cmdlines.txt which i didn't posted), then i can see that what nLite does, is to set winnt.sif so that the built-in admin account is logged into once, and then at T-12(cmdlines.txt), then NLITE.INF is executed and that defines some cmd commands to be run at first logon after the installation(from the 'HKLM\[...]\RunOnce' reg-key), and those cmd commands are almost identical to the ones that i run at T-12, except for these two : net user "Martin Hertz" /add /passwordreq:no net user Administrator /passwordreq:no So... The solution obviously is about defining that extra "no passwords needed" switch which i haden't, whenever using an account with blank passwords. Just strange that the MSFN unattended guide which i have studied so much dosen't mention anything about this ??? Anyway, i'm just happy to have something to try out now, so now i'm off to VMware for testing this possible solution out in real life I'll post back here when i have tested it out... CU, Martin.

Thank you very much for your reply, mate Yes, i had actually also read that in the specification, but i'm still positive that there's a way around it still, since nLite can do this with all passwords blank, but i just don't know how(admin rights user account + built-in admin account with both blank passwords). I had actually also tried a quick test with giving the built-in admin acount a password in winnt.sif just to test it and it didn't worked either, but i also didn't define a password for the actual user account which i wanted to auto-logon. Still, if it would have worked, then i wouldn't have used that solution anyway, as it was just a test to see if it would work or not... Anyway, i'm sure that this can be done with still having blank passwords, since nLite must be doing it somehow, but i would really appreciate any more input on this still from you guys. nLite can autologon fine also with only having a single account i.e. the built-in admin account with blank password, so there got to be a way ??? Again, many thanks for your reply dll32

I have previously always used nLite to define all my unattended settings and user account creation, but i have now decided that i will stop using nLite, since i will not be stripping my source down anymore and i additionally have changed from WinXP to Win2K. Anyway, so from now on then i'll just manually make the winnt.sif and use HFSLIP to update my source, but unfortunetly then i cannot get auto-logon to work for me. I have listed the contents of the relevant files which i use below, and so i would really appreciate if someone would be so kind as to help me out alittle here with this issue of mine. I have also tried with adding AutoLogon="Yes" into winnt.sif, but that will just autolog me in once as using the built-in admin account and then at next logon i'm presented with the logon screen. To me, then it would seem that my files should make it so that a user with admin rights are made at T-12 together with the needed reg entries for enabling autologon for that user, and so since i don't have AutoLogon="Yes" enabled in my winnt.sif, then i would think that autologon would work fine(since AutoLogon="Yes" is only reffering to the built-in admin account only, and since it will only work once when having a blank password defined for the built-in admin account), but unfortunetly it dosen't ? WINNT.SIF : ;SetupMgrTag [Data] AutoPartition=0 MsDosInitiated="0" UnattendedInstall="Yes" [Unattended] UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=No TargetPath=\WINNT [GuiUnattended] AdminPassword=* OEMSkipRegional=1 TimeZone=105 OemSkipWelcome=1 [UserData] ProductID="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX" FullName="Martin Hertz" ComputerName=* [RegionalSettings] LanguageGroup=1 Language=00000406 [Identification] JoinWorkgroup=WORKGROUP [Networking] InstallDefaultComponents=Yes cmdlines.txt : [COMMANDS] "useraccounts.cmd" useraccounts.cmd : net user "Martin Hertz" /add net localgroup Administrators "Martin Hertz" /add net accounts /maxpwage:unlimited regedit /s autologon.reg autologon.reg : Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "DefaultUserName"="Martin Hertz" "DefaultPassword"="" "AutoAdminLogon"="1"

No, you don't...

http://www.msfn.org/board/7-Zip-Switchless...ler-t39048.html ...the forum search/google could easilly have provided you with the same link