Rooba
/
ReC98
mirror of https://github.com/nmlgc/ReC98.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity
887 Commits 22 Branches 3 Tags 53 MiB
Commit Graph

221 Commits

Author SHA1 Message Date
nmlgc c3202f4450 [Reduction] #125: hmem_lallocate 2014-08-22 01:19:52 +02:00
nmlgc 47781cd013 [Reduction] #124: smem_wget 2014-08-22 01:04:46 +02:00
nmlgc 7cde3a50ec [Reduction] #123: smem_release 
Need to do this function before smem_wget() to keep the alignment identical.
 2014-08-22 00:59:18 +02:00
nmlgc ea4db822ab [Reduction] #120-122: Heap memory functions 
With even more misreferences in switch tables.
 2014-08-22 00:17:53 +02:00
nmlgc 969990a819 [Reduction] #119: mem_assign_dos 
Containing, again, fixes for misreferences in TH04.
 2014-08-21 23:30:20 +02:00
nmlgc fc0ccd5e2b [Reduction] #117-118: mem_assign and mem_assign_all 2014-08-21 23:05:54 +02:00
nmlgc d270a625e5 [Reduction] #116: master.lib memory manager variables 2014-08-21 22:54:07 +02:00
nmlgc 99b9963082 [Reduction] #115: dos_ropen 
AKA "fontfile_open()", and originally kept in FONTOPEN.ASM... yeah.
 2014-08-21 22:09:18 +02:00
nmlgc d1ccecdfa9 [Reduction] #106-108: PC-98 EGC setup 
"Enhanced Graphic Charger", hm...
 2014-08-20 22:24:05 +02:00
nmlgc d3aaca7bd3 [Reduction] #90: text_clear 2014-08-20 16:45:24 +02:00
nmlgc eff96385b0 [Reduction] #82-89: PC-98 escape sequences 
I don't know anything about ANSI/VT100/??? escape sequences, but after some
quick research, these sequences and their effect seem to be specific to the
PC-98 (although they're implemented as part of DOS, of course).
 2014-08-20 16:27:28 +02:00
nmlgc 8f6c28c939 Restore master.lib's FUNC and ENDFUNC macros 
With seg000 changed to word alignment and all definitions for "func" removed,
the master.lib functions can keep their exact alignment themselves.

[Binary change] db 0 → nop before get_machine_98() in the MAIN.EXE and
MAINE.EXE files of TH04 and TH05, respectively.
 2014-08-20 15:25:40 +02:00
nmlgc a033b347fc [Reduction] #44: graph_extmode 2014-08-15 16:12:09 +02:00
nmlgc a313ae5d78 [Reduction] #43: Text VRAM variables 2014-08-15 14:26:44 +02:00
nmlgc d95fc3cdd9 [Reduction] #32: get_machine 2014-08-14 14:48:55 +02:00
nmlgc 7b9a30fc8d [Reduction] #31: get_machine_98 2014-08-14 14:30:48 +02:00
nmlgc 1c91cc75e7 [Reduction] #30: get_machine_at 
Um. Not sure if ZUN used an older version there, or if these additional
branches simply resulted from a lack of optimization...
And I even had to convert the labels to local syntax.
 2014-08-14 14:27:36 +02:00
nmlgc af609d5e1c [Reduction] #29: get_machine_dosbox 2014-08-14 13:22:17 +02:00
nmlgc 59688e23fc [Reduction] #28: Machine_State 
We~ll, OK, it's just a single variable, but it's originally stored in its own
.ASM file as well.
And yup, that's how we're going to treat data slices.
 2014-08-14 13:22:14 +02:00
nmlgc cc313d5095 [Reduction] #27: check_machine_fmr 2014-08-14 12:22:50 +02:00
nmlgc 534ba2d142 [Reduction] #5: bfill 
To get anywhere, we must become able to include assembly files that define
their own segments. But this will only work if we include these files in the
order they appear in in our dumps, *starting from the very first one*. And to
include the very first one, we must first get rid of the erroneous references
to the first few bytes of the data segment... and this function happens to be
the first one referencing those.
 2014-08-10 11:47:36 +02:00