cluberti

Well, that'd be the first thing I'd check - does a clean build repro? If it does, there are a few things you could do, including setting one of the files read-only and remove any NTFS permissions to any account but your own and run procmon with a filter on one to see who tries to access it, although that's a bit drastic, it'd work. Since you have problems with both links and pinned items, I'd think testing a *clean* build is a good idea, followed by getting a bit more drastic. If it doesn't repro on a clean build over time, start adding apps until it does. Also, if you use this build in a VM, does it repro in a VM as well?

I've built over 100 Win7 machines with various builds, about 50/50 split between physical and VM hosts, and I've never seen it. I'd say it's very likely a software issue - what do you install on every build you do, specifically? Anything with filter drivers or explorer hooks?

Works on builds 7000 and up, it seems. Just FYI.

Are you seeing the same problems with the official 7000 build? If it works in vmware on generic hardware, but not yours, I'd fall back to a driver problem, but it's hard to say. I've seen lots of problems with 7048 performance "fixed" by using build 7000, which means filing a bug on the build you have (if this works on build 7000 properly) would be the next course of action, as there's a driver bug somewhere, likely in the disk subsystem.

And, a case of the "Use Feedback" button working, for those of you who think these are ignored. Invert selection is back in for Win7 as of the RC.

If a server just locks up hard, and you have no mouse or keyboard at the console of the physical server, that would indicate that something even below the kernel has gone wrong and even interrupts aren't being serviced. While it's entirely possible that the OS is at fault, it's not probable. If you have a PS/2 keyboard attached to the server, you can configure it for a complete memory dump, reboot, and then try the keyboard combination to crash it the next time it occurs. However, if the server doesn't accept the keyboard commands, you may have a hardware problem.

Microsoft also has to worry about appcompat and driver issues, whereas MacOS is a closed system (their OS, closed driver model, limited hardware possibilities, and a known pool of apps written for *that* specific OS architecture). Considering WPF is a .net construct, and the OS contains it, it's logical to assume the GUI would do so, but you'd be wrong. Until all the old GDI stuff can be ripped out and the UI written in .net, you get a compromise like the UI currently in Windows. So, is it behind OSX? If you mean is it 100% accelerated, then yes, it is. If you mean did the vendor drop support for the old UI constraints entirely, breaking a whole generation of apps (unlike Win7, which for example still runs vb6 apps from over 10 years ago....), then no. It would be very nice, yes, but if Microsoft wants to sell copies of Win7, the compromise must exist.

Good question, although as an OS that has been out of support (completely) for a few years, seeing the downloads for updates and fixes disappear will likely be more common in the months and years to come.

Hyper-v will see the partition as it was before, but you will obviously have to redo permissions on the objects on the volumes.

Settle down, warnings issued.

Will this keep all of the customization I've done to the "base" profile? What kind of customizing have you done? Since most settings are stored in the registry, the answer is likely yes.

Sounds plausible, considering they're on Messenger 14.x now. You could probably use one of the alternative messengers that can use the WLM network, assuming any of those run on NT4 (I haven't used it in a few years, so I honestly don't know anymore).

True, but process monitor might help. The error is indeed a generic REGDB_CLASSNOTREGISTERED error, so likely a file or file registration is missing or for some reason your account does not have access rights to it. Running Process Monitor with your .exe as the filter should find you what is missing.

Currently the download period for the beta has expired, but the release candidate should be out in a few months (maybe sooner). If you have an MSDN or Technet subscription, you can still download the beta (build 7000) there.

Also, upload speed on DSL would only be faster if you purchase something with faster upload speeds. Most DSL companies sell you ADSL packages, which mean the upstream is almost always at or lower than what you could get from your cable provider (1.5Mb down/256k up is pretty common for ADSL, at least in my area, which is slower than my 10Mb/1Mb cable package). I've also found that my VPN to work is actually more reliable since I moved to cable than the DSL provider here, which also goes to the quality of the provider's network. If you're happy with your cable, don't switch.

7022 contained the IE8 RC1 build, you are correct. The later 704x (and later) builds are in the RC1 testing phase for Windows itself, and once one of these builds is deemed RC ready, it'll be released as Windows 7 RC1. I believe the latest build available to beta customers is 7048, but that they're into building Win7 with the 705x build numbers already.

I'd say it's a Vista problem with the BIOS, honestly - the BIOS isn't doing something on a reboot that it is when XP does a reboot, there's no reason for the card to be found again unless the BIOS presents it differently after the reboot.

This is why I strongly recommend NOT copying whole profiles, and only the NTUSER.DAT file - which is the registry, which is going to hold HKCU, which is really all you need.

I would say Windows Update on that machine is indeed having issues - there are lots of things that look like they would track back to COM permissions issues - in general, when update.exe starts failing with the error code 0xf201, this is usually COM permissions at the root cause: 1. Open regedit, and export the key HKLM\Software\Microsoft\OLE 2. Inside the OLE registry key, delete any of the following values if they exist (these may, or may not, exist): DefaultAccessPermission LegacyImpersonationLevel LegacyAuthenticationLevel 3. Reboot

Are we sure it isn't a driver autodetect problem in Vista? What would happen if you force 10 or 100MB and force the duplex mode? Also, if it finds a new NIC on every reboot, that would potentially be a BIOS issue, as devices are scanned during boot and compared to the preexisting device table (assuming it's not a sysprep reboot) - Windows would only install a new device if there was no previous device, or if the BIOS reported it with a different hardware information set than it did the previous boot. I'd say there's a problem with this particular driver and Vista's different boot and shutdown behaviors (XP's driver model and boot/shutdown procedures differ from Vista's pretty radically). I would make sure you have the latest BIOS from the motherboard vendor (and make sure there are no Vista firmware issues with the vendor's BIOS), make sure you have the latest Realtek x64 WDF 1.0 driver (not WDM, but WDF), and after that I would try to pester the mobo manufacturer or Realtek (if it's on the motherboard, Realtek won't help you) into getting it to work properly in Vista.

The beta is currently available for Win7 on connect: http://blogs.technet.com/msdeployment/arch...-available.aspx

What happens if you run the program in compat mode, say under Windows XP or Windows 2000 compat mode?

As per this KB article, you can set these options to what you want each to be under the security Zone key that maps to the security zone you want to change. You need to change the value in each security zone you want the setting to be "enabled" under. The security zones are: HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\1 == Local Intranet Zone HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\2 == Trusted Sites Zone HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\3 == Internet Zone Within each zone key, you can set the following DWORD values to 0, which equals "enabled": 1208 == "ActiveX controls and plug-ins: Allow previously unused ActiveX controls to run without prompt" 2200 == "Downloads: Automatic prompting for file downloads" 2201 == "ActiveX controls and plug-ins: Automatic prompting for ActiveX controls" (for reference, 0 == enabled, 1 == prompt, and 3 == disabled for almost all of the DWORD values found under the Zones keys) Once you've set these, simply close all IE windows and the next time IE is opened, these settings should be "enabled". In the future, you should consider using google. It would have found this for you (notice the KB article in question is the very first link returned).

This has been a part of the Set Programs and Defaults since XP SP1. It doesn't remove it, it just removes the icons and shell handlers from the UI, like it always has.

We Are Scientists - Nobody Move, Nobody Gets Hurt