OS/2 Shareware BBS: 2 BBS/02-BBS.zip/geo300a1.zip/NOTEWORK.DOC

Text File | 1996-05-10 | 13KB | 258 lines

______________________________________________________________________

        Notes for GoldED "Firebird" 3.00.Alpha1, May 10th 1996.
______________________________________________________________________

* Welcome to the first GoldED 3.00 Alpha version!  It may not appear
  to have many changes or news on the surface, for such a large
  version jump, but a lot has happened under the surface, and a lot
  more will happen before the final release. Please keep in mind that
  this is very very early in the development phase, and some features
  may be broken or may work slightly differently than you were used to
  from version 2.50.

  NOTE: Discussion of Alpha and Beta versions should be kept in the
  GOLDED.BETA echo. There are no restrictions on who may run the Alpha
  and Beta versions.

  DISTRIBUTION: Please DON'T distribute this via automatic file
  distribution systems. It is likely that a lot of alphas will appear
  over time, and it would be an unnecessary load on the file
  distribution systems, in my opinion. The latest versions are always
  available on my BBS and the FTP site ftp.winet.dk/goldware. Check
  out my homepage on http://www.winet.dk/goldware for the latest news.

* The new Win32 version is currently compiled with Borland C++ 4.02
  using the PowerPack. This means that it will also run as a DOS
  extended version under clean DOS or in an OS/2 DOS box. If you want
  to try that, you must have the files 32RTM.EXE and DPMI32VM.OVL in
  the current directory or the PATH. If you don't have these files,
  get BC4_RTM.ZIP from the place where you got GoldED. If you run
  GoldED/W32 as a DOS extended program, you may find that it uses 100%
  CPU. This is because of what I perceive as a bug in the Borland
  Win32 API simulator. If it bothers you, switch GoldED to use
  blocking keyboard mode. The price is that the statusline clock stops
  and the editor autosave doesn't work when you are not using the
  keyboard.

+ Added a "twirly" (rotating character) during configuration
  compilation. It is currently only working during the GOLDED.CFG
  compile, so it will stop twirling in a short period while the rest
  of the configuration files are being compiled.

+ Added option to uuencode imported files!  This works in the file
  import feature of the internal editor. To uuencode a file while
  importing it, simply put a '#' character in front of the filename.

  Example: #WHATEVER.ZIP    - Will import as:

    begin 644 WHATEVER.ZIP
    [uuencoded data]
    end

  NOTE: This is a very simple implementation of uuencode. It cannot
  split large files over several messages. The file mode number 644 is
  hard-coded and has nothing to do with the actual file mode.

  WARNING: Due to memory constraints, the standard 16-bit DOS version
  of GoldED is usually not able to deal with messages much larger than
  about 10-16k. You can very quickly reach that size when uuencoding
  files. For this reason, you should not use this feature unless you
  are running one of the 32-bit versions (DOS-386, OS/2 or Win32).

- When GoldED looked for a tagline in a message, it was a bit too
  agressive and could find it up in the text in some circumstances,
  causing it to move it down where taglines are normally found. The
  logic has now been changed to this: A line which begins with "..."
  or "___" is a considered a tagline if 1) it is the last line in the
  message or 2) if it is the line just above the tearline or 3) if it
  is the line just above the origin.

! GoldED will no longer update the "times read" field in netmails each
  time the netmails are read. This will give better performance when
  reading netmails, especially for netmail areas in the Squish format.

! In search strings, the character '&' is now reserved as the "and"
  operator (where '|' is the "or" operator). Note however, that the
  "and" search method is *not* yet implemented.

+ AREAFILE PCBoard has been updated to be able to read the FidoNet
  configuration of version 15.22. Version 15.21 is still supported.
  AREAFILE PCBoard now also gets the *.MSG netmail area.

+ The PCBoard mail waiting flags are now updated when you write
  messages to people named in the userbase.

- When deleting a message in a PCBoard area, the area would become
  partially damaged, resulting in a loss of messages when it was later
  packed.

! Changed the implementation of changing a message in a PCBoard area.
  Now when a message is changed, the new edition is saved as if it
  were a new message, with a new message number, and then the old
  edition is deleted. For technical reasons, after you have saved the
  changed message, you will see the old edition with the DEL attribute
  set. The new edition will be at the end of the messages in the
  area. The deleted old edition will go away when you exit the area.
  This behaviour is consistent with the way PCBoard itself works when
  changing a message.

+ The PCBoard "username@tofidoaddress" method is now used for
  addressing netmails in PCBoard format. The "+C" and "+D" flags are
  also supported, and so is the "[fromfidoakaaddress]".

    Example: Joe Sysop@1:234/567 +C +D [2:236/77]

  GoldED will hide the details from you, so instead of the cryptic
  form shown in the example, you will see the name, addresses and
  flags in the expected places and in the expected form in the header
  display. You must *not* enter the cryptic form by hand!

! The "FidoPCB" method of putting addresses and attributes in the
  first one or two lines of the message is no longer supported.

- Added some additional debugging stuff which will hopefully aid in
  locating that nasty "pointer underrun" bug. Please send me log cuts
  if you get underruns.

+ AREAFILE RemoteAccess now also supports RA 2.50 Gamma. Not tested.

- If a SOUP packet contained a message with a Message-ID or Reference
  headerline which started with "<NOMSGID", GoldED would enter an
  infinite loop.

- GoldED would crash if it tried to load a zero-byte *.MSG file.

