Tripredacus

I would recommend re-building the image to be honest. You don't even want to know the headaches you could be facing here if you take into consideration ACLs and Ownerships of files, hidden files and registry keys.

Yes I found that information also. It deals with adding a "custom" resolution, and then reghacking the new keys the cpl creates to make use of resolutions not available by default.

Is the pound character ( # or number sign ) a reserved character? I can't find any full documentation on reserved characters for INFs or Windows.

Slingbox can definately do it, and there are other companies who sell products specifically to do this as well. But a Slingbox is cheaper and Jim Rome likes it!

Verify it isn't DAEMON.EXE, because if so, this is part of Daemon Tools, an ISO mounting program. If you use this program, you should unmount all unmountable volumes before shutting down to see if this issue goes away.

You can use the attrib tool to change the properties. Here are your switches: R = Read Only A = Archive S = System H = Hidden So to make available your standard protected file, use the following: Attrib -R +A -S -H To reverse and set back to how it was before: Attrib +R -A +S +H

Yes a USB key should work also. The Vista PE should automatically detect them, but best if they are plugged in after the PE loads or else they will appear as the C Drive. If you had a USB floppy drive this would also work. That is what we use for those cases.

What packages did you add into your winpe.wim?

Try using the IP of the host instead of the hostname in your UNC path and see if that does anything. Also try to ping the IP address of the server instead of the hostname.

I usually figure the pound is 2x 1USD but that changes often! That's weird if its that expensive. The Oblivion mods were only like $2 each when they came out. But these Fallout ones seem to be a lot bigger.

Well let's look at the problem now. You've pulled off a full recovery. The original problem was you couldn't get to the recovery and couldn't make the discs. So now we are at the point where you need to make the discs? Or, wait you did say that you lost your function key after doing a recovery? I want to make sure I understand exactly what is needed at this point. If you can get into the recovery partition, you do not need to use my steps at all. I wanted to point out, the commands with mbr.exe, they refer to specific things. For example, let's take this: mbr 0 1 /h This is MBR (the program) and 0 (is the physical disk number) and 1 (is the partition number) and /h (means hide). Alternatively, there is an /uh which is unhide that could be used. Now, if HP followed the Best Practices, the recovery partition would be the first partition, and the OS partition would be the second one. OK so I'm going to say if you want to do this step, you're going to need to do some diskpart action. For example: List Disk List Vol List Part these should give enough information. As far as the CD burning deal. You execute this app from Windows. It obviously looks somewhere, like a file or a registry entry, to see if it made a CD before. ... I'm not sure if I should continue about that part of this thread...

I am working on a new base image for a customer and we are trying to add a display resolution. The only ones available are 800x600, 1024x768 and 1440x900. 1440x900 is the maximum resolution of the monitor connected to the computer. The monitor is a Magnavox 19MF338B/27. The video card is a Matrox MGI P65-MDDE64LPF. The operating system is Windows XPe. We are trying to add (or force) a resolution of 1360x768. How would I go about doing that?

OK the reason I asked about the version is that some versions of Windows do not have all the tools. I am not familiar with MCE, so this might not be any help. Your display issues may be rooted into the registry. I noticed there were no standard Local Policies to handle the display properties. You could look into your Local Computer Policy to see if you see anything in there, but there likely won't be. Local Policy is in Control Panel\Administrative Tools. As for the registry, look at this link, under the Active Desktop heading: http://www.kellys-korner-xp.com/xp_abc.htm

Yeah, I hate that "Recovery Partition not found" message. NOTE: I claim no responsibility as to the consequences if you use the following information. I have no tested these tools on a Soft Thinks partition, only on a Windows PE partition. If you attempt the following, make sure you research how to install a standard MBR in case it becomes damaged with these tools. There may be yet another option, and that would be to use the steps I had done in my Recovery Partition project. It requires the use of MBR.EXE, which isn't the same as MBRInst.exe. It is available on Terrabyte Unlimited's website. This is what needs to be done. The MBR.exe needs to be put in the root of the recovery partition. You also need it in the root of the C drive. You run this command first from the MBR.exe on C. You can run it from Windows. mbe.exe 0 1 /H This sets the recovery partition to be hidden (as it should be) mbr.exe 0 /install selm 10 11 "Press F11 for recovery" 0xC 0x1C the 11 and F11 in the above line can be another number. They must equal each other. You can now restart the computer. Press F11 and it should try to boot into the recovery partition. If it fails, you will get a standard error message like operating system not found, etc. If this happens then this method will not work for you. If you cannot boot into Windows after a fail, you need to run the command below somehow, via NTFSDOS or a PE CD. If you are able to boot into the recovery partition, you must run another command before you can boot into Windows again. And that is: mbr.exe 0 /reset The reason is when you press F11, the recovery partition becomes Active and the C drive (may) become hidden.

I do not agree with the idea of distributing unattended install discs to friends and family. You have an alternate method. you could put the Autounattend.xml on a floppy disk. And leave the key field blank. Tell your friend that they must type in their key into the file. Then when you install Vista, make sure to have the floppy disk in the drive. This way you only would be giving people your XML sample, which happens online all the time.

Have you tried this? http://support.microsoft.com/kb/922582 edit: this would be for a technical description only. It does not apply to Vista.

Like I implied earlier, I do not think the Win PE supports suspend states. I was not able to make a booted PE 2.1 to go into S3. Also note that the Hiberfil.sys is not present in your image. You will find the powrprof.dll, but not the CPL to let you enable the suspend state. If you have create a ramdisk PE, making the notebook go into an S3 state may be unwise, especially if there is not enough memory for the ramdisk, the PE and its memory load, and the data the notebook's BIOS attempts to load into memory. You may be able to use S5, but your hard drive would need to be formatted first. Remember, Microsoft has gone at great lengths with this product, and it is not intended to be an operating system.

I don't think it has anything to do with your method of creating the media, as you mention it does work on other systems. This STOP error you are getting means that the instance can no longer access the image. I've seen this happen in the following examples: - not enough memory to store the ramdisk - overworked network or server (PXE only) - certain motherboards do not work Take a look at these two threads: http://www.msfn.org/board/index.php?showto...st&p=749648 http://www.msfn.org/board/error-0xc000000e...90120&st=25 So let's talk about how this specific motherboard works. If at any point, the firmware re-enumerates any of the devices, this could definately happen. For example, let's say that at a certain point of the boot process it re-enumerates the bus that the USB device resides on. This would reset all devices on that bus. If the computer was in process of booting off of something connected to that bus, those devices (as far as the booting OS would be concerned) would have disappeared. This is the case in those times if PnP is not enabled (such as the early boot process of the PE) and while the device is (usually instantly) ready on the system, the PE will not see it until PnP is enabled. Since it cannot see the device, it can't finish loading. This is my guess about the situation since I've also experienced a couple odd-ball boards that can't boot. This same premise is used for certain (or sometimes bad) RAM, or an overloaded PXE server. At some point, the PE at boot time, cannot access all of the boot information as it needs to. It doesn't necessarily mean that the device has been reset. I can easily replicate this issue if I attempt to boot 9 clients via PXE to my 2003 WDS. The maximum connection limit (found via testing) for this server is 4. After this, the additional clients either pause or create BCD errors. Its because the boot process tries to load the next file into memory, or execute it, but if the server is overloaded, It cannot provide those extra computers their next peice of data. In some cases, the PE will wait until it can get it, but other cases it will immediately error out. As far as where to go, I would say try making a flat-file PE to see if you can get that to load. The flat-file method is one that does not create a ramdisk. So this means you will not be able to use the scratch space.

Yes Jaclaz. The MBRINST I had downloaded from HP looks like the one in that blog. Remember that (in my other topics) my SoftThinks software does not come with the MBRINST.exe. The function that it provides is coded into their software via a DLL which exists in the partition. Bottom line, you can try running MBRINST, but only if you can find the MBR.INI in the recovery partition. Use that as your INI source in the command. But be warned, if something is missing, or the file is incorrect (there are more than one in the partition) you may make it so your partition is not bootable. Also note that this tool (from the quote) is being run from Windows, and probably not from the recovery partition itself.

The hives should be in the same place they are in XP. Which is WINDOWS\system32\config.

Notice - Unlocked thread so people can post suggestions to add to the list. This is to be an index of helpful WinPE threads on MSFN only. WinPE is short for Windows Preinstallation Environment. It is a trimmed down version of Windows that is designed to be used to install Windows onto computers. It can be done to make unattended setup disks, or network aware scripted environments. It is also used as a troubleshooting or testing tool. It is the current equivalent to the Live CD idea of Linux. It isn't a full blown operating system. This guide will help you understand what it is all about. System Requirements and Licensing Win PE availability Creating the media Commands for working with Windows PE 3.0 and the new WAIK WinPE 2 Made Easy Boot Methods 1.6: How-TO? Ramdisk on WinPE Problems booting HP DC7800 SFF with UFD 3.0: Boot WinPE 3.0 VHD from HDD Dual boot between Winpe and WinXP WinPE v2.1 From USB HDD Windows Deployment Services Deploy Linux from within WinPE/WDS Installing Winxp via winnt32 under Win PE Applications within the PE WinPE 2.0 Refresh Rate Windows PE as a recovery partition WinPE 2.0 GimageX COM based HTA Drivers and Hardware HP NC373i Multifunction Gigabit Adapter Wireless & WinPE 2 and 3 Third Party Implementations WINPE Builder 1.0 WinPE 2.0 simple Ghost Menu HTA Imagex GUI Open Source List of WinPE builders for WinPE 3 Make_PE3 WIN7PE_SE Gena Winpe1 Modifying the PE 2.x PE 2.0 Boot Screen LDAP in Win PE 2.0 Portable Windows 7 Build from WinPE 3 Unattend Setups How to install Windows x64 from x86 PE

You can delete the file if you are done with it. Its just a text file, and you can always make new ones if you want it again. As far as Logitech, it depends on what device you have. If it is a mouse, you probably do not need their software installed. Even their mouseware installs a bunch of junk that you probably don't even use. If something was deleted that would effect graphics, things would be larger instead of smaller. Check you resolution on the Settings tab in Display Properties. Its probably higher than you would like it. As far as the inability to click on things under appearance, this is usually caused by Local Computer Policy, or the registry which is another way to enforce policies. Do you have XP Home or Professional?

Yes, as you can see there, your default option is to install an MBR. There is an MBR.INI file that is used for that. Using CLI, MBRINST can export an existing MBR that can be used to reimport. But it does not get all of the information. As you can see in the screen, it was programmed for SoftThinks. But while the CLI switches do work, I think they aren't supposed to be used by the end-user. There should be at least two (2) MBR.INI files in the recovery partition already, but these do not work if you import those. They are created when the partition is initially created (I have confirmed this) but they again seem to be incomplete. Its like there is a step missing. MBRINST and the MBR.INI files are definately a part of it, but there must be some other thing that is done also. Let me explain my testing process. 1. Install Windows on a HDD. 2. Install the SoftThinks program. Activate it and create the recovery partition. note that Ghost can redeploy a hard drive with the recovery partition, because it does a volume copy and preserves the MBR, but you need a license to activate it after it is redeployed. 3. Ghost the drive, and redeploy onto another computer. Actually the same computer, but there is no real difference to Ghost since it replaces the Volume entirely. 4. Capture the MBR file. 5. Format the drive, repeat steps 1 and 2. 6. Image both partitions with Imagex. (I had previously determined how to correctly script diskpart to do this) 7. Use MBRINST to install the MBR from the original. Now It does install the MBR, or it would say it couldn't find the recovery partition. Even if it is there, set up as x12, etc. So I think something must be done first before installing the MBR. And also, this process the function key (in my case it is F10) does not work. Neither does the R key. The data is present, but it will only boot into Windows. Disk Management sees the other partition as FAT32, no drive letter, and EISA volume. For my usage, this is normal. I understand that on some other computers like HP, you do not even see the partition at all. So in the end, there seems to be a missing step. It is what stops me from dumping Ghost altogether.

Yes, the changes do not stay because you are editing the registry on the Ramdrive. You should try to load the hive(s) for your source, and make these changes. I am not familiar with working with Win PE 1.x versions, so I do not know if it even has a hive to edit.

I forgot about this thread. I went back to 2.1 on the 2003, and installed the Windows 7 Beta tools on a 2008 x64 server I made just for it.