On 2/17/23 19:53, Fisher wrote:
Meanwhile the whole contraption os giving me fits! Is there a tppd driver that
it will play nice with?
I can't manage it with a floppy drive or a Backpack. After I load up some files
it forgets how to change banks. I suppose I need to be using Teeny or
somesuch, just thought to ask here in the RAM+ users group.
Sean
Consult the manual
http://www.club100.org/library/doc/tsdos.html
And these pimers about binary apps on this platform:
http://www.bitchin100.com/wiki/index.php?title=Loading_a_typical_CO_file
http://www.bitchin100.com/wiki/index.php?title=Run-In-Place_CO
All machine language programs conflict with each other on this platform.
To switch back and forth between different machine language programs,
you have to keep copies of them in ram in .CO file form, and re-load
them into high memory to displace whatever the last other program you
ran was. (multiplan is a little different in this case, where it's
really a rom but also installs a ram component and effectively has the
same problem.)
Usually this means having a .CO file in the ram filesystem, and a small
.BA file launcher which basically just does a clear statement and then
runs the .CO
For instance:
http://www.club100.org/library/ups/diskon.do
This uses up a lot of ram though, since it means you have effectively 2
copies of the program in ram, one in the form of the .CO file, and one
in high memory which is the one that's actually executed.
The copy in high memory gets clobbered every time any other machine
language program runs.
This is true for almost all machine language programs.
There are exeptions but they are rare and fragile. *some* few machine
language apps like TEENY and DSKMGR have special relocating installers
that can edit all of the jumps and address pointers in a program at
install-time, to install the app at some arbitrary offset address, so
that two machine language apps can both coexist side by side in high
memory at different address ranges. Then they can each have what's
called a trigger file in the main menu that just jumps to the right
address. But neither multiplan nor ts-dos has a relocatable installer
like that that I know of. So, they just will always clobber each other.
This is actually the norm for most machine language apps.
TS-DOS has a special option to store the .CO file on the disk instead of
in ram, and in ram you can have a much smaller TSLOAD.CO instead of the
full DOS100.CO. TSLOAD is small and all it does is load DOS100.CO from
the disk into high memory temporarily each time you want to run it, the
same as what Ultimate ROM 2 does.
I can't find a copy of tsload on-line anywhere unfortunately.
I did find a copy for Model 200, but not for 100 or nec. The manual
describes it, and I see Kurt asked about it on the list years ago, but
that's it. For anyone interested, tsload.co for model 200 is here:
http://www.club100.org/library/libpg.html
Most of that stuff, including that particular copy of dos200.co is all
just for Paul's X-OS which is a special alternative OS just for Model
200. But that copy of tsload.co is probably just the ordinary copy from
travelling software for ts-dos on the 200. It doesn't do you any good on
a 100.
Anyway, unless someone can come up with a copy of TSLOAD.CO for 100, you
simply really want TS-DOS in ROM, and since you also want to use
Multiplan which is itself a rom, then you really want a REX# so you can
switch between roms at will.
Failing that, you need to keep a copy of DOS100.CO in ram, and launch it
with a little basic launcher like the one I linked above. This will eat
10 to 12k of your ram but that's just the way it is with machine
language apps on this platform.
--
bkw
