wrecklesswun

oh yeah, and check that if you remember a while back a vulnerability in the jpg renderer or something to that effect disintegrated those extension from windows, check to see that the media you are building pe from hasn't been patched for the same.

try the bootsect utility in the waik...should be a fix all.

virtual memory perhaps...? Everything else i've seen blue screens

i have the waik, and still the header and lib files for wimgapi.dll are missing, know where to find them?

somewhere on this site someone wrote a wonderful creator for all types of boot devices...do a search

the issue resides with sp2 of winxp...if the rpcss service is not installed diskpart will never work.

actually bartpe has support for .net, as well based on the work of another, it was really easy to work it into winpe...besides the 250 mb it adds to the image...it works good. do a search for .net and bartpe, again i take no credit for this.

I have used wise scripting to iterate through all the user profiles...as long as you're an admin of the box...all profile including the default user can be mounted, so that new users as well get the changes.

Does anyone know how to use the WIM imaging format? What i am trying to do is figure out how to transpose this piece of code to VB.Net: BOOL WINAPI WIMApplyImage( IN HANDLE hImage, IN LPWSTR lpszPath, IN DWORD dwApplyFlags ); Parameters hImage [in] A handle to a volume image returned by the WIMLoadImage or WIMCaptureImage functions. lpszPath [in] A pointer to a null-terminated string containing the root drive or directory path where the image data will be applied. The specified path must not exceed MAX_PATH characters in length. dwApplyFlags [in] Specifies how the file is to be treated and what features are to be used. Flag Description WIM_FLAG_VERIFY Verified that files match original data. WIM_FLAG_INDEX Specifies that the image is to be sequentially read for caching or performance purposes. WIM_FLAG_NO_APPLY Applies the image without physically creating directories or files. Useful for obtaining a list of files and directories in the image. WIM_FLAG_FILEINFO Sends a WIM_MSG_FILEINFO message during the apply operation. Return ValueIf the function succeeds, then the return value is nonzero. If the function fails, then the return value is zero. To obtain extended error information, call the GetLastError function. RemarksTo obtain more information during an image apply, see the WIMRegisterMessageCallback function. To obtain the list of files in an image without actually applying the image, specify the WIM_FLAG_NO_APPLY flag and register a callback that handles the WIM_MSG_PROCESS message. To obtain additional file information from the WIM_MSG_FILEINFO message, specify the WIM_FLAG_FILEINFO. The second part is: Captures an image from a directory path and stores it in an image file. C++ HANDLE WINAPI WIMCaptureImage( IN HANDLE hWim, IN LPWSTR lpszPath, IN DWORD dwCaptureFlags ); Parameters hWim [in] The handle to a .wim file returned by WIMCreateFile. lpszPath [in] A pointer to a null-terminated string containing the root drive or directory path from where the image data will be captured. The specified path must not exceed MAX_PATH characters in length. dwCaptureFlags [in] Specifies the features to use during the capture. Flag Description WIM_FLAG_VERIFY Capture will verify single-instance files byte by byte. Return ValueIf the function succeeds, then the return value is a handle to an object representing the volume image. If the function fails, then the return value is NULL. To obtain extended error information, call GetLastError. RemarksTo obtain information during an image capture, see the WIMRegisterMessageCallback function. The last is : Registers a function to be called with imaging-specific data. For information about the messages that can be handled, see Messages. C++ DWORD WINAPI WIMRegisterMessageCallback( IN_OPT HANDLE hWim IN FARPROC fpMessageProc, IN_OPT LPVOID lpvUserData ); Parameters hWim [in optional] The handle to a WIM file returned by WIMCreateFile. fpMessageProc [in] A pointer to an application-defined callback function. For more information, see the WIMMessageCallback function. lpvUserData [in] A pointer that specifies an application-defined value to be passed to the callback function. Return ValueIf the function succeeds, then the return value is the zero-based index of the callback. If the function fails, then the return value is INVALID_CALLBACK_VALUE (0xFFFFFFFF). To obtain extended error information, call the GetLastError function. RemarksIf a WIM handle is specified, the callback function will only receive messages regarding that WIM file. If no handle is specified, then the callback function will receive messages for all image handles. Call the WIMUnregisterMessageCallback function when the callback function is no longer required. Thanx in advance !

try adding a temp drive, and also make sure you have a ramdisk

mount the user profile...then edit the hkey users hive, which will represent the users logged in

It is possible, what i've done is to extract the vbr runtime dll's and then register them at boot time. if you need a sample ask.

I would imagine you would have to register the cdonts on the box...could be wrong

Here's one, how do i get pe to detect the vmscsi drives...it works fine with ide.

Also doesn't detect VMSCSI disks...Sure it works ?

I have had this problem, the only tab control i could get to work is the wells project...on freevbcode. You will have to register the vbruntimes in order for it to work.

To my recollection, do you not need a hard disk online as well in order for the ramdrive to load fully ?

How do i use diskpart to access and partition scsi drives in vmware ? I have the vmscsi driver loaded, but diskpart does not see them.

Using group policy you can prevent exe from running, and or change file assoc for script files to notepad. Proven effective everytime

try unplugging the nic, re-plugging cable or disble nic and re-enable

try buildoptionalcomponents.vbs /?

Figured it out nevermind

try running the oc or oc2.bat files which will register the necessary dll files for vbs support and hta support...

Has anyone succesfully slipstreamed Access (Jet or MDAC) support into PE as well as .net frameork, i've searched but found only people who run using a silent install method...thanx ! Second part is if not, can i use the xp embedded component designer to design these components for pe...since (i think) pe is built from xp embedded...thanx