Tutorial to add a ramdrive to Windows PE:

Note: You must use the Windows PE specivic Ramdisk driver!
This seems to be the problem for most users!
You can find it here (more detailed explained below):

http://download.microsoft.com/download/win...ploymentKit.exe



To create a custom version of Windows PE:


1. Create a Folder on your Harddisk (maybe call it OWN)
2. Copy the content of \WINPE of your original WINPE-CD to the previeusliy installed directory so that this direktory contain this:

Verzeichnis von E:\OWN

03.02.2003 08:04 <DIR> .
03.02.2003 06:33 <DIR> ..
28.08.2002 17:08 38.400 BLDHIVES.EXE
13.09.2002 12:38 99.085 BUILDOPTIONALCOMPONENTS.VBS
28.08.2002 13:00 2.096 CONFIG.INF
14.09.2002 14:04 90.112 DEFAULT
28.08.2002 17:09 13.312 DEPEND.EXE
28.08.2002 17:09 8.192 DSKIMAGE.EXE
28.08.2002 17:30 68.608 EFINVR.EXE
25.03.2002 11:53 2.048 ETFSBOOT.COM
09.09.2002 02:21 11.966 EULA.TXT
13.09.2002 13:38 2.818 EXTRA.INF
17.08.2001 04:03 70.683 FONT.INF
22.08.2001 21:00 212.893 HIVECLS.INF
22.08.2001 21:00 152.986 HIVEDEF.INF
22.08.2001 21:00 299.169 HIVESFT.INF
22.08.2001 21:00 333.380 HIVESYS.INF
22.08.2001 21:00 163.801 HIVEUSD.INF
28.08.2002 17:30 305.664 IA64FACTORY.EXE
28.08.2002 17:30 33.280 IA64NETCFG.EXE
22.08.2001 21:00 807.322 INTL.INF
13.09.2002 13:32 8.636 MKIMG.CMD
28.08.2002 17:08 55.808 OEMMINT.EXE
28.08.2002 13:20 75.776 OSCDIMG.EXE
25.03.2002 11:53 0 SAM
25.03.2002 11:53 0 SAM.LOG
25.03.2002 11:53 0 SECURITY
25.03.2002 11:53 0 SECURITY.LOG
14.09.2002 14:04 147.456 SETUPREG.HIV
14.09.2002 14:04 630.784 SOFTWARE
25.03.2002 11:53 0 SOFTWARE.LOG
25.03.2002 11:54 106 STARTNET.CMD
25.03.2002 11:54 14 STARTOPK.CMD
25.03.2002 11:54 167 WINBOM.INI
28.08.2002 13:00 1.224 WINPEDEF.INF
25.03.2002 11:54 1.190 WINPEOEM.SIF
28.08.2002 13:00 30.802 WINPESFT.INF
28.08.2002 13:00 99.116 WINPESYS.INF
25.03.2002 11:54 11.463 WPEMSCLI.INF
25.03.2002 11:54 2.042 WPENB.INF
12.07.2002 10:42 20.573 WPETCPIP.INF
28.08.2002 17:08 120.832 X86FACTORY.EXE
28.08.2002 17:08 15.360 X86NETCFG.EXE
41 Datei(en) 3.937.164 Bytes
2 Verzeichnis(se), 0 Bytes frei

3. Rename X86FACTORY.EXE to Factory.exe and X86NETCFG.EXE to NETCFG.EXE Note that this is for X86 systems.

4. Edit the WinPESys.inf like following ( you can also use an already modified version, see step 5):
Locate the string "; Nls" (without the quotes).
The following text should be inserted immediately following the Nls registry key settings.
------------------------------------------------------------------------------------------------------------------------------------------

;
;RAMDRV (SAMPLE) Implementation (Based on Rajuram - DDK Support)
;ENTRIES ADDED BY (Sivakn - DS OPK Support)
;

HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-
00C04FAD5171},"Class",0000000000,"Sample"
HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-
00C04FAD5171},"Icon",0000000000,"-5"
HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-
00C04FAD5171}\0000","DriverDate",0000000000,"11-14-1999"
HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-
00C04FAD5171}\0000","DriverDesc",0000000000,"Ramdrv Driver"
HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-
00C04FAD5171}\0000","DriverVersion",0000000000,"5.0.2183.1"
HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-
00C04FAD5171}\0000","InfPath",0000000000,"ramdrv.inf"
HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-
00C04FAD5171}\0000","InfSection",0000000000,"DiskInstall"
HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-
00C04FAD5171}\0000","InfSectionExt",0000000000,".NT"
HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-
00C04FAD5171}\0000","MatchingDeviceId",0000000000,"ramdrv"
HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-
00C04FAD5171}\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,
"{78A1C341-4539-11D3-B88D-00C04FAD5171}"
HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","ConfigFlags",0x00010001,0x4
HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","DeviceDesc",0000000000,"Ramdrv Driver"
HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Driver",0000000000,
"{78A1C341-4539-11D3-B88D-00C04FAD5171}\0000"
HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","HardwareID",0x00010000,"ROOT\ramdrv"
HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Mfg",0000000000,"Microsoft"
HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Service",0000000000,"Ramdrv"
HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000\Control","ActiveService",0000000000,"Ramdrv"
HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000\LogConf",,0x00000010

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

;
; END ENTRIES ADDED by (sivakn - RAMDRV SUPPORT)
;
------------------------------------------------------------------------------------------------------------------------------------------

The default drive letter for the RAM disk drive will be R:. It is defined by the reg key:

HKLM\System\ControlerSet001\Services\ramdrv\Parameters\DriveLetter

The default size for the RAM disk drive is 4MB. It is defined by the reg key:

HKLM\System\ControlerSet001\Services\ramdrv\Parameters\DiskSize


5.Get the ram disk driver files. These files are provided in the MSA EDC Deployment Kit.
Look here and use this driver.
Note Using any other Driver will fail!!!!!!!
I think this is the main Problem for most users:

http://download.microsoft.com/download/win...ploymentKit.exe


Execute this file and let it extract to a Folder (maybe MSDEP)

In the directory MSDEP\EDCAPFDeployment\WinPESupport
you will find the ramdisk drivers needet and also an working WinPESys.inf .


6. Build the Windows PE Files from an Windows XP Pro
Mkimg.cmd source /ownPE/
Source must be the path to an Windows XP PRo CD or the path to the I386 Folder of an Windows XP Pro.

Windows Pe will be build to /ownpe/

7. Go to the created /ownpe/ and add the downloaded Ramdrive to it:
Put the RAMDrv.sys to \i386\System32\Drivers and
RAMDrv.inf to \i386\inf

8. Use Oscdimg.exe to build the Image and burn it.



Optionally you can only build the Registry files and add the new registry files and the ramdisk driver to your existing windows PE so you would not need an Windows XP Pro.


Hope this will help a bit!

I can use it with ERD ? is a winPE clone ..

i try but dont work for me.

i make changes on regedit manually on SETUPREG.HIV with a XP REGEDIT.EXE

"0000000000" are SZ
"0x00010001" are DWORD
"0x00020000" are expand SZ
"0x00000010" are KEY

i put ramdrv.sys and ramdrv.inf on respective paths but dont WORK

can i make to debug the fail ??

thanx

BR Subxero

That's a beautiful tutorial, thanks a lot!

Great tutorial Dobla! It also works on ERD Commander 2002. I have no access to bldhives.exe unfortunately, so I had to use Windows XP's regedit.exe when booted from ERD Commander 2002 to edit the offline registry files of ERD Commander 2002.

If anyone wants to know how. This is a reference to aNewGuy who posted a small article on how to edit ERD's registry:

YESSSS! now it works! Great job, dobla.

where did you find that information?
on this site:

https://www.microsoft.com/technet/treeview/...ld/EDCBLD05.ASP

nothing points to the special WinPE-ramdisk driver


but now another question:

who is able to use a ramdisk larger than 16 MB?
I tried totay, but with a value bigger than:

HKLM,"SYSTEM\ControlSet001\Services\ramdrv\Parameters","DiskSize",0x00010001,0x1000000

the ramdrive wont work. If I try to change to the ramdrive drive letter I get only an error message 'bad operation' (or something like this).
The maximum *working* ramdrive-size here is 16 MB.
would be nice, if I could make it larger. Memory in the system is not the problem.

AIDA32 shows around 100 MB is used. the rest is free (~150 MB)


the switch '/inram' will also not work. This switch should enable WinPE to load in RAM so that you can eject the WinPE-CD. Or did I misunderstand that?

The system memory is 256 MB and I also tried it with 512 MB. But no luck either


any ideas?

rc

Hi all!

