Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.msdos.programmer > #1269 > unrolled thread
| Started by | Harry Potter <rose.joseph12@yahoo.com> |
|---|---|
| First post | 2014-01-31 10:38 -0800 |
| Last post | 2014-02-12 17:39 +0100 |
| Articles | 4 — 3 participants |
Back to article view | Back to comp.os.msdos.programmer
DOS memory model confusion... Harry Potter <rose.joseph12@yahoo.com> - 2014-01-31 10:38 -0800
Re: DOS memory model confusion... pete@nospam.demon.co.uk - 2014-02-01 07:39 +0000
Re: DOS memory model confusion... Harry Potter <rose.joseph12@yahoo.com> - 2014-02-03 06:42 -0800
Re: DOS memory model confusion... "Gisle Vanem" <gvanem@yahoo.no> - 2014-02-12 17:39 +0100
| From | Harry Potter <rose.joseph12@yahoo.com> |
|---|---|
| Date | 2014-01-31 10:38 -0800 |
| Subject | DOS memory model confusion... |
| Message-ID | <d8aa40e0-2e77-4226-9a17-c5b301fd5e00@googlegroups.com> |
I'm sorry for the stupid question :( but I know what the tiny, compact, large and huge DOS memory models look like but not the small and medium. Which has one code and multiple data segments, and which has one data and multiple code segments? Also, how do I handle memory segments and models in the Turbo C++ 3.0 and Open Watcom 1.9 C compilers?
[toc] | [next] | [standalone]
| From | pete@nospam.demon.co.uk |
|---|---|
| Date | 2014-02-01 07:39 +0000 |
| Message-ID | <1391240391snz@nospam.demon.co.uk> |
| In reply to | #1269 |
On 31st Jan 2014 at 10:38 "Harry Potter" <rose.joseph12@yahoo.com> wrote: > I'm sorry for the stupid question :( but I know what the tiny, compact, large > and huge DOS memory models look like but not the small and medium. Which has > one code and multiple data segments, and which has one data and multiple code > segments? Tiny: code, data, stack etc. all in 1 segment (so max prog size 64K) Small: 1 code segment, 1 data segment (usually the default?) Compact: 1 code seg, multiple data segs (small code, large data) Medium: multiple code segs, 1 data seg (large code, small data) Large: multiple code and data segs, max single object/array 64K Huge: like large but with single object size restriction lifted > Also, how do I handle memory segments and models in the Turbo C++ 3.0 and Open > Watcom 1.9 C compilers? Read the doc! Probably specifying -ms, -mc, -ml etc. on the command line. Pete -- Believe those who are seeking the truth. Doubt those who find it. - André Gide
[toc] | [prev] | [next] | [standalone]
| From | Harry Potter <rose.joseph12@yahoo.com> |
|---|---|
| Date | 2014-02-03 06:42 -0800 |
| Message-ID | <6bb641e3-efb0-4b91-9acc-089f60a52f80@googlegroups.com> |
| In reply to | #1271 |
On Saturday, February 1, 2014 2:39:51 AM UTC-5, pe...@nospam.demon.co.uk wrote: > Tiny: code, data, stack etc. all in 1 segment (so max prog size 64K) > Small: 1 code segment, 1 data segment (usually the default?) > Compact: 1 code seg, multiple data segs (small code, large data) > Medium: multiple code segs, 1 data seg (large code, small data) > Large: multiple code and data segs, max single object/array 64K > Huge: like large but with single object size restriction lifted > Thank you!
[toc] | [prev] | [next] | [standalone]
| From | "Gisle Vanem" <gvanem@yahoo.no> |
|---|---|
| Date | 2014-02-12 17:39 +0100 |
| Message-ID | <ldg83c$fmb$1@dont-email.me> |
| In reply to | #1271 |
<pete@nospam.demon.co.uk> wrote: ... > Large: multiple code and data segs, max single object/array 64K > Huge: like large but with single object size restriction lifted And 'unreal mode' was once popular too. Ref: http://en.wikipedia.org/wiki/Unreal_mode --gv
[toc] | [prev] | [standalone]
Back to top | Article view | comp.os.msdos.programmer
csiph-web