Problem accessing APETIME when run along with using APE
Closed this issue · 13 comments
Hi,
when FujiNet and APE are used together and APETIME SIO call is performed both devices answer.
I suggest following options:
- config option for APETIME function in FujiNet (power-cycle-proof) that allows for [permanent off | permanent on | auto-soft-disable]
- Like FujiNet keeping quiet if it detects a remote D1: answering upon boot it could soft-disable APETIME in this case
I really want to say so much here. You're blindly assuming that FujiNet can't take over those duties, and make your Atari not tethered to a notebook, at the same time, and this is, at least, to me, who has spent the last three years making FujiNet able to handle software development workflows, infuriating.
I must state that FujiNet has multiple protocol adapters (including TNFS and SMB, to handle network endpoints at a file level.)
There's also a web UI for mounting/unmounting images.
-Thom
Will implement the disable.
-Thom
have you done any mounting via the web interface?
I have committed code in the master branch to disable the Apetime device on the FujiNet if the following is placed at the bottom of the [ENABLE] section like this:
[ENABLE]
enable_device_slot_1=1
enable_device_slot_2=1
enable_device_slot_3=1
enable_device_slot_4=1
enable_device_slot_5=1
enable_device_slot_6=1
enable_device_slot_7=1
enable_device_slot_8=1
enable_apetime=0
I will work with @markjfisher to fold in a change to the web UI to enable/disable it, but this should get you going, once we do a build.
I apologize profusely for my unbelievably hyperemotional way that I responded to this.
I can't assume a user's use case, nor can I force them to do anything they do not want to do, and I have to remember that any frustrations really are inconsequential, especially if people are using what is made.
We'll get a build out, and let you know when you can install it via the flasher.
-Thom
Ignore first 2 commits, my master got out of sync with upstream and I had to rebase locally.