Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!cbosgd!ihnp4!cuae2!ltuxa!we53!sw013b!dj3b1!killer!tad
From: tad@killer.UUCP (Tad Marko)
Newsgroups: net.emacs,net.micro.pc,net.micro
Subject: MicroEMACS and MS C
Message-ID: <243@killer.UUCP>
Date: Thu, 7-Aug-86 00:24:37 EDT
Article-I.D.: killer.243
Posted: Thu Aug  7 00:24:37 1986
Date-Received: Sat, 9-Aug-86 10:40:30 EDT
Organization: The Unix(tm) Connection BBS, Dallas, Tx
Lines: 36
Keywords: Obscure MS C feature (?)
Xref: watmath net.emacs:2177 net.micro.pc:9536 net.micro:15302

[if you have seen this before, it is because I am reposting it
due to some trouble with a major feed upstream from me.]

A while back, there was a discussion about the standard memory
models offered by Microsoft C, and how none of them were really
right (ie. no small code, large data model).  Well, quite 
accidentally, I stumbled across section 7.11.2 of the MSC User's
Guide, and found the section called "Creating Customized
Memory Models", and said, "Hey, I bet this could be what we all
need!".

I'm not an expert at diddling with these type of things (yet),
but I think the following switch is appropriate:

-Asfd

the s is for short code pointers, the f for far data pointers, and
the d I'm not real sure about.  The manual says that all the
memory models use d as a default which is stack segment equal
to data segment.  The other options are u, for separate DS and SS,
which I think is inappropriate, and w, for a separate SS, but no
fixed DS, which I'm *sure* is not appropriate.

BTW:  Section 7.11.2 is on page 151.

					Tad

P.S.:	There was a problem for a week with a feed somewhere
	downstream from ihnp4, and I think that a *LOT* of 
	people would benefit from a reposting of MicroEMACS
	3.7. (including me!)
--
Tad Marko
..!ihnp4!killer!tad		||	..!ihnp4!alamo!infoswx!ntvax!tad
UNIX Connection BBS AT&T 3B2		North Texas State U. VAX 11/780
If it's not nailed down, it's mine; If I can pick it up, it's not nailed down.