Originally Posted by
blackcat4866
The bug occurred in original firmware version 3.02. The fix is noted in the firmware bulletin for version 5.02.
It probably wasn't worded that way. That's just how I remembered it in my 2 remaining memory brain cells.
Upon checking the database, there was both a Maintenance D and a Maintenance E that got nixed.
=^..^=
Bookmarks