[RAMDisk in WinPE3.0]

As was stated, WIN pe 3, IS a RAM disk,

Instead of using REGEDIT , it is easier to use the DISM command

%DISM% /IMAGE:%mlOCAL% /SET-SCRATCHSPACE=%SCRATCHSPACeSIZE%

Where "scractspacesize' environment variable can be 32, 64,128,256, 512

From what i have read , 512 is the effective limit, but TRY to keep it as small as possible,

the DEFAULT is 32. I use either 256 or 512, BUT remember it TAKES memory, so if you dont have alot

of memory you will impact what yopu are trying to do.

Hope this helps.

J P Morgan

[RAMDisk in WinPE3.0]

I recently upgraded my WINPE from 2005 to 3.0. In my old version of PE I used a utility to create a temporary RAMDisk to store mics. user inputs. This utility does not work in WinPE3.0. Does anyone have any suggestions on a good utility that I can use to create my RAMDrive in WinPE3.0?

Thanks in advance for all the help.

WinPE is a ram drive.

You can write files anywhere in X:\

If you need more space, the ram drive can be increased by modifying the registry of WinPE before building it.

[NETDOM in Win7]

Windows 7 and Vista both have their own NETDOM.EXE, for 32-bit and 64-bit.

You have to install:

Install RSAT (After you have extracted the tools): (took me awhile to find the link)

http://www.microsoft.com/downloads/details...;displaylang=en

start /w pkgmgr /n:%SystemDrive%\Install\RSAT\Windows6.1-KB958830-x86.xml

Enable some RSAT tools (including NETDOM)

start /w pkgmgr /iu:RemoteServerAdministrationTools-Roles-AD-DS-SnapIns;RemoteServerAdministrationTools-Roles-AD-DS;RemoteServerAdministrationTools-Roles-AD;RemoteServerAdministrationTools-Roles;RemoteServerAdministrationTools

You will then have a "c:\windows\system32\netdom.exe" that supports the 'older' Netdom syntax.

HOWEVER, IF YOU MOVE THE 'NETDOM.EXE" FROM THE 'SYSTEM32' SUB-DIR IT WILL NOT WORK???!!

IT WILL JUST 'EXIT' UPON EXECUTION??

BUT , if you WANT to move it, which i did. you have to do 'something' EXTRA.

To whatever sub-dir you move the RSAT NETDOM.EXE to :

1) FOR EXAMPLE, create a sub-dir called : %temp%\EN-US

2) COPY /Y "%SYSTEMROOT%\SYSTEM32\EN-US\NETDOM.EXE.MUI" "%TEMP%\EN-US

Then if you execute NETDOM.EXE from "%TEMP%" you should 'see' the familiar 'help'

messages..

NOTE: I have not, as of Dec 8, 2009 actually TESTED the FULL 'moved' NETDOM.EXE functionality,

but WILL in the next day or so,.

ALSO, someone made the comment that if it was moved' to another compouter it would not work also,

I will verify that statement also.

Hope this helps, as i DONT like the Powershell approach..

J P Morgan james_p_morgan@hotmail.com

[Install returns to Windows PE command prompt]

I know in Pe2 you can use the WPEUTIL command, in a Batch ,to achieve the EXIT/REBOOT.

A URL to MS is

http://technet2.microsoft.com/WindowsVista...3.mspx?mfr=true

Also the Diskpart can run with a script : Diskpart /S "myscriptfile"

You should be able to automate in a Bat, every thing that you are doing manually

Hope this helps.

J P Morgan

[What replaces textsetup.sif in PE 2.0]

Just trying to figure out what in windows PE 2.0 replaces textsetup.sif

i have an application that was being loaded into windows PE 1.6 using textsetup.sif and i need to have it loaded in windows EP 2.0 and it's giving me trouble

Anyone let me know where to look it would be appreciated

Cheers,

Ryan Strope

Distributed Services

(Software package development/testing)

Lockheed Martin Systems Integration Owego

(Cyber City Computers)

ryan.strope@lmco.com

Quid quid latine dictum sit, altum videtur

UPDATE: Jun 23, 2007 - I have created a an INF installer for Win Pe 2 to make the manual changes i documented below.

There is ALSO a good ADSI INF Plugs in at : http://www.deployvista.com/Repository/Wind...73/Default.aspx

Please email if you have need.

J P Morgan - j.p.morgan@lmco.con

Ryan,

As i explained on the Phone, the process that i got to work for me was:

First, Mount the BOOT.WIM, from Win Pe 2 creation output sub-dir, and make some Registry changes to the SYSYTEM hive

Secondly, copy EPHD files into the appropriate sub-dirs

---------------------------------------------------------------------------------------------------------------------------------------

(A) Mount BOOT.WIN and make Registry changes to SYSTEM hive.

(1) I wont go into HOW to Mount the BOOT.WIM, using imagex, i assume you know how to use WAIK and create the 'WINPE_X86" sub-dir

ie : imagex.exe /mountrw c:\winpe_x86\iso\sources\boot.wim 1 c:\winpe_x86\mount

(2) Once the BOOT.WIM has been create and Mounted, EXECUTE REGEDIT.EXE

(a) LOAD the 'SYSTEM' Hive UNDER HKEY_LOCAL_MACHINE

the path would be : c:\winpe_x86\mount\windows\system32\config\ and the file is SYSTEM

(B) give it a Hive name of EPHDSYSTEM (FOR EXMAPLE)

under the EPHDSYSTEM\CONTROLSET001\SERVICES KEY CREATE A NEW 'SERVICE" KEY

(1) Create a Key called "ephdxlat" (without the quotes)

(a) under this key create TWO DWORD keys

(1) start DWORD 3

(2) type dword 1

(d) Edit the Registry key value under [HKEY_LOCAL_MACHINE\EPHDSYSTEM\ControlSet001\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}]

(1) Edit the "UpperFilters" Key and ADD the text "exphdxlat" (without the quites)

such that the MULTI-SZ has a value of :

PartMgr

ephdxlat

THAT SHOULD DO IT..

NOW , UNLOAD the Registry Hive .

(B) Copy files

Add these files to the build directory and place them in the /windows/System32/.

EPHD_Access_utility.exe

EPCL32.dll

EPCRYPTO.dll

The next file is to be added to the /windows/system32/drivers/

EPHDXLAT.sys

Now, UNMOUNT and COMMIT the changes to the BOOT.WIN

NOW, copy the NEW BOOT.WIM to your Flash Key (thats what i use) or recreate your ISO

Now, BOOT from your WinPe 2.0 media

Now, at the Winpe 2 Dos prompt type x:\windows\system32\EPHD_Access_utility.exe

Now enter the ID and Password

You probably will get an ERROR box complaining about "not running Defrag", Click OK to continue

You should then get a dialog box that you now have access to the encrypted drive..

Click OK

You should now 'see' the files on the "C:" drive.

Comments: I find the vendor , "PC Guardian" to be somewhat arrogant and hard to deal with. Their reply was "we dont support vista".

they ALSO require you to have a maint contract, even to look at their FAQS. What gives with this, they must think that

their product is the greatest thing since sliced bread. I dont work for the company, i ONLY used their product TWICE,

to see what was so great about it, and within two days i was able to get it working with Win pe 2.0, They have FULL access

to the sources..

I HOPE the above works for those that need this capability.

Enjoy..

J P Morgan - j.p.morgan@lmco.com