Easy2Boot v1.82SDIf Beta now available

Version 1.82f does not install any choco applications by default now (i.e. Google Chrome and TeamViewer are not installed by default).

I think that v1.82 is getting good enough for release now, so please test and provide feedback.
I am still waiting for a grub4dos bugfix though.

With this version of E2B, you must now install choco applications (or bespoke apps or drivers) by creating one or more of these three Myxxxxxx.cmd text files in the  \_ISO\WINDOWS\INSTALLS\CONFIGS\SDI_CHOCO folder:

• MySpecialize.cmd  - this runs just after Windows Setup at the 'Specialize' stage as User='System' - no user profiles except for 'Public' have been set up. It is best to only install drivers here.
• MySetupComplete.cmd - this runs just before the first user login at the end of setup. The User  profile(s) will not be set up at this point. No console will be visible and no mouse pointer visible - for this reason it should not stop.
• MyStartup.cmd   - this runs once on first user login with Administrator rights. This is the best place to install choco apps. It also runs WSUS offline updater (if you have added it - see previous blog post).

This means you can now easily modify the SDI_CHOCO configuration and when you update E2B with a new version, you will not lose your changes because these three files are not included in the E2B download.

I have provided three Sample_xxxxxx.cmd files for each of these, which you can use as a template (copy and rename each one).

Notes: 

• If the file NoWSUS.TAG is present, then WSUS Offline Installer will not run (even if you have added WSUS to your E2B drive)
• If the file NoSDI.TAG is present, then the Snappy driver installer (SDI) will not run
• If the file NoChoco.TAG is present, then Chocolatey (choco) will not be installed and any choco commands in any of the three Myxxxx.cmd scripts will not work.

Using MySpecialize.cmd, you can copy files and folders from the USB drive to the C:\ drive (e.g. C:\DRIVERS). Then you can use those files to install drivers, applications, etc.

For instance, you can add in your own bespoke Drivers and App install files.

I have also placed a text file in the SDI_CHOCO folder:
          How to add applications and drivers.txt
which has more information and examples. 

Another change is that if the WSUS Offline Updater was run, the system will automatically restart at the end of the installation so that the Windows updates are fully installed.

Example - How to add Chrome and Teamviewer

So for a simple example. let's say we want to install Chrome and Teamviewer whenever we use an 'xxxxxxxxxxxSDI_CHOCO' XML file...

Simply create a new text file called MyStartup.cmd (you can use the Sample_MyStartup.cmd as a template) - e.g.

\_ISO\WINDOWS\INSTALLS\CONFIGS\SDI_CHOCO\MyStartup.cmd

containing the text:

choco install googlechrome -y -r

choco install teamviewer -r -y

That's it!

If you want it to log the result and have it speak too, use:

echo Installing Google Chrome...

%systemdrive%\DRIVERS\nircmd.exe speak text "Downloading and installing Google Chrome"

choco install googlechrome -y -r >> %log%

echo Installing TeamViewer...

%systemdrive%\DRIVERS\nircmd.exe speak text "Downloading and installing Team Viewer"

choco install teamviewer -r -y >> %log%

If you want it to prompt you, so that you can decide which apps to install each time, then do not specify -y, use:

%systemdrive%\DRIVERS\nircmd.exe speak text "Please select which applications you want to install"

choco install googlechrome

choco install teamviewer

Look at the Sample_xxxxxx.cmd files for more examples.