| |
jcompton
Registered: Feb 2006
Posts: 70 |
Release id #152591 : SD2IEC Kernal 1.0
(Moving the discussion of wedge to a forum post)
If feasible, it would be nice to get the Big Three DOS wedge commands:
@ (command channel)
/ (load ,8)
% (load ,8,1)
The browser is a nice option, but the direct route is handy as well if both can be supported. |
|
... 21 posts hidden. Click here to view all posts....
|
| |
Claus_2015
Registered: Oct 2012
Posts: 53 |
I guess it should be easy to fit the wedge in, especially as the actually needed code for the commands should be available in the browser already. So only the parsing would need to be added.
I am not so sure about the general fast loading. Right now, the fastloader detects an sd2iec device during open and then switches to the fastload protocol by sending special m-w and m-e commands. In order to support general byte getting, one would need to maintain sd2iec flags for each opened file. If two files are opened on an sd2iec device, things would get complicated, because as far as I can oversee you cannot really switch between different files and continue loading in the middle of a file. Seems like for these cases, JiffyDOS is the way to go :-).
BTW just to clarify: the fast loading is not limited to the browser, it accelerates the BASIC load command, too. |
| |
Claus_2015
Registered: Oct 2012
Posts: 53 |
Update: I checked back with Ingo Korb (the author of the sd2iec firmware) and he agrees that eload is not able to handle multiple files. The code on the sd2iec expects the transmission to be initialized with secondary address 0, effectively only allowing a single file to be opened at the same time.
So I do not think that I will extend the kernal to accelerate more than normal file loading, as this would require a change to a different loader. |
| |
TheRyk
Registered: Mar 2009
Posts: 2218 |
reasonably quick fast loader plus easy to handle file browser. quite nice to have!
of course, my old combo "5" (JiffyDos KERNAL on my EF3) "↑FB*" (File Browser) + Return somehow is fixed in my brain (and not much harder than "6" (your KERNAL) "Shift+Run/Stop") but with this new solution it ain't a problem anymore to launch file browser without resetting SD2IEC - no matter whether FB is on currently mounted image or not.
Suggestion: Implement F-Keys for stuff like LOAD, DIR, LIST, RUN |
| |
Claus_2015
Registered: Oct 2012
Posts: 53 |
Just for completeness: Enthusi (obviously :-)) suggested to squeeze TurboTape in (which looks feasible). Is there anyone else who thinks that is a good idea? I am a bit in doubt, as an SD2IEC typically blocks the tape port, but it might make sense if people want to use one or the other without changing the kernal. Opinions? |
| |
enthusi
Registered: May 2004
Posts: 677 |
Blocking the cassport for a device to transfer data through the IEC port is a bad idea anyway :-) |
| |
jcompton
Registered: Feb 2006
Posts: 70 |
It's your project, but my feeling is if the premise is to be "a very useful kernel specifically for SD2IEC users", the fact that the vast majority of SD2IEC users have the tape port blocked means that any leftover space would be better used on optimizing outcomes for SD2IEC-specific use, and/or very general-purpose stuff like F-keys, rather than accounting for the narrower audience of people using external SD2IEC power, or using SD2IEC under emulation. |
| |
Claus_2015
Registered: Oct 2012
Posts: 53 |
I originally wrote this kernal to make my life easier when creating/testing cartridges (where you need mass storage, but do not have the module slot free). I meanwhile feel the need for a memory monitor in these cases, so I will investigate if I can fit a simple one in. Holding Run/Stop while resetting would then skip module start and directly enter the monitor. |
| |
Angel of Death
Registered: Apr 2008
Posts: 211 |
"fit a simple one in"
And a fast-loader and a file-browser.
Where did you find all that free space?
I made a Kernal once and without serial comm and tape functionality I only managed to squeeze SJ-load for the SD2IEC (no drive-code) and a few F-key commands in.
(anyway you'd publish the source, maybe? ;) ) |
| |
Claus_2015
Registered: Oct 2012
Posts: 53 |
:-) I decided on eload, because it is a pretty compact fastloader. The browser is the largest part with roughly 1.5 kb. Overall I was able to find 2565 bytes and I really used every available tiny segment (some are only 4 bytes) without wasting a single byte. When it is all done I am happy to share the source, although it is obviously a tad convoluted... |
| |
enthusi
Registered: May 2004
Posts: 677 |
I dont recall this but I posted the rs232 areas I used back then:
http://csdb.dk/release/?id=47403&show=notes#notes |
| Previous - 1 | 2 | 3 | 4 - Next |