@Subxero
It should work, because ERD-Commander is based on Win PE, maybe you can ask MrT, he seems to know how to do it for ERD-Commander...

@rockclimber



Yes its there, just a little bit hidden:
it says : "Add the RAM disk driver files. These files are provided in the MSA EDC Deployment Kit."

And if you scroll down to the bottom of the page you will see:
"
Appendixes
.....
.
.
Click here to download all materials for this guide.
"

If you click "here" you will get a page where you will find a list of files to download there you have to download "05-EDCv1.5DeploymentKit.exe"

Thats all .

Ok, it´s a litte lit hidden.... i took about 10 mins to find the files first time...
Note that theese Values are in Hexadecimal so i think 0xFFFFFF or 0x1000000 should be ca. 16 MB and 0x2000000 is ca. 32 MB, but unfortunately the documentation tells us no maximum size... i will try as soon as i have time for testing.


You are right, but i have no idea because i have never tested /inram, i will try also....


bye!

I noticed there already is a ramdisk.sys in the \I386\system32\drivers-directory of the PE cd, anyone know how to get this one work ?

I have no idea why the ramdisk.sys is there since there is no known way how to use it.

hello Dobla,

Do you also have a tutorial to make a bootable WINPE CD or where can i find it?

BennoK.

Hi!

There is no tutorial till now, but you will now find a Beta of A Windows PE Builder made by Bart Lagerweij:

http://www.911cd.net/forums/index.php?act=...f=2&t=572&st=15


Note that this is still BETA.

bye!

Thanks.
I will try.
BennoK

I copied the regedit from my winXP (nl) and tryed to start it in ERD, but I get an error message syaing I should install the app again and so it won't start... any idea what I'm doing wrong?

thx
Jerom

Your ERD should already come with an regedit ...

I followed the inststructions from aNewGuy in step 2 he says

but that doesn't seem to work with me...
or shoulld I use the ERD regedit? (I tried but had no options to save of load hives)

thx
Jerom

You should use the regedit.exe provided Windows XP. Maybe it's a language incompatibility you're running into. So try using the english version of regedit.exe from the XP SP1, which you can download freely from the M$ site.

@Jerom
Yes, it may be the language incompatibility, but i'm not sure.

One thing that should work is that

when you use ERD commander 2002's wizard to make an ERD iso, there is a step in which it will tell you that you can put any files of your choice now. you click the explore button, it will open a folder from which ERD wizard is going to make ERD iso. then you copy win XP regedit.exe to that folder (or any other folder for example I386, or you can even make your own folder). after copying, then make ERD iso.

i always copy the programs before ERD commander wizard makes its iso, because some programs may not run without the above process.

This should work.

You should be able to do this, but I havent tested it...the max size for the ramdrv should be 32MB, which is achieved by
HKLM,"SYSTEM\ControlSet001\Services\ramdrv\Parameters","DiskSize",0x00010001,0x1ffffff
The reason this may be the max is the driver cant handle anything over that, ie. 2000000 will probably fail, but if anyone has gotten a larger ramdrive, please post cuz right now I have to use at least 12MB for the total commander shell (loading needed plugins)
I also set the letter to B:

I'd like to try and get RamDriveXP to work in PE. It allows you to save your ramdisk as a file and reload it every time. If anyone tries this, please report back. I haven't had time to mes with it yet as I've just moved.

So is ther a way to actualy make/force the WinPE ramdrv to function with a size larger tha 32MB in WinPE. I mean I have almost 2GB of RAM I would like to dedicate like 128 or even 64MB if I could. Can this be done.

MrXP

