xp sysprep hanging at agpcpq.sys

[Bournym]

I have a single image supporting all my corperate hardware (laptops and desktops) This is simply a sysprepped image with all my drivers and software install routines. I have started to come up against issues dropping this onto newer hardware with what I beleive to be different SATA ahci controllers. My current image when dropped onto a toshiba sattelite pro L450 hangs at the agpcpq.sys.

I have attempted to overcome this by adding more sata controllers (Intel Matrix) drivers into my massstorage section od the sysprep inf file but to no success. I have researched the issue and it appears I could be also looking at a HAL issue. I have added support for all HAL types and my reference build is based on ACPI machine. I have dropped this image onto other multi core machines with success so I am starting to doubt this is a HAL issue although some forums suggest this is the next file to load after agpcpq.sys.

I also tried installing XP SP3 CD on the laprtop and this will not even get thru the initial blue setup screen without blue screening. The only thing I have is the Toshiba XP downgrade CD that works fine and I cannot figure out how. I have extracted the drivers from the bundled recovery build for my image and this does not help. I have tried dropping an SP3 test build on and this hangs at the same place,

I need help understanding what is causing the issue and what I can extract fromt the working toshiba XP build to get my single image working with this laptop.

[allen2]

It seems to me like a problem with sata ahci controler drivers not inclued in your image.

[Tripredacus]

What is the STOP error you get when installing with the CD?

I'd recommend you use different images for XP per hardware config, especially in a corporate environment.

[Bournym]

What is the STOP error you get when installing with the CD?

I'd recommend you use different images for XP per hardware config, especially in a corporate environment.

The stop error was not consistent from the XP CD. Your suggestion unfortunatly of creating an image for each different peice of hardware would take me back 5 years of development . I currently have 1 single image supporting 12 different laptops from various manufacturers and over 20 desktop models. Your suggestion would mean I would be supporting nearly 30 different images instead of one. In a corporate environment this is resource suicide for someone managing images. Microsoft do not support what I am doing but when you push Sysprep to do more than what it is written it is supporteed to do it copes fine and works brilliantly (tempremental that it is).

My single image simply needs the correct things added to make it work with the current release machines with more advanced hardware specs such as SATA controller drivers. I have found it increasingly challanging getting the latest hardware built for windows 7 with XP backward compatibility to work on my single image due to controller driver issues.

I have recently added in all the latest intex matrix controller drivers into my Mass storage section and also added in the ones for this model of laptop but I am either doing something wrong or I have the wrong drivers or it not the controller drivers and something else I am missing. I firmly beleive I can get this laptop working on my single image as I have similar spec hardware working fine even AMD as well as Intel hardware (I am proud of that achivement)

Allen2: I agree with your suggestions that I need to add the sata controller driver. How sure are you this is the issue as I have added what I beleive to be the controller into the mass storage but it still does not work. There is suggestions in some forums that the AGPCPQ driver has loaded and its the next driver to load which has the issue which is the HAl. My gut tells me its not the Hal as I have all the hals loaded on my image and my reference build is the correct Hal for maximum hit success on target hardware. I still beleive this is a controller issue but before I pour weeks of resouce down the drain I would like to air this problem to see what everyones opinions are on what this could be.

Hope you can all help me. I am not far away form working on windows 7 images for my corporation and the last thing I need is to create another XP image when my single image does the lot already apart from this one laptop.

[Tripredacus]

What is the STOP error you get when installing with the CD?

I'd recommend you use different images for XP per hardware config, especially in a corporate environment.

The stop error was not consistent from the XP CD. Your suggestion unfortunatly of creating an image for each different peice of hardware would take me back 5 years of development . I currently have 1 single image supporting 12 different laptops from various manufacturers and over 20 desktop models. Your suggestion would mean I would be supporting nearly 30 different images instead of one. In a corporate environment this is resource suicide for someone managing images.

I guess it depends on how you approach it. I currently manage well over 200 XP images without a problem. Its up to you in the end how you want to do it, If Windows 7 comes out for you soon, I agree going back and redoing your XP work will be a waste of time.

[allen2]

Does it crash blue screen when you boot the image on the Toshiba L450 (i suppose it is, if it didn't, you wouldn't have posted here for help) ?

If yes, what is the stop error ?

[Bournym]

Does it crash blue screen when you boot the image on the Toshiba L450 (i suppose it is, if it didn't, you wouldn't have posted here for help) ?

If yes, what is the stop error ?

I would not get hung up on the stop error - this was my attempt of creating a second build to resolve my current deployment of 100 laptops with an adhoc build. I have since managed to get a sp1 multivolume copy of XP installed and updated so I have my adhoc build for this deployment. My issue I would like tyo concentrate on this article is the reason why I am getting stuckk at the loading of the drivers on XP after sysprep at AGPCPQ.sys and the theories around why this happens and what drivers I need to overcome it with sysprep. I still think this is a SATA controller driver in XP sysprep I am missing but looking to explore any other possibilities.

Tripredacus : Thanks for your reply. It does depent on the scenario to how you adopt imaging but I would not be able to sleep at night if I had over 200 XP images when deployment consolidation tools such as sysprep can bring this down to 1-3 images or in my case with the addition of Autoit scripting for job roles down to 1 single image. I am looking again at the latest intel matrix drivers to see if I am missing any.

Any other ideas apart from intel matrix welcome if you think my issue is not matrix storate / sata / ahci driver related.

[Tripredacus]

Tripredacus : Thanks for your reply. It does depent on the scenario to how you adopt imaging but I would not be able to sleep at night if I had over 200 XP images when deployment consolidation tools such as sysprep can bring this down to 1-3 images or in my case with the addition of Autoit scripting for job roles down to 1 single image. I am looking again at the latest intel matrix drivers to see if I am missing any.

Yes well we went this way because of learning the hard way. Part of it is because of left-over imaging policies when there were multiple HALs and non-ACPI compliant hardware. The real deal breaker for us was when HP blew up a bunch of their Intel chipset machines by using a single image that would write in an AMD file and blow up Windows after certain updates were ran. We decided to play it safe and not want to end up with that kind of support nightmare! All it meant for me was that I ended up taking on new responsibilities and end up from a worker type position to a management type position.

[svermaak]

Did you manage to find a solution? Exact same issue...