Michael De Groote wrote: > uhm... that would apply in case of a blank installed system (which i > sometimes do on a dual-boot machine, where i install the basic windows > install and then use the this approach, the reason for this i'll explain > another time) > > I case of a system that already has some applications, the approach of > running postinst.bat is not the thing you want to do i think... > > what i do in that case is > A) see if any of the profiles that i have defined matches what i want to > install, if yes => mapznrun z:\bintodo.pl z:\scripts\< profile.bat> + > z:\bin\todo.pl --go > B) if not, use mapznrun once, then do z:\bin\todo.pl <app.bat> for each > app to be installed, then finally issue z:\bin'\todo.pl --go > > i suppose the appsonly script is doing the latter, but with some extra > stuff to make it more robust... > > Michael >
Hi Michael, your assumption is perfectly right. The appsonly script will create the c:\netinst and c:\netinst\logs and then invoke todo.pl for every package the user wants to be installed. It is intended for PCs that already have an installed OS. Basically it works like the procedure described here http://www.mail-archive.com/[EMAIL PROTECTED]/msg01245.html but in am more convenient way (user selects applications in a multiple choice dialog like he does when doing an OS + apps deployment). I have a demo screen capture here that shows it in a VMware: http://www.badongo.com/vid/596403 Regards Gerhard ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ unattended-devel mailing list unattended-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-devel
