home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Hacks & Cracks
/
Hacks_and_Cracks.iso
/
vol1
/
hslink.zip
/
HSREADME.1ST
< prev
Wrap
Text File
|
1993-12-05
|
6KB
|
113 lines
Date: 12-04-93 (10:08) Number: 153 of 214 (Refer# NONE)
To: Slicer
From: Viceroy
Subj: Hslink v 1.21B7R or any other version.
Read: 12-04-93 (00:14) Status: PUBLIC MESSAGE
Conf: IBM WAREZ (1) Read Type: TEXT SCAN (-)
There are a LOT of improperly registered HSLink versions floating around. Even
if your version says it is registered, it may pay to issue the below command
and reregister it PROPERLY to the AUTHENTICATED BETA CYCLE CODE (ABCC) for
HSlink.
To register HSlink (any version) PROPERLY, type
HSLINK [or FHSLINK] REGISTER 00317 1QQ3DBC
| | | | |
| | | | |
| | | | +--------- Reg Key
| | | +---------------- Serial Number
| | +------------------------ Command to Reg
| +----------------------------------- Fossil Ver
+--------------------------------------------- Regular Ver
NOT EVERY SERIAL NUMBER will work. Some reg patches for HSlink ignore
HSlink's internal serial number checking and register it with
01234 or 12345. Those will *NOT* work, and transfers will just abort.
33839 or any other serial number starting with 33 will also abort with
an errorlevel of 4 or 7.
00317 is a valid BETA TESTER's serial number and it will work in all
Present/Future releases of HSlink. It's a *special* serial number which
turns off certain parts of the serial authentication code inside of HSlink,
thereby letting your copy work with even improperly registered HSlinks.
It also turns OFF a lot of debugging code inside the program if you are using
an HSlink beta (as in v 1.21B6). By turning off the debugging code, it speeds
up the handshaking (not considerably, however.)
If you spread this message, please give me my due credit.
Viceroy
P.s. Look for a file I wrote on this subject back in 1991 called HSREGNFO.TXT
which gives more specific details as to why certain serial numbers
do not function, and how to know if you have a bad serial number.
Here is a sample Configuration File that I have
found to work optimally for all HSlink transfers!
──────────────────────────────────────────────────────────────────────────────
-! - Force remote to use local settings.
-A - Disable transmission of ACKs after each block.
-I2 - Give up time slices to Desqview - Remove if no Dv
-FT10 - Set a 16550 FIFO treshold of 10 bytes.
-K - Keep partial files from aborted xfers
(required for resuming dls, turn off for a bbs)
-NE50 - Set a maximum of 50 repeated errors before aborting
-NG - Do not allow CTRL-G paging (good for a bbs)
-NM - Enable 'Minimum Block' logic (requires MNP or V42b)
-NOC:\PCB\DUPE.LST - Set up a DUPELICATION list for received files
(Great for a BBS)
-NT - Stamp current file time on all received files.
-NV - Disable Direct Video (good for Desqview, REMOVE
this if you are not using Desqview
-O - Allow received files to overwrite existing ones
(required for resuming downloads) (turn off for bbs)
-P2 - Default to COM2:, change to -P1 for COM1:
-R - Resume aborted transfers
(This alone, without -K and -O will work good
for a board, since it will allow the user to
resume downloads, but not to overwrite bbs files)
-S2048 - Set block size to 2048 bytes. 1024 or 4096 good also
-UC:\QMPRO\FILES - Receive all files to this directory.
─────────────────────────────────────────────────────────────────────────────
; This is a sample configuration file that I use. I have found that these rks best. Also, I turn off the ACKs after each
are the best options to use. Please remove -K and -O if you are using
this for a BBS setup, because you do not want users to be able to
overwrite existing files under any circumstances!
; To use this config file, remove all extra text, and just leave the
-x options, one per line. Remove the comments at the bottom as well.
───────────────────────────────────────────────────────────────────────────
Here is a sample PCBRH.BAT (Receive with HSlink) for PCboard 14.5 and 15.x
(This file assumes that HSLINK.CFG resides in the \PCB directory and that
HSlink.EXE is in the path. Remember, HSLINK will try to use the .CFG file
that resides in the SAME directory as the executable. So place them both
in the same directory.)
@echo off
if exist pcberr.fil del pcberr.fil
if exist %DSZLOG% del %DSZLOG%
hslink -p%1 -e%5 -u%6
Here is a sample PCBSH.BAT (Send with HSlink) for PCboard 14.5 and 15.x
(Same .CFG assumptions as above)
@echo off
if exist pcberr.fil del pcberr.fil
if exist %DSZLOG% del %DSZLOG%
hslink -p%1 -e%5 -u%6 %3
Good luck! I can be contacted via PRiMALNET, FiNALNET, DRAGNET, SSN, HYPERNET,
and other nets for questions or comments.
Viceroy