🚀 go-pugleaf

[This followup was posted to fido.novell and a copy was sent to the cited 
author.]

In article <37F0BF44.D27F0C61@interaccess.nl>, oscarm@interaccess.nl 
says...
> 
> 
> tduis wrote:
> 
> > hi there,
> >
> 
> Hi twan.
> 
> >
> >
> > Now i need a connection of these 3 application object for a group and i want
> > to be in controle of the installation order these app come to the
> > workstation (win95 ORS 2.5 and NW Client 3.1).
> >
> > Tried it with forced run on the group, but no control over the installation
> > order.
> 
> Off course you have. the applications are stored in the nds, and are searched
> down from the root. The app that is as highest in the tree defined should run as
> first one whenever using forced run.
> 
> As far as I can remember playing around with the position in the tree of the app
> should manipulate the load order.
> 
> regards,
> ___________________________
> Oscar Muntenaar
> System Engineer
> ___________________________
> INTER ACCESS
> Tel: +31 35 6888 400
> fax: +31 35 6888 552
> ___________________________
> mail: oscarm@interaccess.nl
> http://www.interaccess.nl
> ___________________________
> 
> 
> 
You can order the application push by the description field of the 
Application object.

Ex: Office97sr2a, IE5

If the above two application objects had the above descriptions, IE5 
would distribute first then Office97SR2a would push.  By the description 
I mean the physical description of the object in the application object 
property field within NWadmin.  You can also use logic in cmd or bat 
files to do some of the same stuff.  Main object runs a cmd file that is 
forced run / distribute always that checks for the existence of tag 
files.  If they are not there, it runs the first object by using nal.exe 
/a=.application.context approach.  Once all tag files are present (pushed 
down by each object that is installed) you can either turn off the force 
run or leave it on just in case someone gets a new machine.

Good luck

Jim Britt
NT Integration / NAL Engineer.