cluberti

The only reasons vendors say to buy from them is that they are able to sell you more product, and that they can guarantee it'll work with what came with your PC (I've purchased memory from Dell for an Optiplex that didn't work with the included memory, so they had to send me two new sticks, so don't count on that "guarantee" either). Since other vendors will provide memory compatible with your machine (crucual is one, buymemory.com is another I swear by), there's no reason not to save some $$$ and go with a 3rd party. Don't let Dell scare you!

You can technically run interactive services on Windows Vista, but they must be run under the SYSTEM account (LocalSystem). Since everything that runs under the SYSTEM account runs under session 0 (short of some psexec or windbg hacking to get it to a different session), and session 0 is no longer viewable by anyone but the actual SYSTEM account, no one will see any UI provided by your service, nor will your service be able to send or receive messages from a different user-mode session (this is no longer allowed, due to so-called "shatter" attack vulnerabilities that can exist when this is enabled). The catch is that interactive services only work for session 0. The way it works on Windows 2000, Windows XP, and Server 2003, is session 0 is the session that the user on the physical console logs into – the actual keyboard, mouse and graphics hardware physically plugged into the machine. A twist on this is that in FUS (fast user switching) on Windows XP, the first user to log into the console gets session 0, and subsequent users get their own sessions starting with session 1, then session 2, and so on. Windows XP Professional will allow remote access to session 0 if the user currently logged in locally to session 0 logs in remotely, or if no user is currently logged in. Server 2003 will only allow remote access to session 0 if the /console switch is used with mstsc.exe. Windows 2000 will never remote to session 0, as it was not designed or supported under that OS. This matters because users with other session numbers than 0 will never see the interactive service's UI, and this is now the default configuration in Windows Vista and Longhorn server. If you’re trying to create a dialog box to allow configuration changes, or notify a user of a problem or event in the service, then they will not see the dialog ever in Windows Vista, or until someone physically logs in at the console (or uses the /console switch on Server 2003) for Windows XP and Server 2003. Read the whitepaper for more info on why interactive services on Vista are a bad idea, and for the most part don't work as they did on XP and older OSes. There's also links to helpful hints on how to rewrite your services so that they work under the new configuration in Windows Vista and Longhorn server.

Found this on channel9 - not using a laptop at the moment, so I can't test, but it might work for you. http://channel9.msdn.com/ShowPost.aspx?PostID=172493

Ping works because ICMP is part of the network stack, and once network drivers are installed properly it comes up. However, the workstation service is not ready and running properly until Windows has finished installing (so no network share access during GUI setup). One thing you can do, however, would be to start the install from WinPE, connect to your database, and set the change in a file on the local disk. Then have a routine in GUI setup read from that file.

