Bilou_Gateux

This method is definitively very interesting. I use a small variant. My WinPE image is stored in a sdi file in a subfolder of my %systemdrive% SDI supports NTFS compression and saves a lot of space. Infos to build SDI file comes from http://www.911cd.net/forums System Deployment Image (SDI) is part of Microsoft Windows XP Embedded, SP2 Update Evaluation Edition. Select Windows XP Embedded SP1 Tools option in download products list.

*** removed ***

Not sure it can be done with standard M$ DOS tools. If you own a copy of Symantec Ghost Solution Suite (or download TrialWare version and grab the DOS gdisk.exe tool from it) You can use this command: gdisk.exe 1 /batch:gd.txt gd.txt: /del /all /cre /pri /for /ntfat16 /q

Thanks for this info. I can now choose english build instead of my localized french OPK i already have.

Windows 2003 Server with SP1 Standard or Web Edition: sysoc.in_

Add text in red

@Alanoll, @prathatml Nice suggestion?

How to run an external program within the same window from a console-mode VBScript

One option i would like to have in xpcreate.ini is ability not to call :EXPANDCABS in the script at all. DOCABS variable from xpcreate.ini is checked in xpcreate.cmd script after extraction of all cabs... It takes a very long time when building a new CD on my PIII 1GHz 512 Mb 20 Gb 5400 tpm build box to expand all cabs do some checks and optionally repack them. In most cases, none of the files inside the cabs are upgraded...

Can you explain the double pipe || in your batch script.

[quote name='jimba' date='Sep 6 2005, 03:22 PM']Hi, it seems that the 20 AUG 2005 version doesnt call the SETVARS part (but :XPCPRVAR instead?) in XPCREATE.CMD and therefore doesnt set the STARTSWITCH variable, which has a desastrous effect on the START cmd sequence... [right][post="385559"][/post][/right][/quote] Altough i haven't searched where the error comes from, i have noticed the same behavior as you on my first try on a Windows XP Embedded running box. (As XP Embedded is a very light version of XP (componentized), may be the reason is due to some required functionality missing. On a different running box (Windows Server 2003 Web Edition), i haven't encountered the same issue. I haven't tried to build on a 2000 running box or regular XP running box. GM répondra mieux que moi à ce problème ! GM will better answer to this issue!

:: stop Automatic Update service NET STOP WUAUSERV :: Reset to force client to perform a detection cycle REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update" /v LastWaitTimeout /f :: start Automatic Update service NEt START WUAUSERV

Thanks for your own version of the script. It's more versatile to search for drivers in a directory in ALL used drive letters rather than specifing CDROM or FIXED.

Windows 2003 Server Web Edition VLK: it works

answer here

Sysprep follow dclive recommandations: 1. Image PCs with the same HAL. Every time you get a new PC type, build it manually and figure out what the HAL is. machines that show the same thing under Device Manager's COMPUTER icon will work fine with the same image. and more infos about: Advanced Configuration and Power Interface (ACPI) detection and MSFT KB article: HAL options after Windows XP or Windows Server 2003 Setup

The best method so far. Try it! Drivers From CD (AutoIt Method), A newer, better way. =) and you can get help from the author: hp38guser.

@Xavierxray No. @all Try Drivers From CD (AutoIt Method), A newer, better way. =) and you can get help from the author: hp38guser.

First add red line to your answer file (ENU language) and remove any surrounding quotes (") to "OEM" find the correct string for Croatian language in TXTSETUP.SIF

A "how to" tutorial which give us details about required plugins is enough. We can then build our own image with BartPE builder and install on local hard drive. If you are using your own created plugins, we may need it (like your shell).

*** removed ***

This feature already exists in WinPE 2005: EMS, Emergency Management Services SAC, Special Administration Console Details are explained in WINPE.CHM Help file on the OPK CD. Copy files Sacsess.ex_, Sacsvr.dl_ and Termcap_ from 2003 SP1 source CD, unpack in folder system32. Copy file Sacdrv.sy_ from 2003 SP1 source CD, unpack in folder system32\drivers. ie: expand d:\i386\sacdrv.sy_ -r e:\winpe\i386\system32\drivers Winpesft.inf [AddReg] ; ; HEADLESS ; HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Svchost",headless,0x00010000,"sacsvr" Winpesys.inf [AddReg] ; ; HEADLESS ; HKLM,"SYSTEM\CurrentControlSet\Services\sacsvr","ErrorControl",0x00010003,1 HKLM,"SYSTEM\CurrentControlSet\Services\sacsvr","ImagePath",0x00020000,"%SYSTEMROOT%\System32\svchost.exe -k headless" HKLM,"SYSTEM\CurrentControlSet\Services\sacsvr","ObjectName",0x00000000,"LocalSystem" HKLM,"SYSTEM\CurrentControlSet\Services\sacsvr","Start",0x00010003,2 HKLM,"SYSTEM\CurrentControlSet\Services\sacsvr","Type",0x00010003,32 HKLM,"SYSTEM\CurrentControlSet\Services\sacsvr\Parameters","ServiceDll",0x00020002,"%SYSTEMROOT%\system32\sacsvr.dll" Startnet.cmd: net start sacsvr Build image. drivers\fbwf.sys looks like same feature as Enhanced Write Filter in XP Embedded.

It sounds very interesting. I have a bunch of older Compaq Deskpro ENS PIII/450MHz which are perfect candidates for this OS. Will you post a tutorial with specific plugins to build this OS?

Have you plugged more than one device (both keyboard and keypad) on your running Windows? etskb.inf is inf file for keyboard: USB\VID_109C&PID_0200&MI_01 etskp.inf is inf file for keypad: USB\VID_109C&PID_0101 because the devcon command should list only the connected USB devices. You can try a modded version of my second batch file here Download driverinstall.exe, extract , change some parts of batch file (findstr without /r), <path_to_inf_file> with actual path): @echo off setlocal for /f "tokens=1-4 delims=\& " %%a in ('devcon findall ^=SmartCardReader ^| findstr "USB\\VID"') do ( set VID=%%b set PID=%%c set MI=%%d set SHORTID="USB\%%b&%%c&%%d" ) rem tokens=1-3 no set MI variable SHORTID=="USB\%%b&%%c" for KeyPad for %%a in (VID_109C) do if "%%a"=="%VID%" goto %%a goto :end :VID_109C echo %VID%: ETS keyboard driverinstall.exe updateni <path_to_inf_file>\ETSKB.INF %SHORTID% rem driverinstall.exe updateni <path_to_inf_file>\ETSKP.INF %SHORTID% goto :end :end endlocal goto :eof Reports the results. If something fails, i would like to make it better. It may fails because you have 2 devices with same VID_109C. The batch may need a loop to install both devices. On my computer, i have only one USB SmartCard reader.

@shalti I think osborned_rcc is right. DEVCON RESCAN works in my batch file because i first delete infos about device in registry with: DEVCON REMOVE This command is equivalent to devmgmt.msc (Device Manager), click on the device, right click, Uninstall DEVCON RESCAN Scan for hardware changes works for new devices not already detected. command1 RunDll32.exe Syssetup.dll,UpdatePnpDeviceDrivers is same as command2 DEVCON updateni <inf> <hwid> This command is equivalent to devmgmt.msc (Device Manager), click on the device, right click, Update Drivers... command1 updates all devices instead of only the one specified with hwid infs files have to be integrated first with Pyron's SetupCopyOEMInf.exe command2 uses specified inf file and update only specified hwid