| |
Jammer
Registered: Nov 2002
Posts: 1336 |
TURBO loaders/savers
as in the topic - i really need some information on good turbo loaders and savers. irq ones don't count. it would be also great if they were tass sources, optionally with any relocator. what do you recommend? :) |
|
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
what exactly do you want to use them for and what are required features (is a plain t/s loader ok?) |
| |
yago
Registered: May 2002
Posts: 333 |
iirc, Plushdos has also a turbo-loader (and saver), besides the irqloaders. No sources, though. |
| |
Jammer
Registered: Nov 2002
Posts: 1336 |
they are needed for tools.
the main requirements are that they should be relatively fast, work without errors and cannot hang up the drive.
turbo loader:
- possibilitiy of forcing loading adress for the file
turbo saver:
- possibility of forcing loading address for the saved file
they should work without disabling the screen thus nothing that pokes around $d011.
they cannot watch memory bank setting all the time (explorer's turbo loader/saver does this way).
they should work without problems or hang ups with another drives (up to drive 11).
it would be nice if rom related procedures were executed by kernal jumps, not directly in rom addresses (for compatibility)
|
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
these requirements sound like something you have to write yourself =) |
| |
enthusi
Registered: May 2004
Posts: 677 |
or use TurboTape |
| |
Frantic
Registered: Mar 2003
Posts: 1648 |
Just wanted to say that I also think it would be nice if someone wrote routines like this... precisely for tools.
Codebase64 wants you! ;) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
just code those tools to properly use kernal calls and they'll work just fine with whatever speeder is installed. problem solved :) |
| |
AlexC
Registered: Jan 2008
Posts: 299 |
Just use action replay ;) Jokes aside I think you will need to write one by yourself. I'd take a peek at Covertbitops loader system and dreamload. |
| |
MagerValp
Registered: Dec 2001
Posts: 1078 |
Another vote for "just use kernal calls". Trust the user to have a fastload system installed. Everyone has some kind of fastload system - be it AR6, JiffyDOS, or warp mode. |
| |
Frantic
Registered: Mar 2003
Posts: 1648 |
You're all right about the kernal call stuff. Anyway, what would be really nice is if someone wrote a small little fileselector with dir/load/save capabilities and some options to enforce load/save adresses. It is easy to do, of course, but it would still be nice to have this in public, since it would be reuseable for all tool coding purposes.
Anyway... One benefit of actually having custom turbo load/save routines is that you could load a single file into split memory segments, rather than having to load it in a single chunk in C64 mem. Not a big issue in most cases, perhaps, but at least that is something that put a stop to the plans of using Kernal calls for load/save for me at one time. |
... 15 posts hidden. Click here to view all posts....
|
| Previous - 1 | 2 | 3 - Next |
