From: groepaz (groepaz_at_gmx.net)
Date: 2000-11-16 10:51:51
Hello Martin, Thursday, November 16, 2000, 8:43:36 AM, you wrote: >>mmmh, too bad i don't have any time for my c64 projects atm... but i'll try >>to check that out and have a look. The filesystem i mentioned some (long) time >>ago is actually working in an 'alpha' state and its laid out so you >>can 'mount' your own 'low-level-device-drivers' ... MAHW> Is this a plain driver, that just reads and writes SEQ/PRG files? That's all I need. if the only thing you want is read/write from/to memory without further actions like seeking etc, that works perfectly fine atm (although i doubt anyone else but me could make use of the current code anyway, need to clean it up really ;=/) >>does that implementation allow stuff like seeking then? (wonder how portable >>that part could be, since on the c64/1541 definetly some drive-code would be >>involved) MAHW> Stop that drive-specific-code at once. We are not using a 1541 for all data. MAHW> Some use REU or harddrives. Please make code that access the kernel! thats actually the reason why i designed it so you can mount your own lowlevel drivers. the current driver DOES indeed simply access the kernal, so it should work with most devices that are compatible with kernal calls - this driver does however _NOT_ allow seeking, and it will never do - this is the point where drive-specific code kicks in (take it as part of the driver). This way you could also write some 'specific' driver for REU for example, that would make use of all the possibilities you have with that device (and again, here it would be easy-peasy to implement seeking - unlike if you would be sticking to kernal calls) -- Best regards, groepaz mailto:groepaz_at_gmx.net ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo_at_musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.
This archive was generated by hypermail 2.1.3 : 2001-12-14 22:05:36 CET