| |
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....
|
| |
enthusi
Registered: May 2004
Posts: 674 |
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: 210 |
"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: 674 |
I dont recall this but I posted the rs232 areas I used back then:
http://csdb.dk/release/?id=47403&show=notes#notes |
| |
Claus_2015
Registered: Oct 2012
Posts: 53 |
Ah, thank you! It seems I was a bit more aggressive in kicking out RS-232 related stuff. |
| |
Angel of Death
Registered: Apr 2008
Posts: 210 |
One thing I kept intact that if you try to access device# 1 or 2 you get an "device not present" error message.
Perhaps I lost a lot there. |
| |
CRT
Registered: Oct 2012
Posts: 87 |
Flashed it to my EF3 as a kernal and it will be my prime choice for most SD2IEC operations from now on. It's a great kernal!
Humble requests: I would like an auto run feature from the browser so I don't have to type RUN. A simple wedge would not be wrong either. Also, an auto-detect of active device or even just a tool generate a kernal starting with your device number.. I know.. probably just one byte to change (I'm lazy). Or just give me the address and I will make the tool (I'm not that lazy after all). @%@#%.. I can hack it!
Awesome kernal! |
| |
Claus_2015
Registered: Oct 2012
Posts: 53 |
Thanks a lot, CRT! The address to patch for the start device number of the browser is $f422 (or byte $1422 in the .rom file). I actually expect this to stay the same no matter what I change in the kernal.
Let's see how much is left when the monitor is in, maybe the auto-run can be added (might be smaller than the wedge or function keys). |
| Previous - 1 | 2 | 3 | 4 - Next |
