Category : BBS Programs+Doors
Archive   : THDUTL52.ZIP
Filename : PROCESS.DAT

 
Output of file : PROCESS.DAT contained in archive : THDUTL52.ZIP

THDUTL V3.00 B03 and later, will provide an error message with the
process and situation indicated. The program will also list one or
two files which were currently or recently used. Find the specific
situation below and refer to the process to determine the problem.

Process = What the program was doing at the time of the error.
The files used in the process are indicated.

Sutuation = The specific error encountered during the process.
If others are noted, advise HD.

Files = The two most recent files used by the program. These
variables are NOT cleared when a file is closed and
may point to a file not currently open.

Processes

1. Initialization: Read the configuration and check command line
switches.
THDUTL.CFG
COMMAND LINE

2. If /U is indicated, check default archive and excluded files.
SYSDAT1.DAT
THDUTL.ACX

3. Get the doors list, open the work file and recover the data from
previous runs. Set colors.
DOORS.MNU
THDUTL.WRK
THDUTL.TIM
THDUTL.CLR

4. Open the CALLERS.LOG and if indicated with /T, trim it to length.
If /ST is indicated, put excess in CALLERS.TRM.
CALLERS.LOG
CALLERS.TRM
TMP

5. Retrieve the Door tally data and check for callers to be excluded
for last 15.
THDUTL.DOR
THDUTL.XCL

6. Retrieve the file area paths and upload/download .LST paths. Input
the files-check list and the previous Download/Upload and File counts
for the Top 15
FAREA.DAT
THDUTL.CHK
THDUTL.DLD
THDUTL.UPL
THDUTL.FIL

7. Main process (loop). Start reading the CALLERS.LOG at marked location.
Process downloads as occurring and save the upload information.
UPCHK.DAT
UPLOAD.DAT

8. Build the Last 15 Callers screen and save the data in THDUTL.WRK.
THDUTL.WRK
BULLET1


9. Build the Door tally screen and save the data in THDUTL.DOR.
BULLET2
THDUTL.DOR

10. Build the New users screen and save the data in THDUTL.GUY.
THDUTL.GUY
BULLET3

11. Build the Top 15 screen and save the data in .DLT, .UPL and .FIL.
THDUTL.DLD
THDUTL.UPL
THDUTL.FIL
THDUTL.TTX
BULLET4

12. Build the BBS hourly usage screen and save the data in THDUTL.TIM.
THDUTL.TIM
BULLET5

13. Do Download tracking. Find the file in the .IDX file if available,
else look for it in the .LST file. Increment the # download counter
and rewrite the .LST file with the new data. If this is a special
download listed in FILES.LST, track it in FILECHK.DAT.
THDUTL.LOG
INDEX FILES
FILES.LST
TMP
FILECHK.DAT

14. Screen building subroutine. Print data to one of the BULLET files.

15. Getting new callers City. Open USERS.DAT and find the user name,
extract the City and State and Alias.
USERS.DAT

16. Identifying New caller. Add new data to stored variables.

17. Checking Uploads. Add the file to UPLOAD.DAT, if the /U switch is
used, extract the archive to \$TMP, do virus check on all files in
the archive, repack the files in the default archive, add the ZIP
comment file if available. Build DESC.SDI file and add to archive.
Archive programs must be in path.
UPCHK.DAT
THDUTL.ACX
\$TMP\$TMP.TMP
UPLOAD .LST
DESC.SDI/FILE_ID.DIZ
THDUTL.MSG
$T

18. Tallying usage time. Increment a counter for the hour.

19. Get real user's name if /R switch is set.
USERS.DAT

20. Update the FILES.LST for Uploaded files.
FILES.LST


Sutuations

1-6 Data manipulation error. The data was not in the range expected.
Check the data files in the process indicated.

7 Out of memory, oops!

9 Subscript out of range. Volume of data was larger (or less then 0),
than expected. Check the CALLERS.LOG for garbled data.

11 Division by Zero. Data out of range. Not serious. ignore.


14 String memory space problems. Call HD, the program failed.

24-25 Device timeout. Unable to access Disk. Check hardware.

52-55 File access problem. File does not exist or file already being
used. Check required THDUTL files indicated for the process.
Check FILES.LST files.

58 File already exist. Attempt to create an existant file.

61 Disk full.

62-63 Input past end. A file contained less than expected amount of data.
Check indicated THDUTL files for the process.

64 Bad filename. An expected file was not found. Ensure required
files for the process are present.

68 Device unavailable. Attempted to access a nonexistant drive.
Check path indications in your File Area section.

71-72 Disk not ready/failure error.

75-76 Path/file access error. Attempt to access a nonexistant path.
Check paths in File Area section.




  3 Responses to “Category : BBS Programs+Doors
Archive   : THDUTL52.ZIP
Filename : PROCESS.DAT

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/