GW-BASIC tokenized file - Revision history

Sembiance: /* Sample files */

2024-05-06T01:41:09Z

‎Sample files

Dan Tobias at 03:26, 22 May 2020

2020-05-22T03:26:01Z

Dan Tobias at 03:25, 22 May 2020

2020-05-22T03:25:25Z

Dan Tobias: /* Other links and references */

2020-05-22T01:57:31Z

‎Other links and references

Dan Tobias at 02:42, 16 March 2019

2019-03-16T02:42:05Z

John e at 23:15, 26 August 2014

2014-08-26T23:15:37Z

Jsummers: Sample files

2014-02-07T02:14:23Z

Sample files

Dan Tobias at 17:04, 16 February 2013

2013-02-16T17:04:58Z

Dan Tobias: /* Tokens */

2013-01-24T02:18:18Z

‎Tokens

Dan Tobias at 15:43, 6 January 2013

2013-01-06T15:43:27Z

Show changes

@@ Line 492: / Line 492: @@
 == Sample files ==
 * Many files on [http://cd.textfiles.com/bthevhell/ Between Heaven and Hell Version II CD], such as [http://cd.textfiles.com/bthevhell/200/104/ /200/104/*.bas]
 == Software ==

@@ Line 10: / Line 10: @@
 Like most BASICs of its era, BASIC/BASICA/GW-BASIC used a tokenized format to save its programs, rather than plain-text source code. Printable ASCII characters (space through tilde) generally stood for themselves (except when part of a multi-byte sequence), but other bytes had different meanings. The "high-bit" bytes from #128-#255 stood for the various BASIC commands (some as single bytes, others as part of two-byte sequences), while some of the control characters had special meanings including signifying the start of a binary-encoded sequence encapsulating a numeric constant. A null (#0) byte marked the end of a program line, and some header bytes were used at the start of the line to encode the line number and some byte offsets: specifically, two bytes containing the offset of the next line as a [[Endianness|little-endian]] integer and two bytes containing the line number as a little-endian integer.
-Files saved to disk are preceded by a single byte to indicate if the program was protected: 0FEh if protected, 0FFh if not. Files saved to [[IBM PC data cassette|cassette tape]] omit this byte, because byte 9 of the cassette header holds the protection status.
+Files saved to disk are preceded by a single byte to indicate if the program was protected: 0FEh if protected, 0FFh if not. Files saved to [[IBM PC data cassette|cassette tape]] omit this byte, because byte 9 of the cassette header holds the protection status. The file was terminated with Ctrl-Z (1A hex).
 == Tokens ==

@@ Line 8: / Line 8: @@
 '''GW-BASIC tokenized files''' stored programs in the version of the [[BASIC]] programming language used on IBM PC compatibles in the days when interpreted BASIC was regularly included on personal computers as shipped from the factory. Originally the IBM PC had versions of BASIC called BASIC and BASICA, the latter being an "advanced" BASIC with a few more features. Part of it was in ROM, and part was loaded from disk. Other manufacturers' PC compatibles (or "clones") didn't have the ROM BASIC, but used a BASIC from Microsoft which was compatible to it, and went by a few manufacturer-specific names but was generically known as GW-BASIC (with varying claims existing about what the GW stands for, either the initials of a Microsoft employee (Greg Whitten) involved in adapting it from Bill Gates' original CP/M BASIC, or possibly for "Gee Whiz").
-Like most BASICs of its era, BASIC/BASICA/GW-BASIC used a tokenized format to save its programs, rather than plain-text source code. Printable ASCII characters (space through tilde) generally stood for themselves (except when part of a multi-byte sequence), but other bytes had different meanings. The "high-bit" bytes from #128-#255 stood for the various BASIC commands (some as single bytes, others as part of two-byte sequences), while some of the control characters had special meanings including signifying the start of a binary-encoded sequence encapsulating a numeric constant. A null (#0) byte marked the end of a program line, and some header bytes were used at the start of the line to encode the line number and some byte offsets.
+Like most BASICs of its era, BASIC/BASICA/GW-BASIC used a tokenized format to save its programs, rather than plain-text source code. Printable ASCII characters (space through tilde) generally stood for themselves (except when part of a multi-byte sequence), but other bytes had different meanings. The "high-bit" bytes from #128-#255 stood for the various BASIC commands (some as single bytes, others as part of two-byte sequences), while some of the control characters had special meanings including signifying the start of a binary-encoded sequence encapsulating a numeric constant. A null (#0) byte marked the end of a program line, and some header bytes were used at the start of the line to encode the line number and some byte offsets: specifically, two bytes containing the offset of the next line as a [[Endianness|little-endian]] integer and two bytes containing the line number as a little-endian integer.
 Files saved to disk are preceded by a single byte to indicate if the program was protected: 0FEh if protected, 0FFh if not. Files saved to [[IBM PC data cassette|cassette tape]] omit this byte, because byte 9 of the cassette header holds the protection status.

@@ Line 498: / Line 498: @@
 == Other links and references ==
 * [[Wikipedia:GW-BASIC|Wikipedia article: GW-BASIC]]
 [[Category:Microsoft]]

@@ Line 492: / Line 492: @@
 == Sample files ==
 * Many files on [http://cd.textfiles.com/bthevhell/ Between Heaven and Hell Version II CD], such as [http://cd.textfiles.com/bthevhell/200/104/ /200/104/*.bas]
 == Other links and references ==

← Older revision		Revision as of 23:15, 26 August 2014
Line 9:		Line 9:

	Like most BASICs of its era, BASIC/BASICA/GW-BASIC used a tokenized format to save its programs, rather than plain-text source code. Printable ASCII characters (space through tilde) generally stood for themselves (except when part of a multi-byte sequence), but other bytes had different meanings. The "high-bit" bytes from #128-#255 stood for the various BASIC commands (some as single bytes, others as part of two-byte sequences), while some of the control characters had special meanings including signifying the start of a binary-encoded sequence encapsulating a numeric constant. A null (#0) byte marked the end of a program line, and some header bytes were used at the start of the line to encode the line number and some byte offsets.		Like most BASICs of its era, BASIC/BASICA/GW-BASIC used a tokenized format to save its programs, rather than plain-text source code. Printable ASCII characters (space through tilde) generally stood for themselves (except when part of a multi-byte sequence), but other bytes had different meanings. The "high-bit" bytes from #128-#255 stood for the various BASIC commands (some as single bytes, others as part of two-byte sequences), while some of the control characters had special meanings including signifying the start of a binary-encoded sequence encapsulating a numeric constant. A null (#0) byte marked the end of a program line, and some header bytes were used at the start of the line to encode the line number and some byte offsets.
		+
		+	Files saved to disk are preceded by a single byte to indicate if the program was protected: 0FEh if protected, 0FFh if not. Files saved to [[IBM PC data cassette\|cassette tape]] omit this byte, because byte 9 of the cassette header holds the protection status.

	== Tokens ==		== Tokens ==

@@ Line 487: / Line 487: @@
 == Format documentation ==
 * [http://www.chebucto.ns.ca/~af380/GW-BASIC-tokens.html GW-BASIC tokenised program format]
 == Other links and references ==

← Older revision		Revision as of 17:04, 16 February 2013
Line 490:		Line 490:
	== Other links and references ==		== Other links and references ==
	* [[Wikipedia:GW-BASIC\|Wikipedia article: GW-BASIC]]		* [[Wikipedia:GW-BASIC\|Wikipedia article: GW-BASIC]]
		+
		+	[[Category:Microsoft]]

@@ Line 147: / Line 147: @@
 |BE||190||SAVE
 |-
-|BF||181||COLOR
+|BF||191||COLOR
 |-
 |C0||192||CLS