Both "MacOSX/Classic builds" AND "Classic Only Builds" are subject to
the same memory limitations. How come the first crash and not the other
if they have the exact same settings ?
Anyway, both are set to a very generous amount so it is not that
(obvious) problem.
My question is:
what could cause one to fail starting and not the other ?
My other question is:
does anybody else used the remote debugger stub on a pure OS 9 system
lately ?
('pure' as in 'not a dual boot system with OSX and OS9', just plain
OS9)
('lately' as in 'with RB2005'...)
Alexandre
Le 05-08-31, à 16:56, Norman Palardy a écrit :
On Aug 31, 2005, at 2:32 PM, Alexandre Ayotte wrote:
Hi,
I run the PEF version of my app (Built as MacOS X/Classic)
and it crash when loading itself (very early) with Error Type 3.
The "Classic only" Build of the same app starts and work just fine...
What would be the cause ?
This is a test machine : I cleaned the disk, installed a fresh OS 9.2
and updated it to 9.2.2
And therefore, there is no traces of OS X on it (like Classic
Support, Classic Support UI, etc.)
Could it be related ??
By the way, the Remote Debugger Stub do the same error on startup.
Can others confirm the problem ?
RS: Can you provide the debugger stub recompiled for Classic only ??
(Remote debugging become essential since there is no more Classic IDE
in RB2005)
Have you adjusted the amount of memory the applications is set to
require ?
I'd star with that in the Get Info box or the REALbasic build setings
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|