Jump to content

Bilou_Gateux

Member
  • Posts

    766
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Norway

Posts posted by Bilou_Gateux

  1. This is what I need my script to do:

    Run SMBIOS (I think /G) and redirect the output to a text file

    Search the output file for the "System Information" section

    Search the "System Information" section for the "Manufacturer" line

    Convert the manufacturer string into hex and replace the OEMBIOS files with files named with the hex string.

    My script would not have to be modified when you by another PC from a a new manufacturer all you have to do is collect the OEMBIOS files from your new computer rename them with the manufacturer's hex string (I've already written these scripts) and drop the files onto your CD.

    @for /f "tokens=1* delims=: " %%i in ('smbiosd /t:1 ^|findstr "Manufacturer"') do @set "Manufacturer=%%j" &@call echo/%Manufacturer%

    Previous script based from an original script by Yzöwl

    for converting manufacturer string into hex with batch script, ask Yzöwl batch expert. If you use vbs or wsh, you could not run the script @T39

  2. credits: AppDeploy.com

    Install source is a Virtual CD mounted ISO image and content can't be altered or new abccopy.ini file added.

    I'm using this command line:

    msiexec /i "D:\Adobe Photoshop Elements\Adobe Photoshop Elements 4.0 (fr_fr).msi" USERNAME="ÿ" COMPANYNAME="ÿ" ENCSERIALNUMBER="xxxxxxxxxxxxxxxxxxxxxxxx" /qr /norestart

    Open Command Prompt to kill last Install Wizard windows

    taskkill /f /im msiexec.exe

    Apply some tweaks

    :// avoid users being prompted to look for updates
    reg add "HKLM\Software\Adobe\Updater" /v Entreprise /t REG_DWORD /d 1 /f
    :// disable the Adobe Photo Downloader
    reg add "HKLM\Software\Adobe\Photoshop elements\4.0\Adobe Photo Downloader\Preferences" /v AutoLaunchOnDeviceConnect /t REG_DWORD /d 1 /f
    :// registration done
    reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{EBB7C1C1-D439-4D9B-9FDC-954C10F266B0}" /v "EPIC_REGS_TYPE" /t REG_DWORD /d 4 /f
    reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{EBB7C1C1-D439-4D9B-9FDC-954C10F266B0}" /v "EPIC_REGS_STATE" /t REG_DWORD /d 2 /f
    reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{EBB7C1C1-D439-4D9B-9FDC-954C10F266B0}" /v "EPIC_REGS_LANG" /t REG_DWORD /d 1 /f
    reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{EBB7C1C1-D439-4D9B-9FDC-954C10F266B0}" /v "EPIC_REGS_COUNT" /t REG_DWORD /d 0 /t

    Note:

    export the data value ENCSERIALNUMBER from registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{EBB7C1C1-D439-4D9B-9FDC-954C10F266B0}
    "EPIC_SERIAL"="xxxxxxxxxxxxxxxxxxxxxxxx"

    How to detect end of Install Wizard unattended to kill msiexec?

  3. From Windows XP Embedded documentation:

    The WMI Command Line Utility component provides a command-line interface for the Windows Management Instrumentation (WMI infrastructure. This component includes a set of commands and control functions to manage a Windows environment. This component interacts with existing shells and utility commands and can be easily extended by scripts or other administration-based applications.

    You can access the WMI infrastructure using a command-line interface and intermediate facilitators, called aliases. Aliases capture the WMI class features that are relevant to a specific task, such as network administration. You can use aliases to rename classes, properties, and methods, or to arrange properties that include property values.

    This component enables you to perform the following actions:

    • Define aliases, add output formats, and create and execute scripts
    • Browse the WMI schema and query its classes and instances
    • Get information from a local computer, a remote computer, and multiple computers in a single command

    The following table shows the files and applications included in this component.

    FileDescriptionCli.mofSchemaCliegaliases.mflLocalization schemaCliegaliases.mofAliasesCsv.xslStyle sheet for comma-separated value formatHform.xslStyle sheet for HTML value list formathtable-sortby.xslStyle sheet for HTML table including sortbyHtable.xslStyle sheet for HTML table format Mof.xslStyle sheet for MOF formatRawxml.xslStyle sheet for raw XML formatTexttable.xslStyle sheet for table formatTexttablewsys.xslOptional style sheet for table formatTextvaluelist.xslStyle sheet for value list formatWmic.chm Windows HelpWmic.exeEngine-parserWmiclimofformat.xslDefault MOF formatWmiclitableformat.xslDefault table formatWmiclitableformatnosys.xslOptional table formatWmiclivalueformat.xslDefault value list formatWml.xslDefault XML formatWsl-mappings.xmlDefault style sheet table

    The compilation of Cli.mof, Cliegaliases.mod, and Clialiases.mfl files creates the \\root\cli name space and populates it with aliases. The Wmic.exe file executes queries and calls a method as specified by an alias. The Extensible Markup Language (XML) output is formatted using default style sheets as specified in Xsl-mappings.xml, while other formats can be explicitly specified using /FORMAT:< stylesheet name>.

    Services

    There are no services for this component.

    Associated Components

    The WMI Command component is designed to work with the WMI Core and WMI Provider components. The WMI Command component also requires the Tools component to compile Managed Object Formats (MOFs), which occurs during the first boot.

    The following components have related functionality:

    • WMI SNMP Provider, which is needed if a user wants to query the SNMP name space.
    • WMI DS Provider, which is needed if a user wants to query the DS name space.

    Settings

    There are no configurable settings for this component.

    Notes

    The WMI Command component can only be used by local system administrators, regardless of WMI name space permissions on the local computer.

    At T13, we're using the System account

  4. Actually, i'm using a third-party tool to rename my HP branded computers using a Prepend string HP-followed by SerialNumber.

    zcnclite.exe /wmi:"Win32_BIOS,SerialNumber" /sn:"HP-" /q /forcerun

    With your code, i will use this command:

    <path>NirCmd.exe script <path>fbreseal.ncl

    fbreseal.ncl

    execmd for /f %i in ('wmic SystemEnclosure get SerialNumber') do wmic.exe ComputerSystem Where Name="%ComputerName%" Rename Name="HP-%i"
    regsetval sz "HKLM\SOFTWARE\HP\Image" "" "HP Preinstalled Image"

    :)

  5. Have you used this program during setup? The output looks more like WMI than SMBIOS.

    Yes i've launched Getsys.exe @T39. Here the output:

    MiTeC System Information Utility 10.2.0 - Copyright © 1997-2006 Michal Mutl

    Type /? for options

    SYSTEM OVERVIEW...OK

    Machine: MACHINENAME

    System : PC multiprocesseur ACPI

    Model : Hewlett-Packard HP Compaq dc7600 Convertible Minitower

    UpTime : 2 Minutes, 47 Seconds.

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

    CPU : 1 x Intel Pentium 4 - 2990 MHz

    Cache: 16 KB L1 + 2048 KB L2 + 0 KB L3

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

    Mainboard: Hewlett-Packard 09F0h

    Memory : 503 MB

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

    Operating system: Windows XP Professional [5.1.2600]Service pack : 2.0

    Logged user : SYSTEM

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

    Display adapter: Intel® 82945G Express Chipset Family

    Memory : 128 MB

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

    Fixed : Promise 1X2 Mirror/RAID - 76316 MB (SCSI)

    C: (Primary NTFS - 76308 MB)

    DVD : LITE-ON DVD SOHD-167T - 0 MB (ATAPI)

    D:

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

    Keyboard:

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

    Mouse:

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

    Default printer:

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

    As you can see, @T39 we don't get full infos about PCI PnP Devices because they're not yet installed.

  6. Is HPQSI.EXE publicly available? I know I have a copy of IBM's SMBIOS.EXE, I'll try to see if I can do anything with the output of these files. I don't want to build my script around files that are not freely available to the public.

    :no:

    We can use another command line tool call GetSys.exe, which is part of 'Mitec System Information Component Suite'.

    ReadMe.txt

    MSICS is freeware.

    Sources are available on purchase/registration. Price is 110 euro (EUR).

    For registration details see Order.txt file in this package.

    Distribution pack:

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

    The zip file has subdirectories in it. You must use the pkunzip -d option

    to restore this directory tree or you will have problems because the files

    will not be in their proper subdirectories.

    This is the subdirectory layout:

    .\ Info directory

    .\apps Applications written using this component

    .\demos Sample applications

    .\dll MSICS.DLL library for using MSI data from any app

    .\help HTML Help file

    .\D5 compiled units containing components and packages for installing for Delphi 5 (not in registered version)

    .\D6 compiled units containing components and packages for installing for Delphi 6 (not in registered version)

    .\D7 compiled units containing components and packages for installing for Delphi 7 (not in registered version)

    .\BDS3 compiled units containing components and packages for installing for Delphi 2005 (not in registered version)

    .\BDS4 compiled units containing components and packages for installing for Delphi 2006 (not in registered version)

    .\Sources source files (only in registered version)

    You can get it by downloading the full package, extract and grab the exe in \Apps\GetSys folder.

  7. @Bezalel

    Not tried yet your scripts but:

    shouldn't be %SystemDrive%\System32 replaced with %SystemRoot%\System32 in both batch scripts.

    I would like to switch oembios* files @T39 using SMBios Details to identify System Manufacturer.

    Actually i can output SMBios Details using a HP tool (HPQSI.EXE) launched with a batch script (OCA_MRK.CMD) @T39 but i haven't yet written the script to parse the output and copy the right OEMBIOS* files depending of the manufacturer.

    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\OCA_MRK.CMD)))"

    sample HPQSI.INI

    [ParsedHPQSystemInformation]Product Name="HP Compaq dc7600 Convertible Minitower"

    Product Number="EC834ET#ABF"

    Serial Number="HUB#######"

    [RawHPQSystemInformation]

    BIOSVendor="Hewlett-Packard"

    BIOSVersion="786D1 v01.03"

    BIOSReleaseDate="05/18/2005"

    BIOSMajorVersion="1"

    BIOSMinorVersion="3"

    ECFirmwareMajorVersion="0xff"

    ECFirmwareMinorVersion="0xff"

    SystemManufacturer="Hewlett-Packard"

    SystemProductName="HP Compaq dc7600 Convertible Minitower"

    SystemVersion=" "

    SystemFamily="103C_53307F"

    SystemSKU="EC834ET#ABF"

    SystemSerialNumber="HUB#######"

    BaseBoardManufacturer="Hewlett-Packard"

    BaseBoardProductName="09F0h"

    BaseBoardVersion=""

    ProcessorManufacturer="Intel"

    ProcessorVersion="Intel® Pentium® 4 CPU 3.00GHz"

    ProcessorID="0xf43"

    MemoryDeviceManufacturer[1]="JEDEC ID:C1 00 00 00 00 00 00 00"

    MemoryDeviceSerialNumber[1]="13720101"

    MemoryDevicePartNumber[1]="64T32000HU3.7A"

    MemoryDeviceManufacturer[2]="JEDEC ID:"

    MemoryDeviceSerialNumber[2]=" "

    MemoryDevicePartNumber[2]=" "

    MemoryDeviceManufacturer[3]="JEDEC ID:C1 00 00 00 00 00 00 00"

    MemoryDeviceSerialNumber[3]="13E60101"

    MemoryDevicePartNumber[3]="64T32000HU3.7A"

    MemoryDeviceManufacturer[4]="JEDEC ID:"

    MemoryDeviceSerialNumber[4]=" "

    MemoryDevicePartNumber[4]=" "

  8. 2K is great. Very lightweight and no "favors" are done for you that compromise your system. I get a kick out of the NLITE die-hards who strip enough out their XP so it looks like 2K. Why not just start with a lightweight OS to begin with? Honestly, the only thing I like about XP is the "cleartext" for the LCD monitors. Other than that, it's not my cup of tea.

    A little prob I have with XP is that when doing serious multitasking, and if you want to delete a folder, the OS won't let you. So you close each application one at a time until nothing is running at all. Even after doing that, you still can't delete that folder. Only after rebooting can you delete it. This isn't a one time occurance. It happens quite frequently for me. Well, another issue I have is the crashing shell. It starts up again, but all my systray stuff is gone. I don't know about the rest of the computing community, but I kind of like having a shell that doesn't crash. The only time I had 2k BSOD me was when my hard drive bit the dust. I had more BSODs with XP, even with functional hard drives.

    My 2 cents to solve this issue:

    explorer.inf

    [Version]Signature = "$Windows NT$"

    [DefaultInstall]

    AddReg = AddReg

    DelReg = DelReg

    UpdateInis = UpdateInis

    [AddReg]

    ;Q240130 Disable the "Getting Started with Windows 2000" Dialog Box

    HKCU,"Software\Microsoft\Windows\CurrentVersion\Explorer\tips","Show",0x00010001,0x0

    HKCU,"Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced","ClassicViewState",0x00010001,0x0

    HKCU,"Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced","ShowSuperHidden",0x00010001,0x0

    HKCU,"Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced","Hidden",0x00010001,0x1

    HKCU,"Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced","HideFileExt",0x00010001,0x0

    HKCU,"Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced","SeparateProcess",0x00010001,0x1

    HKCU,"Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced","ShowCompColor",0x00010001,0x1

    ;Clear the Page File at System Shutdown

    HKLM,"SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management","ClearPageFileAtShutdown",0x00010001,0x1

    [DelReg]

    [updateInis]

    cmdlines.txt

    [Commands]
    "rundll32 setupapi,InstallHinfSection DefaultInstall 128 .\explorer.INF"

  9. does anyone have another method to register wups2.dll?

    SVCPACK method:

    \i386\svcpack.inf

    [CatalogHeader][Version]

    BuildNumber=2600

    MinorVersion=1

    MajorVersion=5

    Signature="$WINDOWS NT$"

    [setupData]

    CatalogSubDir="\I386\svcpack"

    [setupHotfixesToRun]

    nircmd exec hide extrac32 /L ~$sys.windir$\system32\ ~$folder.nircmd$\wups2.cab wups2.dll /Y

    nircmd regsvr reg ~$sys.windir$\system32\wups2.dll ~$sys.windir$\temp\wups2.log

    [ProductCatalogsToInstall]

    \i386\SVCPACK folder

    nircmd.exe

    wups2.cab (link is on post #1)

    optional: ~$sys.windir$\temp\wups2.log creates a log file.

  10. You can check the output of this command using devcon tool:

    devcon drivernode =Display

    You will need some batch script expertise to write a full script.

    sample output on a box with driver already installed.

    PCI\VEN_8086&DEV_1132&SUBSYS_004C110A&REV_04\3&61AAA01&0&10

    Name: Intel Corporation 815 Embedded Graphics Controller

    DriverNode #0:

    Inf file is c:\windows\inf\ssigd.inf

    Inf section is ssigd_wht

    Driver description is Intel Corporation 815 Embedded Graphics Controller

    Manufacturer name is Intel Corporation

    Provider name is Intel Corporation

    Driver date is 1/15/2006

    Driver version is 5.0.0.756

    Driver node rank is 8193

    Driver node flags are 00002240

    Inf is digitally signed

    1 matching device(s) found.

  11. Thanks for the program. it is interesting and give me another option to play with.

    Already running 2K3SP1 Web Edition on my laptop and forget about all these annoying useless XP Features (Movie Maker, System Restore, Security Center, and a lot more) only tailored for newbies.

    [EDIT]

    2K3 Web Edition is only available as Corporate licence and don't know exactly what will happen if i apply your conversion pack on running install?

    [/EDIT]

  12. @Markymoo

    Congratulations for this fine tutorial.

    Step 1: done!

    One Olympus MAUSB-300 Portable Reader / Writer with one xD-Picture Card inserted is now seen as a basic disk in Disk Management console (diskmgmt.msc).

    Some input: you can change the string in CFADISK.INF to reflect the exact name of your hardware

    [cfadisk_device]%MAUSB-300_devdesc% = cfadisk_install,USBSTOR\Disk&Ven_OLYMPUS&Prod_MAUSB-300&Rev_1.00

    [strings]

    MAUSB-300_devdesc = "Olympus MAUSB-300"

    The 256 Mb xD-Picture Card was previously formated with WinPE 2K3 SP1 OPK CD formatufd.exe tool. One single partition.

    Step 2: Done but factory.exe fails to initialize NIC. :no:

    Boot PE from Hard Drive

    The same image works fine when booted from Hard Drive. I must retrieve some posts from this board and www.911cd.net/forums board users who have the same issues.

    Step 3: not enough time to achieve this because i should deliver the writer/reader to my customer soon.

    Boot Windows XP Embedded w/SP1 from this UFD. :no:

    Request to all members:

    if someone as already done this with one SanDisk MobileMate Reader , please report your eXPerience.

    i would like to buy one to play with it and SanDisk Extreme® III SD™ Cards

    it should probably works because it can be done with Puppy Linux distro.

  13. Re-read your 1st post and as i understand now, the answer i give to you is not exactly what you were looking for?

    check this URL which may answer your needs: http://grid-it.cnaf.infn.it/index.php?pxefloppy&type=1

    Here the method to use an image of universal TCP/IP network boot disk and boot from PXE [F12] and load the image.

    It requires a Configured DHCP Server and a TFTP Daemon running on a server.

    http://pxes.sourceforge.net/howtos/ms_only_environment/

    On our labs, we're using a Windows Server 2003 Web Edition box but you can use a Windows XP Pro box with tftpd32 freeware.

    • Obtain pxelinux.0 and memdisk from http://syslinux.zytor.com/pxe.php
    • Create /tftpboot
    • Put pxelinux.0 and memdisk in /tftpboot
    • Create /tftpboot/pxelinux.cfg/default
      Here's mine
      PROMPT 1
      DEFAULT ghost
      DISPLAY messages
      TIMEOUT 100
      label local
      LOCALBOOT 0

      label ghost
      KERNEL memdisk keeppxe
      APPEND initrd=netboot.img


    • Create an image netboot.img of your network book floppy you want to boot from and put in /tftpboot
    • Create /tftpboot/messages to show a message on the screen at boot time

    Hopefully your clients will get an IP, get and boot pxelinux.0, show messages, boot the default or selected image

  14. Using *much better* alternative TFTP service method, i have one timeout issue.

    In fact, TFTPD.exe (Microsoft Trivial FTP Daemon) service included in the "Windows XP Embedded Remote Boot Server.msi" installer is exactly the same as the one you can extract from i386 source and manually configure.

    Does Microsoft Windows XP TFTPD fully implements all RFC?

    tftpd -?

    Abstract:

    This implements an RFC 783 tftp daemon.

    It listens on port 69 for requests

    and spawns a thread to process each request.

    TFTPD USAGE and Installation:

    md d:/tftpd (the StartDirectory).

    copy //MohsinA_p90/test/tftpd.exe .

    sc create tftpd binPath= d:/tftpd/tftpd.exe (give full path).

    sc query tftpd (check if installed).

    Start:

    sc start tftpd -f (creates a log file).

    or sc start tftpd

    or net start tftpd

    or sc start tftpd [-dStartDirectory][-e] [-f]

    Options: -e use event log.

    -f log to file.

    -dStartDirectory

    Info:

    sc interrogate tftpd (logs will be updated).

    sc query tftpd Check whether running.

    Stop:

    sc stop tftpd

    net stop tftpd

    Variables that control what files can be read/written and by whom:

    StartDirectory - only files there will be accessible.

    LogFile is created here.

    ValidClients - Clients matching this ip address can read files.

    eg. you can set it to "157.55.8?.*"

    ValidMasters - clients matching this can write and read files.

    eg. you can set it to "" and no one can write.

    ValidReadFiles - only matching files will be served out, eg. "r*.t?t"

    ValidWriteFiles- only matching files will be accepted, eg. "w*.txt"

    Client:

    tftp [-i] servername {get|put} src_file dest_file

    -i from binary mode, else ascii mode is used.

    the timeout issue when downloading image from Boot Server to local host is due to slow performance on some parts of my LAN. I have the same issue using the very basic tftp.exe command line client shipped with XP trying to get a file from server.

    It's not related to your method which works fine using a commercial product:

    WinAgents TFTP Server: Fast and secure TFTP Server workking as native Windows Service.

    WinAgents Software Group has developed freeware replacement for standard TFTP client application that supports all necessary features: 'tsize', 'blocksize' and 'timeout' TFTP options.

    Unattended Setup

  15. If you set the disk RAMDisk size to maximum 32 Mb with the evaluation version, you will not have any message box.

    If you copy an 7zip archive to the RAMDisk, there is no need to compress it because you will not gain a lot of space using NTFS compression on an .7z archive.

    If your 7z archive is larger than 32 Mb and you need to set a larger size for the ramdisk, you can't use the evaluation version and avoid message box.

    As i understand, what you want to do is extracting the .7z to RAMDisk and then launching setup from RAMDisk?

  16. That's what we're presuming.

    Thanks for confirming.

    ws03sp1 is a lot easier to update than wxp. :P

    Stickied topic updated with details.

  17. Still waiting for Microsoft for updating http://v4.windowsupdate.microsoft.com/catalog/en/

    2 critical Updates are missing from them.

    Here the list for important updates

    Security Update for Windows Media Player Plug-in (KB911564)* - (Posted Date: February 13, 2006)

    Download size: 597 KB

    Security Update for Windows Server 2003 (KB901190) - (Posted Date: February 10, 2006)

    Download size: 538 KB

    Security Update for Windows Server 2003 (KB911927) - (Posted Date: February 10, 2006)

    Download size: 626 KB

    Security Update for Windows Server 2003 (KB913446) - (Posted Date: February 10, 2006)

    Download size: 827 KB

  18. If you choose to use my posted method1 (install @T12 cmdlines.txt), you don't need to alter install files like Gosh method.

    My method2 was the same but ramdisk was installed earlier during the setup (install @T39 DetachedProgram in WINNT.SIF).

    I have an issue when installing it @T39.

    at end of GUI mode setup, QSoft RAMDisk (not digitally signed) is replaced by Microsoft RAMDisk (authenticode signed) by WFP because both use the same service name:

    HKLM\CurrentControlSet\Services\Ramdisk

  19. Welcome back.

    It's a long time since your last post.

    Thanks for this info.

    i will check my latest attempt to burn an uACD with added massstorage device drivers.

    The installation goes fine when launched from a RIS server and fails miserabily when launched from uACD with the same MSD. Adding MSD in txtsetup.sif and makecab the .sys binary in i386 folder solves the issue on uACD.

  20. @Bilou_Gateux

    So kind of you. Could you found any clue as to why the commissioned RAMDisk size is paltry 1 MB? I would have been really satisfied if it remained at 16 MB. Anyway i'll give cmdlines.txt+ramdisk.cmd method a try with "DiskSize 01000000" and see what's in store for me.

    BTW, please unearth Method II,if it's not already lost, my guess is it'll be more adventurous. Please.

    Thanks...

    N.B. You didn't mention even a word about No. 4. Was it really not mentionable?

    Editing ramdiskpro.inf and removed semicolon in below ;obsolete and set data values i.e.:

    [DiskAddReg]HKR, "Parameters", "BreakOnEntry", %REG_DWORD%, 0x00000000

    HKR, "Parameters", "DebugLevel", %REG_DWORD%, 0x00000005

    HKR, "Parameters", "DebugComp", %REG_DWORD%, 0xFFFFFFFF

    HKR, "Parameters", "Format", %REG_SZ%, "NTFS"

    ; If you don't want to use the "RAMDisk Format" service , you have to comment out the following seven lines.

    ; To comment out these lines , just precede them with "; " . See for example line : "; OBSOLETE !" and following

    ; OBSOLETE !

    HKR, "Parameters", "DiskSize", %REG_DWORD%, 0x01000000

    HKR, "Parameters", "DriveLetter", %REG_SZ%, "B:"

    HKR, "Parameters", "RootDirEntries", %REG_DWORD%, 0x00000200

    HKR, "Parameters", "SectorsPerCluster", %REG_DWORD%, 0x00000002

    HKR, "Parameters", "DiskCompression", %REG_DWORD%, 0x00000001

    HKR, "Parameters", "AutoResize", %REG_DWORD%, 0x00000000

    I have also changed "Format" to NTFS and enable "DiskCompression". Disk Size set to 0x1000000 = 16777216 (16 Mb in decimal notation).

×
×
  • Create New...