Closed ulboet closed 2 years ago
Ok, that sounds good. Does it come from TSC or from the FLEX community? Coding: The hour, is it 0 - 23 or 0 - 12 plus an AM/PM flag? The minute, is it 0 - 59? To support file time within FLEX a realtime clock would be needed together with a driver code for a generic access to hour/minute from the specific realtime clock chip. Or is it all a "custom hack" with hard coded realtime clock access? To be precise: reserved1 has byte offset 12, reserved2 has byte offset 20 within s_dir_entry.
Indeed it's an extension of FLEX not by TSC. The hour is 0-23 and the minute 0-59. The driver code unfortunately has to be hard coded in FLEX in order to read the clock during creation of a file. It's offset 12 and 20, I was using the FCB-counting.
FlexDirEntry now supports file time (Class BTime). Because it is a FLEX extension both within flexemu or FLEXplorer preferences it has to be activated to use file time. No driver code or FLEX utilities like DIR.CMD or COPY.CMD have been adapted. File time support is on the master branch since 7f271ea171de3cb213f550518a50e22d5d16c244. @ulboet, please verify the feature.
Looks good - thank you very much! I've tested copying in FLEXplorer and using the directory feature (from Linux -> FLEX). For the other direction (FLEX -> Linux) I need to merge with my branch to activate my RTC emulation for generating time-stamps by FLEX.
A FLEX extension contains the file hour at offset 16 (bit 7 indicates sub-directory) and the minute at offset 24 (in struct s_dir_entry reserved1 and reserved2).
One option would be to extend the class Bdate with hour and minute.