cluberti

A few things spring to mind - one, add the server and domain to the "Local Intranet" zone in IE (yes, this actually usually fixes it). If that doesn't work, get a process monitor log of the issue occurring, perhaps along with a network trace as a last resort.

You can edit the common explorer open file dialog box via group policy, either locally, or on a domain GPO: User Configuration > Administrative Templates > Windows Components > Windows Explorer > Common Open File Dialog It can also be done via the registry, as per KB 826214: 826214: How to customize the My Places bar in both the Open and the Save As dialog boxes in Office http://support.microsoft.com/kb/826214

.NET Framework 1.1: http://www.microsoft.com/downloads/details...;displaylang=en .NET Framework 1.1 SP1: http://www.microsoft.com/downloads/details...DB-A83353618B38 .NET Framework 2.0: http://www.microsoft.com/downloads/details...;displaylang=en

The OS itself will be identical between OEM and retail versions - it's the "strings" that come attached to the cheaper OEM license. 1. You can't remove it from the machine you install it on - it becomes tied to that machine forever. If you buy a new machine, you have to buy a new copy of Windows (well, legally). 2. You cannot receive phone or email support from Microsoft, period. You have to call the vendor who sold you the OEM copy of Windows for suppoort (and if it's an online store, YOU become the OEM you need to call. You can see how this would become a problem when you need support, from... you... ). 3. You have to purchase an OEM license with hardware, and in most countries, this is an actual PC. Power cords, screw sets, or even hard drives do not technically qualify as a qualifying OEM purchase. You can still do it, but you will technically violate the EULA, and although they've never been heavy-handed with those types of things, there's no saying it won't happen in the future.

Exactly.

That's because they're no longer in mainstream support, and this is not a security-related update. Therefore, it's for XP and 2K3 only, not 2000 or NT4.

0x000000F4: CRITICAL_OBJECT_TERMINATION One of the many processes or threads crucial to system operation has unexpectedly exited or been terminated. As a result, the system can no longer function. Specific causes are many, and often best resolved by a careful history of the problem and the circumstances of the error message. From the data here, I can decipher some things about your problem: - The first parameter shows us that it was a process (3 for process, 6 for thread) - The second parameter is the terminating object's memory address (84c95578) - in this case, unless you're using the /3GB switch, it was a process running in kernel (80000000 - FFFFFFFF are kernel address ranges when booting without /3GB) - The third and fourth addresses tell us which process it was, and text of the error. However, without a memory dump from your box of the issue, there's no way to tell. If you have any *.dmp files in your Windows directory from around that time, we'll need to review those to give you a full answer.

Hm - sounds like it's crashing or access violating. Perhaps run process monitor while launching, to make sure you aren't getting an access denied to anything.

You'd have to re-write the installer, because it's hard-coded into the installer engine routine. Good luck.

A lot of people install updates, and then when something doesn't work, they blame the update install. Remember that most update installations cause you to reboot, and it's the reboot that causes the issues (in that something done before update install and reboot was just waiting for you to restart the machine so it could take effect ). Perhaps you should roll back your changes to a restore point and try again?

0.2 for your CPU seems like a misprint - perhaps you meant 2.0?

Disabling the DNS client service will keep DNS from working, although if that's running, it'd be something else. You could check and make sure the hosts file doesn't contain any entries to block browsing as well, although it is really hard to tell what could have caused this without knowing anything else about that machine.

Since I've already been PM'ed about this a few times, I thought I'd say that yes, the WRK kernel posted here is valid and not technically leaked, but it is only available to be used legally by persons enrolled in, employed in teaching at, or involved in research at higher education facilities: Eligibility Requirements: Use of the Windows Research Kernel requires academic affiliation with an accredited institution of higher education and direct involvement in teaching and/or research, such as being academic faculty members, system or lab administrators or instructors, students enrolled in relevant undergraduate or graduate programs, or academic researchers working on faculty sponsored projects. http://www.microsoft.com/resources/shareds...archkernel.mspx However, since this is only supposed to be available via MSDNAA, I'd say this is pushing legal limits in some countries.

Are you using a public domain name (domain.com, domain.org, etc) as your internal AD domain name? If so, have you configured split DNS properly?

Have you read this KB yet? 301224: System Restore "restore points" are missing or deleted http://support.microsoft.com/default.aspx?...kb;EN-US;301224

It seems you've double-posted, but that's OK. This is almost always caused by Alcohol 120, although Daemon tools can do it too.

Actually, it's probably asking for the CD due to SFC kicking off and not liking something it found in the dllcache - have you disabled SFC, or deleted things from dllcache?

If both are on different LAN segments (and I'm assuming they are both /24 and on differing segments), you need a router, or switches that can do static routing, to pass traffic between the two. Some higher-end switches can do basic VLAN routing if the networks are on differing VLANs on the same switch.

Is the machine going into standby or hibernate while you're away? I think the inactivity on the machine may be a key here...

Have you considered backing up the user's email to a .pst, and deleting and re-creating the user's mailbox?

This gets asked a lot - no, you can't bypass the initial check, but you can remove RAM once Vista is installed without issue.

Well, STOP 0x7B is "Inaccessible Boot Device"... so sounds like your PE doesn't have a necessary controller driver for the machine you're booting to.

What's the bugcheck STOP code?

Dreamscene isn't quite ready for primetime yet - when it is, you'll see it on extras.

I have pointed people to that site without issue multiple times, so it should work. However, OEM copies of XP Pro are usually less than the $199 you'll be charged on the WGA site, so if you don't mind a clean reinstall, you can save some money there.