Binary .BIN file not loading correctly.

Page 2/2
1 |

By hit9918

Prophet (2868)

hit9918's picture

29-08-2018, 22:54

CLEAR moves HIMEM
I prefere moving BOTTOM (like the BASIC code I posted above. it gives you &h8000 - &hC3FF)
because HIMEM varies wildly dependant what disk drives one has!
and when you move BOTTOM to free at &h8000, there is another 16k right next door at &h4000.

26k is too much, always wipes diskROMs.
time to use page 1 &h4000 - &h7fff
ENASLT the RAMAD1 , copy the BLOAD there
ENASLT the ld a,(&hfcc1) to get back to BASIC ROM to have another BLOAD

By M2X_E1

Rookie (21)

M2X_E1's picture

31-08-2018, 12:57

hit9918 wrote:

CLEAR moves HIMEM
I prefere moving BOTTOM (like the BASIC code I posted above. it gives you &h8000 - &hC3FF)
because HIMEM varies wildly dependant what disk drives one has!
and when you move BOTTOM to free at &h8000, there is another 16k right next door at &h4000.

26k is too much, always wipes diskROMs.
time to use page 1 &h4000 - &h7fff
ENASLT the RAMAD1 , copy the BLOAD there
ENASLT the ld a,(&hfcc1) to get back to BASIC ROM to have another BLOAD

Beginning to realise my application, originally 32kb may not be for use in the msx disk/basic environment. I really only need the disk loader to get the program into memory, after that I'm not concerned with basic or disk loader. I wonder if there is a method of disabling basic and diskloader once the program is in and running, that way freeing up ALL ram except that used by system hooks?

Regards

By hit9918

Prophet (2868)

hit9918's picture

31-08-2018, 15:02

with enaslt you get added another 16k, get 32k easy
without enaslt you are into a 26k fight on a 23k system
the system goes from FFFF down to HIMEM

Page 2/2
1 |