1

(10 replies, posted in Other)

Bashrat - just noticed that AutoImage kicks of the DriverPack integration in 'API mode' - is there any documentation on this, a it sounds like what I was after?

Thanks, Nick

2

(10 replies, posted in Other)

Thanks again - it looks like AutoImage might be the best answer - not seen it before, so thanks for the introduction.

Nick

3

(10 replies, posted in Other)

Siginet - thanks for the link...I'm releived I'm not being completely thick!

I do use RVM already, but also nLite, and I was under the impression that DriverPacks were best done after nLite, and RVM before nLite?

Do you know how RVM achieves the automation of DPS_Base.exe - I've tried adding the /settings:"x:\..." to dps_base.exe and all that does is copy a custom .ini file over to the dps_base.ini (doesn't copy it back if you make any changes though!) - it doesn't start the slipstreaming process automatically. Are there any other command line options?

With the old style DriverPacks, I was able to achieve automation by modifying the run_me.cmd so it didn't prompt for the method or KTD answers

Bashrat - it would be really nice to have this feature back.

Thanks, Nick

4

(10 replies, posted in Other)

Please forgive me if I'm being completely stupid, but I've searched quite extensively on these forums and elsewhere, but not found the answer to my question yet...

Is it possible to run the DriverPack integration process non-interactively? I'd like to be able to pass a customised dps_base.ini file to the .exe and have it run the complete integration process automatically?

Thanks, Nick