Ramdisk for x64

Discussion in 'Windows 64bit' started by =?Utf-8?B?Sm9hY2hpbQ==?=, Aug 3, 2005.

  1. Hello,

    sorry. this post is very long, i know, but if someone can help me, he needs
    all the informations.

    Has anybody a ramdisk-driver for x64? I need a ramdisk under Win PE 2005.
    I don't want to Boot Win PE in a Ramdisk, I want booting WinPE and loading a
    Ramdisk over the Setupreg.hiv as an extra Drive like R:\ which i can use then
    for PE-Sessiontime.

    When creating WinPE for x64 there is a ramdisk-driver under
    '\winpe\AMD64\system32\drivers\ramdisk.sys
    When i try to load the driver over the 'WinPE-Registry' i can't approach the
    ramdisk.
    What is my malfunction, what is the problem? Has anybody an idea

    The Registry-Keys I use are:
    ;
    ; RAMDISK
    ;

    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4},"Class",0000000000,"Sample"
    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4},"Icon",0000000000,"-5"
    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}\0000","DriverDate",0000000000,"01-10-2002"
    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}\0000","DriverDesc",0000000000,"Ramdisk"
    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}\0000","DriverVersion",0000000000,"5.2.3790.1830"
    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}\0000","InfPath",0000000000,"ramdisk.inf"
    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}\0000","InfSection",0000000000,"DiskInstall"
    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}\0000","InfSectionExt",0000000000,".NTamd64"
    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}\0000","MatchingDeviceId",0000000000,"ramdisk"
    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}\0000","ProviderName",0000000000,"Microsoft"

    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE",,0x00000010
    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Capabilities",0x00010001,0x0
    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Class",0000000000,"Sample"
    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","ClassGUID",0000000000,"{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}"
    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","ConfigFlags",0x00010001,0x4
    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","DeviceDesc",0000000000,"Ramdisk"
    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Driver",0000000000,"{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}\0000"
    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","HardwareID",0x00010000,"ROOT\ramdisk"
    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Mfg",0000000000,"Microsoft"
    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Service",0000000000,"Ramdisk"
    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000\Control","ActiveService",0000000000,"Ramdisk"
    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000\LogConf",,0x00000010

    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk","DisplayName",0000000000,"Ramdisk"
    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk","ErrorControl",0x00010001,0x1
    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk","ImagePath",0x00020000,"System32\DRIVERS\ramdisk.sys"
    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk","Start",0x00010001,0x0
    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk","Type",0x00010001,0x1
    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Enum","0",0000000000,"ROOT\SAMPLE\0000"
    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Enum","Count",0x00010001,0x1
    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Enum","NextInstance",0x00010001,0x1
    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","BreakOnEntry",0x00010001,0x0
    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","DebugComp",0x00010001,0xffffffff
    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","DebugLevel",0x00010001,0x0
    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","DiskSize",0x00010001,0x400000
    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","DriveLetter",0000000000,"K:"
    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","RootDirEntries",0x00010001,0x200
    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","SectorsPerCluster",0x00010001,0x2

    The Ramdisk.inf i use:
    ----------------------------------------------------------------------------------------------
    ; RAMDISK.INF
    ; Windows 2000 installation file for installing the Ramdisk driver
    ; Copyright (c) 1990-2000 Microsoft Corporation All rights Reserved

    [Version]
    Signature="$WINDOWS NT$"
    Class=Sample
    ClassGuid={9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}
    Provider=%MSFT%
    DriverVer=10/01/2002,5.2.3790.1830

    [DestinationDirs]
    DefaultDestDir = 12

    [ClassInstall32]
    Addreg=SampleClassReg

    [SampleClassReg]
    HKR,,,0,%ClassName%
    HKR,,Icon,,-5

    [DiskCopyfiles]
    ramdisk.sys

    [SourceDisksNames]
    1=%InstDisk%,

    [SourceDisksFiles]
    ramdisk.sys=1

    [Manufacturer.NTamd64]
    %MSFT% = DiskDevice

    [DiskDevice]
    %DiskDevDesc% = DiskInstall, Ramdisk

    [DiskInstall.NTamd64]
    CopyFiles = DiskCopyfiles

    [DiskInstall.NTamd64.Services]
    AddService = Ramdisk, %SPSVCINST_ASSOCSERVICE%, DiskServiceInst

    [DiskServiceInst]
    ServiceType = %SERVICE_KERNEL_DRIVER%
    StartType = %SERVICE_BOOT_START%
    ErrorControl = %SERVICE_ERROR_NORMAL%
    DisplayName = %DiskServiceDesc%
    ServiceBinary = %12%\ramdisk.sys
    AddReg = DiskAddReg

    [DiskAddReg]
    HKR, "Parameters", "BreakOnEntry", %REG_DWORD%, 0x00000000
    HKR, "Parameters", "DebugLevel", %REG_DWORD%, 0x00000000
    HKR, "Parameters", "DebugComp", %REG_DWORD%, 0xFFFFFFFF
    HKR, "Parameters", "DiskSize", %REG_DWORD%, 0x00100000
    HKR, "Parameters", "DriveLetter", %REG_SZ%, "R:"
    HKR, "Parameters", "RootDirEntries", %REG_DWORD%, 0x00000200
    HKR, "Parameters", "SectorsPerCluster", %REG_DWORD%, 0x00000002

    [Strings]
    MSFT = "Microsoft"
    ClassName = "Sample Driver"
    DiskDevDesc = "Ramdisk Driver"
    DiskServiceDesc = "Ramdisk Driver"
    InstDisk = "Ramdisk Install Disk"
    ;*******************************************
    ;Handy macro substitutions (non-localizable)
    SPSVCINST_ASSOCSERVICE = 0x00000002
    SERVICE_KERNEL_DRIVER = 1
    SERVICE_BOOT_START = 0
    SERVICE_ERROR_NORMAL = 1
    REG_DWORD = 0x00010001
    REG_SZ = 0x00000000

    Many thanks,
    Joachim
    =?Utf-8?B?Sm9hY2hpbQ==?=, Aug 3, 2005
    #1
    1. Advertising

  2. I had thought that Ramdisks was a thing of the past. Of course, it was much
    in use under DOS and it has been around since then - for what unknown
    reason - as 'windows caching' is much faster and more efficient. Back in
    those days the Ramdisk was a necessity, today I cannot guess what would make
    you go through the trouble? Ah, but then I am curious, there is a KB article
    "Q257405" that I'm sure you may know about - this suggest that the Ramdisk
    driver may be a win2k app in its present status and therefor could be
    incompatible with x64.

    That's as far as my expertise goes, I'm affraid. Hope you come to grips with
    whatever it is you're doing.

    Greetings, Tony. . .


    "Joachim" <> wrote in message
    news:...
    > Hello,
    >
    > sorry. this post is very long, i know, but if someone can help me, he
    > needs
    > all the informations.
    >
    > Has anybody a ramdisk-driver for x64? I need a ramdisk under Win PE 2005.
    > I don't want to Boot Win PE in a Ramdisk, I want booting WinPE and loading
    > a
    > Ramdisk over the Setupreg.hiv as an extra Drive like R:\ which i can use
    > then
    > for PE-Sessiontime.
    >
    > When creating WinPE for x64 there is a ramdisk-driver under
    > '\winpe\AMD64\system32\drivers\ramdisk.sys
    > When i try to load the driver over the 'WinPE-Registry' i can't approach
    > the
    > ramdisk.
    > What is my malfunction, what is the problem? Has anybody an idea
    >
    > The Registry-Keys I use are:
    > ;
    > ; RAMDISK
    > ;
    >
    > HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4},"Class",0000000000,"Sample"
    > HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4},"Icon",0000000000,"-5"
    > HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}\0000","DriverDate",0000000000,"01-10-2002"
    > HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}\0000","DriverDesc",0000000000,"Ramdisk"
    > HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}\0000","DriverVersion",0000000000,"5.2.3790.1830"
    > HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}\0000","InfPath",0000000000,"ramdisk.inf"
    > HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}\0000","InfSection",0000000000,"DiskInstall"
    > HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}\0000","InfSectionExt",0000000000,".NTamd64"
    > HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}\0000","MatchingDeviceId",0000000000,"ramdisk"
    > HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}\0000","ProviderName",0000000000,"Microsoft"
    >
    > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE",,0x00000010
    > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Capabilities",0x00010001,0x0
    > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Class",0000000000,"Sample"
    > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","ClassGUID",0000000000,"{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}"
    > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","ConfigFlags",0x00010001,0x4
    > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","DeviceDesc",0000000000,"Ramdisk"
    > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Driver",0000000000,"{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}\0000"
    > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","HardwareID",0x00010000,"ROOT\ramdisk"
    > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Mfg",0000000000,"Microsoft"
    > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Service",0000000000,"Ramdisk"
    > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000\Control","ActiveService",0000000000,"Ramdisk"
    > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000\LogConf",,0x00000010
    >
    > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk","DisplayName",0000000000,"Ramdisk"
    > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk","ErrorControl",0x00010001,0x1
    > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk","ImagePath",0x00020000,"System32\DRIVERS\ramdisk.sys"
    > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk","Start",0x00010001,0x0
    > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk","Type",0x00010001,0x1
    > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Enum","0",0000000000,"ROOT\SAMPLE\0000"
    > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Enum","Count",0x00010001,0x1
    > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Enum","NextInstance",0x00010001,0x1
    > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","BreakOnEntry",0x00010001,0x0
    > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","DebugComp",0x00010001,0xffffffff
    > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","DebugLevel",0x00010001,0x0
    > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","DiskSize",0x00010001,0x400000
    > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","DriveLetter",0000000000,"K:"
    > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","RootDirEntries",0x00010001,0x200
    > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","SectorsPerCluster",0x00010001,0x2
    >
    > The Ramdisk.inf i use:
    > ----------------------------------------------------------------------------------------------
    > ; RAMDISK.INF
    > ; Windows 2000 installation file for installing the Ramdisk driver
    > ; Copyright (c) 1990-2000 Microsoft Corporation All rights Reserved
    >
    > [Version]
    > Signature="$WINDOWS NT$"
    > Class=Sample
    > ClassGuid={9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}
    > Provider=%MSFT%
    > DriverVer=10/01/2002,5.2.3790.1830
    >
    > [DestinationDirs]
    > DefaultDestDir = 12
    >
    > [ClassInstall32]
    > Addreg=SampleClassReg
    >
    > [SampleClassReg]
    > HKR,,,0,%ClassName%
    > HKR,,Icon,,-5
    >
    > [DiskCopyfiles]
    > ramdisk.sys
    >
    > [SourceDisksNames]
    > 1=%InstDisk%,
    >
    > [SourceDisksFiles]
    > ramdisk.sys=1
    >
    > [Manufacturer.NTamd64]
    > %MSFT% = DiskDevice
    >
    > [DiskDevice]
    > %DiskDevDesc% = DiskInstall, Ramdisk
    >
    > [DiskInstall.NTamd64]
    > CopyFiles = DiskCopyfiles
    >
    > [DiskInstall.NTamd64.Services]
    > AddService = Ramdisk, %SPSVCINST_ASSOCSERVICE%, DiskServiceInst
    >
    > [DiskServiceInst]
    > ServiceType = %SERVICE_KERNEL_DRIVER%
    > StartType = %SERVICE_BOOT_START%
    > ErrorControl = %SERVICE_ERROR_NORMAL%
    > DisplayName = %DiskServiceDesc%
    > ServiceBinary = %12%\ramdisk.sys
    > AddReg = DiskAddReg
    >
    > [DiskAddReg]
    > HKR, "Parameters", "BreakOnEntry", %REG_DWORD%, 0x00000000
    > HKR, "Parameters", "DebugLevel", %REG_DWORD%, 0x00000000
    > HKR, "Parameters", "DebugComp", %REG_DWORD%, 0xFFFFFFFF
    > HKR, "Parameters", "DiskSize", %REG_DWORD%, 0x00100000
    > HKR, "Parameters", "DriveLetter", %REG_SZ%, "R:"
    > HKR, "Parameters", "RootDirEntries", %REG_DWORD%, 0x00000200
    > HKR, "Parameters", "SectorsPerCluster", %REG_DWORD%, 0x00000002
    >
    > [Strings]
    > MSFT = "Microsoft"
    > ClassName = "Sample Driver"
    > DiskDevDesc = "Ramdisk Driver"
    > DiskServiceDesc = "Ramdisk Driver"
    > InstDisk = "Ramdisk Install Disk"
    > ;*******************************************
    > ;Handy macro substitutions (non-localizable)
    > SPSVCINST_ASSOCSERVICE = 0x00000002
    > SERVICE_KERNEL_DRIVER = 1
    > SERVICE_BOOT_START = 0
    > SERVICE_ERROR_NORMAL = 1
    > REG_DWORD = 0x00010001
    > REG_SZ = 0x00000000
    >
    > Many thanks,
    > Joachim
    >
    >
    >
    Tony Sperling, Aug 3, 2005
    #2
    1. Advertising

  3. Hello Tony,

    many thanks for your tip, the MS article "Q257405" is interesting.
    But I need a ramdisk after booting from WinPE for x64 to have the
    possibility of buffering data for unattended installation.
    Do you know another method to have such an operation?


    "Tony Sperling" wrote:

    > I had thought that Ramdisks was a thing of the past. Of course, it was much
    > in use under DOS and it has been around since then - for what unknown
    > reason - as 'windows caching' is much faster and more efficient. Back in
    > those days the Ramdisk was a necessity, today I cannot guess what would make
    > you go through the trouble? Ah, but then I am curious, there is a KB article
    > "Q257405" that I'm sure you may know about - this suggest that the Ramdisk
    > driver may be a win2k app in its present status and therefor could be
    > incompatible with x64.
    >
    > That's as far as my expertise goes, I'm affraid. Hope you come to grips with
    > whatever it is you're doing.
    >
    > Greetings, Tony. . .
    >
    >
    > "Joachim" <> wrote in message
    > news:...
    > > Hello,
    > >
    > > sorry. this post is very long, i know, but if someone can help me, he
    > > needs
    > > all the informations.
    > >
    > > Has anybody a ramdisk-driver for x64? I need a ramdisk under Win PE 2005.
    > > I don't want to Boot Win PE in a Ramdisk, I want booting WinPE and loading
    > > a
    > > Ramdisk over the Setupreg.hiv as an extra Drive like R:\ which i can use
    > > then
    > > for PE-Sessiontime.
    > >
    > > When creating WinPE for x64 there is a ramdisk-driver under
    > > '\winpe\AMD64\system32\drivers\ramdisk.sys
    > > When i try to load the driver over the 'WinPE-Registry' i can't approach
    > > the
    > > ramdisk.
    > > What is my malfunction, what is the problem? Has anybody an idea
    > >
    > > The Registry-Keys I use are:
    > > ;
    > > ; RAMDISK
    > > ;
    > >
    > > HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4},"Class",0000000000,"Sample"
    > > HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4},"Icon",0000000000,"-5"
    > > HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}\0000","DriverDate",0000000000,"01-10-2002"
    > > HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}\0000","DriverDesc",0000000000,"Ramdisk"
    > > HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}\0000","DriverVersion",0000000000,"5.2.3790.1830"
    > > HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}\0000","InfPath",0000000000,"ramdisk.inf"
    > > HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}\0000","InfSection",0000000000,"DiskInstall"
    > > HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}\0000","InfSectionExt",0000000000,".NTamd64"
    > > HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}\0000","MatchingDeviceId",0000000000,"ramdisk"
    > > HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}\0000","ProviderName",0000000000,"Microsoft"
    > >
    > > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE",,0x00000010
    > > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Capabilities",0x00010001,0x0
    > > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Class",0000000000,"Sample"
    > > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","ClassGUID",0000000000,"{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}"
    > > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","ConfigFlags",0x00010001,0x4
    > > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","DeviceDesc",0000000000,"Ramdisk"
    > > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Driver",0000000000,"{9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}\0000"
    > > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","HardwareID",0x00010000,"ROOT\ramdisk"
    > > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Mfg",0000000000,"Microsoft"
    > > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Service",0000000000,"Ramdisk"
    > > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000\Control","ActiveService",0000000000,"Ramdisk"
    > > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000\LogConf",,0x00000010
    > >
    > > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk","DisplayName",0000000000,"Ramdisk"
    > > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk","ErrorControl",0x00010001,0x1
    > > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk","ImagePath",0x00020000,"System32\DRIVERS\ramdisk.sys"
    > > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk","Start",0x00010001,0x0
    > > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk","Type",0x00010001,0x1
    > > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Enum","0",0000000000,"ROOT\SAMPLE\0000"
    > > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Enum","Count",0x00010001,0x1
    > > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Enum","NextInstance",0x00010001,0x1
    > > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","BreakOnEntry",0x00010001,0x0
    > > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","DebugComp",0x00010001,0xffffffff
    > > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","DebugLevel",0x00010001,0x0
    > > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","DiskSize",0x00010001,0x400000
    > > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","DriveLetter",0000000000,"K:"
    > > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","RootDirEntries",0x00010001,0x200
    > > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","SectorsPerCluster",0x00010001,0x2
    > >
    > > The Ramdisk.inf i use:
    > > ----------------------------------------------------------------------------------------------
    > > ; RAMDISK.INF
    > > ; Windows 2000 installation file for installing the Ramdisk driver
    > > ; Copyright (c) 1990-2000 Microsoft Corporation All rights Reserved
    > >
    > > [Version]
    > > Signature="$WINDOWS NT$"
    > > Class=Sample
    > > ClassGuid={9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}
    > > Provider=%MSFT%
    > > DriverVer=10/01/2002,5.2.3790.1830
    > >
    > > [DestinationDirs]
    > > DefaultDestDir = 12
    > >
    > > [ClassInstall32]
    > > Addreg=SampleClassReg
    > >
    > > [SampleClassReg]
    > > HKR,,,0,%ClassName%
    > > HKR,,Icon,,-5
    > >
    > > [DiskCopyfiles]
    > > ramdisk.sys
    > >
    > > [SourceDisksNames]
    > > 1=%InstDisk%,
    > >
    > > [SourceDisksFiles]
    > > ramdisk.sys=1
    > >
    > > [Manufacturer.NTamd64]
    > > %MSFT% = DiskDevice
    > >
    > > [DiskDevice]
    > > %DiskDevDesc% = DiskInstall, Ramdisk
    > >
    > > [DiskInstall.NTamd64]
    > > CopyFiles = DiskCopyfiles
    > >
    > > [DiskInstall.NTamd64.Services]
    > > AddService = Ramdisk, %SPSVCINST_ASSOCSERVICE%, DiskServiceInst
    > >
    > > [DiskServiceInst]
    > > ServiceType = %SERVICE_KERNEL_DRIVER%
    > > StartType = %SERVICE_BOOT_START%
    > > ErrorControl = %SERVICE_ERROR_NORMAL%
    > > DisplayName = %DiskServiceDesc%
    > > ServiceBinary = %12%\ramdisk.sys
    > > AddReg = DiskAddReg
    > >
    > > [DiskAddReg]
    > > HKR, "Parameters", "BreakOnEntry", %REG_DWORD%, 0x00000000
    > > HKR, "Parameters", "DebugLevel", %REG_DWORD%, 0x00000000
    > > HKR, "Parameters", "DebugComp", %REG_DWORD%, 0xFFFFFFFF
    > > HKR, "Parameters", "DiskSize", %REG_DWORD%, 0x00100000
    > > HKR, "Parameters", "DriveLetter", %REG_SZ%, "R:"
    > > HKR, "Parameters", "RootDirEntries", %REG_DWORD%, 0x00000200
    > > HKR, "Parameters", "SectorsPerCluster", %REG_DWORD%, 0x00000002
    > >
    > > [Strings]
    > > MSFT = "Microsoft"
    > > ClassName = "Sample Driver"
    > > DiskDevDesc = "Ramdisk Driver"
    > > DiskServiceDesc = "Ramdisk Driver"
    > > InstDisk = "Ramdisk Install Disk"
    > > ;*******************************************
    > > ;Handy macro substitutions (non-localizable)
    > > SPSVCINST_ASSOCSERVICE = 0x00000002
    > > SERVICE_KERNEL_DRIVER = 1
    > > SERVICE_BOOT_START = 0
    > > SERVICE_ERROR_NORMAL = 1
    > > REG_DWORD = 0x00010001
    > > REG_SZ = 0x00000000
    > >
    > > Many thanks,
    > > Joachim
    > >
    > >
    > >

    >
    >
    >
    =?Utf-8?B?Sm9hY2hpbQ==?=, Aug 4, 2005
    #3
  4. O.K. - This is a topic that I have no personal experience with, I can
    remember back when I installed NT4, however, that the resourcekit
    documentation discussed this item for quite some lenght. I also believe that
    this very documentation can be read from the MSD pages.
    (the modern version, presumeably)
    I may be totally wrong here, but isn't unatended installs otherwise most
    conveniently managed through a network? If you are trying to circumvent this
    requirement with a Ramdisk, I suspect it might be a lot easier to invest in
    another machine - an excuse for forwarding your planned update, perhaps?

    No, I am really no authority on the matter, I'm affraid - but do check MSD.

    Tony. . .


    "Joachim" <> wrote in message
    news:...
    > Hello Tony,
    >
    > many thanks for your tip, the MS article "Q257405" is interesting.
    > But I need a ramdisk after booting from WinPE for x64 to have the
    > possibility of buffering data for unattended installation.
    > Do you know another method to have such an operation?
    >
    >
    > "Tony Sperling" wrote:
    >
    > > I had thought that Ramdisks was a thing of the past. Of course, it was

    much
    > > in use under DOS and it has been around since then - for what unknown
    > > reason - as 'windows caching' is much faster and more efficient. Back in
    > > those days the Ramdisk was a necessity, today I cannot guess what would

    make
    > > you go through the trouble? Ah, but then I am curious, there is a KB

    article
    > > "Q257405" that I'm sure you may know about - this suggest that the

    Ramdisk
    > > driver may be a win2k app in its present status and therefor could be
    > > incompatible with x64.
    > >
    > > That's as far as my expertise goes, I'm affraid. Hope you come to grips

    with
    > > whatever it is you're doing.
    > >
    > > Greetings, Tony. . .
    > >
    > >
    > > "Joachim" <> wrote in message
    > > news:...
    > > > Hello,
    > > >
    > > > sorry. this post is very long, i know, but if someone can help me, he
    > > > needs
    > > > all the informations.
    > > >
    > > > Has anybody a ramdisk-driver for x64? I need a ramdisk under Win PE

    2005.
    > > > I don't want to Boot Win PE in a Ramdisk, I want booting WinPE and

    loading
    > > > a
    > > > Ramdisk over the Setupreg.hiv as an extra Drive like R:\ which i can

    use
    > > > then
    > > > for PE-Sessiontime.
    > > >
    > > > When creating WinPE for x64 there is a ramdisk-driver under
    > > > '\winpe\AMD64\system32\drivers\ramdisk.sys
    > > > When i try to load the driver over the 'WinPE-Registry' i can't

    approach
    > > > the
    > > > ramdisk.
    > > > What is my malfunction, what is the problem? Has anybody an idea
    > > >
    > > > The Registry-Keys I use are:
    > > > ;
    > > > ; RAMDISK
    > > > ;
    > > >
    > > >

    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955A
    E4},"Class",0000000000,"Sample"
    > > >

    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955A
    E4},"Icon",0000000000,"-5"
    > > >

    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955A
    E4}\0000","DriverDate",0000000000,"01-10-2002"
    > > >

    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955A
    E4}\0000","DriverDesc",0000000000,"Ramdisk"
    > > >

    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955A
    E4}\0000","DriverVersion",0000000000,"5.2.3790.1830"
    > > >

    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955A
    E4}\0000","InfPath",0000000000,"ramdisk.inf"
    > > >

    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955A
    E4}\0000","InfSection",0000000000,"DiskInstall"
    > > >

    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955A
    E4}\0000","InfSectionExt",0000000000,".NTamd64"
    > > >

    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955A
    E4}\0000","MatchingDeviceId",0000000000,"ramdisk"
    > > >

    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955A
    E4}\0000","ProviderName",0000000000,"Microsoft"
    > > >
    > > > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE",,0x00000010
    > > >

    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Capabilities",0x00010001,
    0x0
    > > >

    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Class",0000000000,"Sample
    "
    > > >

    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","ClassGUID",0000000000,"{9
    D6D66A6-0B0C-4563-9077-A0E9A7955AE4}"
    > > >

    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","ConfigFlags",0x00010001,0
    x4
    > > >

    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","DeviceDesc",0000000000,"R
    amdisk"
    > > >

    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Driver",0000000000,"{9D6D
    66A6-0B0C-4563-9077-A0E9A7955AE4}\0000"
    > > >

    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","HardwareID",0x00010000,"R
    OOT\ramdisk"
    > > >

    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Mfg",0000000000,"Microsof
    t"
    > > >

    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Service",0000000000,"Ramd
    isk"
    > > >

    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000\Control","ActiveService",00
    00000000,"Ramdisk"
    > > > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000\LogConf",,0x00000010
    > > >
    > > >

    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk","DisplayName",0000000000,"Ramdi
    sk"
    > > >

    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk","ErrorControl",0x00010001,0x1
    > > >

    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk","ImagePath",0x00020000,"System3
    2\DRIVERS\ramdisk.sys"
    > > > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk","Start",0x00010001,0x0
    > > > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk","Type",0x00010001,0x1
    > > >

    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Enum","0",0000000000,"ROOT\SAMPL
    E\0000"
    > > >

    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Enum","Count",0x00010001,0x1
    > > >

    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Enum","NextInstance",0x00010001,
    0x1
    > > >

    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","BreakOnEntry",0x000
    10001,0x0
    > > >

    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","DebugComp",0x000100
    01,0xffffffff
    > > >

    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","DebugLevel",0x00010
    001,0x0
    > > >

    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","DiskSize",0x0001000
    1,0x400000
    > > >

    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","DriveLetter",000000
    0000,"K:"
    > > >

    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","RootDirEntries",0x0
    0010001,0x200
    > > >

    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","SectorsPerCluster",
    0x00010001,0x2
    > > >
    > > > The Ramdisk.inf i use:

    > >

    > --------------------------------------------------------------------------

    --------------------
    > > > ; RAMDISK.INF
    > > > ; Windows 2000 installation file for installing the Ramdisk driver
    > > > ; Copyright (c) 1990-2000 Microsoft Corporation All rights Reserved
    > > >
    > > > [Version]
    > > > Signature="$WINDOWS NT$"
    > > > Class=Sample
    > > > ClassGuid={9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}
    > > > Provider=%MSFT%
    > > > DriverVer=10/01/2002,5.2.3790.1830
    > > >
    > > > [DestinationDirs]
    > > > DefaultDestDir = 12
    > > >
    > > > [ClassInstall32]
    > > > Addreg=SampleClassReg
    > > >
    > > > [SampleClassReg]
    > > > HKR,,,0,%ClassName%
    > > > HKR,,Icon,,-5
    > > >
    > > > [DiskCopyfiles]
    > > > ramdisk.sys
    > > >
    > > > [SourceDisksNames]
    > > > 1=%InstDisk%,
    > > >
    > > > [SourceDisksFiles]
    > > > ramdisk.sys=1
    > > >
    > > > [Manufacturer.NTamd64]
    > > > %MSFT% = DiskDevice
    > > >
    > > > [DiskDevice]
    > > > %DiskDevDesc% = DiskInstall, Ramdisk
    > > >
    > > > [DiskInstall.NTamd64]
    > > > CopyFiles = DiskCopyfiles
    > > >
    > > > [DiskInstall.NTamd64.Services]
    > > > AddService = Ramdisk, %SPSVCINST_ASSOCSERVICE%, DiskServiceInst
    > > >
    > > > [DiskServiceInst]
    > > > ServiceType = %SERVICE_KERNEL_DRIVER%
    > > > StartType = %SERVICE_BOOT_START%
    > > > ErrorControl = %SERVICE_ERROR_NORMAL%
    > > > DisplayName = %DiskServiceDesc%
    > > > ServiceBinary = %12%\ramdisk.sys
    > > > AddReg = DiskAddReg
    > > >
    > > > [DiskAddReg]
    > > > HKR, "Parameters", "BreakOnEntry", %REG_DWORD%, 0x00000000
    > > > HKR, "Parameters", "DebugLevel", %REG_DWORD%, 0x00000000
    > > > HKR, "Parameters", "DebugComp", %REG_DWORD%, 0xFFFFFFFF
    > > > HKR, "Parameters", "DiskSize", %REG_DWORD%, 0x00100000
    > > > HKR, "Parameters", "DriveLetter", %REG_SZ%, "R:"
    > > > HKR, "Parameters", "RootDirEntries", %REG_DWORD%, 0x00000200
    > > > HKR, "Parameters", "SectorsPerCluster", %REG_DWORD%, 0x00000002
    > > >
    > > > [Strings]
    > > > MSFT = "Microsoft"
    > > > ClassName = "Sample Driver"
    > > > DiskDevDesc = "Ramdisk Driver"
    > > > DiskServiceDesc = "Ramdisk Driver"
    > > > InstDisk = "Ramdisk Install Disk"
    > > > ;*******************************************
    > > > ;Handy macro substitutions (non-localizable)
    > > > SPSVCINST_ASSOCSERVICE = 0x00000002
    > > > SERVICE_KERNEL_DRIVER = 1
    > > > SERVICE_BOOT_START = 0
    > > > SERVICE_ERROR_NORMAL = 1
    > > > REG_DWORD = 0x00010001
    > > > REG_SZ = 0x00000000
    > > >
    > > > Many thanks,
    > > > Joachim
    > > >
    > > >
    > > >

    > >
    > >
    > >
    Tony Sperling, Aug 4, 2005
    #4
  5. Sorry, I meant MSDN.

    But heres somewhere that might be a starting point:

    http://www.microsoft.com/technet/prodtechnol/winxppro/default.mspx

    Tony. . .


    "Joachim" <> wrote in message
    news:...
    > Hello Tony,
    >
    > many thanks for your tip, the MS article "Q257405" is interesting.
    > But I need a ramdisk after booting from WinPE for x64 to have the
    > possibility of buffering data for unattended installation.
    > Do you know another method to have such an operation?
    >
    >
    > "Tony Sperling" wrote:
    >
    > > I had thought that Ramdisks was a thing of the past. Of course, it was

    much
    > > in use under DOS and it has been around since then - for what unknown
    > > reason - as 'windows caching' is much faster and more efficient. Back in
    > > those days the Ramdisk was a necessity, today I cannot guess what would

    make
    > > you go through the trouble? Ah, but then I am curious, there is a KB

    article
    > > "Q257405" that I'm sure you may know about - this suggest that the

    Ramdisk
    > > driver may be a win2k app in its present status and therefor could be
    > > incompatible with x64.
    > >
    > > That's as far as my expertise goes, I'm affraid. Hope you come to grips

    with
    > > whatever it is you're doing.
    > >
    > > Greetings, Tony. . .
    > >
    > >
    > > "Joachim" <> wrote in message
    > > news:...
    > > > Hello,
    > > >
    > > > sorry. this post is very long, i know, but if someone can help me, he
    > > > needs
    > > > all the informations.
    > > >
    > > > Has anybody a ramdisk-driver for x64? I need a ramdisk under Win PE

    2005.
    > > > I don't want to Boot Win PE in a Ramdisk, I want booting WinPE and

    loading
    > > > a
    > > > Ramdisk over the Setupreg.hiv as an extra Drive like R:\ which i can

    use
    > > > then
    > > > for PE-Sessiontime.
    > > >
    > > > When creating WinPE for x64 there is a ramdisk-driver under
    > > > '\winpe\AMD64\system32\drivers\ramdisk.sys
    > > > When i try to load the driver over the 'WinPE-Registry' i can't

    approach
    > > > the
    > > > ramdisk.
    > > > What is my malfunction, what is the problem? Has anybody an idea
    > > >
    > > > The Registry-Keys I use are:
    > > > ;
    > > > ; RAMDISK
    > > > ;
    > > >
    > > >

    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955A
    E4},"Class",0000000000,"Sample"
    > > >

    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955A
    E4},"Icon",0000000000,"-5"
    > > >

    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955A
    E4}\0000","DriverDate",0000000000,"01-10-2002"
    > > >

    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955A
    E4}\0000","DriverDesc",0000000000,"Ramdisk"
    > > >

    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955A
    E4}\0000","DriverVersion",0000000000,"5.2.3790.1830"
    > > >

    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955A
    E4}\0000","InfPath",0000000000,"ramdisk.inf"
    > > >

    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955A
    E4}\0000","InfSection",0000000000,"DiskInstall"
    > > >

    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955A
    E4}\0000","InfSectionExt",0000000000,".NTamd64"
    > > >

    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955A
    E4}\0000","MatchingDeviceId",0000000000,"ramdisk"
    > > >

    HKLM,"SYSTEM\ControlSet001\Control\Class\{9D6D66A6-0B0C-4563-9077-A0E9A7955A
    E4}\0000","ProviderName",0000000000,"Microsoft"
    > > >
    > > > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE",,0x00000010
    > > >

    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Capabilities",0x00010001,
    0x0
    > > >

    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Class",0000000000,"Sample
    "
    > > >

    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","ClassGUID",0000000000,"{9
    D6D66A6-0B0C-4563-9077-A0E9A7955AE4}"
    > > >

    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","ConfigFlags",0x00010001,0
    x4
    > > >

    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","DeviceDesc",0000000000,"R
    amdisk"
    > > >

    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Driver",0000000000,"{9D6D
    66A6-0B0C-4563-9077-A0E9A7955AE4}\0000"
    > > >

    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","HardwareID",0x00010000,"R
    OOT\ramdisk"
    > > >

    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Mfg",0000000000,"Microsof
    t"
    > > >

    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Service",0000000000,"Ramd
    isk"
    > > >

    HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000\Control","ActiveService",00
    00000000,"Ramdisk"
    > > > HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000\LogConf",,0x00000010
    > > >
    > > >

    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk","DisplayName",0000000000,"Ramdi
    sk"
    > > >

    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk","ErrorControl",0x00010001,0x1
    > > >

    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk","ImagePath",0x00020000,"System3
    2\DRIVERS\ramdisk.sys"
    > > > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk","Start",0x00010001,0x0
    > > > HKLM,"SYSTEM\ControlSet001\Services\Ramdisk","Type",0x00010001,0x1
    > > >

    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Enum","0",0000000000,"ROOT\SAMPL
    E\0000"
    > > >

    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Enum","Count",0x00010001,0x1
    > > >

    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Enum","NextInstance",0x00010001,
    0x1
    > > >

    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","BreakOnEntry",0x000
    10001,0x0
    > > >

    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","DebugComp",0x000100
    01,0xffffffff
    > > >

    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","DebugLevel",0x00010
    001,0x0
    > > >

    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","DiskSize",0x0001000
    1,0x400000
    > > >

    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","DriveLetter",000000
    0000,"K:"
    > > >

    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","RootDirEntries",0x0
    0010001,0x200
    > > >

    HKLM,"SYSTEM\ControlSet001\Services\Ramdisk\Parameters","SectorsPerCluster",
    0x00010001,0x2
    > > >
    > > > The Ramdisk.inf i use:

    > >

    > --------------------------------------------------------------------------

    --------------------
    > > > ; RAMDISK.INF
    > > > ; Windows 2000 installation file for installing the Ramdisk driver
    > > > ; Copyright (c) 1990-2000 Microsoft Corporation All rights Reserved
    > > >
    > > > [Version]
    > > > Signature="$WINDOWS NT$"
    > > > Class=Sample
    > > > ClassGuid={9D6D66A6-0B0C-4563-9077-A0E9A7955AE4}
    > > > Provider=%MSFT%
    > > > DriverVer=10/01/2002,5.2.3790.1830
    > > >
    > > > [DestinationDirs]
    > > > DefaultDestDir = 12
    > > >
    > > > [ClassInstall32]
    > > > Addreg=SampleClassReg
    > > >
    > > > [SampleClassReg]
    > > > HKR,,,0,%ClassName%
    > > > HKR,,Icon,,-5
    > > >
    > > > [DiskCopyfiles]
    > > > ramdisk.sys
    > > >
    > > > [SourceDisksNames]
    > > > 1=%InstDisk%,
    > > >
    > > > [SourceDisksFiles]
    > > > ramdisk.sys=1
    > > >
    > > > [Manufacturer.NTamd64]
    > > > %MSFT% = DiskDevice
    > > >
    > > > [DiskDevice]
    > > > %DiskDevDesc% = DiskInstall, Ramdisk
    > > >
    > > > [DiskInstall.NTamd64]
    > > > CopyFiles = DiskCopyfiles
    > > >
    > > > [DiskInstall.NTamd64.Services]
    > > > AddService = Ramdisk, %SPSVCINST_ASSOCSERVICE%, DiskServiceInst
    > > >
    > > > [DiskServiceInst]
    > > > ServiceType = %SERVICE_KERNEL_DRIVER%
    > > > StartType = %SERVICE_BOOT_START%
    > > > ErrorControl = %SERVICE_ERROR_NORMAL%
    > > > DisplayName = %DiskServiceDesc%
    > > > ServiceBinary = %12%\ramdisk.sys
    > > > AddReg = DiskAddReg
    > > >
    > > > [DiskAddReg]
    > > > HKR, "Parameters", "BreakOnEntry", %REG_DWORD%, 0x00000000
    > > > HKR, "Parameters", "DebugLevel", %REG_DWORD%, 0x00000000
    > > > HKR, "Parameters", "DebugComp", %REG_DWORD%, 0xFFFFFFFF
    > > > HKR, "Parameters", "DiskSize", %REG_DWORD%, 0x00100000
    > > > HKR, "Parameters", "DriveLetter", %REG_SZ%, "R:"
    > > > HKR, "Parameters", "RootDirEntries", %REG_DWORD%, 0x00000200
    > > > HKR, "Parameters", "SectorsPerCluster", %REG_DWORD%, 0x00000002
    > > >
    > > > [Strings]
    > > > MSFT = "Microsoft"
    > > > ClassName = "Sample Driver"
    > > > DiskDevDesc = "Ramdisk Driver"
    > > > DiskServiceDesc = "Ramdisk Driver"
    > > > InstDisk = "Ramdisk Install Disk"
    > > > ;*******************************************
    > > > ;Handy macro substitutions (non-localizable)
    > > > SPSVCINST_ASSOCSERVICE = 0x00000002
    > > > SERVICE_KERNEL_DRIVER = 1
    > > > SERVICE_BOOT_START = 0
    > > > SERVICE_ERROR_NORMAL = 1
    > > > REG_DWORD = 0x00010001
    > > > REG_SZ = 0x00000000
    > > >
    > > > Many thanks,
    > > > Joachim
    > > >
    > > >
    > > >

    > >
    > >
    > >
    Tony Sperling, Aug 4, 2005
    #5
  6. =?Utf-8?B?Sm9hY2hpbQ==?=

    Rob Stow Guest

    Tony Sperling wrote:
    > I had thought that Ramdisks was a thing of the past.


    I know someone who uses a RamDisk in conjunction with VMWare to
    help him with software testing.

    When he reboots his machine, his primary OS creates a 2 GB
    RamDisk and restores an image create by Drive Image to the
    RamDisk. He can then boot off of that RamDisk from within a
    VMWare virtual machine.

    If during the course of his software testing he wants or needs to
    reboot the OS in that VM, it only takes about 3 seconds. Prior
    to using a RamDisk, he had the VM booting from a hard drive and
    it would about a minute.

    IIRC, he is using W2K as his primary OS, VMWare 3.0, SuperSpeed
    for the RamDisk, and runs XP32 inside the VM. He is eagerly
    awaiting VM software and RamDisk software that works with XP64 so
    that he can have more and/or larger RamDisks.
    Rob Stow, Aug 4, 2005
    #6
  7. Well, it would have to be something not quite 'ordinary' run-of-the-mill
    sort of thing. I've always thought that peoples home-knitted solutions to
    varying needs far overshoot all engineered solutions put together. Ah, well
    maybe I'll rephrase that - just think if we had to rely on engineered
    solutions alone???

    Actually, this could be one apparant solution to dodging the need for a
    network, as in Joachim's case.

    x64 compatible VMWare and W2K compatible Ramdisk - sounds feasible, I should
    think. Remains to calculate what will be cheaper - VMWare or an extra
    machine? As for x64 compatibility - I have seen one of VMWare's try-outs on
    PAMD64 - look in the 'apps' folder, or maybe 'miscellaneous'.

    Start here: http://www.planetamd64.com/index.php?

    Greetings Rob & Friend.

    Tony. . .



    "Rob Stow" <> wrote in message
    news:...
    > Tony Sperling wrote:
    >> I had thought that Ramdisks was a thing of the past.

    >
    > I know someone who uses a RamDisk in conjunction with VMWare to help him
    > with software testing.
    >
    > When he reboots his machine, his primary OS creates a 2 GB RamDisk and
    > restores an image create by Drive Image to the RamDisk. He can then boot
    > off of that RamDisk from within a VMWare virtual machine.
    >
    > If during the course of his software testing he wants or needs to reboot
    > the OS in that VM, it only takes about 3 seconds. Prior to using a
    > RamDisk, he had the VM booting from a hard drive and it would about a
    > minute.
    >
    > IIRC, he is using W2K as his primary OS, VMWare 3.0, SuperSpeed for the
    > RamDisk, and runs XP32 inside the VM. He is eagerly awaiting VM software
    > and RamDisk software that works with XP64 so that he can have more and/or
    > larger RamDisks.
    Tony Sperling, Aug 5, 2005
    #7
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Daniel Herrmann

    Upgrading x64 evaluation with full version of x64 prof?

    Daniel Herrmann, Jun 21, 2005, in forum: Microsoft Certification
    Replies:
    0
    Views:
    497
    Daniel Herrmann
    Jun 21, 2005
  2. =?Utf-8?B?TWFsY29sbQ==?=

    X64 trial to x64 full verion OEM

    =?Utf-8?B?TWFsY29sbQ==?=, May 24, 2005, in forum: Windows 64bit
    Replies:
    8
    Views:
    496
    Joseph Conway [MSFT]
    May 25, 2005
  3. =?Utf-8?B?U21lYWdvbA==?=

    Ethereal for x64 -- or Network Monitor for x64

    =?Utf-8?B?U21lYWdvbA==?=, Jun 17, 2005, in forum: Windows 64bit
    Replies:
    0
    Views:
    1,067
    =?Utf-8?B?U21lYWdvbA==?=
    Jun 17, 2005
  4. tim

    running windows NT on a ramdisk

    tim, Aug 28, 2003, in forum: NZ Computing
    Replies:
    7
    Views:
    416
    Richard Malcolm-Smith
    Aug 29, 2003
  5. Giuen
    Replies:
    0
    Views:
    875
    Giuen
    Sep 12, 2008
Loading...

Share This Page