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 a script of mine and a > > script of Metacard, where the Metacard script does not exist in the > > standalone. > > > > I'm guessing that it could lie in Metacard's frontscript/backscript, > > as called from the Metacard Menu Bar, but this is just a guess. > > > > Shari C > > -- > > > > > 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 > http://www.canelasoftware.com > > _______________________________________________ > metacard mailing list > [EMAIL PROTECTED] > http://lists.runrev.com/mailman/listinfo/metacard >
Hi Shari, Under Linux, all the mc-engine executions errors are directly provided to the stdout console output and you can watch at them in opening the system logs or a virtual console-mode terminal. It's probably a way to get the sames infos under Jaguar but i did'nt test this for yet. Bests, Pierre _______________________________________________ metacard mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/metacard