Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to [ADM] EchoList Access Conference...  <--  <--- Return to Home Page
   Networked Database  [ADM] EchoList Access Conference...   [374 / 525] RSS
 From   To   Subject   Date/Time 
Message   Ben Ritchey    All   Echolist Maintenance   March 11, 2017
 10:28 PM *  

Hi All,

The extended maintenance on the Echolist is nearing completion, thanks for your
 
patience. :)

Due to numerous and frequent Database corruptions, and the lack of support for 
the existing system (Echobase 3.48, now deprecated, author abandoned), the 
decision was made to fix it once and for all. I decided to reverse-engineer the
 
Database and re-write the software from the ground up (no source). This 
endeavor has completed an Alpha stage and is entering a Beta stage for extended
 
testing. Once complete, it will be brought online with 99% transparency to the 
previous system.

All existing Mod Add/Upd/Del submissions will work as before. The only major 
change is the lack of a Rules sub-system which can/may be added later depending
 
on feedback received {g}. Existing RULE keywords will just be ignored as will 
anything else that doesn't apply to existing keyword formats.

Important keyword errors (such as missing required keywords) will be reported 
in ELIST. ALL submissions will be reported in the ELIST conference, successful 
AND errors alike. Email/Netmail replies will NOT be sent out at first, subject 
to change, of course. :)

The only enhancement so far, aside from new reporting formats, is the ability 
to Delete or Clear applicable fields, simply by entering a line with JUST the 
appropriate keyword, by itself.

The main advantage here, obviously, is the availability of source code and the 
ability to make timely changes as needed, as FIDOnet evolves. Any and all 
feedback/problems should be reported in the ECHOLIST conference. As noted, 
ELIST is strictly for the MaintBot replies.

p.s. for those interested, EList v4 is being coded in PowerBASIC CC v5 :) and 
no, for now, the source code is not being distributed. {chuckle}


.- Keep the faith, --------------------------------------------------.
|                                                                    |
|    Ben  aka cMech  Web: http|ftpinkp|telnet://cmech.dynip.com    |
|                  Email: fido4cmech(at)lusfiber.net                 |
|    (:)       Home page: http://cmech.dynip.com/homepage/           |
`----------- WildCat! Board 24/7  +1-337-984-4794  any BAUD 8,N,1 ---'

... Insanity is hereditary - you get it from your kids.
--- GoldED+/W32-MSVC v1.1.5-b20161221 ... via Mystic BBS!
 * Origin: FIDONet - The Positronium Repository (1:393/68)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to [ADM] EchoList Access Conference...  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.0752 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_50vjjq53c942l820aie949ijh2, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_50vjjq53c942l820aie949ijh2, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_50vjjq53c942l820aie949ijh2, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0