Revision as of 01:03, 19 February 2017

Who am I

I'm an old C64 scener, look me up at csdk.dk if you don't believe me ;)

2016-11-05: BeOS/Haiku doesn't log anything to LOG_DEFAULT except HardSID messages at startup.
2016-11-05: VSID: add HVSC Songlengths.txt support, maybe STIL as well. (For 3.1 or later)
2017-02-13: *nix make install: fix DOS2UNIX check, doesn't seem to work very well now

The c1541 and vdrive code needs cleaning up

Names like `unit`, `drive` and `device` are used interchangeably: sometimes `unit` is an actual unit number (8-11), sometimes it's an index into a vdrive array, values are arbitrarily AND'ed, OR'ed or subtracted to convert between 'valid' values for unit numbers and drive indici.(FIXED in c1541, vdrive etc have API problems)
Often user input for commands (c1541) is assumed to be correct. Leading to either weird error messages or even segfaults. (FIXED)
CBM DOS command support needs work. The VDrive command handling is lacking some functionality as opposed to the actual CBM DOS.

@@ Line 15: / Line 15: @@
 The c1541 and vdrive code needs cleaning up
-* Names like `unit`, `drive` and `device` are used interchangeably: sometimes `unit` is an actual unit number (8-11), sometimes it's an index into a vdrive array, values are arbitrarily AND'ed, OR'ed or subtracted to convert between 'valid' values for unit numbers and drive indici.(<b>FIXED</b>)
+* Names like `unit`, `drive` and `device` are used interchangeably: sometimes `unit` is an actual unit number (8-11), sometimes it's an index into a vdrive array, values are arbitrarily AND'ed, OR'ed or subtracted to convert between 'valid' values for unit numbers and drive indici.(<b>FIXED</b> in c1541, vdrive etc have API problems)
 * Often user input for commands (c1541) is assumed to be correct. Leading to either weird error messages or even segfaults. (<b>FIXED</b>)
 * CBM DOS command support needs work. The VDrive command handling is lacking some functionality as opposed to the actual CBM DOS.