home *** CD-ROM | disk | FTP | other *** search
Text File | 1998-12-30 | 50.4 KB | 1,149 lines |
- --------------------------------------------------------------------------------
-
- Finished
- --------------------------------------------------------------------------------
- Type : Bug
- Fixed in : 5.12.006
- Fixed on : 19-12-98
- Reported by : James Samuel <james@polbbs.force9.net>
- Reported on : 24-11-98
- Short description : The section on the internet features is not adequate
- Author's notes : A detailed description of how to use ALLFIX to
- send all Fidonet files via the internet to
- downlinks and uplinks has been published on the
- website. A reference to the website has been
- added to the documentation.
-
- Type : Bug
- Fixed in : 5.12.006
- Fixed on : 15-12-98
- Reported by : John Souvestre
- Reported on : 04-12-98
- Short description : Errors creating ZIC files not logged
- Long description : When ALLFIX encountered a problem creating ZIC
- files, nothing was logged. Instead, ALLFIX sent
- the files normally with a TIC file, but not
- compressed into a ZIC archive.
-
- Type : Bug
- Fixed in : 5.12.006
- Fixed on : 15-12-98
- Reported by : Dave Davidson <dad50@primary.net>
- Reported on : 12-12-98
- Short description : Problem with filename in List files
- Long description : FixUtil CompileRequestIdx has a problem when a
- list file contains a filename or something else
- that is not a directory.
-
- Type : Bug
- Fixed in : 5.12.006
- Fixed on : 15-12-98
- Reported by : Tommi Koivula
- Reported on : 13-12-98
- Short description : ALLFIX does not encode files freq'ed from a CD-ROM.
- Author's notes : I'm not 100% sure if this problem has been fixed.
- I believe I know what causes this problem.
- However, since it is not reproducable on my
- machine, I can not confirm that it has been fixed.
-
- Type : Bug
- Fixed in : 5.12.006
- Fixed on : 15-12-98
- Reported by : Paul Yanchenko
- Reported on : 15-12-98
- Short description : Temporary file not cleaned up
- Long description : Paul reports: "1. When I do: Fileecho
- system/LongDesc options/Show example, in the
- temporary
- dir remains a file "files.tmp" with this example."
-
- Type : Bug
- Fixed in : 5.12.006
- Fixed on : 15-12-98
- Reported by : Harald Harms
- Reported on : 15-12-98
- Short description : ALLFIX hangs
- Long description : ALLFIX hangs when it tries to create an email
- message in a directory that does not exist.
-
- Type : Bug
- Fixed in : 5.12.006
- Fixed on : 19-12-98
- Reported by : Harald Harms
- Reported on : 19-12-98
- Short description : Add ability to "freq" AreaMgr services to documentat and website
- Long description : The documentation does not explain that it is
- possible to file request the following "AreaMgr"
- services:
-
- %LIST,
- %UNLISTED,
- %STATUS,
- %QUERY, and
- %HELP
-
- Type : Bug
- Fixed in : 5.12.006
- Fixed on : 24-12-98
- Reported by : Harald Harms
- Reported on : 24-12-98
- Short description : Not processing entire email message
- Long description : ALLFIX was not processing the last line of email
- messages in Outlook and Soup.
-
- Type : Bug
- Fixed in : 5.12.005
- Fixed on : 17-11-98
- Reported by : Joaquim Homrighausen
- Reported on : 17-11-98
- Short description : ALLFIX and ASETUP are not placing all of their temporary files in the TMP directory
-
- Type : Bug
- Fixed in : 5.12.005
- Fixed on : 17-11-98
- Reported by : Gert Schinkel
- Reported on : 17-11-98
- Short description : The RP should not touch CD-ROM drives at all, if possible.
- Author's notes : This is actually a request for change, but I
- decided to implement it anyway. The problem is
- that on large systems, the request processor in
- ALLFIX is simply too slow. Even using the index
- files does not solve the problem. The primary
- reason is that ALLFIX is still scanning the
- harddisk and the CD-ROMs for the files. This has
- been changed so that only the disks are only
- scanned for the file descriptions, which are
- usually located on the harddrive. The request
- processor has become considerably faster,
- especially if you have CD-ROMs online.
-
- It is necessary to run FIXUTIL CompileRequestIDX
- again. Before you do, delete the old one
- (REQUEST.IDX and FIX) just to make sure that the
- file is recompiled completely.
-
- Type : Bug
- Fixed in : 5.12.005
- Fixed on : 28-11-98
- Reported by : Cristoffer Crusell
- Reported on : 20-11-98
- Short description : TOBEREP.* files are not deleted after writing all new file reports
-
- Type : Bug
- Fixed in : 5.12.005
- Fixed on : 24-11-98
- Reported by : Harald Harms
- Reported on : 23-11-98
- Short description : Day and month in emails should not be in all capital letters
-
- Type : Bug
- Fixed in : 5.12.005
- Fixed on : 29-11-98
- Reported by : Berry van Hombeeck
- Reported on : 24-11-98
- Short description : FIXUTIL Allfiles not working with RA 2.02 if file areas not sequentially numbered.
- Long description : Berry reports:
-
- "2) Something goes wrong with converting the
- RemoteAccess 2.02 filebase =
- to Allfix. In my filebase not all areanumbers
- are taken (for example, I =
- have area nrs 1 till 5 and then 20 till 25).
- When I do "FCOMP 6 D:\RA"=
- the areas are put in a list from 1 till 10 as we
- can see in the ALLFILES =
- section of ASETUP. Whenever an Allfiles list is
- created using "FIXUTIL =
- ALLFILES", the aretags all get screwed up and
- some areas are not listed =
- at all. If I rearrange all my fileareas from 1
- till 10, everything is =
- OK."
- Author's notes : The actual problem was due to Berry using BBS
- parameter 6 instead of 15. However, I did uncover
- a small problem that resulted in the file area
- name sometimes ending up empty, even though there
- were no apparent mistakes in the template. This
- has been solved.
-
- Type : Bug
- Fixed in : 5.12.005
- Fixed on : 28-11-98
- Reported by : Arthur Stark
- Reported on : 25-11-98
- Short description : Access violation when editing the system list
- Long description : Arthur reports:
-
- "While resetting up allfix and all my file echos
- I ran into a buglet. True one
- this time as Scott Drake tested it out via beta 2
- under both OS/2 & WIndows as
- well. When selecting the systems in a file echo,
- if you hit esc after choosing
- the sysop option allfix exits out with this error:
-
- Access violation, program aborted.
- Error address : $000B5844
-
- I am using ALLFIX/Universal Beta 4
-
- It also does this both under OS/2 sessions and
- DOS VDM sessions over here..."
-
- Type : Bug
- Fixed in : 5.12.005
- Fixed on : 26-11-98
- Reported by : Harald Harms
- Reported on : 26-11-98
- Short description : Outlook support not working properly
- Long description : The Outlook support was not working properly.
-
- The index files were not being updated correctly
- when writing new messages. Deleting messages in
- the message bases was also not working correctly.
- Author's notes : Everything has been fixed, except for one little
- thing. I have not been able to figure out Outlook
- codes it's sent and received dates. It uses a
- method different from what I have seen before.
- Since the dates do not really have an important
- function, I do not consider this problem to be a
- show stopper. I will continue to try to figure
- out the method they use, and once I do, I will
- fix the problem.
-
- Type : Bug
- Fixed in : 5.12.005
- Fixed on : 29-11-98
- Reported by : Harald Harms
- Reported on : 29-11-98
- Short description : Error editing system list in Fileecho manager
- Long description : When editing an entry in the System list, it is
- possible to delete that entry by clearing the Aka
- field. Doing so, however, corrupted the System
- list and also the way it was displayed on the
- screen.
-
- Type : Bug
- Fixed in : 5.12.004
- Fixed on : 06-11-98
- Reported by : Jeff Shrunk
- Reported on : 28-08-98
- Short description : Outlook support not working
- Long description : ALLFIX is creating outgoing messages, but Outlook
- is not "seeing" them and not sending them out. It
- appears that ALLFIX marks the messages as "sent".
-
- Type : Bug
- Fixed in : 5.12.004
- Fixed on : 09-10-98
- Reported by : Mikael Karlsson
- Reported on : 09-10-98
- Short description : Error in LIST template
- Long description : The LIST template shows a "null" entry in the
- section containing the list of fileechos that are
- "pending". This would result in the following:
-
- Fileecho Description
- Date
-
- --------------------------------------------------
- ------------------------
- null @pdesc
-
- Type : Bug
- Fixed in : 5.12.004
- Fixed on : 09-10-98
- Reported by : Harald Harms
- Reported on : 09-10-98
- Short description : Leaving 0 byte files lying around
- Long description : If you take a look at your ALLFIX directory you
- will most likely find one or more zero byte files
- lying around. I have changed ASETUP and ALLFIX so
- that they should delete all 0 byte files. This
- doesn't really serve any purpose other than to
- keep things neat and tidy ;-)
-
- Type : Bug
- Fixed in : 5.12.004
- Fixed on : 17-10-98
- Reported by : Goran Eriksson
- Reported on : 16-10-98
- Short description : AreaMgr reply contains spelling mistake
- Long description : The reply to a change in compression formats
- contains the following text:
-
- "From now _On, all files will be compressed."
-
- Type : Bug
- Fixed in : 5.12.004
- Fixed on : 17-10-98
- Reported by : Harald Harms
- Reported on : 16-10-98
- Short description : All programs are ending with a runtime error, after completing their task
-
- Type : Bug
- Fixed in : 5.12.004
- Fixed on : 22-10-98
- Reported by : Doug Attig
- Reported on : 22-10-98
- Short description : ALLFIX aborts in a runtime error
- Long description : ALLFIX aborts with the following error when
- trying to write a new file report:
-
- Invalid pointer operation, program aborted.
- Error address : 078F:2FDA
-
- Type : Bug
- Fixed in : 5.12.004
- Fixed on : 02-11-98
- Reported by : Barry Blackford
- Reported on : 24-10-98
- Short description : Scan BadTics and DupeTics directory when a file is missing
- Long description : When processing a TIC file and the accompanying
- archive is missing, it would be logical to check
- the BadTics, DupeTics, and RvcdFile directories,
- since the file may have arrived earlier with or
- without an incorrect TIC file.
-
- Type : Bug
- Fixed in : 5.12.004
- Fixed on : 06-11-98
- Reported by : Harald Harms
- Reported on : 24-10-98
- Short description : Not writing all the new file reports
- Long description : ALLFIX is not writing all of the new reports
- defined in ASETUP. There are several reports set
- up to write new file reports in different
- fileechos, using the PKT system. Only the last
- entry (for that group) is being writting.
-
- Type : Bug
- Fixed in : 5.12.004
- Fixed on : 06-11-98
- Reported by : Darren Parker
- Reported on : 25-10-98
- Short description : Documentation does not explain how to freq files via the internet
-
- Type : Bug
- Fixed in : 5.12.004
- Fixed on : 02-11-98
- Reported by : Harald Harms.
- Reported on : 01-11-98
- Short description : Output from INIUTIL is not hidden in the DOS version of ASETUP
- Author's notes : This as the result of a bug fixed in the
- Universal version.
-
- Type : Bug
- Fixed in : 5.12.004
- Fixed on : 02-11-98
- Reported by : Paul Yanchenko
- Reported on : 01-11-98
- Short description : The Nodes -> Fileechos break down contains cosmetic problems
- Long description : The Nodes -> Fileechos break down does not work
- properly when fileecho names are longer than 12
- characters.
- Author's notes : ASETUP used to generate 4 columns of fileechos
- per node. This has been changed to 2 columns.
-
- Type : Bug
- Fixed in : 5.12.004
- Fixed on : 02-11-98
- Reported by : Harald Harms
- Reported on : 01-11-98
- Short description : ASETUP should clearly indicate that INIUTIL is missing
- Long description : If INIUTIL is missing, ASETUP reports that it
- encountered a problem exporting the data. If
- INIUTIL is missing, then ASETUP should report
- that, so that the user knows what to do about it.
-
- Type : Bug
- Fixed in : 5.12.004
- Fixed on : 06-11-98
- Reported by : Darren Parker <dp@djp.org>
- Reported on : 02-11-98
- Short description : ALLFIX hangs when processing file request via the Internet
- Long description : Darren reports:
-
- "It's now noticing the emails now for freqing,
- but if for example the
- files don't exist then after it searches for
- files and displays '??? Not
- Found', Allfix just freezes.
-
- When it does found the files, it comes up withan
- error, below.
-
- ---cut---
- Heap overflow error, program aborted
- Error address : 14AB:031A
- ---cut---
-
- And then drops to DOS.
-
- I'm running it on Windows95B.
- "
-
- Type : Bug
- Fixed in : 5.12.004
- Fixed on : 02-11-98
- Reported by : Harald Harms
- Reported on : 02-11-98
- Short description : Small cosmetic problem
- Long description : When sending a file without a TIC file, ALLFIX
- would log something like this:
-
- Msg Echoing to 2:281/415.100 (SMTP, )
- Author's notes : This has been changed to:
-
- Msg Echoing to 2:281/415.100 (SMTP, <no TIC
- file>)
-
- Type : Bug
- Fixed in : 5.12.004
- Fixed on : 28-11-98
- Reported by : John Souvestre
- Reported on : 25-11-98
- Short description : F4 search contains a small bug
- Long description : When using the F4 search facility in any of the
- "managers" in ASETUP, it starts searching from
- the current entry. If the text to be searched for
- is contained in the current entry, then ASETUP
- stops searching on the current entry. To fixthis,
- ASETUP should be starting with the search at the
- next entry and not at the current entry.
-
- Type : Bug
- Fixed in : 5.12.003
- Fixed on : 25-08-98
- Reported by : Doug Attig
- Reported on : 11-08-98
- Short description : Heap overflow error with the ANNOUNCE feature
- Author's notes : The memory management routines for the WildCat
- message base have been improved a little,
- hopefully that will prevent these heap-overflow
- problems from occuring again.
-
- Type : Bug
- Fixed in : 5.12.003
- Fixed on : 26-08-98
- Reported by : Goran Eriksson
- Reported on : 24-08-98
- Short description : Deleted echo comes back
- Long description : ALLFIX automatically removed a fileecho when the
- last receiving system disconnected using the
- AreaMgr. After running ASETUP, however, the echo
- has "re-appeared".
- Author's notes : It turns out that the record was only removed
- from the index file and not from the data file.
-
- Type : Bug
- Fixed in : 5.12.003
- Fixed on : 25-08-98
- Reported by : Theo Rosbag, Mike Roark
- Reported on : 25-08-98
- Short description : Run time error in ASETUP
- Long description : Theo reports:
-
- "I've found a bug in Asetup/2 5.12.002 (build 2).
-
- When i go to the System Data -> Pathnames 1
- menu and then return to previous
- menu pressing ESCape , Asetup aborts with the
- following error:
-
- Access Violation, Program aborted
- Error address : $00024A92"
-
- Type : Bug
- Fixed in : 5.12.003
- Fixed on : 26-08-98
- Reported by : Theo Rosbag
- Reported on : 25-08-98
- Short description : File request reports are not being sent out
- Long description : Theo reports:
-
- "Maybe i'm wrong , but when somebody requests
- some files , Allfix sends normally
- a netmail to that particular system .
- Allfix will write this message but it will not be
- send to that system directly
- , after all the files are send that specific
- netmail will stay on my system
- and my mailer will route that message via my
- uplink .
-
- Allfix/2 5.12 build 1 did this exactly the same .
- Earlier versions of allfix/2 works correct."
-
- HH: What I've noticed here is that my mailer
- often reports that the .PKT file does not exist.
- About half the time this is the case, the other
- half it seems to work fine.
-
- Type : Bug
- Fixed in : 5.12.003
- Fixed on : 26-08-98
- Reported by : Vincent Danen
- Reported on : 25-08-98
- Short description : Using wrong aka in .PKT files
- Long description : When creating PKT files, it appears that ALLFIX
- is always using the main aka, if the fake aka is
- not defined. It is also using the main aka even
- when the "Use aka", for that particular message
- (new file announcement, for example) is different.
- Author's notes : The source of this problem is the Fake Aka field
- (see Network addresses menu). When I built the
- PKT routines, I assumed that everyone would use a
- mail tosser that was capable of overriding the
- security features. GEcho, for example, will toss
- anything located in the Secure inbound directory,
- regardless of where it comes from, if it's a
- dupe, etc. By using such a mail tosser, it does
- not really matter what the Origin address is from
- the PKT files created by ALLFIX. However, plenty
- of people do use GEcho nor do they use a mail
- tosser which supports that feature.
-
- The only way to solve this problem, once and for
- all, is to step down from the Fake Aka concept
- and introduce the Fake point concenpt ;-). It is
- imperative that the Origin address of the PKT
- files is NOT identitical to the Aka used for that
- conference. That was the whole reason I introduce
- the Fake aka. We can accomplish the same thing by
- simply using a different point number.
-
- In the Network addresses menu you will find a new
- field called "Fake pnt". The old "Fake aka" field
- has been removed. Enter a point number in this
- field that will most likely never be used,
- something like 9999, for example. When creating
- PKT files, ALLFIX will use the zone, net, and
- node numbers as defined by the Aka you select for
- that New file report or FileFind request and it
- will use the Fake point as the point number.
-
- The benefits of this solution should be clear.
- Each PKT is written in the proper "zone". And
- point addresses allow unique addressing that will
- not foul up the mail tosser.
-
- Type : Bug
- Fixed in : 5.12.003
- Fixed on : 25-08-98
- Reported by : Harald Harms
- Reported on : 25-08-98
- Short description : Viewing template does not work
- Long description : Viewing a template of the type "new file report"
- does not work.
- Author's notes : This feature did not work if the FILEAREA.FIX
- file was 0 bytes. ASETUP did not display any type
- of error when this occured.
-
- Type : Bug
- Fixed in : 5.12.003
- Fixed on : 27-08-98
- Reported by : Vincent Danen
- Reported on : 27-08-98
- Short description : FCOMP is not stripping all tokens from BBBS file area names
- Long description : The following tokens were not interpreted
- properly:
-
- @e, @b, @u, @1.
-
- @1 defines an alternative list file. FCOMP will
- use that file instead ot the standard
- descript.ion file.
-
- Type : Bug
- Fixed in : 5.12.003
- Fixed on : 27-08-98
- Reported by : Vincent Danen
- Reported on : 27-08-98
- Short description : BBBS supports more than one filedirg.??? file.
- Long description : Since BBBS supports more than one filedirg.???
- file, FCOMP should scan them all, instead of only
- accepting one filename on the commandline. The
- new commandline for BBBS is:
-
- FCOMP 30 <path to filedirg.??? files>
-
- Type : Bug
- Fixed in : 5.12.003
- Fixed on : 27-08-98
- Reported by : Vincent Danen
- Reported on : 27-08-98
- Short description : Descriptions not written on one line
- Long description : BBBS uses descript.ion files, in which the
- descriptions are all written on one line. It was
- up to the user to turn on the "One line LongDesc"
- option. I have changed this by hard-coding the
- "One line LongDesc" feature for people who use
- BBBS.
-
- Type : Bug
- Fixed in : 5.12.002
- Fixed on : 16-08-98
- Reported by : Harald Harms
- Reported on : 06-08-98
- Short description : All files abort in runtime error -132 when finished.
-
- Type : Bug
- Fixed in : 5.12.002
- Fixed on : 16-08-98
- Reported by : Gary Gilmore
- Reported on : 08-08-98
- Short description : Runtime error when updating STQ
- Long description : The following runtime error occurs when hatching
- a file, even though it appears that everything
- was updated properly.
-
- 02:57:10 Msg Updating STQ for 1:115/500
- (A72SJ0G0.TIC)
- 02:57:10 Msg Updating STQ for 1:2410/213
- (A72SJ0G1.TIC)
- 02:57:10 Unknown runtime error #3, program
- aborted.
- 02:57:10 Error address : $0001DAAF
-
- This problem occurs when hatching a file. It
- seems that ALLFIX also writes a new file
- announcement, but that it does not clean up the
- TOBEREP files, because that announcement is being
- made each time ALLFIX runs.
- Author's notes : This is the same error as the "Path not found"
- error in the DOS version of ALLFIX.
-
- Type : Bug
- Fixed in : 5.12.002
- Fixed on : 16-08-98
- Reported by : Gary Gilmore
- Reported on : 10-08-98
- Short description : Incorrect warning message
- Long description : When entering the Pathnames (1) menu for a second
- time, ASETUP always gives the warning that the
- Queue directory must be unique, even if it is,
- and nothing was edited in the menu.
-
- Type : Bug
- Fixed in : 5.12.002
- Fixed on : 16-08-98
- Reported by : Mike Roark
- Reported on : 15-08-98
- Short description : The request processor is aborting with a runtime error
- Long description : The following log sample shows what is going
- wrong.
-
- ? 13 Aug 08:42:59 AFIX Not found: BBSSORT.ZIP
- ? 13 Aug 08:42:59 AFIX Not found: EBBSSORT.ZIP
- ! 13 Aug 08:42:59 AFIX Unknown runtime error
- #654, program aborted.
- ! 13 Aug 08:42:59AFIX Error address : $0002724B
-
- This error also occurs when ALLFIX does find the
- file to send, as shown in the next log sample:
-
- # 13 Aug 18:03:48 AFIX FREQ: flist31.zip
- # 13 Aug 18:03:48 AFIX Send:
- E:\TNT_BBS\FLIST31.ZIP
- ! 13 Aug 18:03:48 AFIX Unknown runtime error
- #654, program aborted.
- ! 13 Aug 18:03:48 AFIX Error address : $0002724B
- Author's notes : This problem is also related to the "Path not
- found" runtime error in the DOS version.
-
- Type : Bug
- Fixed in : 5.12.002
- Fixed on : 16-08-98
- Reported by : Cristoffer Crusell
- Reported on : 16-08-98
- Short description : ALLFIX is deleting TIC files before they are being sent
- Long description : Cristoffer reports:
-
- "I just installed the new beta 12.01 and I was
- curious regarding the STQ
- support. I configured Allfix with my FD and
- hatched some files to my
- downlinks. So far, so good. But when I run
- 'allfix.exe file' a couple of
- minutes later Allfix erases my TIC-files with the
- message 'deleting sent TIC-
- file...'"
-
- Type : Bug
- Fixed in : 5.12.002
- Fixed on : 16-08-98
- Reported by : Larry Eggers
- Reported on : 16-08-98
- Short description : Runtime error "Path not found"
- Long description : Larry reports:
-
- "! 14:49:05 Path not found, program aborted.
- ! 14:49:05 Error address : 0783:8853
-
- The wierd thing about this is that it appears to
- be functioning
- properly when unarchiving a file, but it insists
- on reporting
- that the path wasn't found, even though my ARC
- directory with
- all of the archivers that I have, IS in my path
- statement.
- Other than that, everything else seems to be
- normal."
- Author's notes : This problem was located in the routines that
- write to .PKT files. On my system it occured when
- processing a file request.
-
- Type : Bug
- Fixed in : 5.12.001
- Fixed on : 24-07-98
- Reported by : John Souvestre
- Reported on : 28-06-98
- Short description : Problem with insert-sorting files in the FILES.BBS files.
- Long description : When insert sorting files, it seems that files
- with an extension are always placed before a file
- without an extension. Example:
-
- SEE4CB10.ZIP (this one was added by ALLFIX)
- SEE4F10.ZIP (this one was also added by ALLFIX)
- COPYRGHT
- CSDKL32.ZIP (this one was sorted here by another
- program).
-
-
-
- Type : Bug
- Fixed in : 5.12.001
- Fixed on : 24-07-98
- Reported by : Harald Harms
- Reported on : 02-07-98
- Short description : Problem in the system list
- Long description : In the System list, after exiting the little edit
- window that is used to add and change systems in
- the list, the name of the sysop (last edited)
- appears where a title bar for the System list
- should be.
-
- Type : Bug
- Fixed in : 5.12.001
- Fixed on : 24-07-98
- Reported by : Andreas Soehnel
- Reported on : 05-07-98
- Short description : Copyright date in Information screen says 1997 instead of 1998.
-
- Type : Bug
- Fixed in : 5.12.001
- Fixed on : 24-07-98
- Reported by : John Souvestre
- Reported on : 16-07-98
- Short description : Tic numbers cycle every 7 days instead of 30
- Long description : While fixing a previous problem with the tic file
- names, we tried to make the numbers cycle every
- thirty days. However, we made a mistake, which
- causes the numbers to cycle once every week.
- (These numbers are used to determine the tic file
- name).
-
- Type : Bug
- Fixed in : 5.12.001
- Fixed on : 28-07-98
- Reported by : Harald Harms
- Reported on : 19-07-98
- Short description : HatchSec variable should be more generic
- Author's notes : The HatchSec verb in the .TIC files is used by
- HATCH and ALLFIX to make sure that the files were
- hatched on the local machine and not by someone
- else. The value of the verb is the CRC of the
- Inbound and Netmail directories contactenated
- together in one string. Since this combination is
- relatively unique, the chance that someone
- figures out what your HatchSec is, is very small,
- unless you tell everyone what your directory
- structure is ;-)
-
- Type : Bug
- Fixed in : 5.12.001
- Fixed on : 21-07-98
- Reported by : Harald Harms
- Reported on : 21-07-98
- Short description : Memory problems
- Long description : ASETUP was using a lot of memory in the
- "managers" (ex. the fileecho manager). These
- routines have been optimized a little freeing up
- as much as 30 kb of extra memory.
-
- Type : Bug
- Fixed in : 5.12.001
- Fixed on : 21-07-98
- Reported by : Harald Harms
- Reported on : 21-07-98
- Short description : Memory problems in FCOMP
- Author's notes : There were some problems with the memory
- management in FCOMP that caused problems at
- compile time. I cleaned up quite a few things,
- which means that every BBS type in FCOMP needs to
- be re-tested. Could all of you please keep a
- close eye on FCOMP to see if it is still working
- correctly for your BBS type?
-
- Type : Bug
- Fixed in : 5.12.001
- Fixed on : 29-07-98
- Reported by : Paul Voogd
- Reported on : 21-07-98
- Short description : IniUtil is not working in the Universal version of ASETUP
- Long description : Paul reports (in Dutch):
-
- "Ik gebruik AllFix Universal 5.11 onder OS/2.
- Wanneer ik de export functie
- gebruik ( INIUTIL2 ), dan wordt er niets
- geexporteerd. Ook de screenoutput is
- "garbled". Bovendien wordt er aangegeven dat deze
- utilitygemaakt is voor de
- versie 5.10 build 3. Onder DOS werkt een en ander
- wel."
- Author's notes : The problem was due to the fact that redirecting
- a program's output (namely INIUNITD.EXE's), does
- not work when running ASETUP (Universal) in a DOS
- box under OS/2. I have solved this problem by
- clearing the screen, letting INIUTILD.EXE write
- its output to the screen, and then restoring the
- screen. It's the most elegant solution I could
- come up with.
-
- Type : Bug
- Fixed in : 5.12.001
- Fixed on : 22-07-98
- Reported by : Charles Wootten
- Reported on : 22-07-98
- Short description : Asetup gives an incorrect key message
- Long description : ASETUP, for ALLFIX for WildCat, gives an invalid
- key message, indicating that the key has been
- entered in the wrong field. ASETUP seems to think
- that the key should be entered in the DOS key
- field.
-
- Type : Bug
- Fixed in : 5.12.001
- Fixed on : 30-07-98
- Reported by : Vincent Danen
- Reported on : 24-07-98
- Short description : Problem with .PKT files
- Long description : ALLFIX creates .PKT files that contain messages
- with addresses in more than one ZONE. A .PKT file
- may only contain messages for one zone.
- Author's notes : In order to solve this problem, it was easiest to
- simply have ALLFIX write each new file report
- (because is where the problem occurs) to a unique
- .PKT file.
-
- Type : Bug
- Fixed in : 5.12.001
- Fixed on : 31-07-98
- Reported by : Jan Schiffelers
- Reported on : 31-07-98
- Short description : Wrong default filenames for import options
- Long description : The "Import new file reports" and "Import group
- configuration" both show incorrect "default"
- filenames.
-
- Type : Bug
- Fixed in : 5.12.001
- Fixed on : 31-07-98
- Reported by : Gary Gilmore
- Reported on : 31-07-98
- Short description : Error in .TIC files created by Hatch
- Long description : There is an error in the TIC files created by
- Hatch (Universal version). The TIC file indicates
- that it was created by HATCH/2, which would
- indicate the OS/2 version of Hatch.
-
- Type : Request for change
- Fixed in : 5.12.006
- Fixed on : 16-12-98
- Reported by : Harald Harms
- Reported on : 16-12-98
- Short description : Rename "Message type" to "Email client" in Internet options menu
-
- Type : Request for change
- Fixed in : 5.12.003
- Fixed on : 27-08-98
- Reported by : Vincent Danen
- Reported on : 27-08-98
- Short description : The RP does not work with BBBS mailer.
- Long description : The BBBS mailer uses front slashes instead of
- back slashes in path names. The RP uses back
- slashes, therefore, the response files created by
- ALLFIX can not be used by BBBS.
- Author's notes : In the Request Processor menu, the "Flag mode"
- field has been expanded with one extra option
- namely "BBBS". By selecting BBBS, ALLFIX will use
- the front slashes instead of back slashes in the
- paths written to the response files.
-
- Type : Request for change
- Fixed in : 5.12.002
- Fixed on : 16-08-98
- Reported by : Serge Druzhinin
- Reported on : 10-08-98
- Short description : Add new option to put Tag at end of description, on seperate line
-
- Type : Request for change
- Fixed in : 5.12.001
- Fixed on : 22-07-98
- Reported by : Charles Gaefke
- Reported on : 07-11-97
- Short description : Add warnings in ASETUP for obvious mis-configurations
- Long description : In ASETUP it is possible to make configuration
- mistakes in the pathnames menus that can cause
- lots of problems when ALLFIX is executed. A
- number of warnings in ASETUP would make ALLFIX a
- lot easier to use for first time users.
- Author's notes : Problems occur when the inbound directories are
- used for more settings or when the queue
- directory is used is more than one place. ASETUP
- will check for this, and give the user a warning.
-
- Type : Request for change
- Fixed in : 5.12.001
- Fixed on : 29-07-98
- Reported by : Felix Mueller
- Reported on : 17-11-97
- Short description : Add support for the email client Pegasus
- Author's notes : Usage:
-
- Simply select "Pegasus Mail" as the "message
- type" and fill the directory where the mail files
- are stored in, in the "In queue" field.
-
- Type : Request for change
- Fixed in : 5.12.001
- Fixed on : 06-08-98
- Reported by : Gary Laming
- Reported on : 17-11-97
- Short description : Support the Outlook email client
- Author's notes : Usage:
-
- In the Internet settings menu, enter the path and
- filename of the file where the inbound messages
- are stored in the In Queue field BUT DO NOT ENTER
- THE EXTENSION! Do the same for the file where the
- outbound messages are stored and enter that in
- the Out Queue. Then select as message type
- "Outlook Express".
-
- Type : Request for change
- Fixed in : 5.12.001
- Fixed on : 21-07-98
- Reported by : Tommi Koivula
- Reported on : 23-12-97
- Short description : The "Copy" option is not overall available
- Long description : The "Copy" option (available in HATCH) should
- also be available from the commandline (Hatch)
- and in the normal hatch (Hatch manager) in ASETUP.
-
- Type : Request for change
- Fixed in : 5.12.001
- Fixed on : 21-07-98
- Reported by : Tommi Koivula
- Reported on : 23-12-97
- Short description : New template macros
- Long description : Support the following functions:
-
- @uppercase(), @lowercase(), @capitalize()
-
- Example:
-
- @lowercase(@fileecho)
-
- Type : Request for change
- Fixed in : 5.12.001
- Fixed on : 21-07-98
- Reported by : Serge Druzhinin
- Reported on : 28-12-97
- Short description : New macros for Request processor
- Long description : The Carbon copies of File request reports do not
- contain the name and node number of the person
- who requested those files. There are no macros
- available to include this information in the CC
- reports. Macros that would be handy
- include:@freqfrom
- @freqfromaka
- Author's notes : These two macros are only available in the
- request processor templates.
-
- Type : Request for change
- Fixed in : 5.12.001
- Fixed on : 30-07-98
- Reported by : Steve Bainbridge
- Reported on : 04-01-98
- Short description : Add support for Shotgun's SGmail.
- Author's notes : There wasn't really anything to do. SGMail is a
- FrontDoor style mailer, therefore, if the user
- simply selects FrontDoor, then he can use SGMail
- with ALLFIX. I did add the commandline parameters
- necessary for installing ALLFIX as the external
- request processor to the documentation.
-
- Type : Request for change
- Fixed in : 5.12.001
- Fixed on : 24-07-98
- Reported by : Jesper S÷rensen <yeppe@cyd.liu.se>
- Reported on : 14-01-98
- Short description : Support the TZ environment variable.
- Author's notes : The TZ environment variable can be very complex,
- because it also offers the ability to specify
- when daylight savings time is active. ALLFIX does
- not support that part of the environment variable.
-
- Type : Request for change
- Fixed in : 5.12.001
- Fixed on : 22-07-98
- Reported by : James Samuel
- Reported on : 25-02-98
- Short description : Add RP settings for T-Mail to documentation
-
- Type : Request for change
- Fixed in : 5.12.001
- Fixed on : 26-07-98
- Reported by : Joaquim Homrighausen
- Reported on : 26-02-98
- Short description : Add support for FrontDoor's new STQ
- Author's notes : Usage:
-
- Simply select "FrontDoor STQ" as the mailer in
- the Global options menu.
- Then, make sure to enter the path to the
- FrontDoor system directory in the "Outbound"
- field in the Pathnames (1) menu.
-
- Everything will continue to work as before.
- Re-routing files via the internet works, TIC
- archives work, etc. etc.
-
- Type : Request for change
- Fixed in : 5.12.001
- Fixed on : 28-07-98
- Reported by : Tim Strike
- Reported on : 26-02-98
- Short description : Support Telegard 3.10
- Author's notes : Usage:
-
- FCOMP 32 <path to Telegard system files>
-
- Type : Request for change
- Fixed in : 5.12.001
- Fixed on : 27-07-98
- Reported by : John Souvestre
- Reported on : 11-06-98
- Short description : Alter %RESEND parameters
- Long description : Currently, the %RESEND command only requires the
- name of a file. This leads to problems when more
- than one fileecho points to the same destination
- directory, since ALLFIX scans each fileecho
- sequentially to find the file to resend. One way
- to solve this problem is to change the parameters
- for this command so that the user also has to
- specify the fileecho.
- Author's notes : The %RESEND command has been changed so that the
- fileecho must also be specified. The new format
- is:
-
- %RESEND [fileecho]:[filename]
-
- Where [filename] may contain wildcards.
-
- ALLFIX will check to make sure that the node has
- access to the specified fileecho. It will also
- check to see if the specified files are listed in
- the file database. If that is not the case, then
- the files will not be sent.
-
- Type : Request for change
- Fixed in : 5.12.001
- Fixed on : 21-07-98
- Reported by : Pavel Karakchiev
- Reported on : 23-06-98
- Short description : Add support for Tornado BBS
- Author's notes : Tornado BBS is a FILES.BBS system that is used
- quite a bit in Poland and ex-USSR countries. The
- only thing that needed to be done was add support
- for it to FCOMP.
-
- Type : Request for change
- Fixed in : 5.12.001
- Fixed on : 30-07-98
- Reported by :
- Reported on : 17-07-98
- Short description : Route-via option needs to be finished
- Long description : The "Route-via" option was never finished due to
- some technical problems. The idea for the
- "unfinished" version was that the .TIC files
- would be marked for a particular destination
- system and that the user would have to configure
- the mailer to make sure that the files were
- routed to the proper node.
-
- This has been changed. ALLFIX will now send the
- files via the node, as specified in the Node
- manager. It will use the TIC Pack settings for
- the destination node and also route files via the
- internet or move them to the holding directory if
- necessary. If the files are routed via more than
- one node, then it is important that everyone on
- the route uses ALLFIX, otherwise, the .TIC files
- will simply be processed by the first non-ALLFIX
- node on the route. Other ALLFIX systems will
- recognize that the files are not for him, and
- simply ignore them, and let them pass on to the
- next system.
-
- Type : Request for change
- Fixed in : 5.12.001
- Fixed on : 22-07-98
- Reported by : Vincent Danen (vdanen@softhome.net)
- Reported on : 19-07-98
- Short description : Add support for BBBS
- Author's notes : Usage:
-
- Run FCOMP 30 <path + filename of file area
- configuration file>
- Turn the "One line LongDesc" option on (LongDesc
- options menu).
- Make sure the Use FDB option is turned on for
- every fileecho.
-
- Type : Request for change
- Fixed in : 5.12.001
- Fixed on : 25-07-98
- Reported by : Harald Harms
- Reported on : 25-07-98
- Short description : Three different fields in the pathnames (1) menu have been combined into one field.
- Long description : The Pathnames (1) field contained three fields,
- namely, Outbound, DB Queue, and FileBox, which
- are used to define the outbound directories for
- three different mailers. Since these mailers can
- not be used simultaneously, only one field is
- required. Therefore, the later two have been
- removed. ASETUP will automatically update the
- remaining field "Outbound" if you use D'Bridge or
- T-Mail.
-
- Type : Request for change
- Fixed in : 5.12.001
- Fixed on : 31-07-98
- Reported by : Harald Harms
- Reported on : 31-07-98
- Short description : Do not move files if something goes wrong with hatching
- Long description : In 5.11, ALLFIX would not move a file when the
- HatchSec variable in the .TIC file was incorrect.
- It would be preferable if a file was not moved at
- all, if something goes wrong with Hatching.
- Author's notes : When hatching a file, and something goes wrong,
- the TIC file will be moved to the "bad tics"
- directory and the file will not be moved at all.
-
- --------------------------------------------------------------------------------
- 78 items
-