Problem with saving standalone
I have a stack I'm working on, which when I want to save as a standalone (for either Mac or Windows) comes up with the message There was an error saving the standalone application. I can't figure out why, since other stacks save easily as standalones. I'm using Mac OS X (Panther). There are about 135 cards in the stack, with only one small graphic and scripting that isn't especially fancy. Can anyone suggest what might be wrong and how I might go about correcting this? Thanks very much. Steve Goldberg ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Problem with saving standalone
On 6/3/05 10:58 AM, [EMAIL PROTECTED] wrote: I have a stack I'm working on, which when I want to save as a standalone (for either Mac or Windows) comes up with the message There was an error saving the standalone application. I can't figure out why, since other stacks save easily as standalones. I've been collecting a list of possible causes. Check these things: 1. The path to the stack contains non-ASCII characters, such as diacritical marks or accent marks. Avoid the use of accented or non-ASCII characters in path names. 2. The standalone builder is set to search for inclusions but the stack is password protected. Select the inclusions manually instead, or remove the password. 3. Alternately, the standalone builder may be having trouble searching for the required inclusions regardless of password protection. Turn off Search for required inclusions and turn on Select inclusions for the standalone application. Then choose the resources you need to include yourself in the Standalone Settings dialog. 4. The folder name is the same as your standalone's name. You need a unique folder name; make sure you select an empty folder with a name different from the standalone's name. If you have previously built a standalone from the same stack, do not try to build a new one into the same folder. Trying to overwrite an existing standalone with a new one can casue problems. Rename or remove the old folder first, and then build. 5. Your source stack's file name does not use an extension, or uses an incorrect extension. Make sure your stack's file name ends with the extension .rev 6. Your source stack contains duplicate message box or ask or answer dialogs. Remove the embedded stacks and let the standalone builder add them instead. (This usually only occurs with stacks originally created in MetaCard.) Make sure you have done Check for updates to be sure you have the most recent version of the standalone settings stack. -- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Problem with saving standalone
Thanks Jacqueline, Your suggestion worked immediately and there was no difficulty saving the standalone as soon as I turned off Search for required inclusions and turned on Select inclusions for the standalone. I'm impressed with the great talent in the forum. Thanks. Steve Goldberg In a message dated 6/3/05 2:31:53 PM, [EMAIL PROTECTED] writes: On 6/3/05 10:58 AM, [EMAIL PROTECTED] wrote: I have a stack I'm working on, which when I want to save as a standalone (for either Mac or Windows) comes up with the message There was an error saving the standalone application. I can't figure out why, since other stacks save easily as standalones. I've been collecting a list of possible causes. Check these things: 1. The path to the stack contains non-ASCII characters, such as diacritical marks or accent marks. Avoid the use of accented or non-ASCII characters in path names. 2. The standalone builder is set to search for inclusions but the stack is password protected. Select the inclusions manually instead, or remove the password. 3. Alternately, the standalone builder may be having trouble searching for the required inclusions regardless of password protection. Turn off Search for required inclusions and turn on Select inclusions for the standalone application. Then choose the resources you need to include yourself in the Standalone Settings dialog. 4. The folder name is the same as your standalone's name. You need a unique folder name; make sure you select an empty folder with a name different from the standalone's name. If you have previously built a standalone from the same stack, do not try to build a new one into the same folder. Trying to overwrite an existing standalone with a new one can casue problems. Rename or remove the old folder first, and then build. 5. Your source stack's file name does not use an extension, or uses an incorrect extension. Make sure your stack's file name ends with the extension .rev 6. Your source stack contains duplicate message box or ask or answer dialogs. Remove the embedded stacks and let the standalone builder add them instead. (This usually only occurs with stacks originally created in MetaCard.) Make sure you have done Check for updates to be sure you have the most recent version of the standalone settings stack. -- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com -- ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