after searching web a while
i found AR RAM Disk (here http://www.arsoft-online.de/products/product.php?id=1) but i dont know if it ll be working on PE Could some1 check ?
koszopal

PS 2nd
RAMDISK Version 2.2 for Windows 2000 / Windows XP
http://members.fortunecity.com/qualitysoft...isk/RAMDisk.htm

I was unable to get the ram drive to show in my WinPE image/iso. What I did was followed the instructions at the top but only I had copyed the Reg entrys and pasted them into the original WinPE image also copying the ramdrv.sys and ramdrv.sys into the correct place. It just does not map the drive. No B:\ R:\ or Z:\

Any Ideas?

Thanks,

MrXP

By the way if it helps. I am using WinISO 5.3 to just replace the WINPESYS.INF file with the one with all the RamDrv info in it. Putting the ramdrv.sys in the \I386\SYSTEM32\DRIVERS nad the ramdrv.inf in the \I386\INF and saving the ISO it still boots. but the ramdrive does not load.

What am I doing wrong?

Thanks again,

MrXP

As was said in another topic - DO NOT USE ISO EDITORS to add stuff - you must rebuild the image. Also, my problem was that some of the codes were 2 lines instead of one (which they should be) open the winpesys.inf file in notepad - maximize it and make sure each command is one line only - then eith edit your startnet.cmd or issue this command

format b: /fs:ntfs /v:ramdisk < \SFW\Scripts\n.txt > NUL

SFW\Scripts is in the root of my cd which i can give info on how to add this to your cd, but n.txt is just a file with N and {Enter} pressed afterwards...so like this
N.TXT
N
_
(no need for the underscore)

evilvoice,

However i was ablt to create an ISO using only the tools and not using any ISO Mods such as WinISO or anything. I am now seeing that the ISO is not bootable. Total ISO size is like 133MB or so.

The Directory stucture looks like this

\i386\ and all the files in that DIR system32 ect..
win51
win51p
winbom.ini

But WinISO says its a NON Boot CD. And the Image will not boot. Iv tryed

the command im using when creating the iso is
Oscdimg.exe -n c:\winpe\mywinpe\ c:\winpe\winpe.iso

and it does creat the iso only not bootable.

What am I doing wrong.

P.S I am not modify the ISO in any way with WinISO. Im only using it to view the contents and to see if it shows as bootable.

thanks again,

MrXP

Im asuming that you where able to get this to work? As I am not having any luck at all. Can you maybe give me some pointers as I really need / want to get a ramdrive going even if it is only 32MB in WinPE?

Thanks,

MrXP

what are you using to build winpe?...If You copy exactly how the inf file is to be changed from this page, it will not work as the board makes some keys go to a second line, well windows does not interpret this correctly...The lines are as follows


HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-
00C04FAD5171},"Class",0000000000,"Sample"
HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-
00C04FAD5171},"Icon",0000000000,"-5"
HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-
00C04FAD5171}\0000","DriverDate",0000000000,"11-14-1999"
HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-
00C04FAD5171}\0000","DriverDesc",0000000000,"Ramdrv Driver"
HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-
00C04FAD5171}\0000","DriverVersion",0000000000,"5.0.2183.1"
HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-
00C04FAD5171}\0000","InfPath",0000000000,"ramdrv.inf"
HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-
00C04FAD5171}\0000","InfSection",0000000000,"DiskInstall"
HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-
00C04FAD5171}\0000","InfSectionExt",0000000000,".NT"
HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-
00C04FAD5171}\0000","MatchingDeviceId",0000000000,"ramdrv"
HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-
00C04FAD5171}\0000","ProviderName",0000000000,"Microsoft"

HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","ClassGUID",0000000000,
"{78A1C341-4539-11D3-B88D-00C04FAD5171}"
HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Driver",0000000000,
"{78A1C341-4539-11D3-B88D-00C04FAD5171}\0000"

HKLM,"SYSTEM\ControlSet001\Services\ramdrv","ImagePath",0x00020000,
"System32\DRIVERS\ramdrv.sys"
HKLM,"SYSTEM\ControlSet001\Services\ramdrv\Parameters","DebugComp",
0x00010001,0xffffffff


As you can see, these all use 2 lines for a single line command...you MUST make sure that they are one line in notepad...to do this, go to the end of the first line and hit the delete key.

You MUST also format the ramdrive as I also had problems getting the remdrive to be usable (always gave me either an IOCTL error or Device not ready)...Format it as I said...if you want, before it burns the image, create a dir in I386 folder called scripts, make a new file in scripts called n.txt and type N and hit the enter key - save.
Edit startnet.cmd and insert this at the beginning...
format b: /fs:ntfs /v:ramdisk < \I386\Scripts\N.TXT > NUL

This will work.

To make it bootable, just insert the same bootfile you use in your windows xp cd's or windows 2k3 as all these do is look for setupldr.bin and bootfix.bin....you can get a bin file from barts website under bootable cds - windows xp...extract this and find the 2KB file, if you want to be positive you have the right one, hexedit the file and it should say before all the little dots (......) setupldr.binbootfix.binI386 or something like that.


