Tripredacus

Did you build your WinPE with the MDAC package? There's not a lot of info about how to exactly use it but you can find some topics about using MDAC in WinPE to talk to MSSQL. such as http://www.eggheadcafe.com/software/aspnet/33312294/problem-using-ado-in-the-winpe-image-from-mdt-2008.aspx

I can think you could easily make one in AutoIT. I looked at their example scripts and couldn't find one to do exactly what you wanted.

There is a Microsoft Agent present in your system! My first experience with this Agent is your little search friends like Clippy and the Dog/Cat/Wizard. Of course the Agent has since involved to encompass more of the operating system... B) But yes, some files will "return" if they are protected system files. Such files would give you a warning if you try to remove them... but these are more like shortcuts. If you want to get rid of some extra things in your new XP install, you should look at Add Remove Windows Components...

Personally, I've found rootkitrevealer to be lacking in some respects, as I have used it on an infected system and it wouldn't find anything. In addition I would recommend adding GMER to your arsenal.

Welcome to the MSFN!

Fortunately, Google has no such limitation. In order to search MSFN for terms less than 4 characters (or otherwise forbidden such as "color"), type this into Google: site:msfn.org usb

Hmm not exactly the same but closer... EC80R - Alien

Imagex will lock the file for writing/moving but not copying. If you look in the PXE Response tab on your WDS properties, you see an option for "Require Administrator... blah blah" which basically means only allowed clients can get the appropriate PXE response (ie download wdsnbsp) and be able to be imaged. This is more of a manual process however. I've never used this setting, but try out the Configuring the Auto-Add Policy on TechNet.

Searching file contents doesn't seem to work... I did find that installing a program makes it appear (as well as the uninstall option) on the Metro desktop. Also, the CPU beat me in Chess.

This is how to do it. I am not surprised that an MFC icon was not present. So this leads to something else. Possibly you have any programs that allow for customized icons like WindowBlinds (or associated programs), or have you made any modifications to your Windows files in order to have a custom look? Usually, if you end up with the "wrong" icon, you can get the pre-loading "default" icon that would appear before Desktop loads the correct icon, but unless your OS' default icon was changed to the MFC "blocks" icon, it shouldn't show up with that.

It seems most of the DV series has had problems with overheating. Of course in all the cases I've seen this as being the issue, it begins with problems with the wireless card. Does your BIOS have a system monitor option where you can see temperatures? I'd check it after the system locks up and you need to do a reboot. You can try running a memtest on it too. Else, keep track of what programs you have open at the time of the "halt" to see if there is some pattern.

By now you must have found the Win9x and 2k forums! Hope you like them.

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!