Tripredacus

Maybe one of these? Kelly Gruber Kelly Johnson

Today I found my 2nd workstation to be off. Turns out the board took a dive. Built a new system and old HDD booted to Windows fine! Old: - CPU: 6.2 - RAM: 5.9 - Graphics: 3.4 - Gaming Graphics: 5.3 - Primary Hard Disk: 5.9 New: - CPU: 7.1 - RAM: 7.1 - Graphics: 4.1 - Gaming Graphics: 3.5 - Primary Hard Disk: 5.9 +0.01!

Interesting. I've never seen much value in installing that or the mouse software, since Windows can handle those devices just fine.

The Nirsoft app is great. It did indeed fix the problem (removing devices that weren't present) while it did take quite a long time. The worst was when the keyboard and mouse stopped working (no PS2 ports on this system).

I'm not sure where these fanboys are... The only ones I am seeing being "fanboyish" are official or affiliated sources. Surface reviews aside, since that actually seems like it is going to be a nice product.

I've been experiencing problems with USB on my 7PRO32 PC. If I connect or disconnect a USB key, there is quite often a delay (30seconds to 3 minutes) before Windows acknowledges the connection. Here are the two symptoms: Connect USB Key: CPU hits 98% to 100%, with SVCHOST.EXE using about 50%. During the delay, no sounds will play in the OS, for example AIM notifications. Once the delay is up, the Scan/Not Scan box comes up, and then all cached sounds will play at once (AIM, USB Connect) and then the key is usable as normal. Disconnect USB Key: Basically the same as the connect, except the delay is longer, and the drive will still appear in Computer until the svchost.exe process exits and the disconnect sound plays. It doesn't seem to matter what USB Key I am using. The same thing also happens with USB HDD Enclosures. And some devices, such as the Seagate GoFlex flat out won't be detected any more. Safely Remove Hardware doesn't make a difference either. And for the CPU usage, svchost.exe always uses about 50%, but I can't find in Task Manager what else is using CPU to make it hit 98%, since other than System Idle Process (which is ignored) there is usually just a 1-4% on the next item (such as Firefox or IE or whatever I am using. What can I run to determine where the problem is?

I was able to "kinda" get a physical PC to boot into EFI mode... but by forcing all default boot options to use that EFI rom, which results in client lockup. Here are the main problems... the EFI support in Server 2008 R2 (and earlier) is actually the Itanium-based EFI, not exactly the same as the current UEFI spec. So Server 2008 R2 can detect clients with either: -x86 -amd64 -ia64 (efi) But, Server 2012 can detect these (note that Itanium support is removed) -x86 -amd64 -x86x64 -arm -uefi x86 -uefi x64 Note that any client that supports x64 PXE will be detected on Server 2012 as both x86 and x86x64 and may generate an error in Event Viewer. I am not surprised that you can do an EFI PXE Boot using a VM, but then again it is using the legacy Itanium EFI profile. Take a look at these I have posted after much (much) testing:

We have plenty of that here!

I'll bust your bubble... that program ended a while ago... But you might be able to get Vista from a reseller.

You can try looking at Windows 7 Thin Client...

Its not a bug. Either format your list some other way, or uncheck the "Enable emoticons" box inside of the configure post options section.

Announced dates and actual dates are two different beasts apparently... Actual RTM date for Windows 7 was July 24, 2009, a Friday no less.

It could be worse... at a previous company I noticed our RMA forms printed out with each word with the first letter capitalised. Somehow no one noticed it before. The web developer took a look and said it would take too much work to fix. Horrible! Evidently the culprit code was at least 6 years old...

Sorry the correct term is Base Filtering Engine. Look here: http://answers.microsoft.com/en-us/windows/forum/windows_7-security/win-7-base-filtering-engine-service-missing-gone/aaed4af9-3624-4845-aecb-0381b08d198e?msgId=170b2feb-3a23-46ea-976d-19e8d779a062 http://answers.microsoft.com/en-us/windows/forum/windows_7-security/windows-7-base-filtering-engine-is-not-running/d440bf07-e9fa-40e4-9344-4651a2214cdf http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/530e05dc-c97c-405e-b961-6bdf613ca443/ I used this search in google base filtering engine service missing

It won't work that way. If you buy a PC with Downgrade Rights, the OEM/Reseller is supposed to give you a Win7 system with Win8 COA and a copy of Win8 OEM version. If the PC has an OEM COA (doesn't have a product key on it) and Win7 installed, they may provide you with a Win8 Recovery DVD or maybe with both! But a lot of companies will work differently. I can only say which different ways I've seen it. That link will be problematic for most users... since that thread is in the Dev testing forum...

Insane beings from the future says it still works. The part I like is that it was really easy to do. Ease of use is always good for things like this. Well that's enough fiddling for today, back to work...

Has anyone tried this on a later build? I think I'm going to load up Windows 8 and see if it still works.

Windows 8 will allow for Windows 7 Downgrade Rights when RTM hits, which will allow you (like previous times) to purchase a Win8 PC with Windows 7 installed. I'm not sure what you mean by official way to downgrade after the fact...

FAT32X? Wikipedia is very elementary about it.

Something like this?

Maybe you shouldn't. Showing us warez results in us showing you the door.

I will try out the second option in the link. The first option is NOT an option at all. The problem is that the client is not on the domain, but the share is on the DC. I already have an account to use to log into the share and it isn't an admin account in production. It is an admin account on the dev servers but that is just to make things easier for me. I'm not particularly concerned with the credentials being in the shortcut, since the EXE on the share is supposed to delete it anyways.

Thanks for taking a look. It is indeed a DX58SO board, however it is a corporate sample. There are 2 RAID arrays involved besides the RAID5, the other is a RAID1 which holds the boot volume. It is difficult to determine which of these arrays could be causing the problem, other than the MBR read error that Gmer threw. In other testing, the OS will still BSOD when the boot array is degraded (booting with 1 drive). WD Tools flat out refused to test the disks, as it read them as being blank. I had hoped some concrete evidence would show up in the dumps, but an upgrade may be in order. That may either be a total rebuild of the boot array, and/or upgrading the board. Hopefully it doesn't turn out to be caused by the data volume, but since Safe Mode is fairly stable, backing it up shouldn't be a problem.