home *** CD-ROM | disk | FTP | other *** search
-
- CCLINK.ZIP Contents
- -------------------
- CCLINK and CCLINKjr are Windows-compatible communication programs that
- allow users to monitor their serial and parallel ports by displaying lighted
- LEDs on the desktop. Perfect for internal modem users! CCLINK even allows
- you to talk to your modem.
-
- CCLINK release 1.a4 includes:
-
- SETUP.EXE -- installs CCLINK Group to your Windows desktop
- CCLINK.EXE -- allows you to talk to your modem with AT commands
- CCLINKjr.EXE -- almost 20K smaller than CCLINK, minus the AT window
- CCLINK.HLP -- tens and tens of items describing CCLINK features
- CCLINK.DOC -- this information-packed document
- CCLINK.REG -- order form detailing bulk purchases, corporate discounts
-
- If you enjoy this product and would like free patches, upgrades, fatherly
- advice, support, etc., please register online in the SWREG forum, ID 5579:
-
- GO SWREG (ID 5579)
-
- or send ten dollars with your Email address to:
-
- Gary Shaboo
- 319 East Main St. Apt. F-4
- Marlborough, MA 01752
-
- America Online user ID: Garyshaboo
- You can also reach me on Compuserve @ 75274,605
-
- I'll then email or postal mail you the double-secret-probation-registration-
- number checksum. CCLINK and CCLINKjr will operate for 30 minutes without
- being registered, and they will then warn you that they are exiting. One
- checksum per person! I've got to pay the bills somehow...
-
- CCLINK Setup
- ------------
- Run Setup. It's that easy! You can choose to create just a group if desired.
- CCLINK will not delete any pre-existing CCLINK groups, so re-running Setup
- will give you harmless duplicate icons if the CCLINK group already exists.
-
- CCLINK 1.4a Enhancements/fixes
- ------------------------------
- 1. Command-line option number for specifying COM port.
- 2. Added TEST button for Sounds.
- 2. Improved behavior when multiple CCLINKs are running.
- 3. Fixed CCLINKjr bug with not remembering COM port.
-
- CCLINK 1.4 Enhancements/fixes
- ------------------------------
- 1. Connect Time feature.
- 2. Event Sound feature.
- 3. Better Windows 95 logic for detecting data sent and received.
- 4. Stopped opening ports by default.
- 5. Fixed hangs with Internet/Winsock applications.
-
- CCLINK 1.3b Enhancements/fixes
- ------------------------------
- 1. Fixed possible menu corruption when Show Speed disabled during Mini-Mode.
-
- CCLINK 1.3a Enhancements/fixes
- ------------------------------
- 1. Improved Display on different resolutions.
- 2. Allow CCLINK movement in NoTitle mode.
- 3. Allow limited operation in Windows NT.
- 4. Improved compatibility with Windows 95.
- 5. Additional Display option for "super-MiniMode" operation.
- 6. Allow monitoring of non-existent serial ports.
- 7. Auto-Dial displays phone number.
-
- CCLINK 1.3 Enhancements/fixes
- ------------------------------
- 1. New SETUP.EXE creates a Windows group and copies files. Finally!
- 1. New "Display..." option allows customization of CCLINK display.
- 2. New "Fonts..." option allows customization of CCLINK text.
- 3. New MiniMode option displays a kinder, gentler, smaller CCLINK.
- 4. New AutoLoad option allows CCLINK to automatically launch applications.
- 5. Improved Save Settings logic, so CCLINK does not save garbage sometimes.
- 6. Fixed some minor display bugs.
-
- CCLINK 1.2b Enhancements/fixes
- ------------------------------
- 1. "Speed Detect" feature -- show the serial port speed set by applications.
- 2. REALLY fixed bug introduced in 1.2 where incorrect serial port rates
- can be set.
-
- CCLINK 1.2a Enhancements/fixes
- ------------------------------
- 1. "No Title" feature -- just like Windows CLOCK!
- 2. Auto Save of current settings when exiting Windows.
- 3. Added detection of large and small font video resolutions.
- 4. Uses a smaller font for LED text, but this is system-dependent.
- 5. CCLINK and CCLINKjr are now about 5K smaller than version 1.2.
- 6. Fixed bug that caused system hang when minimizing CCLINK (Oops).
- 7. Fixed window-sizing bug when working with wacky resolutions.
- 8. Fixed bug which caused CCLINK to display invalid mouse versions.
- 9. Fixed bug introduced in 1.2 where incorrect serial port rates can be set.
- 10. Fixed problem where initializing older modems could cause them not to
- respond to AT commands.
- 11. Fixed bug which caused CCLINK to occasionally display garbage in
- Info dialog.
- 12. Fixed bug which caused CCLINK to give incorrect information about
- number of colors supported by current video driver.
-
- CCLINK 1.2 Enhancements/fixes
- -----------------------------
- 1. Auto-Send AT Commands.
- 2. Auto-Dial feature.
- 3. CCLINK Help file.
- 3. More Information under Info dialog about CPU and serial ports
- 4. Fixed COM port initialization bug with multiple CCLINKs running. For
- instance, this fix will now allow you to test a NULL modem cable connected
- to COM ports 1 and 2.
- 5. Other minor improvements to be a better user of Windows GDI.
-
- CCLINK 1.1a fixes
- -----------------
- 1. Fixed lockups when testing 16550 on some internal modems
-
- CCLINK 1.1 Enhancements:
- ------------------------
- 1. Monitoring of any hardware port through the "Parallel" option
- 2. Detection of possible interrupt conflicts and port usage by other devices
- 3. 16550a detection
- 4. System information about Windows, your mouse, display, and Windows directory
- 5. Advanced options to fine-tune operation in peculiar environments
- 6. Save all settings like screen position, port speeds, and modem strings
- 7. Run simultaneous multiple copies of both CCLINK and CCLINKjr
- 8. Executables are about 5K-10K smaller than CCLINK 1.0 versions.
-
- CCLINK 1.4 Wish List for future enhancements
- ---------------------------------------------
- 1. Intended compatiblity with DOS applications -- Coming Soon?
- Probably not, but I hope so. maybe in 1996.
- 2. File Transfer -- proprietary file transfer, maybe in 1996.
- This would allow you to transfer between CCLINKs only.
- 3. Real File Transfer between BBSs, etc. -- wow, maybe in late 1996. Maybe.
- 4. INT14/NCSI support -- delayed to 1996. Well, at least INT14.
- 5. A real AT window for talking to the modem -- Delayed to 1996.
-
- And whatever else registered users suggest that I can do (easily)!
-
- CCLINK 1.4a Known Issues/Problems (bugs? -- well, ok, some bugs.)
- -----------------------------------------------------------------
- CCLINK and CCLINKjr do not require a CCLINK.INI file. So, if you need to
- start from absolute scratch after possibly screwing something up, just unload
- CCLINK and rename the CCLINK.INI file. On to the Issues! (Bugs -- whatever):
-
- 1. Enabling "Transparent" background mode displays text on top of text
- sometimes. This is actually "supposed" to happen, since Windows does
- not indicate to CCLINK that a Transparent window needs repainting.
- Whatever, it looks messy, and I want to fix it. So there.
-
- 2. If another port or a modem appears to hang when CCLINK loads on another
- port, try turning off the "Options|Advanced..." option "Verify COM port
- on startup." One possible scenario is a modem on COM4 and CCLINK loading
- on COM2, which usually has the same interrupt as COM4. This will almost
- never be a problem, but some older modems may be sensitive to another
- COM port access triggering the modem's interrupt.
-
- 3. Setting the "Options|Advanced..." option "Check for 16550 FIFO buffers"
- will still not allow the serial port to be checked for 16550 buffers
- unless the "Verify COM port on startup" is also selected. Pretty clumsy,
- I know, but it should work fine.
-
- 4. Improved compatibility with Microcom's Carbon Copy for Windows 2.5/3.0,
- but Guest users may not see the SD and RD LEDs always work. In remote
- control the LEDs should work fine.
-
- 5. While CCLINK uses the Windows programming interface to retrieve the status
- of some COM port signals, CCLINK must go directly to the hardware in order
- to retrieve others. This is due to limitations within Windows and within
- the code (working on those!). As a result, CCLINK may correctly display
- only some of its LEDs while running with a few applications and some
- third-party Windows communication drivers. Examples include the
- MCVCOMM.386 driver explained above, the Microcom PPM.DRV serial port
- redirector, any NCSI/NASI applications, and some remote-access products.
- I would love to hear about any others that seem to give CCLINK a problem,
- and then I can try and address these issues.
-
- Well, enjoy CCLINK and please register like a good doobie. Thanks!
-