Well, then I'd do some checking around - one, check this registry value to see if it's set to one - if so, set it to zero and reboot. Two, make sure UPHClean is installed properly (you did state it is, but making sure you're running the latest version is key). Three, in your computer's BIOS, see if it has an option for power state after power failure (or something like that) - these are usually set to auto, but they can be set to always off or always on - try making sure this is always off. Four, make sure you have the latest BIOS version installed for your motherboard model, as power options in XP rely heavily on BIOS compatibility. And last, but not least, boot into safe mode and see if the issue occurs when shutting down in safe mode.

The only way to see if it worked is to see if you have a .sp4 file on the root of the CD, and an sp4.cab file in the i386 directory. As to the install, if you've already got a partition greater than 137GB, it should format and install no problem - it just won't create a partition larger than that .

Read the Release Notes for a fix if you're using one of the programs that ship with their own version of psapi.dll. It's not a Windows or IE problem. The relevant bits for the lazy :

I'd strongly suggest running "sfc /scannow" at this point, then, and see if the problem continues.

Is Internet Services United your ISP, or are you using them as a proxy for internet access?

Slipstreaming SP4 into a Windows 2000 CD doesn't "fix" the 137GB limit issue. You will either have to partition and format the partition NTFS with something other than Windows Setup before beginning the install (PartitionMagic, GParted, etc), or setup Windows on a partition that is 137GB or smaller and resize after installation.

WDS can deploy "flat" images only when RIS is enabled. WDS natively can deploy WIM images only, so if you make a WIM image of whatever it is you're trying to deploy (XP, Linux OS), then it should be able to attempt to deploy that (XP does work, btw, when in a WIM image).

This is usually caused by 3rd party disk management or monitoring software - if you've got anything like this installed, uninstall and reboot, and possibly run sfc /scannow, and the problem should go away. This is almost always caused by 3rd party disk management software .dll's loading in the mmc, which will crash the disk management mmc more often than not.

If your DC doesn't have itself listed as a DNS server, then yes, AD will be slow and unreliable. Almost everything in AD requires a fully-functional DNS infrastructure, and the DC's need to be pointed at themselves or other DCs running DNS - no non-AD machine DNS information should be in any configuration.

That stop error is caused by one of three things: 1. Poorly written kernel-mode drivers 2. Overclocked processor 3. Faulty RAM To be honest, this one's usually caused by #3, but overclocking your processor can cause this as well. One thing you can do is download and run a memory tester, such as Microsoft's Memory Diagnostic.

What are the DNS configurations on the clients, and on the server? Are they all pointing at the same DNS server(s), and if so, what DNS servers are they pointing to?

Is this XP Home, or XP Pro?

No, because the driver is already unloaded or it's memory address is corrupt (that's why you see only a memory address in the stack). You'll either need to enable driver verifier or special pool (or both). However, I can tell you just from the stack that it is a user mode application calling a kernel-mode driver to do something (likely in nonpaged pool) - if you've installed, uninstalled, or updated an antivirus, antispyware, firewall, or backup application recently, those would then be suspect.

If you download something like Process Explorer, you can see what system call is using the most CPU time - assuming you've configured your symbol path variable, of course: To use the Microsoft Symbol Server 1. Make sure you have installed the latest version of Debugging Tools for Windows. 2. Decide where to store the downloaded symbols (the "downstream store"). This can be a local drive or a UNC path. 3. Set the debugger symbol path as follows, substituting your downstream store path for DownstreamStore. SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols For example, to download symbols to c:\websymbols, you would add the following to your symbol path: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols

No, Home keys cannot be used on Pro discs (and vice-versa), they're product specific.

The only problem I have with dial-a-fix (and it's only my problem, it isn't a problem per-se) is that you don't necessarily have to do any troubleshooting on the problem at hand to use and resolve things via dial-a-fix, and it removes some of the learning involved in developing good troubleshooting skills. More of a pet-peeve than a problem . I feel sometimes like it's the proverbial flame-thrower used to light a candle, but again, just my opinion.

If you've got 64bit Windows, you should already have 32bit IE installed and you can use that to get to windows update. You'll find it in the start menu (non-classic, the 32bit IE is the IE pinned to the top) and under the programs list. If you've removed it from there for some reason, you can find it in \Program Files (x86)\Internet Explorer\.

If you want to find out what is giving access denied error messages, download Process Monitor from the Sysinternals site and run it while trying to change the service's properties. When you get the access denied in the Services control panel, you'll see what you're denied to, and which user account was given the access denied error (sometimes it's not yours).

You must already have a backup. If you do not, you cannot use ASR. To create an ASR backup, sinply run the ntbackup utility and choose the ASR option.

Spooky is correct - you can go through the Microsoft program (links to the program appear after you fail validation on Windows Update, for reference), or you can purchase a new copy of Windows XP from a retailer, install it, and upgrade. However, I'd suggest reporting the vendor who wiped your disk and installed an unlicensed copy of XP, and they should be providing you a licensed copy at this point.

Normally I would suggest something like xplode, but if you are having trouble with WIHU that might be too much for you. I've also used Setup Studio with Windows XP many times, but their version for Vista won't be ready for a few more months. Not sure what to tell you other than dig into WIHU or Xplode and learn, and then ask questions here on how to do things you're having trouble with.