Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations


Posts posted by Bilou_Gateux

  1. Here correct data to use for some values:



    PVConfigs should be set to 2 to indicate that you intend to protect two partitions. PVDisk and PVPart are both REG_MULTI_SZ values. Since you intend to protect {disknumber, partnumber} = {0, 1} and {0, 2} , specify 0 0 for PVDisk and 1 2 for PVPart. Edit using regedit and specify one per line.

    Srikanth Kamath [MSFT]



    I can confirm with my SCT install:


    enabled EWF Disk Mode protects Disk0 Part1 with an overlay size of 8 Gb (8 x 1000 x 1024) decimal 8192000, in hex notation 0x007d0000:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ewf [30 31 1 17]    Group = System Bus Extender    Start = REG_DWORD 0x00000000    ErrorControl = REG_DWORD 0x00000001    Type = REG_DWORD 0x00000001    FBA [30 31 1 17]        PVConfigs = REG_DWORD 0x00000001        OVSize = REG_DWORD 0x007d0000        OVLevel = REG_DWORD 0x00000001        EnableLazyWrite = REG_MULTI_SZ "1"         PVPart = REG_MULTI_SZ "1"         PVType = REG_MULTI_SZ "0"         PVDiskType = REG_MULTI_SZ "0"         PVOptimize = REG_MULTI_SZ "0"         EwfEnable = REG_MULTI_SZ "1"         PVDisk = REG_MULTI_SZ "0" 
  2. I am not sure to get the final "scope", EWF is also not "free", there are a bunch or commercial apps besides DeepFreeze that may do what you need:



    Maybe among them you can find something that can do what you actually want to do.


    Microsoft Shared Computer Toolkit for Windows XP, the predecessor to Windows SteadyState was "free".

    This application [sCT] has been discontinued.

    From the FAQ http://www.microsoft.com/windowsxp/sharedaccess/faq.mspx

    The Enhanced Write Filter (EWF) Volume was not created when Windows Disk

    Protection was initialized. This is likely due to a disk configuration on the

    computer that is not supported by EWF.

    The EWF is an essential component of the Windows Disk Protection feature. It

    protects a disk partition from being written to. It contains two major


    • EWF Overlay: EWF protects the contents of a volume by redirecting all

    write operations to another storage location. This location is called an

    overlay. The toolkit uses a particular mode of EWF that always attempts to

    store the EWF Overlay in the unallocated disk space.

    • EWF Volume: In addition to the EWF Overlay, the EWF Volume stores

    configuration information about all of the EWF-protected volumes on the

    device, including the number and size of protected volumes and overlay

    levels. The toolkit uses a particular mode of EWF that always attempts to

    store the EWF Volume in the unallocated disk space.

    If the disk configuration on the computer contains both an unallocated space

    and an extended partition, the unallocated space is not considered for the

    EWF Volume, only the extended partition is considered. If no free space is

    available in the extended partition, the EWF Volume will not be created.

    If your computer’s disk configuration is not supported by EWF, use a disk

    partition program to change the disk partition configuration to the

    recommended configuration in the Microsoft Shared Computer Toolkit for

    Windows XP Handbook, or to expand the size of the extended partition.

    During initial installation, EWF [2.0.927] is configured but not enabled (done after reboot when setting Disk Protection)

    reg dump:

    HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\ewf [1 31 17 30]    ErrorControl = REG_DWORD 0x00000001    Group = System Bus Extender    Start = REG_DWORD 0x00000000    Type = REG_DWORD 0x00000001    Tag = REG_DWORD 0x00000010    FBA        PVConfigs = REG_DWORD 0x00000001        OVSize = REG_DWORD 0x00000000        OVLevel = REG_DWORD 0x00000001        EnableLazyWrite = REG_MULTI_SZ "1"        PVPart = REG_MULTI_SZ "1"        PVType = REG_MULTI_SZ "0"        PVDiskType = REG_MULTI_SZ "0"        PVOptimize = REG_MULTI_SZ "0"        EwfEnable = REG_MULTI_SZ "0"        PVDisk = REG_MULTI_SZ "0"
  3. Create LIS (Local Installation Source) to default path %SystemDrive%\MSOCache from Office 2003 slipstreamed with SP3 :

    SET SOURCE_PATH=<replace_with_source_path_here>
    %source_path%\setup.exe CDCACHE=2 DELETEABLECACHE=0 PURGE=0 CACHEONLY=1

    Office 2003 setup.exe (enhanced version) version 11.0.6176.0

    Source is built with:




    Method=Direct Integration

    Service Pack=Service Pack 3 (SP3)

    KB923618=Office 2003 Service Pack 3 (SP3)


    for localized versions of Office 2003, office2003-KB943452-FullFile-xxx.exe had to be integrated to avoid issues:


  4. FP_AX_CAB_INSTALLER.exe -install

    Flash Player 10.1 (Argo)

    With the release of Flash Player 10.1, the command line arguments have significantly changed. Users are no longer required to use the -clean/-force argument to force a complete uninstall of the Flash Player when using the standalone uninstaller. However, when using the FlashUtil.exe to uninstall, the user is still required to use the -force argument to perform a complete uninstall.

    Note: The arguments listed below only apply to the EXE installer, not the MSI installer.

    The new command line arguments are:

    -install: Perform a silent install of the Flash Player.

    -uninstall: Perform a silent uninstall of the Flash Player.

    Note: These can be used with the standalone uninstaller, or with the FlashUtil .exe in \Macromed\Flash directory

    -uninstall {activex | plugin}: Perform an uninstall of a specific player, either ActiveX (Internet Explorer) or plugin (other browsers).

    Note: This can be used with the standalone uninstaller, or with the FlashUtil .exe in the \Macromed\Flash directory.

    Note: When uninstalling a specific player, a specific player type must be used in conjunction with the silent -uninstall argument, else it will not work and both player types will be uninstalled.

    Flash Player 9 ( to (Coral).

    The utility file FlashUtil.exe is installed with Flash Player to in the C:\Windows\system32\Macromed\Flash directory. FlashUtil.exe includes functionality required by Windows Vista and by the auto-update notification process. The previous utility (UninstFl.exe) is no longer required by or installed with Flash Player.

    The utility is versioned with the control. For example, FlashUtil9b.exe is installed with the control Flash9b.ocx. FlashUtil.exe also contains several options that developers can use to switch between player and debugger versions during testing. Developers can modify the default behavior by using the following command-line flags:

    USAGE : %s [-uninstallUnlock] [-uninstallLock] [-uninstallControlPath] path]

    If run with no flags , the auto-update notification dialog will appear.

    -uninstallUnlock: unlock the control. Grant write/delete permission to OCX and registry keys without erasing files.

    -uninstallLock: lock the control. Deny write/delete permission.

    -uninstallControlPath path: Optional; override the default path to the control. Must be used in conjunction with one of the other flags. If omitted, the path is located based on registry information.

    The default path is located in the registry key of:


    For example, C:\Windows\system32\Macromed\Flash\Flash8b.ocx

    The use of FlashUtil*.exe with the locking control is best illustrated with an example situation: While developing and testing content, you would like to check playback in Flash Player 8 and Flash Player 9. You keep copies of the and controls in separate named directories. Version is the currently registered control, and you would like to switch to version 8.

    First, unlock the registered control without deleting it so that you can switch back to it later:

    FlashUtil9b.exe -uninstallUnlock c:\WINDOWS\System32\Macromed\Flash\Flash9b.ocx

    Next, register the version 8 control:

    regsvr32.exe c:\windows\system32\Macromed\Flash\Flash8b.ocx

    Now, version 8 is the currently registered Flash Player. The locking controls contain the self-registration code to lock the control.

    Flash Player and earlier.

    Some versions of Flash Player earlier than are installed with an uninstaller program, UninstFl.exe, which is placed in the C:\Windows\system32\Macromed\Flash directory.

    Version Includes UninstFl.exe

    Flash Player 7, and later

    Flash Player 8, and later

    Flash Player 9

    The default behavior of UninstFl.exe is to prompt the user, unlock the control, unregister the control, and then delete the OCX, GetFlash.exe, and GetFlash.exe.manifest. UninstFl.exe does not remove itself and cannot remove files that are in use. UninstFl.exe only works on the new locking controls. Older controls do not contain the registration logic to lock or unlock the file and are not recognized by the UninstFl.exe for deletion. When run on older controls, GetFlash.exe and GetFlash.exe.manifest will be deleted, but the control remains. To ensure clean removal of Flash Player, you should run the general uninstaller, uninstall_flash_player.exe, available from "How to uninstall the Macromedia Flash Player plug-in and ActiveX control" (TechNote tn_14157).

    UninstFl.exe also contains several options that developers can use to switch between player versions during testing. Developers can modify the default behavior by using the following command line flags:

    USAGE : %s [-quiet] [-unlock] [-lock] [filename]

    Only the first character of a flag is relevant.

    -q: Suppress prompt.

    -u: Unlock; grant write/delete permission to OCX and registry keys without erasing files.

    -l: Lock; deny write/delete permission.

    filename: Overrides the default path. The default path is located in registry key of HKCR\CLSID\{D27CDB6E-AE6D-11cf-96B8-444553540000}\InProcServer32. For example: C:\Windows\system32\Macromed\Flash\Flash85.ocx

    The use of UninstFl.exe with the locking controls is best illustrated with an example situation: while developing and testing content, you would like to check playback in Flash Player 7 and Flash Player 8. You keep copies of the and controls in separate named directories. Version 8 is the currently-registered control, and you would like to switch to version 7.

    First, unlock the registered control without deleting it so that you can switch back to it later:

    UninstFl.exe -u c:\windows\system32\Macromed\Flash\Flash8.ocx

    Next, register the version 7 control:

    regsvr32.exe c:\windows\system32\Macromed\Flash\Flash.ocx

    Now, version 7 is the currently registered Flash Player. The locking controls contain the self-registration code to lock the control.

  5. Microsoft LifeCam 3.x


    The only thing that bothered me is that the driver is not available as a standalone download: You need to download a 50MB installer, which then downloads another 150MB: DirectX, the .NET framework and other components required for the (useless) software. Without network connection, you cannot install the driver.

    I have found that you can download two small cab packages:


    and find the URL for your language and OS inside the xml files included in cab files.

    but i haven't found the silent switches (if any) for setupstb.exe

  6. Size now at 307 200 bytes; http://www.mediafire.com/file/k3qdkrucb6ce8ej/boot_sdi_300.zip

    The partition image is now basically constructed like this;

    Sector 0: $Boot
    Sector 1 - 64: $MFT
    Sector 65: $MFT:$Bitmap
    Sector 66 - 73: Root directory
    Sector 74 - 586: $LogFile

    The rest of the systemfiles are found "inside" the $LogFile starting at sector 136.

    It is now much easier to read it too.

    Also tried putting the $LogFile in sector 1 and placing all other systemfiles inside it, but that did not work.

    Btw, it is a really good way to learn about ntfs when working with such a small partition image.


    How do i mount this file as virtual disk?

    With the initial release, i can mount boot.sdi with imdisk:

    imdisk -a -t vm -f boot.sdi -b 8192 -m C:\Dev\boot

    Now your archive contains both 300.part file and boot.sdi

    I tried mounting boot.sdi but can't find NTFS bootrecord which starts with EB5290

  7. Some tools required from Windows Installer 4.5 SDK



    Eset Antivirus install package eavbe_nt32_enu.msi with No Modules. The size is 6.42Mb.

    I receive a "Program component upgrade" message for version 3.0.695, what should I do? (3.0)

    I get this one by using the update program components in Advanced update setup of my previous installed version 3.0.684.

    The latest virus signature database updates:

    LOADER0 em000_32_l0.nup

    PERSEUS0 em001_32_l0.nup

    PERSEUS1 em001_32_l1.nup

    PERSEUS2 em001_32_l2.nup

    ENGINE0 em002_32_l0.nup

    ENGINE1 em002_32_l1.nup

    ENGINE2 em002_32_l2.nup

    ARCHIVES0 em003_32_l0.nup

    ARCHIVES1 em003_32_l1.nup

    ARCHIVES2 em003_32_l2.nup

    ADVHEUR0 em004_32_l0.nup

    ADVHEUR1 em004_32_l1.nup

    ADVHEUR2 em004_32_l2.nup

    CLEANER0 em005_32_l0.nup

    CLEANER1 em005_32_l1.nup

    CLEANER2 em005_32_l2.nup

    ANTISTEALTH0 em006_32_l0.nup

    ANTISTEALTH1 em006_32_l1.nup

    ANTISTEALTH2 em006_32_l2.nup

    Optional but recommended to avoid a small download on first update check

    SYSTEMSTATUS0 em009_32_l0.nup

    SELFDEFENSE0 em013_32_l1.nup

    SELFDEFENSE1 em013_32_l2.nup

    SELFDEFENSE2 em013_32_l3.nup

    Install ORCA. Open package eavbe_nt32_enu.msi

    Delete row Property="NoModules" with Value="1" and save changes.

    Silent Install script:

    ::# create folder
    md "%AllUsersProfile%\Application Data\ESET\ESET NOD32 Antivirus\Updfiles"
    ::# create TARGET_DIR
    md %Temp%\NODInst
    ::# MSI-based installer package administrative install
    msiexec /a eavbe_nt32_enu.msi /qb TARGETDIR=%Temp%\NODInst
    ::# XML configuration file
    copy /Y cfg.xml %Temp%\NODInst
    ::# push latest updates
    copy /Y /V Updfiles\em00?_32_l?.nup %Temp%\NODInst\APPDATADIR\Updfiles
    ::# populates the File table with sizes based upon source directory
    msifiler -d %Temp%\NODInst\eavbe_nt32_enu.msi -v -s %Temp%\NODInst\APPDATADIR\Updfiles\
    copy /Y /V Updfiles\em009_32_l?.nup "%AllUsersProfile%\Application Data\ESET\ESET NOD32 Antivirus\Updfiles"
    copy /Y /V Updfiles\em013_32_l?.nup "%AllUsersProfile%\Application Data\ESET\ESET NOD32 Antivirus\Updfiles"
    ::# Launch install
    pushd %Temp%\NODInst
    start /wait callmsi /i eavbe_nt32_enu.msi /qb- REBOOT=ReallySuppress
    rd /S/Q %Temp%\NODInst >NUL 2>&1

    Adjust the path of executable and msi package. In my script, all files are stored in same folder and updates are in Updfiles folder

    Q: Why using the version 3. Eset just released the new 4.2

    A: I just need an antivirus installed to make Windows Security Center happy. My VPN connection to the company i'm working for requires Antivirus enabled and up to date + firewall enabled and some other security settings activated.

    Q: Can i use the full installer (25.9MB) with Modules included

    A: Yes. In that case, no need to edit package eavbe_nt32_enu.msi with ORCA

    Using the package with no modules help to save some space - 6.42Mb vs 25.9Mb - where sources are stored.

  8. to summarize:

    download latest version at official web page: http://www.mozilla.com/en-US/products/

    Copy and paste to FF.INI sample code posted here (credits: DaMageGR), change settings to your needs.

    Install with command:

    "%inst_dir%\Firefox Setup 3.5.7.exe" /INI="%inst_dir%\FF.INI"

    %inst_dir% is a placeholder to your install path where .exe and .ini files are stored.

    -ms argument not required when using /INI argument as stated here (credit: Grake).


    Mozilla changed the Silent install for FireFox 3.5. Now the switch is "-ms"

    rather than the old "/S"

    Just thought I'd pass that alone if you're like me you've been doing "/S"

    all morning!

  9. http://vscommunity.com/blogs/virtualzone/a...redentials.aspx

    Always Prompted for Credentials

    Another common problem is that you are prompted to enter your credentials every time you access the Administration Website using the FQDN of the Virtual Server host, even after it has been added as a trusted site. This is another issue that is related to the baseline configuration of Internet Explorer. By default, user credentials are automatically submitted for authentication only to sites that are interpreted to be in the Intranet zone. For all other zones, including Trusted Sites, the user authentication dialog box is displayed and credentials must be entered manually.


    To resolve this problem on Windows Server 2003, you can modify the Internet Explorer configuration to automatically submit user credentials for authentication regardless of the zone. Follow these steps to change the Internet Explorer user authentication settings:

    Open Internet Explorer and on the Tools menu, click Internet Options.

    Click the Security tab, and then click the Custom Level button.

    Scroll down to the User Authentication section, and click the Automatic Logon With Current User Name And Password option button.

    Click OK twice.

    The drawback of this method is that you might encounter authentication failures if you have configured other trusted sites for which you need to present a separate set of user credentials. Alternatively, if you are accessing a local instance of the Administration Website (running on the computer that you are logged in on), you can use a non-FQDN for the Virtual Server host in the URL (for example, http://localhost:1024).

    When you are running Windows Vista, you have the added complexity of having to run the Administration Website in Internet Explorer as administrator when User Account Control (UAC) is enabled. If you are running in an isolated test environment, you can avoid this additional step by disabling UAC. Otherwise, follow these steps to grant your user account full administrative privilege in Virtual Server and eliminate the need for UAC:

    Right-click the Internet Explorer icon in the Quick Launch section of the task bar, and choose Run As Administrator from the menu.

    In the User Access Control dialog box, click Allow.

    In the Internet Explorer address bar, type in the URL to the Administration Website.

    In the Virtual Server navigation menu, click Server Properties.

    Click the Add Entry button.

    In the new Permission Entry, type in your account name in the User Or Group text box.

    In Permissions, select the Full check box to give your account full control.

    Click OK.

    Important: In Internet Explorer 7, you must also ensure that the Enable Protected Mode option remains disabled for Trusted Sites. If Protected Mode is enabled, you will receive the following error when you attempt to access the Administration Website: “Could not connect to Virtual Server. Please add the Virtual Server administration Website to the Internet Explorer trusted sites list. You can specify an alternate Virtual Server below.” To learn more about Internet Explorer 7 Protected Mode, review the blog entry written by a member of the Internet Explorer security team at http://blogs.msdn.com/ie/archive/2006/02/09/528963.aspx.

  10. Download Microsoft Virtual Server 2005 R2 SP1 - Enterprise Edition + Microsoft Virtual Server 2005 R2 SP1 Update (KB956124)

    from Microsoft website and save them to <destination folder>.

    Virtual Server usually comes wrapped up as a setup.exe. To use the following procedure and options, setup.exe must be unpacked to the MSI using the following command:

    setup.exe /c /t <destination folder>

    Create admin install point:

    msiexec /a "Virtual Server 2005 Install.msi" TARGETDIR=<destination folder> ADDLOCAL=VirtualServer,VMRCClient,DevAndDoc,VSWebApp,VHDMount SERVICESTARTUPMANUAL=1 WEBSITEDEFAULTPORT=80 CONFIGUREIISFORDELEGATION=0 OPENFIREWALL=1 NOSUMMARY=1 /qb- 
    msiexec /a "Virtual Server 2005 Install.msi" /p KB956124.msp TARGETDIR=<destination folder> ADDLOCAL=VirtualServer,VMRCClient,DevAndDoc,VSWebApp,VHDMount SERVICESTARTUPMANUAL=1 WEBSITEDEFAULTPORT=80 CONFIGUREIISFORDELEGATION=0 OPENFIREWALL=1 NOSUMMARY=1 /qb-


    Keep in mind that the computer used for the various steps must be running IIS if you select VsWebApp (Virtual Server Web Application) component.

    Virtual Server 2005 Install


    msiexec.exe {/i|/a} "msifile" [ALLUSERS=value] [PIDKEY=value] [ADDLOCAL=[VirtualServer],[VMRCClient],[DevAndDoc],[VSWebApp]] [sERVICESTARTUPMANUAL=value] [WEBSITEDEFAULTPORT=value] [CONFIGUREIISFORDELEGATION=value] [OPENFIREWALL=value] [uSERNAME=value] [COMPANYNAME=value] [{INSTALLDIR=value|TARGETDIR=value}] [ALLUSERS=value] [NOSUMMARY=value] [/qb | /qn | /qr | /qf] [/l logfile]



    Installs Virtual Server. You can use /x to uninstall Virtual Server.


    Applies the administrative installation option. Installs Virtual Server on the network.


    Sets the user interface level as shown in the following table.



    q or qn

    No user interface


    Basic user interface


    Reduced user interface


    Full user interface

    For more information about the user interface levels, see "Command Line Options" at the Microsoft Web site.

    /l logfile

    Specifies the path to the log file.


    Specifies the unique product key number required to perform the installation. Do not use dashes when typing the number.


    Specifies what components of Virtual Server must be installed. Options are:

    · VirtualServer: Virtual Server Service

    · VMRCClient: Virtual Machine Remote Control Client

    · DevAndDoc: Documentation and Developer Resources

    · VsWebApp: Virtual Server Web Application


    Set to 1 for manual Virtual Server services startup. The default is 0.


    Specifies the port for the Administration Website.


    Specifies under which credentials the Virtual Server Administration Website must run.

    0 - (default) Configure the Administration Website to always run as the authenticated user (Recommended for most users)

    1 - Configure the Administration Website to always run as the Local System account (Required for constrained delegation)


    Set to 1 to configure Virtual Server exceptions in Windows Firewall


    Specifies a custom folder in which to install the program. If you do not include this parameter, the program is installed in \Program files.


    Specifies a location in which to install the Virtual Server installation package when using the administrative installation (/a) option. The package's data files are uncompressed in this location.


    Determines what users see in the Start menu and in Add or Remove Programs. If ALLUSERS is not set, the installer does a per-machine installation. If ALLUSERS is set to an empty string (ALLUSERS=""), the installer does a per-user installation. In all cases the installer uses folders in the "All Users" profile.


    If this value is set to 1, the summary page will not be displayed. The /qn option will also suppress the summary page.


    The following example shows how to perform an unattended installation. An unattended installation means the Setup program runs without prompting you for input.

    msiexec /i  "<destination folder>\Virtual Server 2005 Install.msi" ADDLOCAL=VirtualServer,VMRCClient,DevAndDoc,VSWebApp,VHDMount SERVICESTARTUPMANUAL=1 WEBSITEDEFAULTPORT=80 CONFIGUREIISFORDELEGATION=0 OPENFIREWALL=1 NOSUMMARY=1 /qb-

    Replace <destination folder> with your own selected path in all commands.

  11. having problem opening virtual server administration website. When you click on it, a window pops up that requires authentication, asking for user name and password.

    Add your computer: localhost

    from IE GUI

    Tools > Internet Options > Security tab > Local intranet zone > Sites > Advanced > Add this web site to the zone: localhost

    Command line:

    REG ADD "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\Domains\localhost" /t REG_DWORD /v "http" /d 1 /f

  12. I have used in the past part of script written by Yzöwl with a nice workaround if we don't have the more command somewhere in our path.

    'Fsutil Fsinfo Drives^|More'

    'Fsutil Fsinfo Drives^|find /v ""'

    Jaclaz script output all drives letters with comma as separator.

    Yzöwl script output only the first found drive letter?

    could you explain why you use Call :_ %%$ instead of Call :_ %%#

    I would like to learn something i currently don't understand.

  13. Ignoring the 'if ACPIAPIC_UP' lines, because I have no idea what you mean[/i

    It's just a reminder. According to hal.inf and CPU, source files are different:




    ; Files common to all x86 MP platforms


    ntoskrnl.exe, ntkrnlmp.exe,,0x3000

    ntkrnlpa.exe, ntkrpamp.exe,,0x3000


    hal.dll, halaacpi.dll,,0x3000


    ; Files common to all x86 UP platforms





    hal.dll, halmacpi.dll,,0x3000

    i will probably update both files outside the script.

    Just noticed files in X:\Path To\SP3_extracted\i386 are compressed, so i have to use an expand -r command instead of copy command. :blushing:

    how to change this command:

    If Exist "%X_%\%%#" Copy "%X_%\%%#"

    with expand command the source file has the last char of the extension replaced by a "low line" _ char.

    ie with my previous list

    if Exist "X:\Path To\SP3_extracted\i386\explorer.exe" expand -r "X:\Path To\SP3_extracted\i386\explorer.ex_" .

    ie explorer.exe %~nx0


    explorer.ex_ %~n0 + 2 characters of extension %~x0 + _

  14. I have a directory tree and i would like to replace each file in this tree with the updated file from new service pack (if found).

    The idea is to replace binaries from SP2 with the same from SP3 but don't touch registry hives.


    I can't use the regular SP3_extracted\i386\update\update.exe from Service Pack to update OS because the target to update is before FBA Windows XP Embedded w/ SP2 run-time image. FBA (First Boot Agent) completes the run-time image build process = setup in a regular Windows XP Professional install (GUI part of install after textmode copy step)

    i use this script to get a list of all files to replace.

    call :loop
    goto :eof

    echo/%%~nxI>> %temp%\filelist.txt
    goto :eof

    for each file in the list, i have to check if updated binary exists in SP3_extracted\i386 folder and copy SP3_extracted\i386\%%~nxI to %SRCPATH%



    i have a few files exceptions i have to take care before replacing them:

    if ACPIAPIC_UP ntoskrnl.exe=ntoskrnl.exe

    if ACPIAPIC_UP hal.exe=halaacpi.dll

    and a dir exception

    skip D:\Windows\system32\config

  15. I'm actually thinking on rewriting the program in c# 3.5 but was wondering if it will be that usefull comparing to autoit version. C# gives me more flexibility and prolly nicer interface/features but enforces NET 3.5 on workstation you use it. So anyone can tell me if they think going 3.5 is good idea or you prefer continuation in AutoIt ?

    NET 3.5 = This is the worst idea I've heard in a long time.

    This tool should have no prerequisite.

  16. I would like to avoid to set %v% variable dependent of MUI language set. Currently, there is support only for only 0409=ENU and 040C=FRA

    and clean even more the code.


    @Echo off&Setlocal enableextensions

    ::# REQUIRED: linkd utility
    SET ExtUtilFName=linkd.exe
    ::# "This command-line tool links an NTFS directory to a target object."

    set DEBUG=1
    if "%DEBUG%"=="1" (set TRACE=echo) else (set TRACE=rem)
    %TRACE% Running script: %0

    call :__preinit
    (%ExtUtilFName% /? 2>&1) | FIND /I "Source" >NUL
    IF ERRORLEVEL 1 call :__checkExtUtils

    set vn=
    set dl=
    set vlabel=

    @Rem -------------------------------------------
    @Rem ! Variables
    @Rem ! You may edit or pass-in vlabel
    @Rem -------------------------------------------
    Set vlabel=%~1
    IF "%~1"=="" (Set vlabel=RamDisk)

    set v=
    For /f "tokens=1* delims=:" %%? in ('fsutil fsinfo volumeinfo %SystemDrive%\ ^|Find ":"') Do (
    (Set "Desc=%%?")&&call :__ParseDesc
    if defined v goto :__DL)

    %TRACE% Search for text string: %v%
    For /f %%# In ('Mountvol^|Findstr [d-z]:\\') Do (
    Fsutil fsinfo drivetype %%#|Find /V "CD-ROM">Nul&&(Set "DL=%%~d#")&&call :__VN)
    goto :eof

    %TRACE% Drive Letter: %DL%
    For /f "tokens=2 delims=:" %%? in ('fsutil fsinfo volumeinfo %dl%\ ^|Find /i "%v%"') Do (
    (Set "VN=%%?")&&call :__VV)
    goto :eof

    for %%? in (%VN%) do (set VN=%%?)
    %TRACE% Volume Name: %VN%
    if "%vn%"=="%vlabel%" call :__found
    rem set vn=
    goto :eof

    (%ExtUtilFName% %temp% 2>&1) | FIND /I "is not linked" >NUL
    IF ERRORLEVEL 1 goto :__checkExtUtilsError
    if not exist %dl%\Temp\NUL md %dl%\Temp
    (%TRACE% Linking Source %TEMP% to Target %dl%\Temp)
    %ExtUtilFName% %TEMP% %dl%\Temp
    set vn=
    set dl=
    set vlabel=
    set eu=
    goto :eof

    ::# functions

    set INST_Dir=%~dp0
    set INST_Dir=%INST_Dir:~0,-1%
    set BIN_Dir=%~d0\bin
    goto :eof

    %TRACE% Parsing: %Desc%
    if not defined v set v=%Desc:~0,-1%&goto :EOF
    goto :EOF

    %TRACE% %ExtUtilFName% not found in PATH=%path%
    if exist %ExtUtilFName% copy /Y %ExtUtilFName% %SystemRoot%\system32 >NUL 2>&1
    goto :eof

    echo Some of the external utilities are not accessible.
    echo Make sure you extracted the archive correctly and confirm
    echo that the utilities are in bin directory under root
    PING -n 2 -w 2222 > NUL 2>&1
    goto :eof

    ::# functions end

  17. You can create the new key and add some data.

    REG ADD HKLM\SOFTWARE\Policies\Microsoft\Windows\DriverSearching /v DontSearchWindowsUpdate /t REG_DWORD /d 1 /f
    REG ADD HKLM\SOFTWARE\Policies\Microsoft\Windows\DriverSearching /v DontPromptForWindowsUpdate /t REG_DWORD /d 1 /f
    REG ADD HKLM\SOFTWARE\Policies\Microsoft\Windows\DriverSearching /v DontSearchCD /t REG_DWORD /d 1 /f
    REG ADD HKLM\SOFTWARE\Policies\Microsoft\Windows\DriverSearching /v DontSearchFloppies /t REG_DWORD /d 1 /f

  18. The sets are interchangable between x86 and x64. A generic x64 key can be found in the MS article titled "Preserving OEM Pre-Activation when Re-installing Windows XP"

    Bezalel, I'm *sure* you know that XP x64 and Server 03 x64 are from the same code base. And thus here, all DLL files (and other binaries) that are present in both XPx64 and 03x64 are the same--identical, meaning you could compare them bit-by-bit and they'd be the same. There are, however, some files that only server has (server-specific DLLs), but virtually all the other DLLs are identical.

    Using Server 03 x64 set for installing XP x64 could be less surprising for me.

    but you're probably right: Windows XP x64 SLP?

  • Create New...