Jump to content

traviskater

Member
  • Posts

    3
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by traviskater

  1. That makes sense. The vast majority of our systems are older P2, P3, and P4 systems, with a few hyperthreaded P4's just now coming in, so the ACPI Uni will probably work the best for us. Thank you very much for clarifying it for me! - Travis Kater
  2. Nevermind. I just realized that I'm the one defining what HAL will be used in UpdateUPHAL! Anyway, sorry to have wasted anyone's time. - Travis Kater
  3. I apologize in advance if this is the wrong section, but I wasn't entirely sure if my question would fall under unattended or device drivers. Since it's the Unattended section under Sysprep I have a question on, I though it would be best to put it here. Anyway, I've been researching the use of sysprep to build a single image for use on all of our PC's. As of right now, we have to maintain roughly 20 different images for our various machines. If there were just on image to maintain, workload would be dropped dramatically. One of the issues I've noted in my research is the importance of choosing the correct HAL for the systems to be imaged. Reading through ref.chm in the WindowsXP-KB838080-SP2-DeployTools-ENU.cab, I noted that the entry, "UpdateUPHAL," under Sysprep.inf: Unattended, seems to solve this issue. If I'm reading it correctly, it seems to say that the recently imaged system will detect and then select the correct HAL based upon the processor discovered. If so, then it would seem to solve the many HAL compatibility issues I've been reading about. However, considering the amount of work done on this issue, I sincerely doubt that the resolution of this problem would be this simple, and therefore I was hoping you might be able to give some clarification as to what the actual purpose of this entry is? Thank you very much for any help you can give. - Travis Kater
×
×
  • Create New...