Msg: 7123 *Conference*
04-17-97 17:50:19
From: RON WIESEN
To : TONY SUDNEY
Subj: U GOT TWO DIFFERENT LOADER.BA FILES
Howdy Tony. Read your MSG# 7143 that Rick sent my way. Be aware, I am not familiar with RAMDSK.CO, other than what I can gather from the excellent details in your message - which is quite a bit. As I see it: (1) You're sharing a single Rampac between a M200 and a M102. (2) The Rampac contains RAMDSK.CO, which spans 2 sectors, beginning in Sector 002 and ending in Sector 001. (3) The RAMDSK.CO that's in the single Rampac is m/l code that's M200 specific in regard to memory allocation (intended for a Top of 59838) and perhaps in regard to functions such as 16-line LCD, etc. This is the main problem - to share the Rampac, you need m/l code that's M200 specific as well as m/l code that's M10x specific. (4) In one instance you used a M10x specific LOADER.BA in the M102 to extract a 1279-byte block which is m/l code specific to the M200. This loader is M10x specific in regard to memory allocation such as Top, etc. Right place, right stuff (m/l), wrong flavor (M200 specific code). In other words, right LOADER.BA extracted wrong code. (5) In one instance you used a M200 specific LOADER.BA in the M102 to extract a 1266-byte block which is m/l code specific to the M200. This loader is M200 specific in regard to memory allocation such as Top, etc. Wrong place, right stuff (m/l), wrong flavor (M200 specific code). In other words, wrong LOADER.BA (extracted the stuuf it's meant to extract but this stuff isn't good for M102 digestion). I recommend this: (1) ASCII Download R100LD.100 and MERGE/SAVE it as R100LD.BA. It is M10x specific. Save it to disk or tape before using it, if you can. (2) Load R100LD.BA into the M102. Run it to create RAM100.CO. Save it to disk or tape before using it, if you can. (3) Invoke RAM100.CO and your M102 can do file I/O with your Rampac. I'm sure the file I/O rules that RAM100.CO uses are the same as those of RAMDSK.CO so you need not worry in that regard. (4) Save RAM100.CO in your Rampac. It'll span 2 sectors, somewhere other than Sector 002 and Sector 001. (5) Then get back to me as to how you fare. We'll talk about how to modify the M10x specific LOADER.BA so it extracts a 1400-byte block of M10x specific m/l code and puts it in RAM as a file named RAM100.CO. Toward this end, from the Upload area you might wish to prepare by ASCII download of RD1OF2.DO and RD2OF2.DO which MERGED are the M10x specific Rampac Diagnostic RD.BA. RD.BA (19,180-byte) is handy for many things such as "tracing" the chain of Sectors of a file in the Rampac. Rather than download documentationfile RD-DOC.BA (21,229-byte), just press ESC while running RD.BA and on-line help tutors you.