cluberti

I've seen this before where the user accounts were power users on the Terminal Server, or had Print Administrator rights assigned. Also seen this happen when the users' printers are initially installed locally via a logon script that is running under a generic service account, rather than the user (like in ScriptLogic, for example).

I've got the IE7 update rollup for XP and 2K3 as KB926874, 11/28/06.

Consider forcing the classic-style logon, rather than the welcome screen, and make sure your .sif doesn't autologon (or if it does, set a limit of 1 or 2 logons if possible). This should keep the box from logging on automagically more than a few times.

It should be there (there was an issue of the Spanish version being released to en-US servers, but that was fixed. Perhaps you should search for "Internet Explorer" in the GUI to see what comes up?

Sounds like it could be that the modem driver isn't handling the standby power mode well - are you sure you've got the very latest stable driver for your modem, and that it was designed for XP?

@spooky - LOL

I'm confused - you want to replace a .bat or .cmd file with a .vbs script, is that correct?

I'd say it's best to make sure your machine is clean (from safe mode) with programs like hijackthis, spybot S&D, and Windows Defender. I'd also say make sure your antivirus software is up-to-date, and do a complete scan with that as well. I see nothing strange in the task manager listing you show, but you also don't have the "show processes for all users" check box checked, so it could be something running as someone else interactively. If the taskbar message is still showing up, it's not gone yet.

That is very possible - glad to hear you got everything working again

I certainly hope you change your mind in the future, and it's sad that you base your opinion of Vista on a beta. It's slow because it's running checked versions of most things in the OS - meaning it's about 50% slower than the release (unchecked) versions of 58xx and up. If you're running RC2, it's probably slow due to this. This is incorrect - it was this way for some reason during the betas, but cooler heads prevailed and the licensing terms are basically the same as XP's. No "one install/activation limit". That is, of course, your opinion. I'm sorry your experience with Vista was not good, but at least give RTM a try - basing your opinion on a product on a beta seems a bit near-sighted, but if Linux works for you, go with it. I've said it before, and I'll say it again - over 50% of support calls are due to buggy, poorly-written, and (for the most part, anyway) unsigned 3rd party drivers. This is a way to try and stabilize the OS, make driver writers more accountable for their driver code, and reduce support costs for the OS by reducing the most common support call. You can disable this in group policy or via the registry if you want your system more under your control. However, I must mention that if you do call for support, they're going to make you turn that back on and reboot before you do anything else.

Does the problem occur in safe mode w/networking? If you've got a PS/2 keyboard, you can also do this to generate a complete memory dump the next time your computer does this: First, make sure that your paging file is at least the size of physical RAM +50MB or so, and that it is on the drive or partition where Windows is installed. Then, do the following: 1. Create or set the following registry value: Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters Value: CrashOnCtrlScroll Type: REG_DWORD Data: 1 2. Right-Click on the "My Computer" icon on the desktop and select "Properties"; this will open the "System Properties" window. Go to the "Advanced" tab and click "Performance Options". Click "Change" under "Virtual Memory". Set the pagefile to be located on the partition where the OS is installed, and set it to be equal to Physical RAM + 50 MB. 3. Also in the "System Properties" window, click on the "Advanced" tab, then click "Startup and Recovery". Make sure "Complete Memory Dump" is selected (see 3a if this is not in the list). You can change the location of the memory dump file to a different local partition if you do not have enough room on the partition where the OS is installed. 3a. If the "Complete Memory Dump" option in step 4 is not available, you will need to manually set this registry value: Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl Value: CrashDumpEnabled Type: REG_DWORD Value: 1 4. You will need to reboot for these changes to take effect. The next time your computer hangs like this, on the keyboard, hold down the RIGHT-hand CTRL key and then press the Scroll Lock key twice. This will bugcheck the box (with a STOP 0xE2), and do a complete memory dump. Once the dump completes, and the computer is restarted, the dump file can then be analyzed to see what's hanging your box.

Do you have any chipset or processor power monitoring software installed, like Intel's chipset application with a core single/duo or Pentium M, or AMD's powernow? You could always take a look at the process with Process Explorer or dump it out with adplus to see what's running in there too.

I've got to second ringfinger - test directly attached to the DSL modem first, then attach the switch and test again.

Has anyone considered that this could be a simple autonegotiation problem between the PC and router/switch port? Forcing the NIC to 100Mb/Full duplex (or whatever the router is supposed to use) resolves a lot of issues like these. When the NIC autonegotiates (approximately once every few seconds to few minutes, btw, depending on the driver), all traffic will cease on the connection until finished. If you know your network's rated speed/duplex (and your NIC and router support said speed/duplex), there's no reason to leave autonegotiation enabled at all - force it.

Give the administrator account a password in the XML, and it'll be activated on install. Since you've probably got the WAIK, it's documented in the help.

And if you activate it in VMWare and then image it to a real machine, there's a very, very good chance you'll need to reactivate again (too many hardware changes).

You really should be using the js method I posted above, because anyone running Vista is going to have this problem, as well as XP and 2K3 users after installing the April '06 cumulative update, or XP or 2K3 IE7 users. Loading activex controls using the Object tag is deprecated, and will stop working altogether on almost all updated machines soon. Consider fixing it before it breaks permanently

The "Idle" process isn't exactly "idle" - things do actually run in the idle process (believe it or not), and the SYSTEM process is the representation of things running in kernel. That's actually a pretty low number for the SYSTEM process .

It is - user-enforced DRM for your documents created in applications that understand the Rights Management client (like Office 2003 and Office 2007).

If that's the case (and you may be right, it probably won't see it if you didn't install it to the hard disk), you'll have to do a repair installation.

Ah, forgot about that. We'll have to use adplus: First, install the "Debugging Tools for Windows" from: http://www.microsoft.com/whdc/devtools/deb...ng/default.mspx Once these tools are installed, do the following: 1. Create a directory called c:\adplus 2. Open a command prompt and change to the directory where you installed the debugging tools. By default, this is "C:\Program Files\Debugging Tools for Windows" 3. Type the following command in the command prompt: cscript adplus.vbs -crash -pn dllhost.exe -o c:\adplus This should generate a crash dump of dllhost.exe in C:\adplus that can be analyzed via windbg or cdb the next time you get a crash. If you don't feel comfortable doing it, I can do it if you PM me.

No - it's either RIS or CD-based flat-file installs, sysprep, or riprep. You can find sysprep on the XP CD, and RIS/risetup can be installed on Server 2003 or 2000 Server.

Note that neither IE7 nor WMP11 will install until your OS is activated - so unless you have autoactivate=yes in your winnt.sif file, you'll not be able to install either on retail versions of the OS untill you've manually activated.

That's correct.

If you've got an Enterprise support agreement with Microsoft, you can contact your TAM to see if they'll send you the MUI for Windows 2000 (although since it's in extended support, you'll probably also need SA and an extended support agreement for W2K). If you aren't an enterprise customer, you're SOL unless you can find an enterprise customer to send you theirs.