FutureVision 4.1 Bug Reports
Maintained by Dave Miller
This list has been started from scratch on July 6th, 1996. Any bugs you know
of that were reported before that time that haven't been fixed yet should be
rereported. I will be attempting to assimilate the remaining contents of the
fvbugs database on galadriel at some point, although its contents are rather
sketchy since people didn't always report things well...
The New User module default emulation selection always tells the user that their
current emulation is "Standard TTY" no matter what the logon autodetect says
they're really using. Dark Dude 10/10/96
Certified mail receipts show the word "letter" instead of the receiver's address
when reporting that "the letter you sent to xxxx was
delivered".
CheezWhiz 8/21/96 (and others earlier)
The Conferencing data compiler fails to either delete 4/MSGCONF.DATA before
rehashing the conferencing data or blank out the entries for non-networked
subboards, so if a subboard number that used to belong to a networked conference
is no longer networked, the network data WON'T go away...
TinMan
8/13/96
Maint 1 fails to address the System Rules file letter when mailing it to a new
user.
TinMan 8/5/96
2/AUTOSIG.WARNING is missing from the distribution archive.
Dark Dude
7/31/96
Filemail Options should be prompted for when available (i.e. "This letter has a
file attached. Press * for Filemail Options" or something to that
effect).
CheezWhiz 7/28/96
Net Scriptor checks for destination sites on all type 3 conferences whether
hosted or not (waste of time on a non-hosted conference).
CheezWhiz
7/28/96
Quote string on mail forward should say "Forwarded by" rather than "Forwarded
from".
CheezWhiz 7/26/96
Sending mail receipt from a staff user aborts instead of sending
it.
CheezWhiz 7/25/96
Days & Months (2/DATE.INFO) missing from distribution file.
Tinman
7/25/96
Email doesn't zero out all the headers before reading in a new email, leaving
trailings from the previous letter if the current one has a less descript
header.
CheezWhiz 7/25/96
New User should use an ssi() to determine whether to ask for SS# or
not.
Dark Dude 7/25/96
Filemail download uses RZ instead of SZ
Dark Dude 7/25/96
3/FILEMAIL.OPTS has escaped control codes in it instead of regular ones. (swiped
from METAL source and commands not removed?)
Dark Dude 7/25/96
MSG.EDITOR doesn't reliably recompile the conferencing data.
CheezWhiz
7/25/96
The following is how I wanted to format them, but the above is what I did
when I was in a hurry, just to get the stuff posted :) I'll fix it later...
(maybe)
Status: Verified/Fix not yet
attempted
Reported by: CheezWhiz@antimatter.ecore.fnet.org
Date
Reported: 07/06/96
File affected: 1/MSG.POSTMSG.L Version:
2.2.6b
Description of bug:
'References:' line often starts with a
comma when posting messages.
Status: Verified/Fix not yet
attempted
Reported by: Tinman@cottage.ecore.fnet.org
Date
Reported: 07/06/96
File affected: 1/NET.SCRIPTOR.L Version:
3.5.8c
Description of bug:
Routing of 'unsopported conferences' to
the DEAD.FILE results in Error #67 - Invalid File Reference Number.
Status: Fixed - new version is
1.1
Reported by: CheezWhiz@antimatter.ecore.fnet.org
Date
Reported: 07/06/96
File affected: 58/AUTO.PURGE.S Version:
not versioned
Description of bug:
The CalcHash routine doesn't
backspace over the user number, so it fills the screen with numbers (minor
cosmetic problem :)
Status: Verified/Fix not yet
attempted
Reported by: CheezWhiz@antimatter.ecore.fnet.org
Date
Reported: 07/06/96
File affected: 1/MSG.POSTMSG.L Version:
2.2.6b
File affected: 1/MSG.BASE.S ? Version:
1.3.3b
Description of bug:
Moderating networked conferences at the
host site doesn't work...
On Write-to-Network the following occurs:
- the message is written to the net as if it were posted by the moderator
(the moderator's information is in the header on the posted message)
- the original header information is posted at the top of the body of the
message in raw form
- the message is posted again (though screwed up as mentioned above) on the
local base, even though it's already there.
- the in-memory pointers for the base get scrambled when releasing a message
to the net, so that the software thinks all of the messages have been deleted,
requiring you to leave the base and return to it to go on to the next message.
Status: Verified/Fix not yet
attempted
Reported by: Dark_Dude@darkcastle.ecore.fnet.org
Date
Reported: 07/04/96
File affected: 1/MSG.POSTMSG.L Version:
2.2.6b
File affected: 1/MSG.BASE.S Version:
1.3.3b
Description of bug:
FV fails to warn the user that Usenet
messages won't show up right away when they post them.
Submit a bug report
Back to the METAL/FV page