cluberti

Get me an adplus -hang dump of outlook.exe in state and I'll tell you what's happening.

I think your idea of what meets the bar to spend (very expensive) dev time fixing versus spending that time fixing actual problems that cause breakage, deployment blockers, etc, are very different from Microsoft's. Many bugs just never get fixed - why? Because they're annoyances without much other side effect, or fixing it will break something else far worse, or it's not reproducible in a test environment, etc. I have to agree with not fixing the first bug you filed there - it's not so much a bug but an annoyance (and one I cannot reproduce here either). I'm not saying your bug filings aren't important to you, but just giving perspective - thousands upon thousands of bugs get filed for each release cycle, and a bar needs to be set as to how critical an issue must be (Microsoft doesn't have infinite resources), and trivial annoyance bugs rarely will ever meet that bar.

Unless you're running XP Professional, have a premier contract, and thus access to the spanish MUIs, no, you cannot change it (at all on Home). Buy the spanish version, save yourself and the user the trouble of figuring this out the hard way.

technically it's nagware - it'll work after the trial, but if you open the main app window it'll ask you to please buy a license. If you just use the menu options in explorer, there's no nag.

The HP/Compaq AMD SP3 issues revolved around them using Intel-based systems to do their original OEM images, and then later using them on their AMD-based machines. It has nothing to do with a "clean" XP CD nor SP3 specifically. I've not experienced these problems with XP or SP3, and I'd wager from the forums that almost no one else does either - whatever it is, it is specific to either your machines or your original media you used. That is my suggestion - get a CD from someone else and try it, before blaming the OS or the service pack, or even HP/Compaq or Dell. The situation seems to all stem from the actual install media (not the blank CDs, but the XP source).

From what you state, install problems on multiple PCs (in the same way, BAD_POOL_CALLER on two different machines, from a "gold" XP disc unmodified) I'd say it sounds like bad install medium. See if you can get yourself another known-good install disc, because that one is likely bad.

You are correct in your assessment, the GPO you've set is causing the unintended desired behavior with UNC paths, whereas the mapping drives behavior is what is supposed to happen otherwise. The way that urlmon works, is that if your path (UNC or otherwise) contains dotted parts, you're not going to be in the intranet zone. It would be better to place these in the TRUSTED SITES zone.

80000005 = an error has occurred (not really useful) and 0xa000000 = what is logged when the next admin user logs on after a machine is forcefully powered off and chooses a reason (any reason) from the unclean shutdown dialog box. Honestly, it'd be better if you could get a complete dump of the entire system the next time this occurs, because what we've got currently is not going to be enough to help you.

explorer.exe hanging as such after opening a network drive would seem to indicate waiting on an LSP perhaps, or something else underneath in the IP stack. Getting a application hang dump of explorer.exe as soon as it hangs like this would be beneficial to see if it is indeed waiting, or if it's really actually hung up.

I know for sure McAfee installs an LSP, and if Sybari is using the Exchange VSAPI, it's probably safe. However, if you remove McAfee (not disable, remove - you have to uninstall the LSP), does it work?

Describe "see" in this sense. If you want network separation/control over different machines on the same network segment, you'll need to do a VLAN on the switch, or perhaps use a firewall if you need finer control. If by "see" you mean browse, if they're on the same subnet it's not possible without some network controls in place.

Lots of programs other than ZoneAlarm that install network LSPs have problems after the DNS update. What exactly DO you have installed on the server?

Correct, VMWare's hypervisor is a MACROkernel, but now they're trying to pass it off as NOT being a macrokernel (well, it's easier than a rewrite to use confusing terminology to fool buyers/customers/users, but it doesn't change anything). I guess marketing sells (or in this case, gives?). As to Enlightened I/O, OSes that have a kernel that understand a hypervisor and are written to run in a child partition on top of a hypervisor actually will be able to run faster because they "understand" how to run virtualized, and bypass a lot of overhead by talking to the VMBus and the hypervisor directly (this is NOT the same as installing integration components - those just make the drivers in the VM more efficient, they do NOT "enlighten" the VM - the VM's kernel must be written to "understand" the VMBus and how to speak to it directly). VMI is "paravirtualization", meaning you have one "root" kernel (in this case, Linux) and "child" kernels running as a "guest" of the root OS (hey, sounds like emulating a microkernel!). The benefits to this are that there is only one real OS doing the "kernel" work, and it is controlling all of the guest partitions inside it running the guest OSes. It's not actually a real "hypervisor" approach, but it does make child VMs faster than type-2 virtualization. VMWare's take on this, if I understand it correctly from their spec, is to install the root Linux partition into the hypervisor, and run the guest partitions off of that root hypervisor VMI (again, sounds a LOT like microkernel design).

Since the related Dell Server has 64-bit Quad-Core Intel® Xeon® processors, he probably will need to take the XP_IA64 drivers. I am missing something. Just because a chip is dual core, quad core, octal core, <insert n core here>, etc - the architecture is still x86_64, not Itanium. If he's using a Xeon, it's _not_ an itanium and he'll need x86_64 drivers (x64). Did I miss something here?

Well, do some research into the macrokernel+vendor provides hypervisor drivers versus microkernel+root partition+synthetic drivers architecture (ESX vs Hyper-V) before assuming VMWare's offering is better than Microsoft's. There are a lot of drawbacks with a macrokernel hypervisor like ESX uses, and there are some pluses as well. Especially if you're going to run a lot of non-Microsoft VMs and want integration components, ESX is going to be a better choice due to better non-Microsoft OS support. If you're going to run a lot of Microsoft VMs, however, hyper-v is likely going to be faster (and if you run Vista SP1 or Server 2008 VMs that are enlightened for the hypervisor in kernel, they'll be much faster on hyper-v). There can also be some security issues with a macrokernel you won't run into with a microkernel hypervisor, and you can also find it more common for a misbehaving VM driver in a macrokernel hypervisor to affect the rest of the VMs than would happen in a microkernel hypervisor (because the VM's drivers don't go directly into the hypervisor, and thus the root has more control). The macrokernel is going to be a tad faster than a microkernel hypervisor, because you don't have accesses through the root partition drivers thus increasing speed. AMD-V and Intel-VT significantly reduce this hit at this point, but it's still there and ESX still provides a bit better I/O to a virtual disk. Once the next versions ship with Nehalem and the next Opterons, this will shrink, but an I/O intensive VM should be using a passthrough disk anyway . It's pluses and minuses on both sides, you have to decide which pluses you want, and which minuses you can live with. I've used both ESX and Hyper-V extensively, and the only reason I would choose ESX at this point would be if I was virtualizing a Linux or another Unix-based OS.

List the 6 patches your app says you need, and we can find out if they're in MS08-031 or not .

I've found that using vLite to strip out all languages but the actual one you're going to use reduces the SXS folder size to a more manageable ~1.8GB after x64 install (not sure about x86). I've actually got everything installed on this box (including VS 2008) and I'm only at ~4.5GB, which is smaller than a base x64 OS without stripping languages was (about 6GB after install).

DNS registration is probably not getting updated to reflect the new IP address. If you run "ipconfig /registerdns" on the laptop after switching connections, then watch the event logs on the server and client, make sure it updates properly (if not investigate the failures in the event log). If you're using a Windows-based DHCP server, consider configuring the scope to always update A and PTR records when an IP address is given to a client (it does not do this by default unless the client requests it).

No, IAS really isn't documented as well as it probably should. However, using google does yield results. You can be the judge of whether or not they're good ones .

Are these domain groups, or global groups that you're trying to add the users to?

IAS works without AD.

# for decimal 10107 / hex 0x277b WSASYSCALLFAILURE winerror.h # A system call that should never fail has failed. I'd honestly suggest either a system restore to when it worked, or to remove all antivirus/firewalls/network drivers and reinstall the NIC drivers. Then, run the following from a command prompt as an administrator: netsh int ip reset resetlog.txt Once this completes, reboot and check to see if connectivity is working again.

From what you've stated your goals are, the quad core is good for running VMs simultaneously, and 8GB RAM should be plenty if you're running 2008+Hyper-V. As to disk I/O not good for VMs, Hyper-V supports pass-through disks that will show up as virtual disks in the VM, but the I/O goes directly to the disk and not through the hyper-V partition or the synthetic I/O filters. Thus, I/O is identical to the actual hardware (and this is the recommended config for VMs running things like SQL, Exchange, BizTalk, etc). If these are just testing VMs, it'd be better to spend money on slower, bigger disks and use a good RAID controller to make a RAID0 (or RAID 10 for RAID0 speed but RAID1 redundancy, if you don't mind the 50% disk space hit). I/O is going to be the limiting factor, but I have a 16GB box that routinely use 14GB or so for VMs concurrently, and I had to upgrade the disk subsystem to handle the passthrough disks I needed way before I hit 10GB RAM used by VMs - 8GB with a good slower, larger RAID array and a quad-core is a much better VM solution. Can't speak to games, as I don't.

Yeah, one of the ATI .dlls loaded, caused one of the ATI .exes to crash, which caused csrss to fail to load, thus causing winlogon to log the user off (which is apparently expected when this type of crash occurs). This is (one of the many reasons) why Vista / 2008 winlogon doesn't allow hooking anymore. Too many vendors doing things they shouldn't, causing crashes, and causing system instability.

Actually, you would want to UNINSTALL drivers and ATI software and reinstall with the most minimal driver set possible (no supporting software, reinstall JUST DRIVERS).