cluberti

You might want to post this in one of the programming sections of the forum for quicker response. Also, consider reading up on the delprof.exe tool from the W2K resource kit, as it does exactly what you are wanting to do...

Usually, taking that long to load is caused by a driver or startup service/application, and disk fragmentation can also make things take longer as well. You could just use msconfig (start > run > msconfig) and disable all non-Microsoft services and startup items and reboot to see if that speeds things up a bit, as well as defrag the disk Windows is installed on. If using msconfig and disabling those items speeds things up, just re-enable things until you find the culprit. If you want a prettier interface, you can use autoruns from Sysinternals.

Considering the network stack changed completely between XP and Vista, I'd say it won't work. You can always try though...

Pressing F5 and choosing "Standard PC" will get the setup to load the file hal.dll as the hal, rather than the hal it has determined you need (halaacpi.dll). Using the "Standard PC" option isn't necessarily a good choice long term (no acpi or apm support, so no power management, for starters), but it will be a good test to see if the disk installs otherwise. If that works, then it is indeed a problem with the file on the CD - if it fails, it could be something else innocuous like a BIOS setting (or even a BIOS update), or a piece of hardware it doesn't like, etc. I'm still leaning towards the CD itself having the issue, but I never rule out hardware, especially on older machines. That's why I suggested this test - it should tell us which is the culprit.

Content advisor is meant to block a site by content, not by page, but it can work for the most part. A better way to do it would be to install a proxy server and force everyone to use that, but content advisor will work on a small scale without too many problems. There's even a KB on it: http://support.microsoft.com/kb/310401

You could always just edit the registry locations that the group policy sets (hint - group policies are, for the most part, just registry changes)... http://support.microsoft.com/kb/242557

On Windows 2000 RIS servers, if you install MS02-050 on the RIS server but not the DC's, this can happen. This shouldn't happen with W2K3 servers, as that OS was released after the MS02-050 update and W2K3 binaries were not affected by this issue. If you've got Windows 2000 servers in your organization, you should make sure all of the DC's have MS02-050 installed (or SP4 with update rollup 1, which is a better choice as it includes a few other critical RPC updates that you should also install). Basically, if you're running RIS in an AD, make sure the RIS server and your DCs are all at the same patch level and you won't run into the types of problems that can occur when they are not .

From what you've posted, it sounds like Windows is complaining that the file cannot be loaded due to it either not being there, or being corrupted. If you press F5 when you see the "Press F6..." text along the bottom, and choose the "Standard PC" option, does the installation continue properly from that point?

I've been installing SAV10 on Vista without too much issue thus far, but I ended up using a transform to install it rather than the command line (because the "disable Windows Defender" checkbox doesn't appear to be exposed as a public option switch in the MSI package). Rather than fighting to figure out the command, I just installed with a transform.

Are you attempting to use the UPN name to authenticate, rather than just the username in oschooser? Also, did this computer name (computer account) previously exist, and built by RIS previously? We usually only see this error when the RIS server has MS02-050 and one (or more) of the DCs do not, the user tries to use a UPN to authenticate in the oschooser screen rather than just their username and password, or the computer account you are trying to use was previously built by RIS, but the computer itself is different (and thus will have a different GUID).

It appears that I get the same behavior - when I install on XP with the IE7 download package, it works, and when I use an IEAK package (with no customizations either), it does not.

If you log on with another account to that same machine, does that account not have the problem on the same machine your account does not work on?

According to that hex value, the return code is "ERROR_SHARING_VIOLATION" with the error "The process cannot access the file because it is being used by another process". If you run handle.exe on your box, do you see any open handles to this image while it's not being downloaded to clients? Also, are you sure your antivirus application is not scanning realtime on this server, or at least the volume that contains your images?

If you were one of the many who visited the powertogether.com site and finished the required videos, I would expect you would be receiving that email message.

If you were one of the many who visited the powertogether.com site and finished the required videos, I would expect you would be receiving that email message.

Technically, all versions of Windows have come with a license that forbids installing one license on multiple machines, unless it was a VLK license. Windows XP's activation was the first attempt at enforcement of this, but the VLK loophole still existed (and that's why most pirated copies of the OS use VLK keys to get around the check). However, with Vista, even VLK copies will require activation with a KMS or use a MAK that requires activation from Microsoft, therefore to get around it in Vista it's likely that cracks and other means of patching the OS will be required.

If you do not wish to run IE6 SP1 for XP SP2, then you'll have to forgo installing XP SP2, as there's no way around the IE update that SP2 brings.

I've actually still got a Linksys befsr4 router (the same as yours, without the wireless), and I upgraded it to the latest firmware - there are no screens that I can see that provide you this functionaility. You'll either have to replace that with a router that can block websites, set up a squid proxy (or similar) on another machine that will be able to block the requests, or use a hosts file on each machine. The only one that allows you the password bypass will be a proxy, however, so be aware that you'll probably be best served by replacing that 2001-era Linksys with an old machine running as your proxy.

Sysprep is what you're after, I believe. Sysprep removes most of the machine-specific information about an XP machine, so it can then be imaged onto other machines. The hardware needs to be similar, of course, but it does what you're asking. Read up on it, and play around with it until you're comfortable with it.

Assuming you're getting your IP information from DNS, what DNS server information are you pushing down to the machine?

You have to check the "Show Updates" box at the top of the window to see updates - they're hidden by default .

Well, I tried it on a clean XP machine, installed IE7, then changed the reg key (didn't install Microsoft Update) and it didn't change the text as you describe. I installed Microsoft Update, and it did not change the text. In IE7, if I run regmon while starting it, it doesn't appear to even be reading this reg value - it's either not configured to change at all in IE7, or it's located somewhere else in the registry. I'll keep looking to see if I can find it .

You need to right-click on the Administrator account object itself to see the option. It's in the right-click menu itself - also note that if you are not logged on as the domain admin, or with domain admin privileges, you will not be able to reset the password for the domain Administrator account.

I hate to ask, but describe "slow" - is it slow by a second or two, minutes, hours, days , etc? And what is slow, exactly - the actual loading of the page, displaying certain parts of pages, getting a web site resolved, etc?

That is very true - parts of the kernel itself are configured to be paged out as necessary. Disabling the paging file isn't necessarily a good idea, and even though you usually don't need it when you have large amounts of RAM, some software will still insist on using it (photoshop, for example). Set the paging file to a system-managed setting, or set it to something like 1024 or 2048 for both min and max values. 70% RAM used is about the time Windows will go and start paging unused bits of memory out - remember, it does this on a percentage basis, not an actual free memory number. 70% seems about right.