旼컴컴컴컴컴컴컴컴컴� � � � UpLoadProcessor Revision History File � � � � � � � � � � 靈캠 � � � � � � � � � � The following is a list of the most � 聃컴� � 봬캭 � � recent changes made to the ULP system � � � � by revision level, in reverse order. 읕컴컴컴컴컴컴컴컴컴� � 袴袴袴袴袴袴袴袴袴袴� * NOTE: I've gotten several questions regarding ARJ SFX archives and ULP's inability to detect them. This is not a limitation of ULP, but bugs in ARJ versions 2.21, 2.21a and 2.22. The ARJ SFX signature was not inserted into the ARJ SFX header, therefore no program relying on this signature (such as ULP) cannot detect ARJ SFXs created with these versions. Versions 2.20 and 2.30 correctly insert the signature. 0.96� - A fault in the duplication system appeared on my system recently, (9/6/92) forcing a change in the database file format. Unfortunately, existing databases cannot be converted, as one piece of information required is not maintained. Hence, it will be necessary to regenerate the duplication database. Also, you will note the database will be about 60% larger in size. There is good news: the scanning routine is greatly improved (3 to 5 times faster by one user's estimation), which should greatly reduce the time required to rebuild the database, especially systems running CD-ROMs and/or LANs. This change will also allow development of a purge function for removing old CRCs from the database. NOTE: The FWKCS import function still works if you would like to import old data into your database for improved integrity. The ZDCS import function has been disabled until I can work on deciphering the database (I need to see if the information required is available). CONFIGURATION FILE CHANGE!!! ULP and ULPTEST can now be forced to pass, without testing, specific files defined by file extension. This is intended to be used for non-DOS files such as Unix Tar Z and Macintosh files that some boards accept. Refer to the NO_PROC_EXT for more information. ULP, ULPTEST and ULPDB now check the drive specified in WORK_DIR to insure there is enough space left for 4 times the size of the archive being processed. This will help prevent unpacking errors on RAM disks. If there is not sufficient space, it will unpack on the drive where the file is located (a warning for CD-ROM users). Note that you MUST include the drive spec in the WORK_DIR parameter, if used. CONFIGURATION FILE CHANGE!!! ULP, ULPTEST and ULPDB are now capable of swapping themselves out of memory when executing external programs. While I have taken great pains to keep ULP's memory requirements low (128K typical), small DESQview windows can be difficult to work in, especially with programs like ARJ that have large memory requirements. Using the SWAP parameter in the configuration file, the ULP programs will swap to EMS, XMS and disk (in that order). ULP and ULPTEST now check the number of subdirectory levels contained in an ARJ archive that has embedded pathspecs. If all files contained within are at the same level, the file will be processed without regard to paths. If there are varying levels, then it will be rejected as before for embedded paths. The reasoning for this is that ARJ includes pathspecs by default, and many users who upload using ARJ don't realize it. If this seems like a good idea to incorporate on ZIP archives, let me know. I'm undecided since a person has to consciously force pathspecs to be kept in a ZIP file; logic would indicate that the person had a reason for doing so. The age checking has been changed to fail an archive for average age. This change was made because occasionally a user would upload an old archive, but after having tinkered with a file (e.g. a configuration file), resulting in it being incorrectly passed. Instead of the file being rejected based solely upon the newest file date, an average age is now calculated, and if the average is greater than AGE_LIMIT, the archive will be rejected. ULPDB can now merge two ULP CRC-32 databases together, using the -M command line switch. This will be used to develop pre-built CRC databases for CD-ROM disk that sysops can merge with their existing CRC databases for fast installation. ULP, ULPTEST and ULPDB now check the temporary subdirectory prior to unpacking for stray files and deleting if necessary. This is needed if one of these programs hangs or is aborted for some reason, since unpacked files may be left behind. ULPDB will now add unknown format files to the CRC database when discovered. Previously, these files would not be added, resulting in various .DOC, .TXT, .MAC, etc. files from being included in the database. ARJ SFX archives would always fail the screening process. Fixed. More recoding for improved speed and efficiency. Also, Salt Air (PCBoard Support BBS) has granted me an ULP support conference on their system. It is conference #42, and I will be monitoring it at least twice per week. 0.95� - The ULP programs now operate off of a binary configuration file (7/30/92) generated by the ULPCFG program. In it's current incarnation, ULPCFG simply reads in your existing text configuration file and outputs a binary version (don't remove your text version though; it will be needed to make configuration changes). However, by doing so, ULPCFG does extensive data checking searching for common configuration errors. This program will be evolving over the next few revisions into a full-fledged configuration program, eliminating the text file entirely. NOTE: please implement all configuration file changes into your text configuration prior to running ULPCFG. (ULPCFG syntax: ULPCFG -TULP.CFG -CULP.BIN) After answering some questions about ULP registration codes, the absurdity of having 2 codes dawned on me since nothing would change if I only had a single code. However, a benefit to having a single code would make changing executable types easier. Beginning with this version, only the 086+ registration code is required for all versions. CONFIGURATION FILE CHANGE!!! ULP is now capable of updating your DOWNLOAD.TXT file with the correct extension if the archive format has been changed during processing. This feature will allow utilities that scan DOWNLOAD.TXT for file information to reflect correct information. Refer to the UPDATE_DLTXT and DLTXT_FILE parameters in the configuration file. CONFIGURATION FILE CHANGE!!! Against my better judgement, I have installed the ability for ULP to insert BBS ads. To me, this seems hypocritical, given the ability of ULP to remove the damned things. However, the request has been made many times, so I have added the ability. I STRONGLY recommend against them; BBS ads are aggravating to other sysops, so please be considerate and use the ARJ or ZIP comment instead. Refer to the BBS_AD_FILE parameter, which is commented out by default. CONFIGURATION FILE CHANGE!!! The DEST_HDR parameter is no longer required. Delete it from your text configuration file, or else problems will result. ULP and ULPTEST now use the WORK_DIR subdirectory as the base directory for temporary file storage during processing. This can be set to a RAM disk for greater speed and less hard disk wear and tear. However, be careful that you have enough free RAM disk space to decompress a large archive, or the file will be failed as an unpacking error. ULPDB can now import ZDCS databases as well as FWKCS databases into an ULP database for ease of installation and transition from a previous system. See the '-I' command line switch in the documentation. ULPDB now requires much less memory to compile the database under most conditions, allowing use in low memory situations such as small DESQview windows. ULP now retains the original archive date and time when running in mass conversion mode (-M) versus stamping the file with the conversion date and time. ULP and ULPTEST now maintain the file date and time stamps on the files when copying. Before, sysops wanting to date their archives with the newest file date instead of the current date (for example, using the '-o' parameter for PKZIP), was getting the date stomped by my file-copying routine. Fixed. The ULP programs could not use a root directory for any of the pathspec parameters. The only place this usually posed a problem was RAM disks being used for the work directory, and just specifying something like "D:\" would cause ULP to choke. In addition, the ULP programs will attempt to create the work subdirectory if not found upon startup. This will also benefit the use of RAM disks for ULP programs. ULPDB 0.94� had a bug where the CRC database index file would be written with 0 for the indeces under certain conditions. Fixed, and was generally distributed as ULPDB 0.94�1. ULP had a bug in which if an archiver command line containing the DOS redirection character '<' was incorrect or the process failed, ULP would remove the original files, create 0-byte files in the destination directory and log huge files sizes in the log file. Fixed a data-damaging bug, however, some of the problem was tracked to DR-DOS not handling redirection the same as MS-DOS. DR-DOS requires a space before and after the redirection character; this is not required with MS-DOS. For example: ARC_PACK pkzip -a -ex -z