sam13

I think, I figured it out - well I got closer. The Foxconn support mentioned nothing, that helped either. But they mentioned the HDMI port and that got me testing again. Previously I connected my monitor to the VGA port, where the native resolution of 1600x1200 is supported. Testing with the HDMI port with a DVI adapter showed no lag at all! This port only supports 720p and so I retested the VGA port with that resolution, but the lag remains. That indicates, that there's something strange going on with the GMA and VGA output. Something, that doesn't affect the HDMI port. Maybe it's something Intel did intentionally with the PineTrail NM20 chipset, like the limited video resolution of 720p.

I got a new Foxconn Nettop based on Intel Atom D525 (2x 1.8 GHz) with Pineview-D chipset. It also has 2 GB RAM. I installed Windows 7 32bit with all drivers either from the Foxconn site or from the manufacturer site, if newer. The system runs fine without any error or problem, but one. When I tried to watch videos I notices, that there's a short hang in the video for about half a second and this repeats exactly every 30 seconds. The remaining time the video runs fine and the statistics don't mention any dropped frames. But it gets better: Also the mouse hangs at the same time. Usually I'd check, if there's a background process stalling the system. I used Process Explorer, but it doesn't show any spike for any of the processes. Also some other tools don't show any peak in utilization. It seems more, that the whole system stalls. I checked with a diagnostic disc based on Windows PE and still the same result, even with the harddisk removed. I also booted a Linux from disc (DSL and Knoppix) and get the same result here. BIOS is the most current one from the web site. In the BIOS I disabled the network card and the HD audio and I removed the wireless card from the system, all with no different result. So it seems to be a problem with the hardware itself. Has anyone a clue or hint where to look? I'm running out of ideas how to troubleshoot any further.

I haven't found a way to fully disable them, but you can delay them almost indefinetly. Put the following into a file, name it hover.REG and double click on it. It should use that value latest on the next login. I personally set this value to 10 seconds. Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced] ; extend thumbbail preview in milli seconds "ExtendedUIHoverTime"=dword:FFFFFFFF

I'm not an expert in deploying technologies, but rather interested in what WinPE can help me with. If you use that howto for a 32-bit deployment, it should also work for a WIM containing a 64-bit installation. My guess is, that you should be able to use the 32-bit WinPE and eventually substitute some commands. If BCDBoot (sorry, misread that tools name before) can't be used, use 32-bit BCDEdit and generate a new entry for the 64-bit installation on drive D:. Another way might be to start d:\windows\syswow32\BCDBoot.exe.

Hi Brian, Not sure where to start. The 32-bit edition of WinPE can only run 32-bit applications and the the 64-bit one only 64-bit ones. Every usage, that differs is not supported and results in the error message you mentioned. BCDEdit is used to modify the boot settings, which are not dependant on 32 or 64-bit, so it doesn't matter, if you edit the settings of a 64-bit Windows with the 32-bit edition of BCDEdit. This applies also to OSCDIMG. From my point of view, it would be the easiest to only use the 32-bit editions of the tools and stick with either WinPE 32 bit. If you really need the 64-bit edition you should be able to build the WinPE from the WAIK. The image for AMD64 is included in the packet. In this case the build instructions are basically the same. Just keep 64-bit in mind and include the 64-bit edition of the mentioned tools (BCDEdit, OSCDIMG) to the image. The included documentation should help you. Do not mix IA64 which is used for Intel Itanium (I don't think, there is a Windows 7 edition for that) and AMD64, which is the common one for current Intel Core and AMD processors. IA64 does use EFI, that is why the CD boot loader is not included here, look at the AMD64 folder.

Yes, but reading those statements lets you think, you have to defend you opinion. I guess it will be hard to convince everybody, if you want to. Win 7 doesn't need any defending and trying to is pointless. Picking your OS is based on certain things, and those differ from user to user. Just because you choose one means, it is the right one for everybody and that other peoples choices are fundamentally wrong. I read in a forum, you wouldn't go to a supermarket and shout at other customers: "Don't by that washing powder, because it's [overpriced | not better | manufacturer is a monopolist | ... ]". Well that seems to be a valid option on the internet.

OK, brainstorm: 1. Why not, have you tried it? 3. Nobody forces you to upgrade to Windows 7 or to use a specific OS these times. 3. Vista came to me preinstalled on my laptop in the pre-SP1 time. It felt sluggish and the whole system not any faster than the old one. What made me downgrade was the "several seconds stalls". As I read in the blogs for 7, this was caused by applications stalling the GUI while swapping - because this is single threaded in Vista. As I recently got a new hard disk and the RC was just available, I gave it a try. Biased by the Vista experience I was soon convinced to see something that works for me. I couldn't find a showstopper or a problem, that couldn't be fixed with the help of some Vista tips. The good support for applications and drivers is certainly different to when Vista was released. I'll stick with it.