HOW TO: Make a RAM driver disk in WINPE "startnet.cmd" . Now

[Robell_Liu]

NOW I build a WINPE CD image from Windows OPK 2005.

I want to Make a RAM driver disk such as "M: DISK ".

According to the WEB SIZE can download the free RAM disk driver install file such as "ramdisk.sys ,RAMDriv.reg".

where could I download it?, and HOW could I use it?.

THANKS.!

[Robell_Liu]

if anybody reply?.

if my question is too simple ? or nobody understand my sentence.!

.

I only want to virtual a about 64MB RAM disk. when my WINPE was booted finished.!

[Albuquerque]

Looking back through the forums, ramdisk within a standard Windows PE created from the ODK never is 100% reliable. The most I was able to get reliably out of the ramdisk driver in my own Windows PE 2005 image was 4mb. Any more than 4mb and it would fail randomly; the larger the ramdisk, the more often it would fail, until about 32mb where it almost never worked.

I "fixed" this by using the SDI image method. Rather than loading a ramdisk from ISO file like you're doing now, I load a ramdisk from an SDI file. SDI files are actually complete harddisk images that will also give you the ability to non-permanently "write" to the free space just like a ramdisk. The downside is obviously the memory usage penalty you'll incur, but the upside is plenty of useable room.

However, I think it may be possible that the SDI disk has a limit on how much is writeable, I'm thinking it may be near 32mb. Something to consider.

Want to give it a try? Follow this guide here: http://www.myitforum.com/articles/8/view.asp?id=8832

[Robell_Liu]

TO: Albuquerque

are you upload the youself WinPE 2005 SDI image ?

if have could you give me the download web size links for me?

I want to refer to you builded WinPE 2005 SDI image .!

THANKS.!

[Albuquerque]

Can't do that for multiple reasons; the biggest of which is possible legal consequences for distributing Microsoft ODK components without MS's authorization. Our SA agreement forbids me to do this. I'd also be giving out automation code and service account login credentials that are proprietary to my company which would be quite severe too.

So, the best I can do is answer your questions and point you in the right direction. The FAQ I linked you to has everything you need to create an SDI image from scratch.