Tripredacus

Welcome to the MSFN!

I missed an opportunity to go there once... it would have been too expensive.

Your signature is a little lighter...

Velvet Revolver - Interstate Love Song

This topic may be misplaced, as it covers both Hardware, Networking and Server 2008. My current project is mostly solved, save for one small thing... Can I PXE Boot via UEFI? I am starting with a supported motherboard, the Intel DQ67OW which supports UEFI bootable devices. When this is turned on, I can choose alternate UEFI SATA HDD or UEFI ODD (USB or SATA) as choices in the boot menu. However, the IBA (Intel Boot Agent) does not get that special prefix. If I want to be able to properly install Windows to a GPT disk, I would need to boot the installation media via a UEFI boot option. If I choose the UEFI DVD drive, I can install Windows to the GPT disk, do a reboot and everything is great. If I choose the regular DVD drive option, I can install Windows to the GPT disk but will get a 2TB disk OR Windows won't boot. BUT, Network boot all but works fine with one exception! WinPE can't see the BCD Store on the OS volume after deployment. This is specified in Installing Windows Server 2008 and Windows Vista SP1 on UEFI Systems (UEFIGuide.docx) here: A lot of work on getting a NIC to get the proper (EFI) boot rom from WDS is located here: http://social.technet.microsoft.com/Forums/en-US/winserversetup/thread/ceca6149-bedd-4860-8a7f-a1c83bf99aa4/ So is this about NIC response to the PXE request for architecture type? I checked the WDS logs and found that this particular client is returning a Arch value of 6, which is EFI IA32. But in any case, the EFI rom isn't being used as evidence of WinPE can't find the BCD when using BCDEdit or BCDBoot. BCDEdit reports it can't find the store, but BCDBoot says there is a file copy error. How to proceed? Its already too late for me to send a request to Quad, so I can do that on Monday. And unfortunately those steps in the above link of running commands in the EFI Shell aren't very helpful since the Intel Desktop boards do not have an EFI Shell, and the Intel Server boards (while they do have an EFI Shell) do not support UEFI unless using a RAID controller. I suppose I could "fool" it into using 1 drive on JBOD but that won't help me on the Desktop boards. But back to the Arch value, does the Arch value listed in the table here: 0 Intel x86PC 1 NEC/PC98 2 EFI Itanium 3 DEC Alpha 4 Arc x86 5 Intel Lean Client 6 EFI IA32 7 EFI BC 8 EFI Xscale 9 EFI x86-64 Relate to the Arch value that WDS reports in the Event Log? So does anyone have any insight on this topic? Also, is it possible I'm trying to do stuff ahead of its time?

I know what you mean. I'm not sure about other brands, I only get to see MSI. But those ones have the same boards in them as their netbooks do. That might be part of the problem? Well actually I haven't seen a netbook with a Radeon in it yet... but they are called Wind Top for a reason.

Bring back Reversi for RTM?

I think what is happening is that most AIO systems are going to go more towards the HD-TV standard rather than older panel resolutions. Because of this, I can only find panels that are 1080p at 24" ! So I can't help. I looked at MSI AIO PC (Wind Top) and they are all *1080, however they all have HDMI inputs, meaning you could connect a HD source to it. I'd expect this trend to continue since if people wanted to watch a BD on their AIO, it would default to 1080 resolution.

On an interesting note, after installing Server 2008 R2 with UEFI, a UEFI option appears as a prefix to the HDD in the boot menu. After imaging it, this option disappears, however a "Windows Boot Manager" option is then available that doesn't do anything. I need to reload again and capture the System Reserved partition and try to apply that and see what happens. Updates: I seem to have the correct method here, but the problem lies with WinPE not being able to see the BCD store on the OS volume after deployment. The reason for this appears to be that in order to deploy a UEFI image using WinPE, it must be booted from a UEFI enabled device, such as a CD/DVD or a USB drive. Unfortunately, my WinPE boots from PXE. Some additional reading: http://www.microsoft.com/whdc/system/platform/firmware/uefiguide.mspx http://technet.microsoft.com/en-us/library/cc765951%28WS.10%29.aspx New topic created specifically for the UEFI issue in Hardware Hangout.

Have you installed the latest chipset drivers?

Will the system only boot if that one USB key you used to install with is inserted? Have you tried booting with a different USB key plugged in?

SEAT BELTS - Rush

Hard to believe less than 300Mb for a x64. Probably no x86 support and only a command prompt or pure explorer. Well my talk about no x86. I know a dev preview for x86 was released, but I was referring to old info where MS said Win 8 wouldn't have a 32bit version. Obviously they are backing off on that a little bit, HOWEVER it is interesting that the Dev Tools version only is 64bit. As far as my "size" talk... Looking at the default Win PE 4 size of about 500MB, it doesn't have OS parts like your project does. Even my current WinPE 3 x64 boot images are not full OSes (or attempts) they are deployment platforms only. Very few additions as far as extra content or drivers... I'd say less than 10MB. So this is why I have small files. I admit the Win PE 3 x86 I have on USB Key I made with Make_PE3 is a lot bigger!

