From 0cc541938c040a9a5513d751f1dab004a4b7060f Mon Sep 17 00:00:00 2001 From: ksherlock Date: Mon, 29 Jul 2013 09:49:29 -0700 Subject: [PATCH] Updated Technical Note PT37: Using MPW for Non Macintosh 68000 Systems (markdown) --- ...ical-Note-PT37:-Using-MPW-for-Non-Macintosh-68000-Systems.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Technical-Note-PT37:-Using-MPW-for-Non-Macintosh-68000-Systems.md b/Technical-Note-PT37:-Using-MPW-for-Non-Macintosh-68000-Systems.md index 5cb63f0..6c7a204 100644 --- a/Technical-Note-PT37:-Using-MPW-for-Non-Macintosh-68000-Systems.md +++ b/Technical-Note-PT37:-Using-MPW-for-Non-Macintosh-68000-Systems.md @@ -244,7 +244,7 @@ In the case of C, this initialization is performed by a routine in the file `CRu This is what `_RTInit` does: -1. Call _DataInit(). +1. Call `_DataInit()`. 2. Save the return address back to whomever ran this program. 3. Check to see if launched by MPW. If not, then setup argv and argc to indicate the name of the program with no parameters. 4. If launched under MPW, initialize some things so that the run-time environment will integrate with MPW. 5. Calls the Memory Manager, so make sure that this part of the code is never executed. This is not likely to happen, as `_RTInit` checks and validates several memory locations before it gets this far.