cluberti

Well, if it happens in safe mode, I'd say you probably have an issue with a kernel filesystem filter driver. Have you removed your antivirus and/or antispyware application(s) as a test?

Yes, you can click next without entering the key. And yes, reboot after disabling UAC and before installing Office. 1. Install Office 2007 with UAC disabled - do not enter product key when prompted 2. Turn UAC back on and reboot 3. You should get the "not installed for this user" warning at this point when running Office 4. Turn UAC back off and reboot 5. Enter product key in Office 2007 (it's in the Options > Resources menu, I believe, for Word or Excel) 6. Turn UAC back on and reboot 7. Run Office - it should now work for regular UAC-enabled users

What happens when you do this in safe mode then?

It depends on what you're doing and what you're running - if you're going x64, make sure that you have all drivers for your hardware (signed drivers!), and all of your software is x64 compatible (most is, but some apps have trouble under x64). Also, any antivirus and antispyware 32bit applications will need to be replaced with x64 versions, as you cannot install 32bit filter drivers in x64, no exceptions.

One thing I would strongly suggest you do while installing Office 2007 is to NOT place the product key when asked - I had this problem back in RC2, and I fixed it by installing Office 2007 without the product key, and after receiving the warning I turned UAC off, entered the product key, ran once, then re-enabled UAC and everything worked fine after that.

You either need to add quotes around the command line to use the variable, or you need to substitute the 8.3 path instead of the variable for the command to work. I see you've got it in runonceex format, so it should probably look like this: "\"%programfiles%\Symantec AntiVirus\VPDN_LU.exe\" /S" /f

Usually in the properties of the modem in device manager, there is a checkbox for allowing the modem sounds to be heard, and yes, this is disabled by default (not sure why, but it was). As to your URL issue, that seems very odd - have you installed IE6 SP1?

If you run autoruns to disable all non-Microsoft items, and shellexview to disable all non-Microsoft shell extensions, then reboot, does the problem persist? Also, does the problem occur while you are in safe mode?

It is - it is called the Wave Volume API pre-Vista, and Windows Audio Session API in Vista (a rewrite of the audio API). However, I think the nirsoft tool uses the mixer API, which most drivers support (it was added in Win98, but it is possible some audio drivers still will not expose mixer controls). A high-level overview is here: http://blogs.msdn.com/larryosterman/archiv.../15/504158.aspx

If you click the "click here" link, does it tell you which module rundll32.exe is having a problem with? If you've got the ATI driver package installed, that'd be the first I'd remove, I think.

Dreamscene hasn't been released yet, but should be shortly. http://windowsultimate.com/blogs/extras/ar...dreamscene.aspx

Perl is actually a good language to start learning, if your ultimate goal is C or C++ - they're somewhat similar in structure and form, and perl to C is a fairly easy transition.

I tested the page with Vista/IE7, XP SP2/IE6, XP SP2/IE7, and 2K3/IE7 and everything seems to display just fine.

Have you downloaded the latest Vista drivers for your device if they exist? That error only happens if you're out of resources on the USB bus (which you don't seem to be), or the driver isn't being allowed to start or is crashing on startup.

Hm - works just fine here. Have you vlited your install, or disabled any services?

Moving to more appropriate forum.

To be honest, I've only seen this error for 2 reasons - one, viruses. Two, ATI driver software . Removal of the viruses worked for one, and uninstalling the ATI software solved the other. Happened just the way you've said it does, too, in both cases. Since you're going into add/remove programs, my money's on one of the installed apps (like the ATI control panel nonsense).

The documentation will get there, although the stuff here will probably still be as good or better . As to running things post-install, you can find that in the unattended vista and application installs sections of the boards - this kind of thing gets discussed a lot in those places, especially unattended vista .

First things first - install Vista clean on the box, and then sysprep right away (install nothing). If it works there, reinstall clean, then install the software you need (again, no drivers) and try again. As before, if it works, you should be golden (although it is quite possible the filter driver from Avast is causing this). Usually I suggest antivirus installations to always be post-image, as they require kernel-mode drivers that can be configured machine-specific, and sysprep will break that.

Well, that's hard to say (although it does sound very suspicious). Have you scanned your machine for viruses and spyware lately, with up-to-date tools?

I'm not so sure that is still true. The license agreement changed in September of 2005, in that you must sell a PC to sell an OEM license, and you must be buying a PC to buy an OEM license unless you are a royalty OEM. Therefore, buying an OEM license from a store, whether online or off, must also include the purchase of a PC. If someone sells you an OEM copy of Windows without qualifying PC hardware (see below), they've technically violated the license agreement, and your copy is not valid. Again, I don't believe Microsoft has ever tried to uphold this, but they could decide they want to at any time. Section 4.1: Section 6: Section 15.1: So, in short, a whole PC, or you can't legally acquire or sell OEM software. If you're unsure about the vendor, check the Authorized OEM software distributor list from Microsoft.com.

Usually, these errors are due to problems with permissions on the HKEY_CLASSES_ROOT key and it's subkeys for the user running the command or the installation. Run Process Monitor while running regsvr32 against msxml2.dll, and see if you get any access denied errors specifically to the registry.

Hm - that's very odd that it would hang after the second boot. I just need to make sure that I have this right before I continue: you can always install successfully (I'm assuming you've done this a few times), and then it always fails after windows update install? Can you cancel the update install / download, then reboot to see if it's the updates, or the reboot?

Well, considering NTDLL.dll is just an API dll to kernel-mode code, ntdll is not your problem - something else running in kernel is. Have you run autoruns to disable all non-Microsoft items, reboot, and see if the problem persists?

What IP addresses do these machines have, and do they both have the same DNS (and/or WINS) servers configured?