Defects: Difference between revisions

From Color 64 BBS Wiki
Created page with "These are the observed or reported effects currently being tracked. If you'd like to report an error, please post in Discussion or report it on the itchybutt discourse at itchybutt.org. <ul style="list-style: none;"> <li>Priority 1: Critical / Fatal error</li> <li>Priority 2: High Priority Error / Non-Fatal</li> <li>Priority 3: High Priority Error / Non-Fatal with Workaround</li> <li>Priority 4: Annoyance</li> <li>Priority 5: Enhancement/Desired</li></ul> {| class="wik..."
 
No edit summary
 
(7 intermediate revisions by the same user not shown)
Line 15: Line 15:
! Observation
! Observation
! Status
! Status
|-
| Punter Transfers / WifiModem / TCPSER
|3
| Punter Transfers fail in the WifiModem and TCPSER environments. Standard Modem transfers unknown. Workaround: XModem works fine.
| Fix released under Build 31JAN26
|-
|-
| NW1 not recalling information
| NW1 not recalling information
Line 30: Line 35:
| If Sysop tries to copy a file in DOS Wedge "X" command and if the file already exists, DOS Wedge will kick out an error saying File Exists and end the process. Desired: Prompt Sysop if they would like to overwrite the file instead.
| If Sysop tries to copy a file in DOS Wedge "X" command and if the file already exists, DOS Wedge will kick out an error saying File Exists and end the process. Desired: Prompt Sysop if they would like to overwrite the file instead.
| Pending
| Pending
|-
| User Banner Not Deleted After User Purge
| 4
| If a user is deleted from the system, their banner is not properly being removed with the user account. As a result, the banner of the old user will show up for a new user when assigned that ID. Observed in LTK 08NOV25 build. Workaround: If a user is purged, Sysop can delete the respective banner in user profile drive area if one exists.
| Pending
|-
| User Signature causes "String too long" error in 36003 bbs.msgs
| 1
| If a user creates a signature, it may cause a "String too long" program error on the user's next sign-in, causing BBS restart.
| Fix released under Build 31JAN26
|}
|}

Latest revision as of 21:40, 31 January 2026

These are the observed or reported effects currently being tracked. If you'd like to report an error, please post in Discussion or report it on the itchybutt discourse at itchybutt.org.

  • Priority 1: Critical / Fatal error
  • Priority 2: High Priority Error / Non-Fatal
  • Priority 3: High Priority Error / Non-Fatal with Workaround
  • Priority 4: Annoyance
  • Priority 5: Enhancement/Desired
Defect Tracker
Defect Priority Observation Status
Punter Transfers / WifiModem / TCPSER 3 Punter Transfers fail in the WifiModem and TCPSER environments. Standard Modem transfers unknown. Workaround: XModem works fine. Fix released under Build 31JAN26
NW1 not recalling information 2 When Network Setup is run on an existing network configuration, details of a Node are not always recalled properly, leaving all details blank. Under Investigation
Password Records with Address Garbage 4 Some user entries after being created show garbage / random characters in address field. May cause random screen behavior when being displayed by Sysop. Sysop must edit field to remove behavior. Pending investigation
Copying File in DOS wedge with existing present 5 If Sysop tries to copy a file in DOS Wedge "X" command and if the file already exists, DOS Wedge will kick out an error saying File Exists and end the process. Desired: Prompt Sysop if they would like to overwrite the file instead. Pending
User Banner Not Deleted After User Purge 4 If a user is deleted from the system, their banner is not properly being removed with the user account. As a result, the banner of the old user will show up for a new user when assigned that ID. Observed in LTK 08NOV25 build. Workaround: If a user is purged, Sysop can delete the respective banner in user profile drive area if one exists. Pending
User Signature causes "String too long" error in 36003 bbs.msgs 1 If a user creates a signature, it may cause a "String too long" program error on the user's next sign-in, causing BBS restart. Fix released under Build 31JAN26