what does this limit imply? does it mean i can write 60300 bytes of source code(about 1000+ lines i think), or that the translated binary instructions at 60300 bytes long, or i can store 60300 bytes of data?
that sounds really limited in contrast to 640kb conventional memory.
Where do you see that message?
YouTube channel: https://www.youtube.com/channel/UC7HbC_nq8t1S9l7qGYL0mTA
Collection: http://www.digiloguemuseum.com/index.html
Emulator: https://sites.google.com/site/capex86/
Raytracer: https://sites.google.com/site/opaqueraytracer/
wrote:what does this limit imply? does it mean i can write 60300 bytes of source code(about 1000+ lines i think), or that the translated binary instructions at 60300 bytes long, or i can store 60300 bytes of data?
It's for the tokenized binary representation of your code, plus data. There are things like (IIRC) string space and communication buffers that can be adjusted from the command line if you check the manual.
As mentioned above, you only get a single segment. You can always (ab)use DEF SEG to save/load data in other segments, but that's probably not a good idea unless you know what you're doing.
64K might look limited, but most other machines which ran old-school MS BASIC dialects tended to have even less RAM free for programs.
i found that ibm bascom1.0(ms bascom 5.xx) compiled binaries can only use <64kb of ram aswell.
qbasic can use <192kb(arrays<160kb, strings<32kb) of ram.
quickbasic interpreter mode can use <384kb(arrays<320kb, strings<64kb) of ram.
ibm bascom2.0(ms bascom6.0) and quickbasic compiled binaries can use almost all available conventional ram, although strings are still limited to <64kb.
wrote:It's for the tokenized binary representation of your code, plus data. There are things like (IIRC) string space and communicati […]
wrote:what does this limit imply? does it mean i can write 60300 bytes of source code(about 1000+ lines i think), or that the translated binary instructions at 60300 bytes long, or i can store 60300 bytes of data?
It's for the tokenized binary representation of your code, plus data. There are things like (IIRC) string space and communication buffers that can be adjusted from the command line if you check the manual.
As mentioned above, you only get a single segment. You can always (ab)use DEF SEG to save/load data in other segments, but that's probably not a good idea unless you know what you're doing.64K might look limited, but most other machines which ran old-school MS BASIC dialects tended to have even less RAM free for programs.
String space is included in that 60300 bytes.
I never thought of using DEF SEG that way.
"old-school" is misleading. It is 8-bit systems that had this limitation, because the operating system and BASIC had to load into the total 64K address space. A typical value under CP/M was about 29K.
Sincerely,
Gene Wirchenko
