ProfitPress Mega CDROM2 Shareware Freeware (MSDOS)(1992)(Eng)

home *** CD-ROM | disk | FTP | other *** search

/ ProfitPress Mega CDROM2 …eeware (MSDOS)(1992)(Eng) / ProfitPress-MegaCDROM2.B6I / UTILITY / FILE / CDPSW51D.ZIP / ABOUT.CDP < prev next >

Wrap

Text File | 1991-02-27 | 25.4 KB | 618 lines

The latest shareware release of CDPSW (CDPSW16G) features a new manual, BIGMAN.CDP, complete with a table of contents which we hope will be helpful. Also, the screen colors have been changed to darker hues, which we hope will be easier on the eyes. If you get the registered version of CDP, you will be able to choose whatever colors you like. There are no actual changes to the program. This file contains 3 sections about CDP which were formerly separate files, in an effort to simplify the CDP package. SECTION I History and Revisions --------------------- CDP was originally distributed through regular retail stores in July, 1987, under the name of Directory Assistance (DA), advertised in magazines such as PC WORLD, sold in stores such as Fry's, reviewed (favorably) in PC Magazine (June 28,1988, p. 46). The current CDP is vastly better! It was always a better product than its competition, but the distribution was poorly planned. The product as released was weakened by suppression of features deemed too sophisticated for targeted users, and inclusion of features with what marketers call "sizzle", even though they had no proper place in CDP. CDP is better than its competition. We invite comparisons. The shareware version, CDPSW, was first put on a BBS in March, 1990. Features and Fixes since Shareware Release ------------------------------------------ 03/19/90 VIEW enhancements: AltB - Works as a GOTO BEGINNING MARKED FILE key. If you are in VIEW, CDP will stay in VIEW in the same mode (ASCII or HEX) that VIEW currently has. AltN - Works as GOTO NEXT MARKED FILE. The above keystrokes are extremely convenient for easily viewing in quick succession all the files marked by a FIND command. They operate either outside or inside VIEW. Once you enter VIEW, they stay in VIEW. nG - In VIEW only, nG will move you to line n of the file. A or C - These keystrokes drop an anchor at the current line. B or D - B goes to where anchor A was dropped. D goes to C. 03/31/90 Allowed the DOS PRINT command to work with CDP. CDP by design prevented other TSRs (which Print is) from coming up when CDP is running, on the basis that they might mess up CDP. We have relented on this idea, hoping no one will be foolish enough to bring up another TSR when CDP is doing something on the disk actively (simply bringing up another TSR harms nothing). Note that you can bring CDP up while another program is active on the disk; CDP can perform disk actions anytime that you bring it up. It will not interfere with disk operations of another program. CDP waits until everything is safe before it comes up. Most other TSRs cannot do this safely. If you run Print BEFORE running CDP, Print can continue spooling while CDP is up. However, if Print is installed AFTER CDP is installed, it cannot spool while CDP is up because CDP may have swapped Print out of memory. So run Print before you run CDP if you wish to spool stuff to the printer while CDP is up. ----------------------- 04/11/90 In the past, CDP deliberately refused to attempt to switch DOS directories (alt-D) or execute a program (alt-X,P,W or ctrl-X,P,W) when the success of the operation was not clear. Technically, this situation occured when the current PSP of the system was higher than that of either copy of CDP that was running. If that were not the case, it indicated that some other program was running at the DOS command line level. If CDP attempted to issue a command, that command might be dumped into the middle of an active program. No harm would occur since the program involved simply would not recognize the command given. But some people might not understand WHY the effort was ineffective; or be alarmed at the reaction of the surprised program receiving the string. No longer! CDP will now go ahead and attempt the operation. After all, the danger of harm occurring is virtually nil; and the user really should know whether he is at the DOS level or in the middle of WordPiddle. The gain in utility outweighs occasional harmless startlement to a careless or forgetful user. ----------------------- Version 1.4 04/28/90 Several minor bugs were fixed. CDP would not pop up correctly over CGA bit-graphics mode. The bug was a direct result of adding the shareware screens to CDP (originally a store-distributed product - see above). A second "bug" was that CDP failed to recognize the GREY ENTER key as the ENTER key, mistaking it for ctrl-M, the hot key for the MOVE function. Perhaps CDP should simply ignore the key, since it seems very stupid to have two ENTER keys on the same keyboard; but CDP now recognizes it as being the same as the key that by sensible people is called the <CR> key or the RETURN key. A fix was also made to the length of the string allowed for invocation of a Word Processor (SetUp in the Xecute menu or SET CDPEDIT= in DOS). The maximum length of such a string is 39 characters. But CDP formerly got confused at strings longer than 20 or so when the alt-W command was used to invoke a word processor. Please note that you need not add .EXE or .COM or .BAT when specifying the command; nor specify the disk and path. Give the string EXACTLY AS YOU WOULD TYPE IT ON THE DOS COMMAND LINE. ----------------------- Version 1.5 05/11/90 This version differs from 1.4 in the following 2 respects only. The name of the hidden scratch file used during swapping on the disk has been changed from DASWAPQP.FXK to CDPSWPQP.FXK. A fix peculiar to DOS 4.0 and 4.01 has been made. Actually, it accommodates what can only be called a bug in DOS; and version 1.3 was correct with respect to this problem, which occurred only after 1.3 was changed to make its interface with DOS 4.? totally consistent. After the change was made, DOS 4.0 and 4.01 VDISK & RAMDRIVE would not work. Apparently, IBM and MicroSoft did not change the drivers for those ramdisks to be consistent with the drivers for physical disks. If you don't use DOS 4.?, this fix is irrelevant. ----------------------- 06/02/90 Version 1.6 This version corrects a bug that prevented CDP from finding its help when the CDP*.EXE file was stored on a disk with 4096-byte clusters, the pre-AT cluster size on many hard disks. No code was changed in CDP itself. The batch file that built CDP was changed to pad out CDP's actual code to a multiple of 4096 bytes before "sticking" the help and shareware screens to it. As a result, the size of CDP.EXE and CDPSW.EXE is actually decreased by 2048 bytes, and the size of CDPW2.EXE increased by 2048 bytes. This results in smaller CDPSW??.ZIP and CDP-PACK.EXE files also. 06/21/90 One other fix was for the sub-sub-standard use of CDP from a ram disk of only 256 bytes per cluster. CDP could not find its help in that case. ----------------------- 10/17/90 Version 430 This version breaks the previous version number sequence. It starts with 43 because it supports 43-line video mode on an EGA as its default mode. That is to say, if the mode is 25 lines, CDP will change the mode to 43 lines while it is up. There are other new features in this version as well. See the file VERS-501.ME for complete details about the additions in this new version. ----------------------- 12/28/90 Version 500 This version does 50 lines on a VGA monitor. ----------------------- 01/17/91 Versions 431 & 501 These versions allow CDP to operate on disks containing more than 2800 files, the former maximum. Because of memory limitations CDP can still keep track of only 2800 files at a time, but by the use of a DOS SET statement, directories may be selected which CDP is to EXCLUDE from consideration. CDP simply behaves as if those directories did not exist; EXCEPT that the actual space that they and their files occupy is inviolate, and will not be used in any fashion by CDP. So long as the total number of files in the non-excluded directories is less than 2800, CDP will behave in its normal fashion. The syntax is best given by example: SET CDPXCLD=C:a/dz,g/mZ;d:r/Tz,m/pz;g:F/mz (notice that the case of alphabetics does not matter) says on disk C:, ignore directories ( & their subdirectories) at the root level, whose names sort between the strings "a" & "dz" and those with names between "g" & "mz" on disk D:, ignore directories with names between "r" & "tz" and between "m" and "pz" on disk G:, ignore directories with names between "f" and "mz". There are no restrictions or exclusions on other disks. Also, CDP can export to any directories on the restricted disks, even the excluded directories. The exclusions apply only to the disk that CDP is currently "logged" to. It is important to note that the exclusion specifications apply only to root-level directories and all the descendants of those excluded root-level directories. In the above example, the directories C:\ALPHA\FARFLE\ and C:\GLOTZ\FARFLE\ would be excluded, but C:\FARFLE\ALPHA\ and C:\FARFLE\GLOTZ\ would be ok. All four directories would be allowed on disk D:. Directories G:\FARFLE\GLOTZ\ & G:\FARFLE\ALPHA would be excluded. The only limit on the number of exclusions that may be made is the DOS limit on the length of a SET statement. A fix has been made that affected DOS 4.xx only, and only when the users CONFIG.SYS file contains: BUFFERS=xx where xx > 29 CDP could not always make DOS aware of what it had written to the disk. This resulted in "lost" clusters and files, which could easily be corrected with CHKDSK /F. No good data was overwritten or destroyed. SECTION II CDP Features & Performance -------------------------- CDP is the ONLY program, period, which can have two copies of itself simultaneously installed as TSRs. If you have two hard disks (physical or logical), you may have a copy of CDP logged to each of the disks. And if you have enough EMS for swapping both copies, the two combined use only 18K of your PC's 640K DOS memory and pop up instantly at any time! They may also swap to disk if you haven't enough EMS. Or run just one copy and use only 9K! Overall, CDP is more than just a file or disk management program. It can be considered to be a shell, also. But it is perhaps the best single program available for examining the contents of the files on a disk. It possesses the most admirable features of the most popular FM (file manager) and search programs I know of), and is faster than most of them. 1. CDP is up to 80% faster and can find strings in binary files, which the most popular search program cannot do. 2. On a typical disk that I use (33 Mb, approx. 2100 files) the most popular FM will not run in 141 KB. It will run in 165 Kb. CDP will run in 175 KB, and after you run it, you can then run the other FM with CDP resident!! In that amount of memory, the other FM cannot shell to ANY program, even very small ones like MAPMEM or CHKDSK. CDP can shell to any reasonably sized program (including the FM!). CDP is a fine program just for viewing files. It scrolls faster than most programs dedicated to the purpose. With its ability easily and quickly to mark files according to values found in them, and then page through them with a single keystroke (alt-N - go to NEXT MARKED), one can examine the contents of a disk more smoothly than any other product I know of, regardless of size, cost, or extravagant memory use. And CDP can do it all when popped up over a great space-wasting word processor that can't even show you a useable directory listing. Things In Which CDP Is Unique ------------------------------ Foremost, of course, is the fact that CDP is the only disk and file manager program that runs as a TSR using as little as 9KB of memory! It is the only disk manager that swaps the bulk of its code to either LIM-EMS or a hard disk, depending on your system. You can run it underneath WordStar, WordPerfect, Lotus 1-2-3, etc., in spite of the huge size of those programs. Because it is a TSR, it is the only file manager that can pop up over such programs instantly to let you examine your disk without leaving the program (even if they can shell out to DOS, such programs do not generally leave enough space to run a conventional FM. I commonly run 2 copies of CDP simultaneously with ProComm. I can search a local copy of a BBS directory (having downloaded it) much faster than the BBS can, without shelling out to DOS. I can also examine files and directories easily without ever leaving ProComm. ProComm never knows the difference! 1. Can compare not only entire directories, but entire directory trees. 2. It is the only program that will compare files either on contents or by date and time only. 3. Alone among shells that I know of, it runs a program just as it would run from the command line. 4. It is the only program that I know of that, when shelling, can alter directory residence to accommodate the program being run. 5. It is the only file manager in which window sizes are adjustable. 6. It is the only file manager which can search for strings in files and produce a report on them. Moreover, the file can be saved on disk. 7. It is the only program that will sort by disk location. This is often useful, believe it or not. 8. It is the only program which allows you to "point and shoot" to change your directory residence (^D). 9. It is the only one which comes up "instantly". 10. It is the only one which can (effectively) run in less than 160 KB. (It requires only 9 KB when resident). 11. It is the only one which can be called up when in the middle of editing. 12. It loads faster originally (1st time) than any other FM, although some others approach it. 13. It moves entire directories almost instantly. 14. It can toggle marked files and display "only marked" files. It can display "not matched" files. This gives it a Boolean file specification capability which is unique. (Note: The most popular searcher can do this and also 6. above. But it is not a full-fledged file manager, and CDP is much faster.) 15. CDP has more functions than any other FM, and most may be invoked by a single "mnemonic" keystroke. That is faster than a mouse or a menu. Few FMs approach CDP in ease of use. 16. CDP is the only FM program that can view a "Hex" file in Ascii. 17. CDP is the only FM program that can search for strings in either a hex or an Ascii file. 18. CDP is the only FM program that has a TRUE restartable backup capability (via the Archive option). 19. Although CDP has no editing capability of its own, it is the only FM program that can instantly put you into the Editor of your choice with a SINGLE keystroke from its own viewing function. 20. CDP is the only program that can produce a neatly formatted listing by directory of all files on a disk, almost instantaneously (LIST function). 21. CDP is the only FM that can search files and "mark" the "find"s in a manner suitable for immediate contextual examination of the finds. 22. CDP is a fortiori the only FM that can then page thru the marked files with a single keystroke (Alt-N -- go to NEXT MARKED). 23. CDP allows you to copy or move files by "point and shoot". I might add that CDP is also the smoothest program of all the FMs for viewing a file. Also, if one is dealing with multiple directories and often returning to or referencing the same one, the CDP F4 key still works to remember the directory path one was in before (indefinitely), and it can be called up by rtshift-rtshift at almost any time. This is often very useful. Perhaps the single most impressive thing about CDP is its ability to run using only 9K of memory. It really catches the eye if you run MAPMEM & it shows SideKick using 60-110 KB, PCO using 140K, a leading search program using 180K, and at the bottom, another FM using 165 KB. CDP is very "compatible". It will even run with several notoriously "incompatible" "desktop" TSRs and shells. In some cases, CDP MUST be run either BEFORE or AFTER the other program; the other way round won't work. We cannot name those programs here lest we offend the large companies that produce them. Performance Tests ----------------- These tests were made on a 16Mhz Compaq Deskpro with a 132 MB Compaq disk, partitioned as C:, D:, E:, F:. A directory on D: containing 400 files is copied to an existing, empty directory on C:. The files contain 737,543 bytes but require 1,103,872 bytes on the disk. The total number of files on C: is 1854 + the 400 being copied. All operations are performed while logged in to C:\ (root dir on disk C:). The files on D: are ordered by extension and name in DOS, and CDP & the leading FM also copy them by that order. The results were: Copying to an empty directory ----------------------------- CDP: 3 min. 39 sec. the FM: 15 min. 32 sec. (DOS) COPY: 8 min. 13 sec. Copying a 2nd time (i.e., over top of the files) ------------------------------------------------ CDP: 1 min. 54 sec. the FM: 8 min. 23 sec. (DOS) COPY: 6 min. 32 sec. CDP is 4.25 times faster than the FM and 2.16 times faster than COPY. Here are 2 tasks that NO OTHER PRODUCT CAN DO: Comparing all data in all files in both directories --------------------------------------------------- CDP: 2 min. 49 sec. Comparing the directories by file size and time only ---------------------------------------------------- CDP: 1 min. 20 sec. I performed a further test on searching (vs. a leading searcher). The test was performed on 2254 files. The searcher won't search on binary files, so CDP was instructed to search on ASC only. The string searched for was "lars" (case not counting). I have observed that the searcher does not search .EXE, .COM, nor .OBJ files (although I haven't seen it state the fact). For fairness, I marked .EXE, .COM, and .OBJ files, toggled the marks, and then searched on MARKED only. The results: CDP: 3 min. 25 sec. - 44 finds other: 6 min. 05 sec. - 55 finds CDP was 1.80 times faster. The different number of finds, I discovered, was because the searcher was not always as good as CDP at deciding what was a binary file or not. It was finding names in binary data base files. I redid the search with CDP on ALL files (still not .EXEs, etc., however), and got: CDP: 5 min. 37 sec. - 73 finds That is, even then CDP is 1.08 times faster than the searcher. CDP is clearly a "superior-type" product. SECTION III Problems One May Encounter With CDP ----------------------------------- The most likely problems are: Bad Or Invisible Cursor ----------------------- If your machine has a "shaded-grey" monitor or is a laptop with a blue, red, etc. screen, use CDP .... Y on the command line in the case that the cursor or other stuff might not be visible Disk ---- Over 2800 files or 200 dirs on a logical disk cannot be handled. CDP cannot be brought up on a Network disk, nor log to one. It will work on RAM disks (VDISK, etc.). If you use DRIVER.SYS for a floppy that has a letter higher than C:, CDP thinks it is a hard disk. It will reject the unit if a good floppy is not in it. These problems do not apply to 99%+ of users. CDP simply will not work on such disks (DRIVER disk is OK as long as a diskette is in it.) But it WILL WORK CORRECTLY on all other disks on the system. Over 132 MB on a LOGICAL disk cannot be handled. Nor can disks that have sector sizes of > 2048 bytes. These 2 limits are equivalent. OS -- CDP will not run in OS/2, even in the DOS compatibility box. Nor do I intend to attempt to make it do so. We do not like OS/2. DOS 4.0 shell may hang (but I have trouble installing the DOS shell correctly -- I could not get it to work properly, even with CDP not present.) Plain DOS 4.0 works just fine, however. BUT you should not use it with FASTOPEN running or directories in EMS. DOS may foul up in that case (CDP won't; disks will be correct -- but DOS tables in EMS may not be updated, so you should do frequent CHKDSKs). No such problems exist with DOS 3.x or 2.x. Nor is there any problem without FASTOPEN and/or EMS-resident directories. In PC Computing Magazine, Nov., 1989, p.253, an article devotes quite a bit of space to warnings about FASTOPEN under DOS 4 (IBM or MicroSoft). Seems it is a potential disk-destroyer. "still has problems with certain programs like Paradox, SideKick Plus, Javelin, and DESQview." Use of Disk Optimizers by Bridgeway, Golden Bow, Mace, and Norton may destroy your disk. DOS often reports the amount of free disk space incorrectly when a TSR deletes files. This does NOT indicate a harmful situation. DOS simply does not always adjust its free space total until it performs some file actions itself. The disk itself is correct and DOS's internal tables are up to date. CDP is not the only program that encounters this quirk. Use of CHKDSK clears this up. Frequent use of CHKDSK is advised anyway, on all systems. In DOS 4, use a LIM-EMS Driver and disk-cache program to speed up your hard disk if possible. Or you can use VDISK or RAMDRIVE to make a ram disk in your expanded or extended memory. CDP can use either LIM-EMS or ANY RELIABLE RAM DISK as a swapping area. If you have qualms about MS-DOS 4.?? (or any other system, for that matter), you may proceed cautiously with CDP as follows: CDP 3 ;will swap to EMS if present, but not to disk Then try the VIEW function on some large files. This will not write on any disk. When that works, modify a large file toward the end of the disk so that you have 2 slightly different files. Because problems will happen only past the 32MB mark on a disk, use CDP's Sort by location to pick a large file that is located past the 32MB mark, if possible (I can't tell you just how large the cluster number must be, because that depends on the disk's format). Do a COMPARE of the 2 files with the CURRENT option. (A COMPARE of single file with another by CURRENT does not bother to log results to disk). Next, get yourself a 1.2 MB floppy and XCOPY (on the EXPORT menu) some entire trees to a floppy. If all that works, you're pretty safe doing anything else at all. Windows and DESQview -------------------- I have never tried CDP in MS Windows or DESQview. I am told it doesn't run in Windows, but that it runs in DESQview as a non-resident program. We do not really give a fig for Windows. It is much too slow and ungainly for the work we do. And we believe the same is true for potential CDP users. So, DO NOT TRY CDP in WINDOWS. If you should do so, DOS might lose track of files. CDP keeps the disk in perfect shape, regardless of OS or shell that is used. But CHKDSK or DOS functions in Windows might overwrite a correct disk because of incorrect internal tables. CHKDSK might or might not be able to straighten things out. Never do a CHKDSK /f as a first try in such a case. CHKDSK might mess things up. You might try CDP in DESQview - cautiously. Remember, if you do not use ctrl-Q or one of the switching functions (eXecute, etc.), CDP never needs to go resident. Let DESQview do the switching & swapping - that is what it is for. CDP will still be the best file manager and disk examination program you can find. But be careful in DESQview, as you are in unknown waters! Observe the precautions mentioned under "qualms" above. Try CDP out with unimportant files first. Removing CDP From Memory ------------------------ A complaint was made that CDP does not always remove itself from memory when alt-R is done. The fact is that it cannot always remove itself safely. If another program is in memory (TSR or command-line level) that has taken over a BIOS interrupt used by CDP, then the system would crash. Many other TSRs do remove themselves at any time, often crashing the system. Sometimes CDP may not remove itself until after 2 attempts. This may occur if a TSR further down in memory is removed without performing any DOS commands before attempting to remove CDP. In that case DOS has not yet rearranged the pointers in memory to reflect the removal of the other program. Usually, CDP detects such removal before DOS does (provided that removal was done correctly by the other program). But sometimes it may not. A similar situation may also occur in which CDP will not immediately become active after its hot key is struck. Usually, simply striking ENTER will cause CDP to come up on the screen. Final Words ----------- I don't want to frighten you with the above. There are absolutely no problems that I know of on a plain DOS 2.x, 3.x, or 4.x system that is not running something like Windows, DESQview, or the DOS 4.0 shell or FASTOPEN. There is NO problem with OS/2 -- CDP just refuses to run! Just remember -- the official advice is: Use CDP on DOS 4.xx -- but not with the DOS Shell or FASTOPEN! Be extremely cautious about trying it under Windows! DESQview is an unknown! But CDP should work OK if not made resident. CDP actually behaves better than any of the better known, widely- distributed disk managers and search programs that I have seen, TSR or not.