NOTES:
On further investigation, I did try and set a 64MB ramdisk 0x2ffffff and this did not seem to work, so it must be that the ramdriver can only handle 32MB...maybe there is a better solution that will allow a bigger size with a different driver, but using the winpe supported ramdisk does not support larger than 32MB, or moreover doesnt support anything higher than 1ffffff - try setting it to 2000000 and see if it works, if it does, maybe my virtual machine had too little ram.

Sorry for the constant questions,

But where in the mkimage or the oscdimg does the switch or what not make the ISO bootable?

As it is making my ISO but its not showing as bootable.

Thanks,

MrXP

use oscdimg and the option -b followed by the bootsector file here it is the Bootsect.bin.

If you want to put other things on this cd to be also Bootable you can use the loader.bin of bootscriptor and boot bootsect.bin later with bootscriptor or cdshell.

Any attemp to modyfy the Iso will cut the (extra)long filenames of the WINSXS so that WINPE will still boot but will fail to run any program

Note: Make sure that you only use the ramrdive driver that is mentioned in the tutorial.
I never had succes with any other ramdisk driver.

bye!

Cant seem to find the bootsect.bin file that contains the WinXP non SP1 anywhere? How can I get it or make it?

MrXP

Test

Botsector file schould be the same for every windowws PE version.

It is always in the root directory.

bye!

What program can I use to extract the bootsect from the Windows PE CD so I can import it into my current custom WinPE cd/image?

Thanks,

MrXP

ULTRAISO RULES!!!
but also look at...isobuster or winiso.

Well now im confused because I was told not to use anything other than the oscdimg to make the ISO so I dont corrupt the ISO and to keep the longfile names in the WINSXS folder. Ok so I have used the WinISO to save the bootsect to a file but its a WinISO file type. How do I get that into the ISO that iv already created with the oscdimg command without corrupting the ISO?

MtXP,

Talk about troublsome task.

YEEEEEE HAAAAAAAA

I got it. I got the RamDrive going and working. But I had to use WinISO to get the ISO bootable. So now some programs dont work becuase it truncated the \i386\system32\winsxs folder. Im still having that same problem. Im still a lil confused on how im suppost to get the bootsector off my WinXP cd and saved to a file so that I can create an ISO with oscdimg using that bootsector so that I can not have this long folder name issue that stops my programs from running.

Im almost done

Thanks again guys for all the help.

MrXP

Sweet Good Grief good lord. I got it both the Booting and the long folder name deal. Everything looks great now.

Thanks again for all the help and not being too pissed and annoyed at the dumb questions iv kept asking

This will help out a lot.

MrXP

oops it looks like my ramdisk is like 1.5MB. what is the reg entry in the WINPESYS.INF for the 32MB ramdrive?
I used
HKLM,"SYSTEM\ControlSet001\Services\ramdrv\Parameters","DiskSize",0x00010001,0x1ffffff
but that gave me the 1.5mb ram disk.

got it i now have a 32MB ram drive. YAY. now I just need to get Drive Image 2002 to work. Il keep you all posted.

MrXP

@MrXP
Can you tell me what the setting was for 32mb?
Thanks.

Could someone help me out here pls.

I already have a PE cd with apps i've added. I copied the contents of it to
hd and put the ramdrive files where they should be but couldn't find where WINPESYS.INF
goes. I searched the contents of my existing, custom made (PE Builder) cd for the file
but couldn't find it anywhere. It don't exist on my cd !!! Strange.

So could someone pls tell me where this thing goes and/or what i'm doin wrong ?

-Tried format command but no luck.


Thx for ur help

~Dunt




** BTW, these files aren't in my original winpe cd **
HIVECLS.INF
HIVEDEF.INF
HIVESFT.INF
HIVESYS.INF
HIVEUSD.INF
IA64FACTORY.EXE
IA64NETCFG.EXE

@cumdunt

You probrably have Barts PE Builder and that one has none of the mentioned files. This guide applies if you have the MS OPK Kit, where you can add that stuff once to .inf files.
If you have Barts PE Builder you have to manually edit you file setupreg.hiv. Look also here for for the difference and how to add it to PE Builder.
If you have an original MS OPK CD, you should find WINPESYS.INF in that dir. The files you mentioned: the .inf files are build by their builder and the IA64* are only needed for Intel Itanium (if you have one ). You can use this builder as descripted in this topic.

SAM

Thanks for the help sam. I actually have both vers it's just I dont' know what to do with the dang opk cd Bah, doesn't matter. Bought it for $1 for winpe.