Otherwise it was fun releasing the software, and knowing that it was programmed for any situation (for the poor or rich alike) made me feel like I did something perhaps the way Bil Herd or one of his contemporaries at CBM would have wanted it to be if they had released it on one of their demo-disks. Because first of all, things have to WORK. After that, it becomes a question of how compatible you write your software. Like, never use low-level routines in programs that someone else may try to use with an incompatible drive or cartridge. That means always use the kernel jump table; typical routines like BASEOUT and CHROUT are routines that work with almost every and any type of drive and are therefore highly recommended over low level ones like TALK, UNTALK, etc. All those routines are documented in the C128 programmer's reference guide. Try to think about how far you can take the AUTOEXEC thing when using WsDos, but more importantly, when you write your own programs, PUBLISH them for crying out loud. If they're good then someone else can use them. Especially myself Take care guys. It was fun. Remember to throw a little change into the karma kitty the next time you hit the store. It comes back to you
That last note was for when you need to disable RAMDOS before backing up or restoring the 1750 but there is an even more elegant way to do this. It involves a little timing, a little finger magic and you must press the RESET to initiate all this.
Okay you need to bail from RAMDOS. Press the RESET button, wait a second and hit the STOP key (ESC in X128). If you timed everything right you will see a blank screen with "BREAK IN 0" written on it.
And that was all you need, now you can back up or restore as needed.
Okay another useful trick I know is using CRT files to boot C64 programs directly from assembler. When combined with WsDos, the C64 can be programmed to take advantage of the c64 cartridge start routine which in effect bends how the BASIC portion of the operating system is initialized.
CRT files are those apps and stuff that manipulate what the C64 does when it boots - mimicking a C64 cartridge.
First, the code to be changed exists at $8000 to $8009. This is a memory HEADER marker that the C64 OS looks for. If the PETASCII text "CBM80* exists from $8003 to $8008, the C64 will automatically jump to the address stored within $8000/$8002- the other remaining vector is used to point to a customized RUN/STOP and RESTORE vector.
This helps mostly when the file you want to boot is binary and will not start with RUN.
DOSEDIT should be able to provide at least a half-solution to this, as a separate basic editor is also needed.
NOTE: None of that does any good if you don't boot the file while in 128 (WsDos) mode first. The whole trick is to load while in 128 mode and start in 64 mode. The idea is to be able to boot binary programs in C64 mode *after* 128 mode boots them and that's why an additional editor is required. This would load a binary template where only the jump destination has to be edited
Talk about being late to the game. First of all, I didn't know that WSDOS even existed until a few weeks ago. I stumbled across it on the GENie software repository and instantly was amazed by it. Then, I just discovered this thread about WSDOS on the 128 forum, started by Sid Davis, the developer of WSDOS. Fantastic! I'm going to take some time and play with this latest version. Thanks, Sid, for the update to this great utility!
@ Judland - I am also nothing but a user in the long run and I like software. Feed me software (arrgg) . I am glad you like the program,
On another note I hope nobody blames me or something for not maintaining a user logon. I'm not a nice guy and I have a history of ruining my life, and that's why if anyone really wants to know. I don't play well with the public, that's all.