lkeneston

Thanks

I have to ask because i am confused, i currently have an image that works on every system in our ORG, i currently use sysprep and ghost, what could i benefit by using WinPE, seems like that method takes longer as i can have an image on a box in 15 minutes. Thanks, Lee

I loaded the image back on my baseline box, resysprepped it, and it worked, not sure what happened. Thanks all.

I understand that the winnt.sif is basically the same, its just that there is no text mode install in a sysprepped image. I'll try that with the driver, but which i386? The one on the root that i copied from the cd or the one in my sysprep directory Thanks in advance, Lee

I'll try that, but i am not sure that syspep uses txtsetup.sif, winnt.sif am i wrong? Doesn't the .sy_ just mean it is a cab and needs to be extracted?

in my c:\sysprep\i386?

Hello, I am trying to add a Intel® 82801GR/GH SATA AHCI Controller (Desktop ICH7R/DH) to the mass storage options on my sysprep image to add support for a HP XW4400, I copied iaahci.cat, iaahci.inf, iastor.cat, iastor.inf, iastor.sys, and txtsetup.oem to the c:\windows\inf directory, and added [sysprepMassStorage] PCI\VEN_8086&DEV_27C1&CC_0106=c:\windows\inf\iaahci.inf ; Intel® 82801GR/GH SATA AHCI Controller (Desktop ICH7R/DH) PCI\VEN_8086&DEV_27C5&CC_0106=c:\windows\inf\iaahci.inf ; Intel® 82801GBM SATA AHCI Controller (Mobile ICH7M) PCI\VEN_8086&DEV_2652&CC_0106=c:\windows\inf\iaahci.inf ; Intel® 82801FR SATA AHCI Controller (Desktop ICH6R) PCI\VEN_8086&DEV_2653&CC_0106=c:\windows\inf\iaahci.inf ; Intel® 82801FBM SATA AHCI Controller (Mobile ICH6M) PCI\VEN_8086&DEV_27C3&CC_0104=c:\windows\inf\iastor.inf ; Intel® 82801GR/GH SATA RAID Controller (Desktop ICH7R/DH) PCI\VEN_8086&DEV_24DF&CC_0104=c:\windows\inf\iastor.inf ; Intel® 82801ER SATA RAID Controller (Desktop ICH5R) PCI\VEN_8086&DEV_25B0&CC_0104=c:\windows\inf\iastor.inf ; Intel® 6300ESB SATA RAID Controller PCI\VEN_8086&DEV_2652&CC_0104=c:\windows\inf\iastor.inf ; Intel® 82801FR SATA RAID Controller (Desktop ICH6R) My image is still blue screening, any ideas? I know this isn't a hal issue, as i use the Advanced Configuration and Power Interface (ACPI) PC", ACPI PIC HAL (Halacpi.dll) on the base image and use a script to copy the right hal in. any ideas? Thanks in advance. sysprep.txt Not sure why the attachment is comming out that way, i uploaded it twice, I assure you wordwrap is off, and it doesn't look that way in the inf iy you save as and open in notepad it looks fine.

Well it's working now, and i'm tired of working on it right now ;} Your idea seems to be the way to go if i only had 2 different hals, once we get rid of some of the older boxes i'll have that chance i guess. I appreciate the assistance.

Example pickhal.txt HALMACPIb.txt HALMACPIb.reg.txt

I still used the script but bypassed it, but then I changed it again, I created a folder called hals in the system32, then created 2 copies of each hal like this HALACPIa, HALACPIb, a is for desktops, b is for laptops in the script,in each of those directories is the perspective hal files. When you chose a machine before mini setup ends it creates a runonce that runs a batch file on first boot up that manually replaces all the hal files, when it is done it actually asks to reboot, I tried it on 2 separate machines, now that I have those batch files a and b I can add install scripts that can differ from machine or desktop vs. laptop. I work nights tonight but I’ll post the .reg, and bat files to show you.

ok, now i tried the original image i had that hung when i chose the mp hal, i chose nothing and it loaded the Advanced Configuration and Power Interface (ACPI) PC, However, when i went to computer in device manager and clicked roll back, the machine rebooted came up found the mp hal, then rebooted again, all is good as per http://www.msfn.org/board/index.php?act=ST...=70&t=27202 Now the question is can i roll it back from a script? after first reboot?

ok, takes a bit but it boots up, but it uses the hal shows Advanced Configuration and Power Interface (ACPI) PC, It won't auto detect the mp hal

i wanna say i tried that and it hung on boot up, but i can't remember, i'll try again, and let you, thats a good start, Thanks..

If i leave it, the hal used when building is used, which is uni, i guess i could do that then just change the hal after manually, but thats too much for some of our staff.

mini setup completes, i choose the mp hal, then reboot, right into safe mode choices, then i go into safe mode it detects the hal, upon next reboot all is good. heres the code, simple really kernel maybe?? pickhal.txt

Thats what mine was when i built it. HALACPI = uniprocessor right? stickzilla can i add UpdateUPHAL="ACPIAPIC_UP,%WINDIR%\Inf\Hal.inf" UpdateUPHAL="HALACPI,%WINDIR%\Inf\Hal.inf" I need to have support for all 3

This is what i got. sysprep.inf

I believe that i built it on a D810, but like i said it works on the other machines, i have to add a few apps, so i can rebuild it on another machine, maybe the core duo's? So this is a hal issue i assume, i wonder if i do build it on the multi processor machine, then have the scrpt change to back otherwise, like stickzilla said, or just have it auto choose. Can i add multiple entries for UpdateUPHAL= or just the one, I heard there are draw backs from using UpdateUPHAL=

XIMAGE HMM Sounds like your from GE I appreciate the help, i just didn't want to go over it again. Didn't mean to be Krass

mmarable: pay attention, i already said that it works on those machines, so i am switching hals I have a script that places the correct hal and kernal at the end of minisetup, it is in the cmdlines.txt

Hello, I have a Multi platform PC ghost image, currently it works on. Dell GX110, GX150, GX300, GX400 (HALACPI) Dell GX240, GX260, GX270, GX280, GX520, GX620 (HALAACPI) Dell 8000, 8200, 8100, C400, C840, D400, D800 (HALACPI) Dell D410, D810 (HALAACPI) Dell D420, D820 (HALMACPI) and more i would guess, However when i choose the D420 / D820 Windows always comes asking to go in safe mode, once in safe mode the pc will detect the HALMACPI i believe, then when i reboot it works fine. Anyway i could bypass this safemode step, is it possibly that the minisetup cannot write the hal change cause of the sata drivers before boot? or is it just the hal,? Any help would be appreciated.

Maybe a dumb question, but i just need to know, Why not multi-platform ghost image? I am creating a platform solution at work, and it still seems to me that a Why not multi-platform ghost image is quicker then an unattended install, if i am wrong please let me know so i may reevaluate how i do this. We use altiris, so i can push unattended installs and images. Thanks in advance, Lee