cluberti

Yes, it's a build from over 2 months ago. It's already far out of date.

There are features that you get with Ultimate, for example, that you don't get with Home Premium. However, the running of applications themselves, or the ability to use the RAM, is not different between the two versions.

Well, do you have anything additional running Windows-wise when you reboot and then start using your computer versus when you resume from sleep and use the computer? Assuming the usage patterns is the same, this is likely a driver issue.

If you can ping it and/or run psexec remotely on it when it's hung, you could use that to call notmyfault or crash.exe from the remote psexec prompt.

Please post your vLite-related questions in the vLite forums, if you would. Thank you.

Didn't even notice that on first read. Good questions, all .

As per our forum rules, I would suggest using something other than Hiren's - the tools you use inside the CD might be fine, but the whole of the disc does contain copyrighted and non-free apps, and thus we consider Hiren's here to be warez unless you happen to own licenses for the (many) software tools inside that are non-free. I would instead strongly recommend the bitdefender tools, here. As to getting them to boot from the hard disk, that's another matter entirely that I'll let someone more knowledgeable than I answer.

The kernel required for an x86 Windows OS requires server 2003. XP SP0 doesn't contain such a kernel that I am aware of, but if you have links otherwise you should post them here.

I'm not familiar with the Dell tool, but what format are the images in? If they're WIM files, you can deploy them with WinPE from WDS. If not, see if they can be deployed from a bootable WinPE image over the network (Dell should be able to answer this).

When building a lab that will not be accessible anywhere but in the virtual network, I tend to use any old domain name. You will get errors about DNS delegation, but that isn't an issue when setting up a DC on an isolated network and you can click "Yes" to continue. For my DCs in test labs, I usually install DHCP, DNS, and AD DS, and then run dcpromo (saving the configuration log on the first run, so I can re-use it every other time I rebuild the domain). Again, if you have an isolated network, you will get one DNS delegation error on dcpromo, but it can be safely ignored.

You can change the options in GPO so that the user is not logged on until the network connection is up and available. Computer Config > Admin Templates > System > Logon > "Always wait for the network at computer startup and logon".

Probably want to make a new thread for that or take it into PM until we do (or do not) get a definitive working install for that component. That way this thread stays "clean", at least as much as possible. I hope you figure it out though.

Yes.

Opera 11 is also compiled LARGEADDRESSAWARE, so both browsers (Firefox and Opera) will be able to use more than 2GB of VA, which will likely show up as more RAM usage before they crash. Good to see you've at least found something that helps.

I've never seen the errors people usually get when doing this, but I also build in a VM with no network adapter at all, so perhaps that could be it. I would concur though, stopping those services before running sysprep is usually a good idea.

From what I understand, Firefox 4.x builds are compiled LARGEADDRESSAWARE, but 3.x and older are not. If you're running FF 4.x, that would make sense. If you are running anything older than that, the /3GB is probably allowing something else to expand, but it won't be Firefox. I can't argue with the results, but again only FF 4.x 32bit builds are compiled LAA, so unless you're using that the /3GB switch is not helping Firefox specifically.

The MPS HAL options are the same as the Standard PC HAL options, but with support for multiple processors and Advanced Power Management (APM). MPS HALs do not support ACPI, though, whereas the ACPI HALs obviously do (ACPI HALs support machines that use both ACPI and APM - if you have a system that supports APM only, you will use an MPS HAL). The Compaq SystemPro HAL is specific to old Compaq SystemPro machines and non-PCI Compaq ProLiant machines. The SystemPro was basically a server board design in a desktop chassis and was of course a custom motherboard design (and as such needed a special HAL to work properly - it was from 1989 after all). Non-PCI-based ProLiant machines used a similar setup, and thus worked properly with the SystemPro HAL. Again, these things are ancient, so running XP on them for anything other than some sort of nostalgia or a joke would be unwise . These would be better running NT 3.5x or 4.0 if they had to run Windows. The ACPI HAL supports APM power, but also supports the newer ACPI system and power design, as well as APIC in addition to the original x86 PIC processor designs from the original x86 8086 and the PC/XT. If you have a system that meets these requirements, you will use the ACPI Multiprocessor or Uniprocessor HAL on an APIC machine, and the regular ACPI PC HAL on a non-APIC machine that still supports ACPI. The "other" HAL type I've never seen used, but it would come up if a system didn't even meet the "Standard PC" HAL requirements (an Intel 486 CPU or compatible, or higher, and doesn't fall into one of the other HAL types). I suppose really old Cyrix or AMD CPUs "could" have fallen into this bucket, but most of those were Intel compatible at this time. There's more than that, but Technet has some additional information if you want to get geeky about what hardware types cause which HAL to be used.

Sorry you feel that way, but the rules are there for our protection and yours. Failure to follow rules may result in a ban, and you did agree to them when you signed up. Perhaps you should have read them completely and/or taken them more seriously. Again, sorry to see you go, but your attitude pushes the "may" into a "will" when it comes to the possibility of a ban.

As long as you don't need to know files or file types, yes, task manager is easier. Resmon is good if you need a bit more detail, and if you need process and file / registry information, you use procmon.

The beta is timebombed - since you used rt7lite to slipstream it, it cannot be reinstalled or modified in any way, at least not one that would make your system potentially unbootable in the future. I concur with MagicAndre, you should simply back up and reinstall - you will not be able to install post-SP1 hotfixes after a short time once they drop the pre-release build from the list of acceptable install builds, and you'll be up the proverbial creek without a paddle.

A few things - that error does usually indicate corruption of the SoftwareDistribution components, and potentially pending.xml operations that have not cleared. The only other time I've seen it is when antivirus software installed does actively interfere with the installation (I've seen McAfee, Avira, MSE, Forefront, Symantec, and Trend all cause an issue with Vista SP's in the past with the same error code - uninstalling each, installing the SP, and reinstalling the antivirus product worked every time). If you're running antivirus, uninstall and re-test, just to make sure, would be a start. The CBS logs do indicate your CBS store isn't 100% kosher, although CheckSUR didn't find anything that would block the SP install.

That's up to you. /PAE adds some memory manager overhead, but if you need the memory, then you'll have to make that decision. You don't need the /3GB switch unless you 1. have an application that is compiled /LARGEADDRESSAWARE and needs access to the additional 1GB of virtual address space that /3GB provides (remember that virtual address space has nothing to do with RAM), and 2. don't mind running your system at dangerously low levels of PTEs. You can use the /USERVA switch to modify the range of that 3rd GB of VA to give some of that kernel virtual address space back to the kernel (and thus increase the size of paged pool slightly and get back more PTEs), but you really want to avoid that route unless it's absolutely necessary. Given that you were first asking about doing this on a 2000 Workstation, I'm guessing you really don't need /3GB, and probably don't really need /PAE to get access to the last 512MB or so of RAM on the system. It might make more sense for you to consider XP x64, or better, Vista or Win7 x64 if you really need access to more RAM on a workstation system.

It should - you might want to check and make sure someone isn't using a security filter or WMI filter to apply that policy, which would obvioiusly exclude Win7 clients.

I know many organizations with systems not accessible from any public network that only install service packs, and would only install a non-SP hotfix if there was a critical bug resolved by it that they were running into. Those systems tend to be up for years at a time with no reboot.

To answer the original question though, any service that is set to Manual (that has no dependency that causes it to start anyway) does not load in any way - I suppose it could get cached by the prefetcher and superfetch if it runs regularly, but as to being loaded, no.