-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
NO!!
I just backtracked to an older version of my stack (from a backup) and
tried with that, and it worked!
It looks like my stack file became corrupt somewhere down the line. I
guess I need to start going back through backups until I find the
Frank D. Engel, Jr. skrev:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Okay, I'm getting the infamous There was an error while saving the
standalone application message for just one specific stack.
* I checked to ensure that the stack had a .rev extension, it does.
* I tried saving to a new
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm not using MetaCard (I don't have a license for that, and have never
even tried it), and I never did anything to add a nonempty resource
fork to my stack (technically, all files on an HFS filesystem have a
resource fork, but they are typically
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I never use the single-byte , = or = versions in any of my scripts.
I just checked the only other script I may have added from an outside
source since this last worked, and they are clean.
I tried suppress messages and save standalone, no good.
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Okay, I'm getting the infamous There was an error while saving the
standalone application message for just one specific stack.
* I checked to ensure that the stack had a .rev extension, it does.
* I tried saving to a new empty folder on my desktop.
On 5/3/05 10:14 AM, Frank D. Engel, Jr. wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Okay, I'm getting the infamous There was an error while saving the
standalone application message for just one specific stack.
* I checked to ensure that the stack had a .rev extension, it does.
* I
Frank,
I'm a very new user and I'm not sure my help would be that valuable but I've
struggled with the identical problem and here's what I discovered...
- Someone, somewhere suggested to change the preferences in the Standalone
Application Settings to NOT search for required inclusions when
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There are no non-ASCII characters in the filename.
The standalone app settings are definitely set to allow me to specify
the inclusions myself rather than having them searched for.
I am building for both OS X and Windows; no Classic Mac or UNIX/Linux
Frank,
Have you tried to enable *all* of the libraries, even the ones you're sure
you don't need... that's what I'd do
Var
On 5/3/05 1:27 PM, Frank D. Engel, Jr. [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There are no non-ASCII characters in the filename.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Okay, just tried that. Same problem.
On May 3, 2005, at 5:05 PM, Varen Swaab wrote:
Frank,
Have you tried to enable *all* of the libraries, even the ones you're
sure
you don't need... that's what I'd do
Var
On 5/3/05 1:27 PM, Frank D. Engel, Jr.
I would add only 2 things to your list, which I expect you have done,
but just to have a complete list in the archives:
* don't use any weird characters in file, folder or app names
* specify inclusions instead of asking Rev to search
Sarah
On 4 May 2005, at 1:15 AM, Frank D. Engel, Jr. wrote:
Frank,
Also, have you tried to create an entirely new mainstack, add a button or
two and save that as a standalone? It'd be interesting to see if that
works..
One other thought is to disable saving to either/or the Mac and Windows
flavors, just do one at a time.
Var
On 5/3/05 3:10 PM, Sarah
On 5/3/05 3:27 PM, Frank D. Engel, Jr. wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There are no non-ASCII characters in the filename.
The standalone app settings are definitely set to allow me to specify
the inclusions myself rather than having them searched for.
I am building for both
Okay, I'm getting the infamous There was an error while saving the
standalone application message for just one specific stack.
* I checked to ensure that the stack had a .rev extension, it does.
* I tried saving to a new empty folder on my desktop. Nope.
* I tried saving to my home directory.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Both are already covered ;-)
On May 3, 2005, at 6:10 PM, Sarah Reichelt wrote:
I would add only 2 things to your list, which I expect you have done,
but just to have a complete list in the archives:
* don't use any weird characters in file, folder or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have several other stacks already which are working fine. It's the
biggest, most important one which is causing all the problems. Just
this one specific stack.
Doing one at a time sounds good, didn't try that yet. I'll try that
first thing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The passwords are added to the final stack by Standalone Builder. My
source stacks are not password protected.
This worked fine until recently. I think the last time I built this
stack as a standalone was under 10.3.8, and I've just upgraded to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Okay, so I did try it tonight...
Either way (OS X only or Win32 only) still gives the error.
On May 3, 2005, at 8:06 PM, Frank D. Engel, Jr. wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have several other stacks already which are working
Hi Frank,
Here are a couple of other suggestions.
1) If you're using a Mac, make sure = is two characters not one.
2) Try commenting out all preOpenStack/preOpenCard openStack/openCard
handlers and then build the standalone. If it works, then you can assume
you're doing something in the handlers
19 matches
Mail list logo
