Free Ramdisk for Windows Vista, XP, 2000 and 2003 Server
- Parameters registry is
HKLM\System\CurrentControlSet\Services\RRamdisk\Parameters\
Why RRamdisk? Because XP SP1 contain a Ramdisk driver for XP Embeded.
- Parameter: DiskSizeM, DiskSizeK
Your desired disk size, the unit is M bytes or K bytes. The DiskSizeK has higher priority.
- Parameter: MediaType
The reported drive type:
1 — RAM Drive
2 — Fixed Media (default)
3 — Removable Media
4 — Floppy Diskette - Parameter: DriveLetter
Name say it is, default is R:
- Parameter: SectorsPerCluster
Your desired cluster size, zero for driver pickup:
<= 2M FAT12, cluster=512
<= 32M FAT16, cluster=512
<= 64M FAT16, cluster=1k
<= 128M FAT16, cluster=2k
<= 256M FAT16, cluster=4k
<= 512M FAT32, cluster=2k
<= 16G FAT32, cluster=4k
and more...You can specify smaller cluster size, force pre-format as FAT32.
- Parameter: Image
Maintained by rdutil utlilty, mainly for preload NTFS image. Eg:
- Load ramdisk, don’t write anything.
- Format the ramdisk
FORMAT /FS:NTFS /Q /V:RamDisk /A:512 R:
- Adjust logfile to minimum size
CHKDSK /L:2048 R:
- Reset access rights
CACLS R:\ /G: BUILTIN\Adminstrators:F
- Create necessary structure
MKDIR R:\TEMP
- Pack the disk image and save to registry
rdutil R: registry
Notes:
- You should leave RamDisk as clean as possible before packing, the max packed image size is 64K.
- The disk image only valid to same RamDisk size, you should re-create disk image when size changed.
- The driver internal formater will disable if this registry present, corrupt/size-mismatch value leave an un-formated disk.
rdutil Utlility Usage:
- Backup registry image
rdutil save filename
- Restore registry image
rdutil load filename
- Report packed image size
rdutil R:
rdutil registry
rdutil unpacked_fileSecond command reading DriveLetter from registry, while the third is packing an unpacked image file.
- Packing image & save to registry
rdutil R: registry
- Packing image & save to file
rdutil R: packed_file
- Unpacking image
rdutil unpack packed_file unpacked_file
- Link NTFS junction to Ramdisk
rdutil link temp \
- You can re-format RamDisk except RAMDrive media type. Eg:
FixedMedia type:
FORMAT /FS:NTFS /FORCE /Q /V:RamDisk /A:512 R:RemovableMedia type:
ECHO Y | FORMAT /FS:NTFS /FORCE /Q /V:RamDisk /A:512 R:You can place your format command to startup script. I don’t recommend re-format to FAT, the pre-formated RamDisk is more efficient than other format utililty.
- Pagefile support - You can set pagefile to FixMedia type disk w/ pre-formated system. If you need other MediaType or re-format, use the addswap.exe utility:
addswap r:\pagefile.sys 16 32
Create pagefile r:\pagefile.sys with min=16M max=32M.
- TEMP directory - You should set TEMP/TMP directory to TEMP sub-directory, don’t use the root directory.
- NTFS junction point to RAMDrive - You can’t create NTFS junction point to RAMDrive media type, Fixed & Removable Media type should work.
- Connectix VirtualPC compatibility - Someone report problem with VirtualPC+physical volume/disk. Please set MediaType to RAMDrive/Removable.
- Mountpoint without DriveLetter
Clear DriveLetter registry value will not create Drive Letter for Ramdisk.
Attn. Don’t delete the DriveLetter registry, which fall to default R:. You can setup mountpoint/junction linking to this unnamed Ramdisk. Eg:
rdutil link C:\ramdisk
link C:\ramdisk to root of Ramdiskrdutil link C:\TEMP TEMP
link C:\TEMP to \TEMP at Ramdiskrmdir C:\ramdisk
rmdir can remove the link without clear target contentNoDriveLetter configuration isn’t recommended, because most AntiVirus software cannot realtime scan Volume w/o Drive Letter.
Pages: 1 2
Get help or contribute tips or tricks at My Digital Life Forums.Related Articles
- Download Microsoft Virtual PC 2004 for Free
- Windows Updates Downloader 2.25 Released for Free Download (WUD)
- Windows Server “Longhorn” Beta 3 Free Download
- Restore Windows NT Backup (ntbackup) .bkf in Vista and ‘Longhorn’ Server 2008
- Best and Worst Microsoft Products
- Restore Windows XP and 2003 .bkf Backups in Windows Vista and Longhorn Server with NT Backup Restore Utility
- Install Windows Server 2003 Administration Tools Pack (adminpak) on Windows Vista
- How to Install KMS Server to Activate Windows Vista Business or Enterprise
- Download Key Management Service (KMS Host) for Windows Server 2003
- How to Install Recovery Console as NTLDR Boot Startup Option on Windows XP/2003/2000
March 1st, 2008 04:58
found the reason why it fails
http://support.microsoft.com/kb/257405
Windows XP Update:
Installing the Ramdisk sample driver in a NTFS only machine might make it unusable. To resolve this problem make the following change:
While you call the IoCreateDevice function (RamdiskAddDevice function in pnp.c), change the device type from FILE_DEVICE_VIRTUAL_DISK to FILE_DEVICE_DISK and recompile the driver. After you install the driver, restart the system in order to access the Ramdisk through Explorer.
Someone please inform Gavotte and have a fix made. Thank you
March 1st, 2008 04:05
05.23.2007 version and greater allows for x64 support
March 1st, 2008 04:03
The ramdisk driver has an error. Setting the ramdisk media type to ramdisk is missing a component for proper initialization (the other file types work well). Another drive that has removable media is required to load up required drivers for this ramdisk - without the removable media the ramdisk is RAW. As soon as the removable media is inserted the Ramdisk is usable.
This is most likely an oversight as that the writer having this dependent component loaded up in the background didn’t realize it was dependent. Systems without this component do not work. There is a newer release as well 01.01.2008 which allows for >=4GB ramdisks (the error is still apparent within this new release)
February 28th, 2008 03:35
Dear Chang,
I don’t know the behaviour of Rramdisk under Win Vista. I still use Win2000. In my oppinion this is the most stable one among all the Windows family. Not all what is newest is always the best.