2 Intern

 • 

2.4K Posts

December 20th, 2006 20:00

Just take the contents of the 2KXP_INF folder and let Sysprep install it
 
Or use setup.exe /S

22 Posts

December 20th, 2006 21:00

Thanks for the suggestions. The /S option functions the same as /K - I still get the reboot prompt. As for the sysprep, I don't put anything in the i386 folder. I use 1 image for about 10 different Dell and HP models and then simply add all the different driver installs to my Altiris job after System Setup is done. This always works great but for whatever reason ATI just doesn't provide install flags like other drivers. I've opened a call with ATI so I guess I'll see what they say.

2 Intern

 • 

2.4K Posts

December 20th, 2006 23:00

reprogram the ISS file
 
setup.exe /R specify no reboot and then use the new SETUP.ISS file (found in c:\windows)
 
you need to do it on a clean machine because it will run through the install to get the ISS file

22 Posts

December 21st, 2006 12:00

I've already tried that too.  More as a gripe but I wish Dell would require vendors to provide a full range of install flags or switches.  I realize this wouldn't be a benefit to the majority of Dell's customers so it will never happen but it's nice to wish for it.  I'm still waiting to hear from ATI.  Hopefully they will have something.  Thanks for your suggestions Hydralisk00222.

2 Intern

 • 

2.4K Posts

December 23rd, 2006 20:00

that's kinda worrying, i do that to plenty of other installshield programs and they all work with that

22 Posts

December 27th, 2006 12:00

Hydralisk00222,
 
Check this out.  Below is my question to ATI and the response below that.
 
Q:  Is there someplace where I can get a list of the install flags or switches that are available to install the drivers for an ATI X1300PRO? Currently, I'm using the /k switch after setup.exe but I get prompted to answer yes or no to reboot. I would like the entire install to be completely silent and reboot automatically.
 
A:  No i'm sorry we don't have anything like that.  I checked with senior technical support.  Perhaps Installshield has one?
Sure, blame it on Installshield.  That's like blaming the hammer for pounding in the nail crooked.  In this case, ATI is the one holding the hammer.  I kind of had to laugh.  Anyway, if I come across anything, I'll let you know.

22 Posts

December 28th, 2006 15:00

Problem solved. I should have thought of this sooner. Instead of using the main .exe file, I split out the separate .exe and .msi files and run them all separately instead. It's a little more involved but it works. Sometimes I have to remember to think outside the box.
No Events found!

Top