READMAKE

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
(Software)
 
(One intermediate revision by one user not shown)
Line 25: Line 25:
 
** 10/08/97 (7.10): {{CdTextfiles|simtel0101/simtel/txtutl/read710.zip|read710.zip}}
 
** 10/08/97 (7.10): {{CdTextfiles|simtel0101/simtel/txtutl/read710.zip|read710.zip}}
 
** 03/08/98 (8.06): [https://archive.org/details/hot-shareware-cd36 Hot Shareware 36] → FICHEROS/DUTI/READ806.ZIP
 
** 03/08/98 (8.06): [https://archive.org/details/hot-shareware-cd36 Hot Shareware 36] → FICHEROS/DUTI/READ806.ZIP
 +
 +
* {{Deark}}
  
 
== Sample files ==
 
== Sample files ==
Line 33: Line 35:
 
* {{CdTextfiles|nogames3/012a/pgold11.zip|pgold11.zip}} → README.EXE
 
* {{CdTextfiles|nogames3/012a/pgold11.zip|pgold11.zip}} → README.EXE
 
* {{CdTextfiles|thebbsorg/ddsbbs/makelst.zip|makelst.zip}} → README.EXE
 
* {{CdTextfiles|thebbsorg/ddsbbs/makelst.zip|makelst.zip}} → README.EXE
 +
* {{DexvertSamples|document/readmake}}

Latest revision as of 18:50, 14 November 2024

File Format
Name READMAKE
Ontology
Extension(s) .exe
Released 1993

READMAKE is a DOS utility for creating a DOS EXE file that, when executed, displays a text document in a full-screen viewer. It was developed by Bruce Guthrie and Wayne Software.

READMAKE is related to READ (a.k.a. READ.EXE), a text file viewer by the same developer.

[edit] Identification

The executable part of a generated file is compressed with EXEPACK.

The EXE code segment (refer to MS-DOS EXE#Special file positions) at offset 512 starts with ASCII "blREADINCL". While not a deliberate signature (it's some sort of linker artifact?), it could be a fairly effective way to identify the files.

The overlay always starts with the same 62 bytes, the first four being 3e 00 00 00 (presumably a segment size field). However, some other EXE files from the same developer also have this trait.

[edit] Software

READMAKE was usually packaged with other software by the same author. The individual programs have revision dates that serve as their version numbers. Each package as a whole has an apparent 3-digit version number, probably loosely derived from the release date.

[edit] Sample files

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox