Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

soi xp txtmode drivers needed iahci and iastor drivers - NO Deployanywhere

Created: 09 Oct 2012 | 9 comments

First lets get this out of the way.  Using deployanywhere is not an option there is a bug in it that prevents me from using it and they are working on a point fxi for me.

Ok I can't figure out why I can't get these drivers into my soi.  Does anyone have any recommendations?

I have tried putting them everywhere modifying the txtsetup.sif file and I can't seem to get these files copied to the drive for use.  I have taken my current soi deployment solution and I can find the drivers if I boot off a CD and look for them after the copy process.  If I do this with Altiris Deployment soi I can't find them ever.

I'm not sure if I'm just all alone in not using deployanywhere but I need a solution that does not involve deployanywhere.

I'm on cms 7.1 sp2 mp1.

Comments 9 CommentsJump to latest comment

andykn101's picture

I think you need to add them to the Mass Storage section of sysprep.inf before you reseal the image. This should put them into the critical drivers database.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

jlawson's picture

Andykn101 -  I'm not using Sysprep.inf (images) as I'm doing SOI(Scripted OS Install) install.

andykn101's picture

You need to edit or use TXTSetup.oem file with the corrrect driver files and edit the MassStorageDrivers and OEMBootFiles sections of unattend.txt, it's a bit fiddly.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

jlawson's picture

My understanding of the txtsetup.oem method and your unattended file is that you can only add one mass storage driver at at time using this method and can't add multiple types of mass storage drivers.  If this is the case it does not resolve the issue for me.  As I need a solution to add multiple types of mass storage drivers to an already built XP ISO.

andykn101's picture

Using CMS you could do a WMI query in WinPE to ascertain the mass storage device and then copy the correct driver and unattend.txt file accordingly.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

ianatkin's picture

I've messed for days trying to get multiple textmode drivers working on scripted installs. The text mode driver addition is particularly tricky and I've never been able to devote enough time on getting this working myself with XP.

My advice is to use NLite to add these drivers -it does the right thing every time. Point it at a local copy of your i386 XP source and whizz through the interface to add the text mode drivers.

http://www.nliteos.com/

Then you can copy your source up, renaming it with a nice path to remind yourself it's been modified. My respect for this tool leapt 10 fold when I realised how neatly it handled these text mode drivers.

Kind Regards,
Ian./

Ian Atkin, IT Services, Oxford University, UK

Connect Etiquette: "Mark as Solution" those posts which assist you most in resolving your problem, and give a thumbs up to useful articles and downloads

jlawson's picture

Nlite is a great utility but it presents a huge problem that I don't believe anyone is aware of.  Or knows how to fix.

 •can we use the tool in the corporate or commercial environment (no, just for personal usage)
 

And there is no way to pay or have the ability to use this tool in a corporate environment.  I'm guessing 98% of all users of this utility are corporate or commercial users but that doesn't make using it ok.

ianatkin's picture

You might note that this is limitation to NLite is not present on the website in any form. This is only visible to the few who actually read the full license agreement on installation when you scroll down the License page.

The reason this exemption is there (as I understand it) is to protect the creator from being sued if it goes tits up for you. It also protects the creator from Microsoft. As an aside, I have not heard of the creator, Nuhi, EVER suing anyone over it's use.

Legalities aside, another approach you could have here is to install this on a personal machine. You could then see what files have been changed (and where) in the source point (NotePad ++ is great for file comparisons) once you add a couple of text-mode drivers. You could then learn from this how to import text mode drivers into your i386 source and apply this methodology to your business environment.

Kind Regards,
Ian./

Ian Atkin, IT Services, Oxford University, UK

Connect Etiquette: "Mark as Solution" those posts which assist you most in resolving your problem, and give a thumbs up to useful articles and downloads

jlawson's picture

Actually that was cut from the website.  I do agree on the sueing deal but I can't tell my employer I'm going to use software that says I can't use it.  This is basically my job on a platter.

As far as adding the drivers I have a decent understanding of this but Altiris appears to work a bit differently.  We use and have been using Remote Installation Services for SOI deployment.  I have added myself all the text mode drivers needed to this build.  Altiris deployment doesn't appear to work though the same way as I can never get these drivers loaded.

Example I put the drivers in i386 folder on RIS then I copy the drivers and same txtsetup.sif file from RIS to Altiris but it does not work.  Altiris never copies the drivers.

I see many have ran into this but I never see an exact workable solution.