You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When booting the APOD viewer client (2021-05-01 version), either on an ATR disk image (containing MyDOS and the program) or as an XEX directly, using an SIO2SD with high speed I/O (the config on mine shows sio high speed: 59659.08 ($08)), the APOD client cannot ever properly fetch the current time & date via FujiNet's APETIME protocol.
Unlike what happens when either (a) FujiNet is detached or turned off, or (b) the APOD client is booted so quickly that FujiNet is not yet up and running (I generally use my The Ultimate Cart SD cartridge, as it's the quickest way to fire up the XEX), which seems to be APETIME protocol coming back with an empty string, it instead seems to return some kind of gibberish. (What I've seen the APOD viewer client parsing it as were either "2000-00-15", or "2000-120-15".)
When booting the APOD viewer client (2021-05-01 version), either on an ATR disk image (containing MyDOS and the program) or as an XEX directly, using an SIO2SD with high speed I/O (the config on mine shows
sio high speed: 59659.08 ($08)
), the APOD client cannot ever properly fetch the current time & date via FujiNet's APETIME protocol.Unlike what happens when either (a) FujiNet is detached or turned off, or (b) the APOD client is booted so quickly that FujiNet is not yet up and running (I generally use my The Ultimate Cart SD cartridge, as it's the quickest way to fire up the XEX), which seems to be APETIME protocol coming back with an empty string, it instead seems to return some kind of gibberish. (What I've seen the APOD viewer client parsing it as were either "2000-00-15", or "2000-120-15".)
Based on this, I added extra sanity checks in APOD client (FujiNetWIFI/fujinet-apps@f0d7212).
The text was updated successfully, but these errors were encountered: