Go Back   TechArena Community > Technical Support > Computer Help > Windows XP > Windows x64 Edition
Ramdisk for x64 Ramdisk for x64
Become a Member!
Forgot your username/password?
Register Tags Active Topics RSS Search Mark Forums Read SiteMap

Tags: ,

Sponsored Links



Ramdisk for x64

Windows x64 Edition


Reply
 
Thread Tools Search this Thread
  #1  
Old 03-08-2005
Joachim
 
Posts: n/a
Ramdisk for x64
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



Reply With Quote
  #2  
Old 03-08-2005
Tony Sperling
 
Posts: n/a
Re: Ramdisk for x64
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" <Joachim@discussions.microsoft.com> wrote in message
news:C8014E04-CE25-40A6-9537-B1C4270DC81B@microsoft.com...
> 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
>
>
>


Reply With Quote
  #3  
Old 04-08-2005
Joachim
 
Posts: n/a
Re: Ramdisk for x64
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" <Joachim@discussions.microsoft.com> wrote in message
> news:C8014E04-CE25-40A6-9537-B1C4270DC81B@microsoft.com...
> > 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
> >
> >
> >
>
>
>
Reply With Quote
  #4  
Old 04-08-2005
Tony Sperling
 
Posts: n/a
Re: Ramdisk for x64
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" <Joachim@discussions.microsoft.com> wrote in message
news:32412E99-8C27-46A1-B0B2-FC402F284B09@microsoft.com...
> 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" <Joachim@discussions.microsoft.com> wrote in message
> > news:C8014E04-CE25-40A6-9537-B1C4270DC81B@microsoft.com...
> > > 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
> > >
> > >
> > >
> >
> >
> >


Reply With Quote
  #5  
Old 04-08-2005
Tony Sperling
 
Posts: n/a
Re: Ramdisk for x64
Sorry, I meant MSDN.

But heres somewhere that might be a starting point:

http://www.microsoft.com/technet/pro...o/default.mspx

Tony. . .


"Joachim" <Joachim@discussions.microsoft.com> wrote in message
news:32412E99-8C27-46A1-B0B2-FC402F284B09@microsoft.com...
> 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" <Joachim@discussions.microsoft.com> wrote in message
> > news:C8014E04-CE25-40A6-9537-B1C4270DC81B@microsoft.com...
> > > 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
> > >
> > >
> > >
> >
> >
> >


Reply With Quote
  #6  
Old 05-08-2005
Rob Stow
 
Posts: n/a
Re: Ramdisk for x64
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.
Reply With Quote
  #7  
Old 05-08-2005
Tony Sperling
 
Posts: n/a
Re: Ramdisk for x64
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" <rob.stow@shaw.ca> wrote in message
news:enFPUPSmFHA.1464@TK2MSFTNGP14.phx.gbl...
> 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.


Reply With Quote
Reply

  TechArena Community > Technical Support > Computer Help > Windows XP > Windows x64 Edition

« PCI modem driver Smart Link 56K Voice Modem    Microsoft UAA Bus Driver for High Definition Audio »

Thread Tools Search this Thread
Search this Thread:

Advanced Search


Similar Threads for: "Ramdisk for x64"
Thread Thread Starter Forum Replies Last Post
Run Mozilla Firefox on a ramdisk Vj@y.Deenanath Technology & Internet 9 04-12-2011 12:18 AM
Is it wise to move Windows 7 pagefile.sys to RAMDisk With RamDisk Plus & 10GB of RAM Alfons Operating Systems 5 09-03-2011 10:08 PM
Free Windows 7 RAMdisk application Hakesh Operating Systems 4 07-03-2011 12:56 PM
create a RAMdisk on the server MassMan Networking & Security 3 07-03-2011 06:31 AM
ramdisk.sys is corrupted Bannana_Kaaboom Windows XP Support 2 11-03-2005 08:59 PM


All times are GMT +5.5. The time now is 07:49 AM.

Contact Us - TechArena - Privacy Statement -