Thanks, I did not know that I need to type in the command manually. I thought after selecting the file in the box above it is sufficient. It is working now.

Hi, I habe done exactly what you are suggesting and it does not work in my case. Attached is the project file. Regards, Steffen

Hi,

After looking into your mspproj file, i observed that the install command was missing.You had just browsed the file but did not add the command

I have attached the screen shot which explains you where to add a command

I am also attaching the modified mspproj file that contains the install command. With this you will be able to successfully generate an APF

Thanks & Regards, Avinash

I tried to use it, but I get an error message: APF File Failed to generate. What shall I do with this message - not telling me any reason for the failure or at least a hint.

Hi,

The error could be caused because of associating a file without providing an install command. In your case I suspect you’re doing the same for StartUpLdr.exe

If that is the case, Please follow the steps below

1. Add all the files which are required using general template

2. Navigate to commands section of package builder

3. Click on "Add New command" button

4. In the command section enter the install command

For ex: for startUPldr.exe you need to provide the command as

\Temp\StartUpLdr.exe

5. Generate an APF and it should be successful

If this does not solve the issue please attach the project file (*.mspproj) for debugging purpose

Thanks & Regards, Avinash

Is this version of the builder the same as the one that is integrated into MSP? Or are these completely different with different functions?

Andy - I've only played around with this for a few hours but I'm really impressed with the look and usability so far. Go ahead and pass  I just wanted to check on what documentation will be made available once this goes through the full supportcentral web positing process. If there's already a reference guide can you make it available here? Specifically I'd like a document outlining what looks to be newly available templates for adding files (e.g - Persistent CAB Install 2).

We're undecided about replacing the OS Update package builder at this time.  OSUPPB contains components from other organizations within Motorola that are not supported.  So that's why OSUPPB has never been a released product but is in permanent beta. 

Thanks for the post!  So moving forward we will still provide a standalone package builder, it's just the "airbeam" package builder is what has gone EOL.

Thats correct John

Will there be an O/S Update package builder that will be based on this version of Package Builder?