(I have more than once sent Scott the wrong crash data!
Embarrassing!)
tereza
Would that qualify as sending him on a wild bug chase?
;-)
--
--Shareware Games for the Mac--
http://www.gypsyware.com
___
metacard mailing list
[EMAIL PROTECTED]
I forgot to add that this error only occurs when the stack is a
stack. When I turn it into a standalone, the error seems to go away.
Hence the conclusion that there is a conflict between a script of
mine and a script of Metacard, where the Metacard script does not
exist in the standalone.
On Friday, May 30, 2003, at 08:19 AM, Shari wrote:
I forgot to add that this error only occurs when the stack is a stack.
When I turn it into a standalone, the error seems to go away. Hence
the conclusion that there is a conflict between a script of mine and a
script of Metacard, where the
On Fri, 2003-05-30 at 19:29, Mark Talluto wrote:
On Friday, May 30, 2003, at 08:19 AM, Shari wrote:
I forgot to add that this error only occurs when the stack is a stack.
When I turn it into a standalone, the error seems to go away. Hence
the conclusion that there is a conflict between
Have you tried:
1. A fresh install of MC
2. Running with extensions turned off
3. Testing it in another OS and/or another computer
4. Running Macbus and getting a stdlog file
Best regards,
Mark Talluto
Metacard itself does not run on my computer with extensions off. I
am about to compile it
It's probably a way to
get the sames infos under Jaguar but i did'nt test this for yet.
Bests, Pierre
So far the only thing I've done with the console window in Jaguar is
to meet Eliza, the psycho-analyst. My fella horned in on the
conversation, and he taught Eliza words she never heard of
on 05.30.03 8:07 PM, Shari wrote:
Does anyone know how to pull errors out of the console/terminal
window in Jaguar (whatever the divil that DOS like thang is called...)
Open the console application and check Eenable crash reporting and
Automatically display crash logs in the preferences.