JFYI, a lot of members on MSFN (myself included) has no idea what may or may not happen on the other forums. So if there is some sort of problem between members, it cannot be public on MSFN. This isn't a place for that sort of thing. Also, there isn't a need to take sides about whose Win PE maker is better. Its not a competition. The fact that someone may want to make a new one, and not work with existing projects, does not automatically mean there is something wrong with those projects. Of course, comparisons to other projects can be done! I can see that maybe there is something that Make_PE3 does good that Winbuilder doesn't and vice versa. Who knows about all the other Win PE makers out there. There will always be gap-bridging projects and attempts and that is just fine. Besides, its not like anyone is charging for their PE maker. Basically what I see for this thread is that a basic plan must be made. Its the same as any other real programming (or even a database project). Plan out everything first then figure out how to tackle it. If that means you want to compare and contrast other Win PE makers, that's fine. Just make sure to keep things on topic. B)

(bolding is mine) Is a far too strong shock for my aging heart...... jaclaz Yes but that is the initial size. I haven't tried it yet, but further along you'll see the final size is about 500MB or something. That is still a lot bigger than the current PE sizes I deal with, which is less than 300MB for a 64bit WinPE. But in a related note, Windows 7 Embedded's minimal image size using the Digital Signage method is 1.6GB too.

Did you see this link from Arwidmark?

What about the third (features) option? Or worst case, there may end up being a bunch of threads on how to modify your Windows 8 to have the Windows 7 features, similar to what you have done... Presuming such things will work by that point.

Fear Factory - Full Metal Contact

There is some trick to make a USB key boot so a Win7 ISO (contents) can be on it. I never knew the exact trick. The only USB key I have that can boot a WinPE was made with Make_PE3. For more info on USB Windows installs, you can check out this section which is specifically for such things: http://www.msfn.org/board/forum/157-install-windows-from-usb/

You may be correct about that, even tho it isn't documented! I just tried to use an Intel DQ67OW and enable UEFI boot, but the OS still isn't booting and I am getting the same results. My emails are unanswered at the moment, but I know my reps are at BUILD so I shouldn't be so surprised. Update: I was able to do a new install from the DVD that put the OS on the GPT disk and formatted the full volume. However there is no MSR partition... Here was how to do it. 1. Enable UEFI boot. 2. Use boot menu and choose UEFI DVD (there is a regular DVD there too, even tho this is USB DVD drive) 3. Boot off Server 2008 R2 DVD (usb key inserted with answer file) 4. At the first page, SHIFT+F10 for CMD. Use Diskpart to clean DISK 0 and CONVERT GPT 5. Continue install as normal. That's it. So I will try to capture this image and redeploy it with Imagex and see if that works.

You should be able to tell if they are MFC applications with ResHack or a similar program. It would be interesting to know if the stock MFC icon exists within those EXEs. if they don't then this could be something else.

I could definately see a lot of us waiting for Server 8 to use instead of Windows 8 on our desktops.

That time frame it would defiantely be a 1.0 controller. USB 1.1 controllers came out shortly before the USB Zip 100 drive to give a time frame. The reason I know this is because I worked for Iomega at that time and MANY people (in the year 2000) had computers with USB 1.0 controllers. The behaviour of a USB Zip 100 on a 1.0 controller was either: 1. Didn't work at all 2. Was really slow or data corruption 3. BSOD/Lockups The reasons for this is that USB 1.0 only supported unidirectional data transfer. So things like keyboards, mice, microphones, webcams... these were fine for the most part. Even those legendary Altec Lansing speakers (being the first ever USB device to have drivers built into a version of Windows) would probably be fine. Any devices that needed to send and receive data would have a heck of a time on a USB 1.0! However USB 1.1 solved this problem as it allowed data to be sent and received. Many of the early controllers got a bad rap just because they were 1.0 and people didn't know until they tried to use a 1.1 device on it. Some notable ones were SiS, VIA and ALI, all of which usually used the term "Open Host Controller" in Device Manager. As for how to specifically tell if you have a 1.0 or 1.1, you'd need to test out another confirmed (send/receive) USB 1.1 device. It wouldn't have to be a Zip 100, you could use a USB Floppy drive. But even then, it may not mean so much, since WiFi USB adapters, especially on older USB controllers (even 1.1) can be flakey. I had similar problems with getting USB WiFi to work on my Win98 (and PCI WiFi also) with either BSOD, Windows Protection Errors or plain not working. And my motherboard has USB 2.0 ports in it! If all else fails, you can try to find a USB 2.0 PCI card if your PC has a slot available for it.

I didn't think you could pass an argument through wupdmgr to Internet Explorer, so your solution is probably the best method.

MFC is the Microsoft Foundation Class. For some programs, it is fine to have this icon, but programs that normally have other icons shouldn't. As to why this has happened for you, I am not sure.