Difference between revisions of "NEX file format"
From SpecNext official Wiki
(Initial version, lacks any details about header) |
m |
||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
The NEX file format was designed as very simple and straightforward format to load self-contained applications into memory and start them. Through various extensions it did reach v1.2 at this moment, which allows even for more complex use cases. | The NEX file format was designed as very simple and straightforward format to load self-contained applications into memory and start them. Through various extensions it did reach v1.2 at this moment, which allows even for more complex use cases. | ||
Revision as of 23:30, 27 March 2019
The NEX file format was designed as very simple and straightforward format to load self-contained applications into memory and start them. Through various extensions it did reach v1.2 at this moment, which allows even for more complex use cases.
The basic structure of the file is:
| block size | optional | description |
|---|---|---|
| 512 | "Next" string followed by file header, containing also map of memory banks stored in the file | |
| 512 | * | optional palette (for Layer2 or LoRes screen) |
| 49152 | * | Layer2 loading screen |
| 6912 | * | classic ULA loading screen |
| 12288 | * | LoRes loading screen |
| 12288 | * | Timex HiRes (512x192) loading screen |
| 12288 | * | Timex HiCol (8x1) loading screen |
| n * 16384 | * | 16kiB raw memory bank data in predefined order: 5,2,0,1,3,4,6,7,8,9,10,...,111 (particular bank may be omitted completely) |