Originally posted by: Smilin
Disabling intelppm.sys on an AMD machine will not cause any problems for you down the road.
However, the reason that you need to at all is a sign of something more troubling. Your hardware is not being redetected since this is an inbox driver for intel processors.
That's a good point; I assume that they've missed something during the image creation, as they've only ever worked with Intel before, and would have done what is necessary to get the image to work, not necessarily planning ahead... :roll:
Important:
Could we get some more details about how they are imaging? Are they using Ghost/sysprep, RIS/Riprep, ADS, what? Taking the wrong shortcut somewhere can give you the appearance that your imaging process is all fine and dandy when you can have serious enterprise wide problems later on.
AFAIK, it's Ghost and Sysprep, with some modifications made. For example, when they managed to get the machine booting, the regular "Loading your personal settings" dialogue box had a large amount of text going past, and the process took around fifteen minutes, with the network going flat-out the entire time. I assume this is Intellimirror / MSI package deployment on first boot?
Common pitfall that admins run into:
A single image is sometimes not a realistic goal. You CANNOT jump hals. You might be able to pound a square peg in a round hole once to get things to work but if you try and use a single image on multiple hals you ARE going to have problems. Desktops and Laptops often have different Hals for instance.
True. We have tried to gently poke them into making two images, but apparently it's "not an option", and we're inclined to try and get the single image working, because that means they can go with AMD & Intel hardware. If not, then they'll have to settle for Intel only, which means they'll probably choose Dell over us.
Take one of your intel machines, run normal windows setup on it. Goto device manager and see what kind of hal is listed under the PC. Now do the same thing for one of your AMD boxes (no shortcuts or images!! must let windows setup run!) Compare the two hals. If they are the same then the long story made short is you'll be able to get it to work. If not, make two images.
On first glance, it seems that the HALs aren't the problem, as the machine will boot into Safe Mode without any trouble, and the same image works across a range of chipsets, from 845, 865, 915 to 855 and 915 mobile stuff. I could be wrong, however. I'll ask them to get a virgin copy of XP on both platforms and compare the HALs.
edit: added the extra italics/bold/underline. Your "guys who really know what they are doing" are doing something very wrong. Please reply with some details about the process they are using.
I agree. It's entirely possible that they've ballsed-up the hardware detection stuff, but they absolutely wouldn't let me take a copy of their image to play with; I assume that their admin passwords would be stored on it somewhere, and they don't really want "just anyone" peeking into their network setup in depth.
Facebook
Twitter