Snappy Driver Installer 2. Chocolately application installer 3. You can create these files (any size or content) in the CONFIGSXXXX folder to control SDICHOCO (e.g. NoInternet.TAGDuring the Specialize phase (e.g. SDICHOCO.cmd and MySpecialize.cmd), full network functionality may not be available.Connect an Ethernet cable and add the NoInternet.tag file. Settings in the XML file can affect this behaviour.Can also use OfflineChoco.tag. Windows 8.1:Use NoInternet.TAG + OfflineChoco.TAG.

Chocolatey.nupkg is required. Windows 7Use NoInternet.TAG + OfflineChoco.TAG + NoWSUS.TAG. Use E2B v1.B9 or later. Chocolatey.nupkg is required.For Windows 7 you must add the Offline package file for. Download and add ISOWINDWSinstallsINSTALLCHOCO NDP452-KB2901907-x86-x64-AllOS-ENU.exeOr follow these instructions for fully updated Win7 ISO.(instructions courtesy of Nathan):.

In this article, I will show you how to install Chocolatey on Windows 10. Chocolatey is an easy-to-use Software Package Manager for Windows similar to apt on ubuntu/debian or brew on OSX. Steps to Install chocolatey/choco on Windows 10 Click Start and type “powershell“ Right-click Windows Powershell and choose “Run as Administrator“ Paste the following Read More.

You must update the Win7 ISO first using. Download or later. Also download UpdatePack7R2-20.2.21.exe from the first post. Recommended download to help with choco install otherwise SDICHOCO script will look like its frozen while it downloads.net and installs it. Optional downloads not required but can help later. Remember to download 32 or 64 bit versions where available to match your iso. Do not download the following as it causes issues with SDI and crashes computer. Getting StartedHere are the steps you need to prepare the E2B drive for SDI, choco and WSUS: Prepare your E2B USB drive for SDICHOCO1.

This feature works when using standard Microsoft Windows Installer ISO or.imgPTN files. It may work with some other ISOs (or may not!).You need to have either:. A large E2B USB 'Removable' type Flash drive + Windows Installer ISO files (recommended)OR. An E2B USB Hard Drive + Windows Installer ISO files + a small 'Removable' type USBIf you are using a 'Fixed Disk' type of USB drive and E2B v1.A8 or later, you will need 2GB+ of RAM (No WinHelper drive required).OR. An E2B USB drive with Windows installer.imgPTN files (see end of this page)Note: If using a Virtual Machine, use E2B v1.A8+ and2gb+ of RAM. Take care not to wipe the USB drive!Copy a suitable Windows 8.1 or 10 ISO file to the E2B ISOWINDOWSWIN8 or WIN10 folder, if not using.imgPTN files.Note: There are internet connectivity bugs in some Windows 10 TH2 and Anniversary ISOs.If you now try one of the SDICHOCO XML files, it will work, but it will not yet install any extra drivers or applications or updates.2. (optional) If you want to install missing, newer or 'better matched' drivers, we must first download all the SDI Driverpacks (approx.

Benz New EPC & EWA Net Keygen Key Generator Free Download January 4, 2018 auto Auto Software Download & Installation 0 Here I share the Mercedes Benz EPC & EWA Net Keygen download link.This software without protection can move any device/hardware.

13GB) onto the E2B drive.This can be done on any Windows computer. Double-click on a ISOWINDOWSINSTALLSSNAPPY SDI.exe file to start the Snappy GUI (64-bit is faster). Accept the Windows Firewall prompt. Now click on (click here to start the download), tick the Application and Indexes boxes and select all the Driverpacks you want. Download all the Driverpacks and latest SDI.exe files ( do NOT click on the green Install button!). Or - if you wish, you can download the latest full SDI version with all drivers and then copy the files to the E2B USB drive.Once finished, I suggest you make a backup copy, in case you lose your E2B drive, to save having to download the driverpacks again.Note: You should select for download the latest version of SDI (tick ' application') and the latest Index.

You can delete older versions of the SD??????exe files and just leave the latest version (one 32-bit and one 64-bit) - SDICHOCO will always use the most recent.exe file that is in the folder.The sdi.cfg file determines the Snappy settings. E2B uses a default sdi.cfg setting which installs drivers which are 'Not installed', 'Newer' or a 'Better match'.Note that some drivers can cause problems, so you may find it best to omit the ones that can be difficult to identify correctly - the Touchpad driver can often cause problems as often notebooks require a very specific version. You may also wish to omit any graphics drivers too. You can delete the driver.zip files if you have already downloaded them.To change the settings, simply run the SDI executable and tick/untick the boxes. This will change the sdi.cfg file.Note: Updating E2B will restore the default settings. You may wish to copy your sdi.cfg to Mysdi.cfg so that you have a copy.Note: Latest versions seems to have a 'GNU GENERAL PUBLIC LICENCE' EULA which requires you to click on the Accept button. Make sure you do this before starting an automated install.3.

How to install bespoke drivers (example for Lenovo)In my experience, specialized products such as notebooks, tablets, netbooks, etc. Require bespoke drivers.They also require additional drivers which are not inluded in SDI, such as ACPI and hotkey drivers.I would highly recommend that you always use the correct manufacturers drivers for these products.Lenovo provide Windows 10 downloads for the IdeaPad 300 notebook in the form of executables.1.

These must first be extracted as follows:. Double-click the.exe file to run it. Click NextOK to extract the files to the C:DRIVERS folder - I suggest you rename the folder name and remove any spaces. Do NOT proceed to install the drivers - untick the box and click Finish.Do this for each of the drivers/applications.2.

Create a ISOWINDOWSINSTALLSCONFIGSSDICHOCONoSDI.tag file to prevent the Snappy SDI from installing the generic drivers. Install your own packagesYou can install applications by adding the packages to your E2B drive first.You can download application install files from. Choose the versions you want and copy them to the E2B USB drive's ISOWINDOWSINSTALLSAPPS folder (use sub-folders for each one, e.g. MyStartup.cmd is only required to be changed if you do not copy any.cmd file to the C:DRIVERSAPPS folder.So if you did not copy any.cmd file to%systemdrive%DRIVERSAPPS to install FoxIt, then you need to add the silent install command into MyStartUp.cmd - e.g.start /wait C:DRIVERSAPPSFOXITFoxitReader734enuSetupProm.exe /silentThe advantage of installing apps directly, is that internet access is not required and you can disable choco (using NoChoco.tag). The installation is thus completely offline.Note: StartUp.cmd already contains the lines::: - BESPOKE APP INSTALL -:: Install any apps we have added - run all.cmd files in DRIVERSAPPS folder.FOR%%I IN (%systemdrive%DRIVERSAPPS.cmd) DO CALL:loopbody%%I. You may also wish to use to install applications. If you use the Pro version you can use the /Silent switch to install apps silently and /freeze for offline installs.

Silent Install switchesMost installation packages will accept parameters so that they will install automatically without requiring any user input (e.g. App.exe /s).The parameters that you need to use can be found using Google or you can use the application (may be outdated) or search the for installation tips.Install Choco applications offlineIf you install choco (either online install using the standard SDICHOCO cmd script or an offline install of the choco package), then you can point choco at an offline choco package (e.g. Make a new XML file for your system or find an existing SDICHOCO.xml fileMake sure it has a RunSynchronous section for the Specialize pass which runs your CONFIGSxxxx.cmd file (look at one of the existing xxxxSDICHOCO.XML files for reference).If your XML file does not have a Microsoft-Windows-Deployment component entry, simply paste one in directly under the line for both x86 and amd64 components.Note: If there are already RunSynchronous entries, make sure you change the x Order number!Make sure you change 'SDICHOCO.cmd' to 'DellXPS27Dev.cmd' ( four places).5. Now you can edit the My.cmd files to install applications or drivers (use the SampleMyxxxxx.cmd files as templates).The config control files that you will need to edit/add for each configuration are.TAG and My.cmd.Using SDICHOCO with.imgPTN files (for UEFI booting).

(optional) Create a e2bMyConfig.cmd file and add a 'set CONFIG=' line as the name of your main configuration file - e.g. If you want it to run ISOWINDOWSINSTALLSCONFIGSIdeaPad300.cmd, then use:set CONFIG=IdeaPad300.cmdIf you don't create a MyConfig.cmd file, SDICHOCO.cmd will be used.6. Ensure that RMPartUSB.exe and FindCSMandRestoreE2B.cmd are present in the e2b folder. Ensure that WINHELPER.USB does NOT exist.Required files:Unattend.xmle2bStage1.cmde2bStage2.cmde2bFindCSMandRestoreE2B.cmde2bRMPartUSB.exee2bMyConfig.cmd (optional) IMPORTANT: Note that the XML file needs to be named Unattend.XML if it does NOT contain a WindowsPE configuration pass, or AutoUnattend.xml if it does contain a WindowsPE pass.

Required files (when boot.wim is mounted under Windows):C:mount1Unattend.xml (or AutoUnattend.xml)C:mount1e2bStage1.cmdC:mount1e2bStage2.cmdC:mount1e2bFindCSMandRestoreE2B.cmdC:mount1e2bRMPartUSB.exeC:mount1e2bMyConfig.cmd (optional)Note: The Unattend.XML file must contain a Specialize RunSynchronous section that looks for and runs e2bStage1.cmd and not the SDICHOCO.cmd file (see included example in the MPI.csme2b folder). IMPORTANT: Note that the XML file needs to be named Unattend.XML if it does NOT contain a WindowsPE configuration pass, or AutoUnattend.xml if it does contain a WindowsPE pass. How it worksWhen the E2B drive boots, the original E2B partition is hidden. Windows can only see the.imgPTN partition. Stage1.cmd first copies Stage2.cmd and some other files to the target hard drive (C:DRIVERS). It then runs Stage2.cmd.

Stage2.cmd runs from the hard drive and calls FindCSMandRestoreE2B.cmd which switches back the E2B drive to 'E2B Mode' - this makes the E2B drive contents and the ISOWINDOWSINSTALLS folder accessible. Stage2.cmd then locates the E2B USB drive and calls the required configuration file - e.g. ISOWINDOWSINSTALLSCONFIGSSDICHOCO.cmd. From then on, the process is the same as if you installed from an ISO file.Note that the next time you boot to E2B from the USB drive, it will be in 'E2B Menu mode' and not 'CSM Menu mode'.The Stage2.cmd file will look for a USB E2B drive which will only be found if the drive is detected as a USB drive. For this reason you cannot use a VM which configures the E2B USB drive as a hard disk instead of a USB drive (e.g. Use VMWare and allocate the E2B USB drive as an attached USB drive and boot from it via UEFI.

The 'no internet' problemThe first release of Win10 TH2 did not correctly set up the network interface when it reached the Specialize phase during Windows Setup. Microsoft fixed this in later versions of TH2.Windows 8.1 did not have this issue.Microsoft have also repeated the same mistake(!) in the first release of the Anniversary version of Win10!SDICHOCO attempts to get round this by running msoobe for ten seconds and then killing msoobe. This seems to fix the problem.If there is still no internet connectivity and you are installing Win10, SDICHOCO will launch msoobe again which allows you to set up a WiFi connection (if not disabled in the XML file settings using true). Once you have done this, use ALT-TAB to switch back to SDICHOCO and press ENTER to continue. SDICHOCO will then terminate msoobe.If you only install apps using choco using MyStartup.cmd, you may be able to avoid this issue because the internet connection may be working by then!Tip: Add the file NoInternet.TAG to the ISOWINDOWSINSTALLSCONFIGSSDICHOCO folder to stop SDICHOCO from checking for internet access and launching msoobe. You can add offline choco application packages. Changing the ComputerName.

LoggingLog files will be present in the C:Temp folder. Some errors may be logged in separate.ERRORS.log files.C:TempSDICHOCO.logC:Tempsetupcomplete.logC:Tempstartup.logC:TempSDICHOCO.cmd - a copy for reference onlyIf the main SDICHOCO.cmd file was run (or whatever config set was specifified in the XML file) the file C:WINDOWSDONESDI.tag will be present. If that file is not present, then the XML entry was not executed, so there was a problem in the XML file!Tip: If some of the.log files seem to be missing some lines and start with text generated by lines of code that you have written, check for syntax bugs in your code where you have written %log% instead of %log%!!!Debugging and Troubleshooting. If you place the command ' echo on' at the beginning of a file, it will allow you to see what happens in your MySpecialize.cmd and MyStartUp.cmd.Use ' pause' to stop execution until you press ENTER to continue.Also, remove any %log% text from your MySpecialize.cmd and MyStartUp.cmd files if you want to see any output from the commands.For instance, if you have a line of code which does not seem to work, such as:xcopy /herky%USB%ISOWINDOWSINSTALLSDRIVERSIDPAD300W81064.%systemdrive%DRIVERSIDPAD300W81064 nul. Xcopy /herky%USB%ISOWINDOWSINSTALLSDRIVERSIDPAD300W81064.%systemdrive%DRIVERSIDPAD300W81064echo xcopy has runpauseecho offand start an installation. You should find that when the script file is run, it will stop at 'About to run xcopy', then press ENTER and it should copy the files over using xcopy and then stop again with the message 'xcopy has run'.

This will allow you to see if the xcopy worked or reported an error. Finally, press ENTER again and the installation will continue.When it is all working, you can remove the extra lines.The script files, SDICHOCO.cmd and startup.cmd both start with the line ' echo off'.

This stops all the commands from being displayed in the console. If you wish, you can change ' echo off' to ' echo on' at the start of these files, so that you can see all the commands being executed.

About Choco SolverChoco is a Free and Open-Source Software dedicated to Constraint Programming.It is written in Java, under license.It aims at describing real combinatorial problems in the form of Constraint Satisfaction Problems andsolving them with Constraint Programming techniques. Structure of the main packageYou can download on the website of Choco Solver.You will get a zip file which contains the following files: choco-solver-4.10.2.jar A ready-to-use jar file including dependencies;it provides tools to declare a Model, the variables, the constraints, the search strategies, etc.In a few words, it enables modeling and solving CP problems.

Choco-solver-4.10.2-no-dep.jar A jar file excluding all dependencies and configuration file;Enable using choco-solver as a dependency of an application.Otherwise, it provides the same code as the jar with dependencies. Choco-solver-4.10.2-sources.jar The source of the core library, to be loaded in your favourite IDE to benefit from the javadoc while coding. Choco-samples-4.10.2-sources.jar The source of the artifact choco-samples made of problems modeled with Choco. It is a good start point to see what it is possible to do with Choco. Apidocs-4.10.2.zip Javadoc of Choco-4.10.2 logback.xml The logback configuration file; may be needed when choco-solver is used as a library.Please, refer to README.md for more details.