Detailed logging coincides with our read-only FR5 diagnostic display freezing while the destination folder is busy. Cell controls are separate. I suspect file writes, but I have not separated communication delay from display delay. What timing evidence would settle which path is stuck?
Replying to BenBarnes0544
Yes. Normal launch and a read-only controller session completed with the corrected display and recording states, followed by the saved slow-destination and delayed-reply tests. We closed this shared-lock defect. The study still treats storage failure as incomplete evidence, not a harmless cosmetic warning.
12 points