Tripredacus

I have so far done the following: 1. Copy boot.wim from Vista Business DVD to e:\source 2. Import the boot.wim into Boot Images in WDS (you can see that above) 3. Use imagex to export the Vista Business image (instance 1) from install.wim on Vista DVD. This file goes into e:\source 4. Add the new vista_business.wim to Install Images in WDS. This allows me to deploy multiple versions of Vista from the WDS. In the previous screenshot, you see I have all seven versions of Vista. I removed these extra items for now. Those appeared when you import the entire install.wim into the Install Images container. So far it seems the only way for WDS to use an answer file is to use it on the Server Properties, as previously mentioned. I attempted to put my Autounattend.xml into the root of the vista_business.wim but this did nothing. I may now try to put a simple unattend file into the boot.wim that contains HDD formatting options, and network passwords. In case anyone is wondering, this is my scope: Currently I create Vista images by handloading an Unattended DVD. Then install the drivers, apps, etc, generalize, reseal/audit and then capture the image. This is laid out here: http://technet.microsoft.com/en-us/library/cc709683.aspx To replace the DVD method and use a WDS via PXE method instead.

Its a "downloadable content pack" for Fallout 3 where you can now play in Pittsburg instead of just Washington DC. http://fallout.wikia.com/wiki/The_Pitt_(DLC)

The only thing I found was some AutoIT scripts made to encrypt files, and use this file extension format: http://www.autoitscript.com/forum/index.php?showtopic=23071 http://www.autoitscript.com/forum/index.php?showtopic=27279

I'm also kinda confused on this subject. The computer in my servers named 7Server has a HDD enclosure (internal) with a SAS backplane (because I had to replace it) and has 3 SATA drives connected to it. But I am not running SCSI drives or anything remotely relating to that.

Be careful when considering modifying the MBR on any system that uses a SoftThinks recovery partition. Part of the reason why your HP software may be broken is that the SoftThinks software (it has another name that I won't mention) writes information to the BCD, MBR and other files that needs to all work together. Damaging any one of these peices may cause the recovery partition to become unworkable. Another possibility is that your partition does not have its license anymore, or the license is there but the FAT does not see it anymore. As far as how to fix your issue, I can't help you with that. All I can say is that I've had many experiences with SoftThinks and I have not been able to ever fix a broken partition before without recreating it.

Welcome to the MSFN!

This place will certainly help stay up on Windows developments!

This should be here: http://www.msfn.org/board/index.php?showforum=4

Geinoh-Yamashirogumi - Requiem This is a track from the anime OAV Akira. It is on the official soundtrack.

To get back into the feel, I just reinstalled Morrowind again!

If you do not need to change this key at every boot, or you only need to do it once, you can edit the offline registry.

This was atop the Register: http://www.theregister.co.uk/2009/03/26/co...ation_analysis/

Welcome to the forum! I had a PCI USB card in my old computer and I could not go into the BIOS with a USB keyboard. This was a long time ago, so your motherboard might allow you to do it. You'd have to try it and see.

It may be hidden via the MBR also. I have found with recovery partitions in this case, diskpart's ability to set or clear hidden is useless.

I do not use the WAIK. My company is not licensed to use it. We use the OPK Tools instead. My files are proper as they are downloaded from the OEM Channel sites that I have access to. Please be aware that the documentation is still largely incomplete, and in some cases incorrect. This is still a beta afterall. And I will say that perhaps the OPK and WAIK documentation have different wording. I do not have the WAIK documentation to compare to. This was the title of the page: Walkthrough: Create a Custom Windows PE Image I had the OPK Tools installed on a computer that was not fast enough. If you look at my servers, you will see that 7Server is currently my Technician computer for Windows 7 Beta. Unclesocks is my Technician Computer for XP and Vista.

Try telling that to MS! 'Windows PE 2.0', 'Windows PE 2.1', and 'Windows PE 3.0' are the terms used by MS in the Documentation accompanying the WAIK. You should have a browse through the Users Guides. They're quite informative. For example, page 1 of the 'Windows Preinstallation Environment (Windows PE) Users Guide for Windows 7': Also, everywhere on the web. For example: http://www.svrops.com/svrops/articles/winvistape2.htm I understand what you mean, but it is possible to have an older version of the PE with newer functionality. And this specific combination could cause problems in certain instances. I will use the PE I maintain as an example. It is a Windows PE 2.0 (hence my version number) but it has the 2.1 Servicing module installed into it. A PE 2.1 and my hodgepodge PE 2.0 would be different. So to say that I have a Win PE 2.1 with a Win PE 2.0 version number. Do you see what I mean?

From the imagex.hta file. I didn't know if I was allowed to post the code snippet, so I just referenced the line numbers.

IIRC, ATI drivers require .Net Framework 2.0 to be installed.

You might want to contact their support department to see if they know of this issue. Their support page isn't well organized, you can try looking through there but it may take you a while. Does it give you this message at install and not allow you to continue? I am going to download the demo as well and see if I can replicate the issue.

...

Also, AOL should have the ability to connect to their service without using their software. When I had AOL a really long time ago, I only connected into their telco and just opened the browser, not actually their software. Or if you are using it on broadband then you also wouldn't need it, although if you are using a PPPoE setup you might have to do some additional configuring.

Is it possible to embed a private video like that? Maybe if you were logged into Youtube and then posted it in another tab within the same browser?

I have confirmed this. You need to be logged into the domain in order to add a WDS. Simply having the computer added to the domain is not enough. I'm struggling with the User Account control however. After adding a boot image to WDS on 2008, I wanted to add it into my WDS console on 2003. It adds properly, but a message comes up about how either WDS is not installed or there is no access to the other computer. I cannot any way to add a local user of another computer into the Member list on the Server 2008. I can add domain users however. I'm going to play with it a little more. EDIT: I didn't need to add a local user. I forgot that the domain controller logs on with a domain account. I still could not add the 2008 to the 2003, but I could add the 2003 to the 2008. I guess this issue is resolved for now.

This is the full error code: 1. What version of the Win PE are you using? 1.2, 2.0, 2.1 are not valid version numbers. For example, the version I use is v6.0.6000. You can get this version by either booting into your PE and look at the command prompt, or adding your winpe.wim into the Boot Images container in the WDS Snap-in. 2. Are you attempting to update a WinPE image using a different version of the WAIK or OPK Tools than the one that intially created the PE? 3. Are you attempting to inject the driver into a Windows XP image? A better clarification: 1. INF files tell Windows how to install the driver files. 2. DLLs are resource files that the driver needs to make its calls to the OS or other programs. 3. SYS files are the actual driver file. And I agree, make sure you are only using Vista 32bit drivers for your PE, unless it is a 64bit PE. Do not use XP or other OS drivers.

Have you tried a different display? I get different resolutions on different monitors, including different LCD displays. I've never had to install a video driver. Also, Geezery uses the following VBScript to set the screen resolution, however it runs after wpeinit, so I am not sure if it actuall will resize the actual screen, or the HTA that contains the script. On the current version, this info is on line 63-77. This also requires you to include the Scripting and WMI packages into your PE if you haven't already.