Tripredacus

Oh btw, most Atom CPUs nowadays support 64bit. As a testament to this, I haven't had to use a 32bit WinPE on teh WDS in so long, Its been disabled for over a year now to save menu space. Regarding the "uninstallability" it is referenced on this download page: http://msdn.microsoft.com/en-us/windows/apps/br229516

I read that if you install this, you can't uninstall it. So be careful if you install it on your regular computer. Use a VM or such!

I know, I said this is "Flashing Cursor Month" earlier. B) I may wait until tomorrow and try a different board. Anything I can find about using a GPT "disk" on an Intel server board has to do with enabling RAID, rather than using a single 3TB disk in the system. Also, it appears this board (among other current products) do not support either installing or booting Windows from a GPT disk, but again it refers to the Embedded RAID controller. http://www.intel.com/support/motherboards/server/s5520sc/sb/CS-031582.htm I hear maybe I can use one of the Sandy Bridge (6x ) series Desktop boards to do this. But if this isn't supported either I am wondering why I got this project. Of course, I can always go back to the "Why would you want 2TB+ for your boot volume" question but customers then think you are making them feel dumb for wanting such a thing.

Yes, that is why there is a NIC driver in it. This particular board has a problem with its NIC that makes Windows unusable if the default Microsoft driver is used.

You may need to get a memory dump. Check the sticky in the XP forum (where this topic will go)

So perhaps the original info saying that there will be no 32bit release is true, since the Developer Tools are only available in 64bit. I'll check this out, but this topic is more News than Win PE.

I am working on a modification of the GImageX HTA to have the ability to deploy images to a GPT disk. When this is finished, I will be able to post some code for people who want to update it. The problem I am encountering is that after a reboot, I am getting a flashing cursor when trying to boot off the HDD. First here is some reference info: Manage Multiple UEFI-based Hard Disks I have created a Server 2008 R2 SP1 image and it is on the WDS. It is the base OS + a NIC driver. Normal deployment to an MBR disk works fine, this was tested on both a notebook and a server board. For the UEFI platform, I have the following items: Intel S5520HC with 1 Xeon CPU and a 2GB RAM Seagate Barracuda XT 3000GB Here is the general process I am using to set the system up and deploy the image: DISKPART sel disk 0 clean convert gpt create part efi size=100 sel part 1 format fs=fat32 label="System" quick assign letter=s create part msr size=128 create part pri sel part 3 format fs=ntfs label="LocalDisk" quick assign letter=c Use imagex to apply WIM to C: run BCDBOOT C:\WINDOWS reboot Then I get the flashing cursor. I confirmed that all partitions are created properly (as above) and that the data is actually on the C vol. What step am I missing?

It would also be nice to see what your startnet.cmd has in it.

Are you sure that your USB on this PC (SiS) is a 1.1 controller? Does a USB key work on it doing a read and a write?

hellohellocat!

Beastie Boys - Flowin' Prose

The default is "Same domain as the Windows Deployment Services server." Are you trying to change it to another option? What do you need to change this for?

I'm always worried once any browser wants to use more than 250MB RAM, much less 4GB. What type of memory intensive thing would that extra RAM allow? I can see maybe certain Flash or other related animations being better... save Silverlight. Else, maybe it means I could have hundreds of tabs open...

Ok, but why are you configuring option 60 on the WDS Server? You need to configure option 60 on the DHCP server. If you don't have the WDS role added to the DHCP server, you'll need to add the additional options I mentioned in step 4 of my link. My DHCP server has the WDS role that I use to remotely administer the WDS Server, which seems to figure itself out easier without as much manual configuration.

Well its possible no one know the answer of your question. I will move this to customization forum, maybe you can get a start there.

So are you getting these permission denied errors on the DHCP server? Your WDS should be just fine using default settings.

Well since you can change your DHCP options, check out my guide, Step 4 is the full set of things you need to set on the DHCP server to point it to the WDS.

That's fine, my guide is for two servers, one is DHCP and one is WDS. If you do not have rights to change settings on the DHCP server, you'll need to talk to your network administrator. Otherwise, you'll have to get your WDS off your corporate network.

Oh sure, the Win 7 setup doesn't care what is on the server. It just needs a path and credentials to connect to it. If Server 2008 can deploy Linux, why not Linux deploy Windows 7? Definately get the WAIK. Start with Scenario: Deploy from a Network

The DHCP server is the PXE server. You configure its PXE response option to point to the IP\hostname and bootrom path of the WDS. For an example of this, see step 4 of my WDS guide: Its for 2003 but it should give you an idea.

This isn't a unique situation. I had encountered this with a Compal notebook in the past 6 months, but it would only refuse to boot off the CD if the OS on the HDD was in Hibernate. Any time it wasn't in hibernate it would work fine. Does your notebook have a boot menu where you can select the boot device?

If you really want to do a recovery on the system, we can probably ignore the SVCHOST issue. You are getting the STOP 0x7B with an XP CD via a USB CD-ROM because the USB driver is not in the XP CD. Because you can boot OPHCrack doesn't help (other than it means you have a usable drive) because that OS (Linux) either has the driver for the USB in it or doesn't try to use it the same was the XP disc does. You have two options. You can learn to slipstream the USB drivers into your XP MCE CD, but you will need to have a working CD writer. The other option is you can build an XP install on a USB Key. So for the moment, I'll put this topic in XP Unattend section.

You can use the BOOT.WIM from the DVD and put it on the USB key. You can make an XML that looks at your network drive for the INSTALL.WIM. I haven't tried something like this but I know it is possible. I am going to guess you aren't using a specific server technology?

You are right. Even tho I install the IE9 x64 package, the default browser is still the 32bit client. I had to go out of my way to open the x64 version. I confirmed that Silverlight does not work with it.

64-bit IE is hardly a common browser (probably well below 1%). Not that I would use silverlight in the first place as not enough people have it installed (nor is its future certain). And the percentage of browsers that properly supports a decent subset of the HTML 5 features is still WAY too low to be "viewable universally" like you want. Flash has a good install base but it's not supported by a some devices, like the iphone/ipod/ipad and a bunch of other mobile devices (including a lot of android devices). If you can live without those gadgets, then HTML 4 + Flash is still an option. Where does this tidbit come from? I just did a test, deployed Win7 Pro x64, and installed IE9 x64 with Silverlight. My test page was http://www.mahorney.net and that site works fine. I did have to install a newer version of Silverlight for it to work, however.