cluberti

I'm assuming you're using 2003 RRAS to do the connection management, so technically yes, you could put some traffic rules in place. However, you'll have to be more specific in defining what "restrictions" you want to do.

Microsoft's Updates Servers are cached globally - Limelight is a known WU cacher, so seeing their IPs as a "source" for WU traffic is normal. Also, this has been asked and answered here on msfn before, so remember to search.

Well, there could be 2 reasons I can think of for this issue that would be most common: 1 - one or more of the hard drives in the array has some sort of problem, and is breaking the array 2 - the drivers are causing write problems, which breaks the array Assuming you're using the latest versions of the nvidia drivers, I'd suggest running a test on the hard drives in the array to see if any of them are suspect and would need replacement.

If you want an easy way to do it, look into the Microsoft Deployment Toolkit. If you want the manual way to do it, drivers can be injected using the Windows System Image Manager (WSIM) via answer files (peimg is for modifying Windows PE images, not full OS images, although some drivers do actually inject into Vista WIM files via peimg - it's just not supported). As to default user profile modification, this can be done in the auditUser pass with the CopyProfile value. And, actually, there is some good documentation on these sorts of questions here, and two other places, as well: http://www.msfn.org/board/Is-there-way-to-...-s-t119440.html http://firegeier.unattended-sponsor.de/en/sitemap.html http://blog.stealthpuppy.com/deployment/cu...lt-user-profile Those are the best links I know of to modify the default user profile. Obviously you could just copy a stock profile over post-imaging, but as the links above show, it can be done other ways as well. I prefer using MDT and SCCM for my deployments, but I know a lot of people like to do it manually (either not a large scale, or want to learn "the nuts and bolts").

The PTE table in question is for the nvidia network driver, not the video driver. I'm not sure how you got the video driver from my previous post, but I see nothing wrong with the ATI video driver. The queued DPC error appears to be coming from PTE corruption, and it looks like it's affecting the nvidia network driver (nvlddmkm.sys).Hopefully I'm being clear, I thought I was.

I just took your challenge and it worked fine, and I was able to do it on a Vista image as well. sysprep /generalize is all that's needed for this to work, so if you're having issues it's probably not the fault of Windows. Vista/2008/W7 are all images to begin with, so there's no "scripting" per se like the old NT installer the previous versions of Windows use - however, because the imaging is done from WinPE, you can drop the .wim image of a Windows install down onto a machine, and since you're still in WinPE, you can do whatever you'd like to it before it boots (and there are still methods using unattend and .cmd files to automate things once Windows reboots and starts applying). This is *far* more powerful than the old NT installer, not worse.

Well, it's an instruction in user mode, I can tell from the address range, and the error code (0xc0000096) just maps to exception of privileged instruction. If it happens in every user-mode app, it would seem to be something with a global hook causing it - does it reproduce in safe mode or safe mode w/ networking? Also, if you run autoruns and shellexview, disable anything non-Microsoft, and reboot, does it continue?

See my last post.

It's not there because you have more than 3GB of RAM, likely. You can still set it in the registry, and this has been a problem since Windows 2000, fwiw. It's not a Vista thing. As to the dump, it appears to be an issue with patch protection on x64, and a misbehaving driver. I do believe it to be the nvidia driver, as the other queued DPCs are all TCPIP timers, but unfortunately I can't seem to get access to the callstack before the dump. I've seen this before though, and either you'll have to install the QFE kernel and hal.dll from KB 950772, or wait for Vista SP2 (the hotfix is included in SP2). It's not entirely easy to get a QFE update on a Vista machine, so unless you want to go through the entire process to extract the QFE for Vista and pkgmgr install it, I'd suggest waiting until Vista SP2 and apply SP2 when it releases to get the fix. Also, I'd bring this to nvidia's attention, as there is some random odd patterns in the PTE memory for this, which would indicate potential driver corruption (hence the patch protection crash you see here).

I'm assuming you mean make the Sidebar hide automatically, and only appear if you hold the mouse over the side of the monitor where the sidebar is? Unfortunately, the answer is no. The only real options for it you have is off, enabled, and enabled (and stay on top).

Hmmm - email notification seems to be working here properly. Are you talking about notification of your monitored threads?

If you're not running Vista Business, Enterprise, or Ultimate, you don't have gpedit.msc.

As much as I detest people who can't read for comprehension, I must say that I've answered your original question/statement entirely, even if you don't realize it. You discuss the old menu, specifically the fly-out menu components, which is a part of the classic shell code for the start menu. Hence, that code is gone from Win7, and as such enabling the option isn't possible.

Yes, and PM sent for upload location.

Overlapped modules aren't going to cause a C7, sorry to break it to you. This is actually normal on a Vista box due to ASLR. Anyway, this is a driver issue, but without the .dmp file itself (at least a kernel dump) we won't be able to say for sure. However, I can tell you what the dbg help says about a C7 bugcheck: If you want a real answer, you're going to have to .zip and post the .dmp file somewhere so we can look at it.

I understand people will hate Vista and Win7, but I'm not sure this is the best forum for this. It's widely known Microsoft has removed the classic start menu code and all the start menu GUI built on top of it, so asking if they'll enable it will get you an obvious answer - no, it's been removed.

Build 7077 is basically build 7105, so I doubt a minor version bump is going to get you anything spectacular.

2 things: 1. a product key that works on RTM will work on SP3, so if it's complaining about your key it's one of two things - one, your original source was OEM and you're using a retail key (or vice versa - neither will work on the other media type), or it was likely blacklisted by SP3. Assuming you did buy it retail, you should have the COA sticker that came with it and the product key - I'd call Microsoft and get a new key that works, as yours appears to have been blacklisted. If you're using an OEM key on a retail install, or a retail key on an OEM install, it won't work. 2. Using nlite to slipstream SP3 and updates is probably a good idea, as well as make sure the drivers for your laptop for XP are integrated as well (to avoid the 7B bugcheck, which is "INACCESSIBLE_BOOT_DEVICE".

Well, that's incredibly odd. You can't even see your regular hard drives. Did you install anything or update anything recently that would have installed a filter driver (like antivirus or virtual drive software), or modify the source with nlite?

I'd uninstall them all, and see if vobiw.sys gets removed from the system. If it doesn't, you'll probably have to ask Pinnacle that (technically it's their driver, so making sure all the versions are completely removed *should* remove their drivers). If uninstallation does remove it, I'd see if installing the latest version gives you a newer version of the driver. If not, you'll have to talk to Pinnacle about the issue, as it's their driver that's buggy. If they don't know about the issue, however, I don't know that they would have fixed it, so if that's the case it may explain new versions shipping with an older driver. I wish I had something better for you, but if you're using the product you'll have to harass them to get it fixed if they haven't already.

Yeah, actually it's quite a well-known issue now that both Spybot and Java can cause the problem, and that running regsvr32 actxprxy.dll seems to fix it as well if you install IE8 onto a machine with either of those two apps already installed. I am still not sure why, but it seems at least those two apps seem to interfere with the proper installation of IE8, and specifically that .dll, causing the very slow performance issues people are seeing.

I'm not entirely sure, but I'd think it would have to do with all of the oddities of booting a stub OS and a vhdfilter that perhaps they've been unable to get reliable scoring? I dunno for sure.

Heh. If it doesn't work, let me know. I think I still have a VS6 box here somewhere.

Agreed, although if you're stuck with 6.0 for something specific you can put the .dll in question (if you can find the right version) in the same folder as the .exe, and create a <executablename>.exe.local file in that folder. It'll load any .dll files in that directory before attempting to load them from anywhere else, no matter what. This doesn't work on Vista or higher, but your screenie shows XP, so it would work there.

Except the licensing terms I quoted above don't change, regardless of your opinion. The license is for the OS install, the CAL is to allow clients to connect to services licensed by the CALs. That's it. End of story . Except client OSes do have limitations - 10 inbound persistent connections. This doesn't exist in server, plus comparing Windows 95 to an NT-based OS (server or client) isn't really a valid comparison. We're lucky enough Win95 had built-in TCPIP, let alone server software .