Jump to content

Bilou_Gateux

Member
  • Posts

    766
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Norway

Posts posted by Bilou_Gateux

  1. After long search in the dark, i finally found how to install Outlook XP (2002) on my Windows Server 2003 with OE6 removed.

    to setup Office Outlook and add a new e-mail account connecting to POP3 server.

    Extract 3 binaries from an original Server 2003 CD (they are probably removed from your nLited CD!) to %SystemRoot%\system32

    inetcomm.dl_
    inetres.dl_
    msoert2.dl_

    with Dependency Walker i have checked inetcomm.dll and found that this dll requires msoert2.dll

    to register inetcomm.dll inetres.dll is also required.

    Have a look in msoe50.inf:

    [RunOnce.Reg]
    HKLM,"Software\Microsoft\Windows\CurrentVersion\RunOnce","RunOnceEx",2,"rundll32.exe %11%\iernonce.dll,RunOnceExProcess"
    HKLM,"Software\Microsoft\Windows\CurrentVersion\RunOnceEx\OEWAB OS Setup","OE5_2",0,"%11%\inetcomm.dll|DllRegisterServer"

    You can register from the command line:

    regsvr32 /s %SystemRoot%\system32\inetcomm.dll

    to launch Office Outlook, some infos have to be merged in registry.

    Have a look in msoe50.inf:

    [User.Stub.50]
    HKLM,"Software\Microsoft\Active Setup\Installed Components\%GUID_OE%",,,"%MS_OUTLOOK_5%"
    HKLM,"Software\Microsoft\Active Setup\Installed Components\%GUID_OE%","IsInstalled",0x10001,01,00,00,00
    HKLM,"Software\Microsoft\Active Setup\Installed Components\%GUID_OE%","Locale",,"%STR_LANG%"
    HKLM,"Software\Microsoft\Active Setup\Installed Components\%GUID_OE%","ComponentID",,"MailNews"
    HKLM,"Software\Microsoft\Active Setup\Installed Components\%GUID_OE%","CloneUser",0x10001,01,00,00,00
    HKLM,"Software\Microsoft\Active Setup\Installed Components\%GUID_OE%","StubPath",0x00020000,"""%ProgramFiles%\%STR_MAILNEWS_DIR%\setup50.exe"" %APP_OE% %CALLER% /user /install"

  2. Hello everyone,

    I've updated Fedit to v2.0. With this update I've totally rewritten Fedit, now there is almost no disk access, wich should result in a great speed increase, and new features such as case sensitive/unsensitive, substring searching and a "before" line.

    Very usefull tool. I'm using it whereas other tools (gsar.exe or sed.exe) canno't be used before T39 (ntvdm error in my VM Virtual Machine.

    Missing is a replace option to change data:

    gsar script

    gsar -sPlayer:x22:x2c0x00010001:x2c1 -rPlayer:x22:x2c0x00010001:x2c0 -o ..\inf\syssetup.inf

    sed script

    move /y ..\inf\syssetup.inf ..\inf\syssetup.txt
    sed 's/"Windows Media Player",0x00010001,1/"Windows Media Player",0x00010001,0/g' ..\inf\syssetup.txt >..\inf\syssetup.inf

    fedit script

    fedit -f ..\inf\syssetup.inf -rem -l:c "HKLM,\"SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\WindowsFeatures\",\"Windows Media Player\",0x00010001,1"
    fedit -f ..\inf\syssetup.inf -add -l "HKLM,\"SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\WindowsFeatures\",\"Windows Media Player\",0x00010001,0" -s:c "WMPFeature.AddReg" -once

    The 3 scripts do the same thing: replace value 1 with value 0 in this line

    syssetup.inf

    [WMPFeature.AddReg]HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\WindowsFeatures","Windows Media Player",0x00010001,0
  3. My first notebook: (still using it from time to time)

    Compaq Armada 6500 6300/T/6400/D/M/3

    Mobile 6500 Expansion Unit

    Armada 6500 Convenience Base

    Multibay drives: DVD-ROM Drive + SuperDisk LS-120 + Iomega Zip Drive + 1.44-MB Diskette Drive

    OS: Windows NT Workstation 4.0

    images619567.gif

    My others computers:

    OS:

    Sticker-WXPeB.jpg

    Windows XP embedded w/ Enhanced Write Filter (EWF) feature >>> protect the operating system (OS) image from any changes.

    :w00t:

  4. VMware server free server virtualization.

    Use the same tips as described in VMware Knowledge Base article for Installing GSX Server Silently

    To install VMware Server silently on a Windows host, complete the following steps.

    Extract the individual installation packages. Open a command prompt and, on one line, type:

    VMware-server-installer-<xxxx>.exe /a /s /v"/qn TARGETDIR=C:\temp\server"

    (where <xxxx> is a series of numbers representing version and build numbers)

    Run the silent installation on the extracted installation packages. At the command prompt, on four separate lines, type:

    msiexec -i "C:\temp\server\VMware Server Standalone.msi" ADDLOCAL=ALL DESKTOP_SHORTCUT=0 SERIALNUMBER="XXXXX-XXXXX-XXXXX-XXXX" /qn

    msiexec -i "C:\temp\server\VMware Management Interface.msi" ADDLOCAL=ALL /qn

    msiexec -i "C:\temp\server\VMware VmCOM Scripting API.msi" ADDLOCAL=ALL /qn

    msiexec -i "C:\temp\server\VMware VmPerl Scripting API.msi" ADDLOCAL=ALL /qn

    This installs all four components of VMware Server.

    The installation command can be customized using standard Microsoft Windows Installer installation properties as well as any of the following

    specific Properties

  5. [off topic]

    I would like to convert:

    MICROSOFT WINDOWS SERVER 2003 R2 STANDARD EDITION ENGLISH VLK Media to OEM Media

    [/off topic]

    I don't believe there is such thing...in my knowledge Windows Server 2003 R2 is only available as retail/vlk...not as OEM

    Here in France, HP ships some ProLiant servers with French OEM PreActivated Windows Server 2003 Standard R2.

    But i would like an English version...

    I haven't done a smart compare between Volume Licence an Retail versions. OEM versions have few differences:

    DPCDLL.DL_ both dlls are used to check PID Key

    PIDGEN.DLL

    NT5.CAT digital signature catalog file for core OS binaries

    OEMBIOS.BI_

    OEMBIOS.CA_

    OEMBIOS.DA_

    OEMBIOS.SI_

    SETUPP.INI controls how the CD acts

    EULA.TXT

    Thanks for the MGADiag tool link. It's probably intended only for Windows XP. On my running OEM WS03 R2 Standard version, it returns Unsupported OS

  6. None of them are included in Server 2003 R2

    Server 2003 R2 description:

    CD1 software is an interim release that is built on Windows Server 2003 Service Pack 1 includes launcher CD2CHAIN.EXE

    CD2 includes a variety of features and improvements

  7. You guys are trying to reinvent the wheel here. Do a google search for "wsname". This little utility does everything you guys are wanting and more. I set the "ComputerName=*" in the sysprep.inf and then let this utility run in the cmdlines.txt to rename the computer account to the correct name.

    Works great. I even set up a login script to collect MAC addresses and computer names to populate a file that can be used with "WSName". If anyone wants to see specifics I think I still have the files so I can show you.

    :yes: share your knowledge!

  8. I would like to replace with a string (# lengh).

    string (# lengh) ???

    if i want to insert a string which length is superior to the current 'Microsoft Corporation' string length?

    [off topic]

    I would like to convert:

    MICROSOFT WINDOWS SERVER 2003 R2 STANDARD EDITION ENGLISH VLK Media to OEM Media

    I have already replaced required dlls and edit required INI file to convert it to OEM. But one error subsist during install:

    07/15/2006 16:56:14,d:\srvrtm\base\ntsetup\syssetup\log.c,316,,Setup detected that the system file named [c:\windows\system32\dpcdll.dll]is not signed properly

    by Microsoft. This file could not be restored to the correct Microsoft version.

    Use the SFC utility to verify the integrity of the file.

    I'm looking for an owner of OEM Media to get one missing file i need to replace : NT5.CAT

    If you can send me this file, please write me a PM, thanks.

    [/off topic]

  9. with MS Virtual PC you can try this approach

    - MMTool 2.22.1(google is your friend)

    - hex-editor / ultraedit

    - resource hacker

    • Open Resource hacker and extract BIOS resource, the 256kb file extracted is the bios to be edited, rename it to bios.rom
    • next, open mmtool "powertool" and open that bios.rom, select dmi and extract it to dmi.rom
    • Open it with UltraEdit and replace the original contents, like: "Mircrosoft Corporation" , "Virtual Machine" etc etc, with the ones of your choice, save
    • In mmtool use the replace function to replace the DMI with the just saved dmi.rom - save
    • In resource Hacker replace BIOS, 13500 resource with the bios file saved in the step above ("BIOS, 13500, 1033")
    • save and test ;)

    @FreeStyler

    Nice work with modded Virtual PC bios.

    I'm using M$ Virtual Server 2005 R2 and would like to achieve same mods.

    Step 3 use hexeditor to change "Microsoft Corporation" string. I would like to replace with a string (# lengh).

    could i add / remove spaces when hexediting ?

    I can PM you DMI.ROM file if you would like to hexedit it and attach it on the board?

  10. I'm currently working of this kind of solution:

    1/ I'm starting with a RestoreCD Plus from HP and a 2nd CD which contains an OEM Windows XP Professional OS sysprep'ed in factory mode.

    2/ I boot the 1st CD, let the restore process copy required files and then ask for the 2nd CD (OS) and restore it, reboot the computer a first time to let HP tool checks hardware and configuring drivers and applications and when computer reboot, boot from WinPE and backup the HDD with a cloning tool to a VMWare virtual machine.

    3/ inside the virtual disk (.vmdk) which i can mount with Ken Kato VDK driver on my host computer as drive, i can do all the changes required (inject drivers, configuring sysprep.inf oobeinfo.ini and winbom.ini, make appropriate changes to registry hives).

    4/ and then restoring the virtual machine disk to a physical computer.

    Some limitations: my OS is OEM preactivated and i can't use the image on different brand of computers.

    I have some problems with oobeinfo.ini to make the first boot fully unattended.

  11. 3) Deploy

    ------------

    WIM-image to ANY machine (laptop, desktop...) by using ImageX from (PXE/CD/USB) using the same BartPE iso. I then run a tool that detects the HAL, massstorage, pnp drivers, and inject them+sysprep modifications into the image that has just been deployed but before you boot from it.

    Can you give us more details about this HW detection tool?

  12. :w00t:

    I have a working solution for Royalty OEM RIS install.

    I'm using the first 3 Manufacturer Characters - like: HEW,DEL,MED,ACE,FUJ,ASU,IBM,SON instead of converting Manufacturer string to hex and renaming multiple OEMBIOS.* files.

    ristndrd.sif

    [GuiUnattended]
    OemSkipWelcome = 1
    OemSkipRegional = 1
    TimeZone = %TIMEZONE%
    AdminPassword = "*"
    DetachedProgram=".\system32\cmd.exe"
    Arguments="/Q /C FOR /F %I IN (%SystemRoot%\SYSTEM32\$WINNT$.INF) DO (FOR %J IN (%I\$OEM$) DO (IF EXIST %J (%J\NirCmd.exe exec hide %J\OEMBUILD.CMD)))"

    [SetupParams]
    UserExecute="\$WIN_NT$.~LS\$OEM$\nircmd.exe script \$WIN_NT$.~LS\$OEM$\fbreseal.ncl"

    Destination folder $oem$

    copy compname.exe

    copy nircmd.exe

    for each manufacturer create a subfolder named with the 3 leftmosts chars of the manufacturer string and copy OEMBIOS.* + oemlogo.bmp to this subfolder.

    Example for Hewlett-Packard, in $oem$ i have HEW subfolder and inside

    OEMBIOS.*

    oemlogo.bmp

    script launched by DetachedProgram @T39

    @REM ==================================================================
    @REM © Copyright 2006 Bill Gates Development Company, L.P.
    @REM
    @REM Royalty OEM PCs - RIS (Remote Installation Services) based install
    @REM
    @REM Credits: Bezalel for initial idea and coding for CD based install
    @REM
    @REM Credits: idle.newbie hp38guser schalti Pyron a06lp for drivers from CD based install
    @REM http://www.msfn.org/board/index.php?s=&showtopic=51406&view=findpost&p=358011
    ==================================================================

    @FOR /F %%a IN (%SystemRoot%\SYSTEM32\$WINNT$.INF) DO (FOR %%b IN (%%a) DO (IF EXIST %%b (SET DOSPATH=%%b)))
    @for /F "tokens=2* delims=: " %%i in ('%dospath%\$oem$\compname.exe /s ^|findstr /L /c:"System manufacturer"') do @set Manufacturer=%%j &@call :oem "%%j" &@call :model
    @echo/[General]>%SystemRoot%\System32\oeminfo.ini
    @echo/Manufacturer=%Manufacturer%>>%SystemRoot%\System32\oeminfo.ini
    @echo/Model=%Model%>>%SystemRoot%\System32\oeminfo.ini
    @echo/supporturl=%supporturl%>>%SystemRoot%\System32\oeminfo.ini
    @echo/>>%SystemRoot%\System32\oeminfo.ini
    @echo/[Support Information]>>%SystemRoot%\System32\oeminfo.ini
    @echo/Line1=' '>>%SystemRoot%\System32\oeminfo.ini
    @echo/Serial=%Serial%>>%SystemRoot%\System32\oeminfo.ini
    @copy /y %dospath%\$oem$\%oem%\oemlogo.bmp %SystemRoot%\System32\oemlogo.bmp >nul

    :jump
    for %%? in (bi si da ca) do (
     copy /y %dospath%\$oem$\%OEM%\oembios.%%?_ %SystemDrive%\$win_nt$.~ls\i386
     expand -r %dospath%\$oem$\%oem%\oembios.%%?_ %SystemRoot%\system32\
    )

    :drivers
    :: Set Drivers Location Folder
    SET DRV=%SystemDrive%\Drivers
    :: Ticker script
    ECHO.exec hide %dospath%\$oem$\Process.exe -r setup.exe >%SystemDrive%\Ticker.ncl
    ECHO.wait 10000 >>%SystemDrive%\Ticker.ncl
    ECHO.exec hide %dospath%\$oem$\Process.exe -p SetupCopyOEMInf.exe high >>%SystemDrive%\Ticker.ncl
    ECHO.exec hide %dospath%\$oem$\Process.exe -s setup.exe >>%SystemDrive%\Ticker.ncl
    ECHO.wait 50000 >>%SystemDrive%\Ticker.ncl
    ECHO.script %SystemDrive%\Ticker.ncl >>%SystemDrive%\Ticker.ncl
    :: Pre-Install (Suspend Setup, and Set Setup to Low Priority)
    %dospath%\$oem$\Process.exe -s setup.exe
    %dospath%\$oem$\Process.exe -p setup.exe low
    :: If Compressed Drivers Exist, Unzip Them & Change Drivers Location Folder to Hard Drive
    IF EXIST Drivers.7z (
    SET DRV=%SystemDrive%\Drivers
    %dospath%\$oem$\7za.exe x -y -aoa -o"%SystemDrive%\Drivers" "%dospath%\$oem$\Drivers.7z"
    )
    :: If Compressed Drivers Exist, Uncab Them & Change Drivers Location Folder to Hard Drive
    IF EXIST %dospath%\$oem$\EC834ET.TAG (
    IF /I "%Model%"=="HP Compaq dc7600 Convertible Minitower" (
    SET DRV=%SystemDrive%\Drivers
    extrac32 /y /l %SystemDrive%\Drivers\Video %dospath%\$oem$\11725988.cab *.*
    extrac32 /y /l %SystemDrive%\Drivers\NIC %dospath%\$oem$\b57win32.cab *.*
    extrac32 /y /l %SystemDrive%\Drivers\Audio %dospath%\$oem$\rtkazaud.cab *.*
    )
    )
    IF EXIST %dospath%\$oem$\D1944.TAG (
    IF /I "%Model%"=="SCENIC C620" (
    SET DRV=%SystemDrive%\Drivers
    extrac32 /y /l %SystemDrive%\Drivers\Video %dospath%\$oem$\IALMNT5.CAB *.*
    extrac32 /y /l %SystemDrive%\Drivers\NIC %dospath%\$oem$\b57win32.cab *.*
    extrac32 /y /l %SystemDrive%\Drivers\Audio %dospath%\$oem$\smwdmch6.cab *.*
    extrac32 /y /l %SystemDrive%\Drivers\Misc1 %dospath%\$oem$\cmeu0wdm.cab *.*
    )
    )
    :: Run NirCmd Ticker Script (code above)
    START %dospath%\$oem$\NirCmd.exe script %SystemDrive%\Ticker.ncl
    :: Install Drivers
    %dospath%\$oem$\SetupCopyOEMInf.exe "%DRV%"
    :: Post-Install (Close NirCmd, Setup Priority back to Normal, Resume Setup)
    %dospath%\$oem$\Process.exe -k NirCmd.exe
    %dospath%\$oem$\Process.exe -p setup.exe normal
    %dospath%\$oem$\Process.exe -r setup.exe
    :: Delete Ticker File
    DEL %SystemDrive%\Ticker.ncl

    goto :eof

    :model
    @for /F "tokens=1* delims=: " %%k in ('%dospath%\$oem$\compname /s ^|findstr /c:"model"') do @set Model=%%l
    @for /F "tokens=1*" %%m in ('%dospath%\$oem$\compname /d ?s') do @set Serial=%%m
    @for /F "tokens=1-2*" %%n in ('findstr "%oem%" %~s0') do (set supporturl=%%o)
    @goto :eof
    :oem
    @set oem=%1
    @set oem=%oem:"=%
    @set oem=%oem:~0,3%
    @goto :eof

    [Manufacturer]
    FUJ http://support.fujitsu-siemens.com/com/support/index.html : Fujitsu Siemens Computers
    HEW http://welcome.hp.com/country/us/en/support.html?pageDisplay=support : Hewlett-Packard
    NEC http://help1.nec-computers.com/main.asp?lang=com : NEC Computers International
    TOS http://www.csd.toshiba.com/cgi-bin/tais/su/su_sc_home.jsp : TOSHIBA

    nircmd script launched by UserExecute @T9

    execmd move /y ~$sys.systemroot$\system32\dllcache\oembios.cat ~$sys.systemroot$\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}

    regsetval sz "HKLM\SOFTWARE\OEM\Image" "" "Royalty OEM Preinstalled Image"

    exec show "~$sys.systemdrive$\$win_nt$.~ls\$oem$\zcnclite.exe" "/wmi:~qWin32_BIOS,SerialNumber~q /sn:~qSN-~q /q /forcerun"

    [EDIT]

    Done some rewrite of the script for RIS

    [/EDIT]

  13. Although my method is currently working SFC is aware that the files have been changed because oembios.cat was parsed before the files were changed. If the end user ever runs SFC manually they will be prompted for the oembios files that match the origional oembios.ca_ that was left on the CD. My two question now are:

    When SFC parses the oembios.cat file where does it store the thumbprints of the remaining oembios files? (I am able to delete the oembios.cat file, it is not protected but SFC still knows that the files aren't origional)

    oembios.ca_ replacement may require to rebuild database as described in MS KB822798 Article - Method 3

    I haven't checked myself if it would works, which OEMBIOS.* should we use in a MS virtual machine :}

  14. @jdoe

    Thanks.

    Here the answer you give through PM.

    À l'offset hexadécimal 36F29 ou (225065 décimal), tu trouveras les deux bytes suivant "737A" ce qui représente "jnb 5B3E7BA5" en assembleur (5B3E7BA5 étant où le jump doit aller pour éviter la vérification de la signature de syssetup.inf).

    Donc pour éviter cette vérification on n'a qu'à changer jnb par jb ce qui veut dire en résumé qu'à l'offset 36F29 il faut changer 73 par 72.

    If we change jnb 5B3E7BA5 to jb 5B3E7BA5 then we skip the verification and our modified SYSSETUP.INF is not recognize as an invalid file. This mean that only one byte patching is needed. So, at offset 36F29 you should read and write the following :

    73 7A : jnb 5B3E7BA5

    Changed by

    72 7A : jb 5B3E7BA5

    [EDIT]

    Offset address value is for both 2003 Server w/ SP1 ENU or FRA syssetup.dll.

    [/EDIT]

    And a good hexeditor recommendation from jdoe:

    FRee Hex ED

    Haven't yet read the help file to check if command line support (unattended) exists?

    nLite patched syssetup.dll add more features:

    Added automatic hacking of syssetup.dll for OOBE disabling (if you choose to remove it, this will not crack Activation).

    SFC is entirely disabled too simply by copying hacked dll from Data and adjusting registry.

  15. I'd like dll to be registered like the others, without using regsvr32 somewhere.

    You want it the hard way :P

    You'll have to work hard on this one but I give a way to do it.

    1) You need to unlock Windows XP setup and for that you need a patched syssetup.dll

    2) You must edit the [OleControlDlls] section of syssetup.inf and add the file you want to register.

    I can give you the patched syssetup.dll but for the rest, like I said, you'll have to do some work because I don't know what you are trying to do.

    Unlock Windows XP Setup

    :hello: L'Azimuté !

    I would like to do Windows Server 2003 w/SP1 ENU syssetup.dll patching automated with XVI32 script run from the command line. I need to locate the offset where to change some bits.

    File compare between original and nLite patched

    Search for differences

    1. B:\syssetub.dll: 1,047,040 bytes

    2. B:\syssetup.dll: 1,047,040 bytes

    Offsets: hexadec.

    148: 65 F7

    149: CE F1

    35CB3: 8B 33

    35CB4: FF C0

    35CB5: 55 C2

    35CB6: 8B 04

    35CB7: EC 00

    36F45: 56 33

    36F46: 56 C0

    36F47: 56 EB

    36F48: 56 29

    5B4FE: 75 90

    5B4FF: 07 90

    13 difference(s) found.

    :wacko:

    which one should i change? I have PM nuhi hoping he would find some time to answer.

    Instead of storing two copy SYSSETUB.DL_ and SYSSETUP.DL_ in source folder and renaming it with nlhive.inf at 1st GUI launch

    [Version]

    Signature = "$Windows NT$"

    [nLite]

    HKCU,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce","nlsf",0x00020000,"cmd.exe /C move /Y ""%SystemRoot%\System32\syssetub.dll"" ""%SystemRoot%\System32\syssetup.dll"""

    we can try to reverse patch on the patched DLL and get back to original unpatched syssetup.dll

    Could you help me to write the xsc script. Or for starting with this stuff, is the example for patching XP SP2 ENU syssetup.dll according to infos posted at your patches Webpage correct.

    something like:

    %ProgramFiles%\xvi32\XVI32.exe %temp%\syssetup.dll /S=%ProgramFiles%\xvi32\syssetuprepl.xsc 33679 73 72

    REM goto offset %1
    ADR $%1
    REPLACE %2 BY %3

    Merci pour l'aide que tu pourras m'apporter, ami francophone de l'autre côté de l'océan.

    Thanks for help.

  16. Thanks Albuquerque for your scripts.

    I have myself posted two scripts with some "take care of" logic in it.

    Files are deleted according to data listed in txtsetup.sif or .inf files and i have to add some exceptions.

    Storage class device driver, remove default one included in WinPE 1.5 (2004) & WinPE 1.6 (2005)

    Network Driver Interface Specification (NDIS) miniport driver, remove default one included in WinPE 1.5 (2004) & WinPE 1.6 (2005)

    My next step is to keep only base minimum required fonts.

    And then binary files.

    I will use your scripts to remove them but your list includes some files not related to WinPE: i.e. i don't have ximage.exe in \I386\SYSTEM32

  17. Question related to the OSDWinPE.wim image included in Microsoft® Systems Management Server (SMS) 2003 Operating System (OS) Deployment Feature Pack release [sMS2003OSDFP_ENU].

    Is the Windows Image (WIM) format used by the Microsoft Systems Management Server (SMS) OS Deployment Feature Pack the final version that Windows Vista will use?

    A. No, the WIM format that the SMS OS Deployment Feature Pack uses can be thought of as version 0.9 of the WIM format, whereas Vista will ship with version 1 of the format. SMS 4.0 will fully support the Vista WIM format (1.0) and potentially an update will be made available to make SMS 2003 Vista WIM format compatible. The new Vista deployment tools (e.g., Ximage) will work only with version 1 WIM files and not files created with the SMS Deployment Feature Pack.

    I have downloaded SMS 4.0 Beta 1 but too bad, as stated above, the ximage binary included don't work with the oldest 0.9 wim format.

    Where can i get a compatible ximage.exe or does one of you have a compatible copy (please PM me).

    I do not plan to install SMS2003 on my network, just want to play with the OSDWinPE.wim. I have access to MSDN subscriptions CDs but don't know where to find it.

    Thanks.

  18. Mitec GetSysInfo.exe will not be available for one year.

    Instead of using IBM smbios tool, why not using:

    Compname.exe was written using the excellent Mitec SysInfo by Michal Mutl (see www.mitec.d2.cz) and Indy.

    @for /F "tokens=2* delims=: " %%i in ('compname /s ^|findstr /L /c:"System	manufacturer"') do @set Manufacturer=%%j &@call manufacturerhex "%%j"

    EDIT: previous script modified to trim any leading/trailing spaces &call Djé script.

    Djé manufacturerhex.cmd script modified to take manufacturer string as 1st parameter

    FOR /F "tokens=1* delims=: " %%i IN ('smbiosd /t:1 ^|findstr "Manufacturer"') DO SET "TEST=%%j"

    SET TEST=%1

    SET TEST=%TEST:"=%

    echo Manufacturer: %TEST%

×
×
  • Create New...