+ New keyword FRQNODEMAP <to-node> <from-node>. This keyword is used
  for the file request feature (Ctrl-F). It allows you to define
  mappings from a nodenumber used in a file announcement to another
  nodenumber. This is useful in the cases where a multi-line system
  announces files using their primary nodenumber, which may be a
  regular V34 modem number, but they also have an ISDN number, which
  you would prefer to use instead. Examples:

    //         change-to: from:
    FRQNODEMAP 2:236/99   2:236/100
    FRQNODEMAP 2:236/1043 2:236/43

  So, if I saw a file announcement from 2:236/100, and requested some
  files, the request would automatically be addressed to 2:236/99.

- If you hard-deleted a soft-deleted message (one marked "DEL") in
  a JAM area, GoldED would mistakenly count down the active msgs
  counter in the JAM base header. GoldED doesn't rely on this counter
  for anything, so it would not be affected itself.

- The trick for preventing processing of an Internet address as
  template tokens did not work for the token types labeled as
  "conditional" and "insert" in the manual. It will work now. For
  example, "testing@@new.net" will now be properly converted to
  "[e-mail]". Earlier that line would be ignored unless you
  were writing a new message, and even then it would look wrong.

+ The input fields are now capable of editing data that is longer than
  the width of the field on the screen. This means that you can now
  enter long Internet addresses. Note however, that even though you
  can now also enter a very long name or subject in regular FidoNet
  mail, the messagebase may have limits that in effect truncates the
  name. Most messagebases limits names to about 35 chars and subjects
  to about 70 chars. Internally in GoldED the current limit for names
  and subjects is 127 chars. In comparison, the limit in JAM is 100
  chars and in PCBoard it is 120 chars.

  NOTE: The new implementation of the input fields is not 100%
  complete and full-featured (compared to the old implementation), but
  it will do the job for now. Comments and suggestions are welcome.

+ The WildCat! 4.x messagebase format is now supported. There is not
  yet any AREAFILE WildCat. You must define the areas by hand using
  the AREADEF keyword, like this:

    AREADEF MYTEST "My Test" 0 Echo WCat <path\basename> etc.

  There is also a new keyword WILDCATUSERNO, which works just like the
  other <msgbase>USERNO keywords. By default GoldED will use the first
  record in the lastread file (*.LRD), so if you are not the first
  person in the userbase, or you are sharing the messagebase with
  others, you may have to change this user number. The userbase is
  currently not supported (ie: you can't set the number to -1 to let
  GoldED find the correct user and lastread automatically).

  NOTE: The WildCat support is currently not very well-tested, so use
  it with caution. In my limited testing, I have not found it to be
  damaging the messagebase, but you should probably test it on less
  important areas and/or make backups until it is determined that it
  is safe.

  Please read GOLDWCAT.DOC for important notes about the current
  implementation.

+ The AdeptXBBS messagebase format is now supported. You can use
  AREAFILE AdeptXBBS to let GoldED automatically get all your areas.
  You can also define the areas by hand using the AREADEF keyword,
  like this:

    AREADEF MYTEST "My Test" 0 Echo XBBS <path\basename> etc.

  If you don't use AREAFILE AdeptXBBS, you must set the new keyword
  ADEPTXBBSPATH <path> to the path where you keep your AdeptXBBS.

  There is also a new keyword ADEPTXBBSUSERNO, which works just like
  the other <msgbase>USERNO keywords. By default GoldED will use the
  first record in the userfile and lastreads. If you are not the first
  user in the userfile, or are sharing the messagebase with other
  GoldED users, you must either set this keyword to -1, or use a
  different number for each user. Each user must be defined in the
  userbase.

  Please read GOLDXBBS.DOC for important notes about the current
  implementation.

+ A new Win32 API based console (text) mode version has been added to
  the GoldED family: GoldED/W32. It will run under Windows NT and
  Windows 95 as a textmode application. Note that the screen update
  speed may seem slow, especially under Windows 95. This is because
  screen access has to go through some fairly complex (Win32) API
  functions, which are designed to hide the underlying screen access
  method and thus have a lot of overhead compared to direct screen
  access under DOS or even the simpler API under OS/2.

  Known limitations/problems/bugs in the Win32 version:

  - Can't change the screen mode (like from 25 to 43/50 lines).
  - Can't change the border (overscan) color.
  - Can't switch between blinking and intense colors.
  - Can't change the palette.
  - Some keystrokes may not give the key you wanted.
  - Turning on caps lock will also shift the numeric keys.
  - Shelling to the OS may not work.
  - No sound support, except for the standard beeping effects.
  - Standard beeping effects may not be working under Windows 95.

  Also, there seems to be a bug somewhere that in some circumstances
  causes GoldED/W32 to crash during exit of the program.

- If the nodelist index was missing, the screen would get messed up.

+ The AREALISTSCAN keyword now accepts an additional parameter,
  [-Delete], which will cause GoldED to delete the list file after
  scanning the areas in it. For example, if your mail processor
  generates a list of the areas that it tossed new mail to, you could
  add the list as a menu item on the scanning menu and use it to scan
  only those areas with new mail. Note that some mail processors
  automatically delete their list after using it for replylinking. You
  may want to do some creative stuff with batchfiles to grab a copy.

- There was a problem with garbled dates in the logfile, when GoldED
  exited to report a problem.

- In the new GOLDLANG.CFG for version 2.50, there was a lanuage item
  with text like this: "blabla. \"EXIT\" blabla". But the \" was not
  substituted with a single " as it should have been. Now it is.

______________________________________________________________________

    Previous notes were for GoldED 2.50 Public Release and older.
______________________________________________________________________