Tripredacus

When you say you copied into the WinSxS folder, do you mean in your winpe source or after the PE was loaded? Were you following the advice of website? You can try opening up a ProcMon and then try to run your app and see if you can locate what files it is missing. Also, it is possible that it is attempting to use files of the wrong version? Its also obvious that something is different from your testing pc (where you are running depends) and your PE. Is this testing pc also running Vista with the same architecture as your PE? Are these 3 files from sqlcmd part of a retail product or something that is available in a demo somewhere? Did you build your PE for x86 or amd64?

I will leave it here for now. I do recommend instead of directly linking to a download file, such as your zip previously, that you link to a page that can download your zip instead.

The only part that sometimes end up getting bent is where you put in the CPU fan. Often the back side of that part looks a little warped.

HP for Vista uses a customized WinRE environement. HP for XP is a customized WinPE 1.x.

Did you try my method with mbr.exe ahmad?

Yes I am past this part. This specific project is on hold at the moment. I am using the WDSClientUnattend on the server side, and another unattend on the image. I am getting errors with the server file.

I see a lot of strange configs come through here sometimes.

Check out the Hardware Hangout section.

My favorite Rammstein album was their first one. Tom Petty & The Heartbreakers: Free Falling

1. Please post the full error message. 2. What packages did you install into your PE?

I have reversed those changes. I downloaded a new build and it has an "install to USB" option. I have that put into the PE now but I can't test it atm because my test computer is being used for my recovery partition project. I put in a request to get another test computer, but until I get that I won't be able to do further testing.

Yes, the partition will be after, which is how our current recovery partition is used. I am using an HTA for the partition. I am going through its development testing now.

OK, all you guys that want to try something out to restore the F10 or F11 or whatever key functionality to your partitions can try this. I cannot garauntee that this will work! First, you need to have access to Windows or a PE environment. Otherwise you won't be able to do this. 1. Make a folder on your C drive to put your files in. ie: c:\mbrtools 2. Download PARTINFO from Terabyte Unlimited. Extract it into c:\mbrtools. 3. Download MBR Utility from Terabyte Unlimited. Extract it into c:\mbrtools. 4. Open a command prompt (elevated if need be) and switch to the c:\mbrtools folder. 5. Run the following command: "partinfw > partinfo.txt". This will make a text file in c:\mbrtools. Open it up and you will get something like this: PARTINFW 1.11 Copyright (c) 1996-2008 TeraByte, Inc. All rights reserved. Run date: 01/09/2006 0:52 ==================================================================== MBR Partition Information (HD0 - 0x488BBB22) (CHS: 1022/254/63) (WCHS: 9729/255/63) +====+====+=============+====+=============+===========+===========+ | 0: | 80 | 0 32 33 | 7 | 1023 254 63 | 2048 | 127426560 | | 1: | 0 | 1023 254 63 | 17 | 1023 254 63 | 127428608 | 28870656 | | 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 | | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 | +====+====+=============+====+=============+===========+===========+ BOOT SECTOR INFORMATION ------------------------------------------------------------------------------- File System ID: 0x7 LBA: 2048 Total Sectors: 127426560 ID: 0x1 Jump: EB 52 90 OEM Name: NTFS Bytes Per Sec: 512 Sec Per Clust: 8 Res Sectors: 0 Zero 1: 0x0 Zero 2: 0x0 NA 1: 0x0 Media: 0xF8 Zero 3: 0x0 Sec Per Track: 63 Heads: 255 Hidden Secs: 2048 NA 2: 0x0 NA 3: 0x800080 Total Sectors: 0x07985FFF MFT LCN: 0x0C0000 MFT Mirr LCN: 0x07985FF Clust Per FRS: 0xF6 Clust Per IBlock: 0x1 Volume SN: 0x72B4864EB48614AF Checksum: 0x0 Boot Flag: 0xAA55 ------------------------------------------------------------------------------- File System ID: 0x17 LBA: 127428608 Total Sectors: 28870656 ID: 0x2 Jump: EB 52 90 OEM Name: NTFS Bytes Per Sec: 512 Sec Per Clust: 8 Res Sectors: 0 Zero 1: 0x0 Zero 2: 0x0 NA 1: 0x0 Media: 0xF8 Zero 3: 0x0 Sec Per Track: 63 Heads: 255 Hidden Secs: 127428608 NA 2: 0x0 NA 3: 0x800080 Total Sectors: 0x01B887FF MFT LCN: 0x0C0000 MFT Mirr LCN: 0x01B887F Clust Per FRS: 0xF6 Clust Per IBlock: 0x1 Volume SN: 0x785C98125C97C8F0 Checksum: 0x0 Boot Flag: 0xAA55 The above code is from my testing Recovery partition project. The first drive has a File System ID of 0x7, which is NTFS. The Second partition has a file system id of 0x17. The 7 still means NTFS, but the 1 before it means it is hidden. NOTE: If both your System and Recovery partitions have the same File System ID, this may not work! 6. Run the following: mbr 0 /install selm 10 11 "Press F11 for Recovery" 0x7 0x17 Here is a run down of the options in the above command: mbr = the program name 0 = the disk ID (Disk 0 should be your boot hard drive) /install selm = the command needed, do not change this. 10 = timeout in seconds. This is the length of time the keypress message will stay on the screen. I use 5 seconds myself. 11 = The function key number. I use the F11 key for testing, so this number is 11. If you want to use a different function key, type in a different number here. "Press F11 for Recovery" = Make sure to use the quotes around this. This is the message that appears prior to booting the system partition. You can make it say anything you want. 0x7 = the type of partition the recovery partition will be changed to. This must match the file system that is currently on it. 0x17 = references the recovery partitions File System ID that PARTINFO displayed. This is designed presuming you only have 1 partition of this type on the computer. There are some additional caveats to using this method. The primary one is that after you hit F11 and it boots into the recovery partition, your PC will not be able to go back into Windows unless you run another command. If you can gain access to the command prompt in the recovery partition, you can do this, or if you have a WinPE on a USB or CD you can do it also, but you need to put the MBR.EXE onto that media! You may be able to access the MBR.EXE on the C drive where you saved it, but it would be safe to have it elsewhere as well. After booting into the recovery partition, you need to run the following: MBR 0 /reset This resets the Master Boot record changes that pressing F11 changed. If you cannot do this from the recovery partition, you can boot to a WinPE CD and run the command that way. So you need to run this before you can get back into Windows. If PARTINFO does not show that your Recovery Partition is hidden (ie starts with 0x1) you could try to hide it with MBR.EXE. However, this will hide it from Windows and you cannot unhide it using Diskpart. Diskpart will not show that it is hidden! That command is: MBR 0 1 /H or to unhide: MBR 0 1 /UH If you hide your recovery partition (so that PARTINFO says 0x17) then you can use the command to add in the F11 key. You can even run this command from within Windows, but the changes will not be in effect until a reboot when the PC reads the MBR again. Only other issues is that if your BIOS has its Boot Sector Virus detection turned on, it may give you a warning on your reboot. So if your PC has this option, turn it off during testing. I doubt Ahmad had this since it would have given him an error with all the testing he has done so far. And lastly, I will add again that I do not have access to an HP or its recovery software as they do it. So I can't be very specific on a case to case basis.

I think the problem I am experiencing is that the Recovery partition is NTFS, and in my test, I used Fat32. 0xC 0x1C is for FAT32 and not for NTFS, which is the format for it now. By using Terabyte Unlimited's Partinfo tool, I was able to determine the following: The OS partition ID is 0x7. The Recovery Partition is 0x17. going to try this instead: mbr.exe 0 /install selm 5 11 "Press F11 for Recovery" 0x7 0x17

I found some on Newegg.

Uh oh. The fact you installed Windows 7 on there may have done who knows what to the BCD. As we know from the other thread, HP's Vista and WinRE make good use of the BCD.

If they are separate physical disks and not partitions, and you are concerned or unsure, you could just disconnect them before your recovery process. I recently ran a repair install/upgrade on my home computer and I had done this and everything turned out ok.

Do you get this problem if you use a Vista boot image?

For generic images, I always install Vista, then do reg-tweaks or GP edits, then capture. I never install any software or drivers. And always use the generalize switch for sysprep. I then have hardware specific images for a couple setups.

I don't think you can change the colors of that menu with the boot.ini. Also, the OP needs to determine if his Boot Manager is being handled by the boot.ini or the BCD that Vista and 7 uses.

For nLite questions, have you checked out our nLite forum? You should be able to get all your 64bit Windows Updates from the Microsoft Download page.

What program is this happening in? I have experienced this in IE8 Beta 1 but no others. Try out your methods in not only the browser you use, but also try Notepad, Wordpad or any other program that lets you type.

Welcome to the MSFN! 1. Do you have any other information in the Event Viewer? 2. What Operating System are you using? 3. How much memory in the computer? 4. Do you get this error in Safe Mode?

Ah so you have obviously found the nLite sub-forum already!

I personally feel that the only reason to run a 64bit OS is to be able to do things a 32bit OS is not capable of doing. And having additional RAM, is not one of those reasons. IME the only reasons I have had to run 64bit OS is for large volumes and the ability to run 3 sound cards in one computer. But, hey, if you want to play around with it, that's cool too!