Download CONNECT! v2.0 patch

Added to site2002-12-31
Rating95/100
Votes12


connectv2.0patch.zip (89874 bytes)

namesizecompressed
CONNECT.TXT 19763 8293
CONNECT.NFO 817 510
Connect! 2.0 - Fortech.url 89 89
Download programu CONNECT! 2.0.url 112 110
English.exe 124007 62745
FILE_ID.DIZ 352 234
FLMfiles.exe 32813 17107

CONNECT.TXT

 CONNECT! 2.0 Program Set
 Direct Cable Transfers
 IBM PC 80286 minimum
 
 Speeds available:
 57600bits/s Modem =
 5KBytes/s RJ-11 2-Wire
 115200bits/s Serial =
 10KBytes/s Serial 3-Wire
 20-40KBytes/s Serial Turbo 7-Wire
 70-110KBytes/s Parallel 4-Bit 11-Wire
 125-180KBytes/s Parallel 7,8-Bit BiDirect 17-Wire
 450KBytes/s Parallel 8-Bit ECP 18-Wire

 RUNNING from REAL DOS MODE:

(1) Start a REAL DOS MODE MOUSE DRIVER to make CONNECT easier
    to work with or use the TAB Key to navigate.
(2) Setup Configure Files CONNECT.INI and RIGHTS.DSK
    using CONNECT.EXE then exit when done. 
(3) Start KERNEL.COM in REAL DOS MODE on BOTH Computers. 
(4) Start SSERVER.COM then SKLIENT.COM on BOTH Computers.  
(5) Transfer files between the two Computers using the DOS COPY 
    COMMAND using the Mapped Drives, just like you would do using
    Network Drives or the program INTERLNK. 
    You can send and receive in both directions simutaneously. 
(6) CONNECT.EXE need not be running for the LINK to Function. 
    But it provides Testing and Monitoring Functions as well,
    and initial connection handshaking for the Modem section. 

 Usually just run Batch File SIT.BAT then CONNECT.EXE

 CONFIGURATION INFORMATION:

 Beforehand, you must set up CONNECT.INI and RIGHTS.DSK properly
 using CONNECT.EXE. All the Programs reference CONNECT.INI and 
 SSERVER.COM references RIGHTS.DSK and BOTH MUST BE SET UP CORRECTLY. 

 Step-by-Step Walk Through setting up CONNECT.INI and RIGHTS.DSK:

(1) Make a  *NEW*  file CONNECT.INI by starting CONNECT.EXE 
    with NO CONNECT.INI in it's current folder. 
(2) CONNECT.EXE informs you it is making a new CONNECT.INI file 
    using Default Values. 
(3) Go to the New Setup portion of the CONNECT.EXE Menu. Select 
    Params Environment. Check off the "Best" and "Normal" for 
    the Dialect, Keyboard, and Fonts Checkboxes. 
(4) Go to Klient section, find an unused Disk Drive, double click it
    and Map it to for example the C:\ Drive for the Remote Computer. 
    SKLIENT.COM  *MUST*  find a Mapped Disk when it starts. 
(5) Go to the Server Section and select Access Rights. Make sure it 
    says Unassigned Path Permitted. If not, add any path, then delete 
    it, then when asked, select ALL PERMITS. 
    This creates File RIGHTS.DSK with full access rights. SSERVER.COM 
    *MUST*  find this file in order to Transfer Files over cable link.
(6) Go to the KRNL section, select Settings, then select the type of 
    Cable you want to use. Highlite it then click on Select. 
    Click on Settings and make sure the Port and Interupt were 
    Auto Detected  Properly. Test to make sure Interupts function. 
(7) Exit CONNECT.EXE to save the CONNECT.INI file. Restart Computer.  
(8) Select KRNL, Test Functions. This will only work if you run  
    KERNEL.COM, SSERVER.COM, and SKLIENT.COM, then CONNECT.EXE in 
    their proper order, AND if you have a good Cable that is properly 
    connected. If all goes well, and you see test Packets being 
    Sent and Received, you are ready to EXIT CONNECT.EXE and check 
    the Mapped Drives and try them using the COPY and DIR commands, 
    just like a Network Drive. 

You can also type /? or /H for help at a DOS Prompt for each of the 
Programs for extra Options and Settings Help. 

KERNEL, SSERVER, and SKLIENT are TSR Type Programs. 
They can be removed from Memory using their /O Option. 
Normally, their function is transparent to you, 
except for the fact of the added Mapped Drives. 

What does most of the work is the 23KB file KERNEL.COM which 
Communciates over various Cables using the .FLM Loadable Modules.
The 16KB file SKLIENT.COM makes requests through KERNEL.COM 
for whatever file you may want to Transfer, requesting Services 
from the 14KB file SSERVER.COM on the Server side of the Link. 

RUNNING FROM WINDOWS:

Windows 9x CAN start these programs WHEN BOOTING by using: 
CALL SIT.BAT
from AUTOEXEC.BAT. Windows runs in special Compatibility Mode. 
You will see the Mapped Drives in File Explorer. 

CONNECT MODEM SECTION

The Modem Section of CONNECT.EXE is Fully Functional and Works Well. 
Connect can actually do a Direct 2-Wire cable Transfer using a 
common 6-Foot RJ-11 Telephone Extension Cable. (Tip&Ring-No Ground!)
Thousands of feet are possible compared to Serial and Parallel Cables!
However, the maximum speed is limited to only 56kbps or about 5KB/s. 
Note that Connect Server Mode will only process calls originating 
from another Computer running CONNECT.EXE so it isn't really meant 
as a General Purpose Modem Communication Program. But it CAN be used 
from one Telephone to another via the Local Phone Company.

The CONNECT! Direct Connect Modem section is a very clever and 
handy feature, if you have absolutely NO other way to connect 
either a serial or parallel cable between 2 Computers, 
but they both have Modems in them, and you need to transfer files. 

As it is unusable in Windows, it is recommended to set up the Modem 
Section in DOS using non-Plug'N'Play standard type Modems with 
jumperable Port and IRQ selections. Use of WinModems is impossible. 
Check to make sure your BIOS has configured the Modem as ISA or DOS, 
rather than Plug'N'Play. If Modems fail to Communicate properly with 
CONNECT.EXE, this is an area you should double check. Chances are 
that if a Modem works OK in DOS with a Program like PROCOMM or 
QMODEM, it should work OK with CONNECT! Both of these two programs 
can be set up to do almost the same thing, using the special INIT 
string for the Modem so the Modem doesn't need to hear a Dial Tone.
( INITIALIZATION = ATX3C1Q0V1&C1&D2E1L1S0=0 )

MODEM SETUP:

Setting up the Modem Section to function is a little complicated, 
compared to a normal Serial or Parallel Cable Transfer setup. 

(1)You should first set up a Users Database file named CONNECT.CUB by 
going to "Modem/Users Database" and naming the Database "CONNECT".
Click "OK" then enter a User named "CONNECT". Enter a simple password 
for Pass1 and Pass2 like "Pass1" and "Pass2". Click "Right" then
"Remove" then "All Permit" then "OK" then "OK" again. 

(2)Next go to "Modem/Dial a Connect" and make a Dummy Dialing Entry.
Recommended for "Name" is CONNECT. Any number for a Phone Number.
Recommended for Dialing baudrate is 1200 or 2400 baud at first until 
fully debugged. Only in Dialing can you enter a reduced baudrate. 

(3)It is recommended to run the Modem functions with the MODEMSRV.FLM 
driver module and the original (modified) CONNECT.EXE Init String. 
Go to "JKRNL/Settings" and highlite RLE+DCA Modem 
(Server Modem; MODEMSRV.FLM). Click on "Select". Then Click 
"Settings" and setup the proper Port Address and IRQ settings. 
Baudrate should be the maximum the Modem is capable of. 
Click "OK", then "Close", then Terminate CONNECT.EXE to save 
these settings to the CONNECT.INI File. Restart CONNECT.EXE and 
return to this section and click on "Test" to check that the 
Modem responds OK. If you get good results, you are ready to 
have KERNEL.COM load the Modem Driver at System Startup in DOS. 

(4)Several of the following steps will have the CONNECT Labels 
"Greyed Out" if KERNEL.COM is not running first. 
Restart the Computer, making sure KERNEL.COM starts either 
during BOOT, or just before CONNECT.EXE does in DOS Mode. 
Both SSERVER.COM and SKLIENT.COM should be running too. 
Use the Batch File SIT.BAT to easily start everything up. 

(5)Start CONNECT.EXE and go to "JKRNL/Test Functions". 
If you have an Internal Modem, you may get Control Signal errors, 
as CD RI DSR CTS and RTS may not be present with an Internal Modem. 
Don't be worried about that. 

(6)Go to "Modem/Modem Settings" and copy/write down the INIT 
String. Then Click on "Modems" and select the Generic Modem 
at the top of the list and Click "OK". When you then return 
to the previous screen, re-enter the original CONNECT.EXE 
INIT String, THEN Click "OK" again. Terminate and restart 
CONNECT.EXE to save this Info to the CONNECT.INI file. 
Be advised that the &K3 term and S1=0 can cause problems with 
some Modems hanging when CONNECT does a Modem Initialization. 

(7)Go to "Modem/Server Settings".
Recommended for "Station Name" is CONNECT. Baudrate should be the 
maximum that your Modem is capable of. Put an "X" in Auto Baudrate. 
Go to "Modem/Other Settings", check off "Continuous" and ALL Logging 
options, then click "OK". 
Later, you can view CONNECT.LOG to debug connection attempts. 

(8)Click on "Modem/ResetConnection". It's a good idea to do this 
BEFORE entering the Answer/Dialing Modem Modes. Get into the habit 
of using it often. There is also "Modems/Terminal/ResetMDM" 
and "Modem/Wait for Connect/Cancel Connect" that does the same thing. 

(9)"Modem/Wait for Connect" places the Program in Server Mode. 
It Answers Phone Calls, or you can use a 10DB Padded Telephone Cable 
to connect 2 computers Modem-to-Modem for up to 56K (5KB/s) Transfers. 
(Details of this special cable construction further down).
Press F10 to do this in Server Mode, after selecting: 

(10)"Modem/Dial a Connect/Dial/Off Hook" on the other Computer first. 
Press F10 within 10 seconds of going Off Hook, or the Modems may not 
perform proper HandShaking. Seeing a Baudrate appear shows this is OK.

*** REQUIRED CONNECT SCRIPTS: ***
For testing and debugging, just use the (Patched) CONNECT.CSL Script. 
Then later, set up a Script using the Connect Script Language (CSL). 
These five lines are all you need to enable File Transfers: 

ScriptHead(Enable Transfers)
ClearRights(mode_Enabled)
EnableFileTransfer(mode_Enabled)
WriteMess(File Transfers Enabled)
Stop(cmd_LogOK)

Select the Script FileName in "Modem/Server Settings/Connect Instruct"
You can Both Create and Edit Scripts by using CONNECT's built-in 
Editor in "Modem/Connect Instruct", and files are named: *.CSL
The Script file has to be in the same folder as CONNECT.EXE

WriteMess sends a Message to the Dialing/(Off Hook) Computer 
when the script runs on the Answering/(F10) Computer.
If you see "File Transfers Enabled" on the Originating Computer, 
and a list of Enabled Drives, you should be all set. 
When the Call is Answered, "OK" will Appear. Click "OK" and then you 
can check Activity in JKRNL/Info and Server/Info. Exit CONNECT and
drop to DOS and check the Mapped Drives using DIR and COPY commands.  

If the Connection attempt fails, yet in CONNECT.LOG you see the 
Name and Call Back Number from the Dialing Computer, chances are 
that the Script, or the Dialing Computer Modem's receive, or the 
Answering Modem's Transmit is at fault. Or, you are trying to 
Run in Windows or are using a WinModem. (Won't work!)
(But see later on a Note concerning using Modems in Windows)
Try different CSL Scripts for User Passwords, Log Messages Etc.
Try using some of the other sample scripts like DATABAZE.CSL or
FORTECH.CSL or try writing your own script that logs in a User, and 
accepts a password then sets up some Access Rights. You should also 
have SKLIENT.COM and SSERVER.COM running on both Computers with at 
least ONE Drive Mapped just like you would have to do with a normal 
Serial or Parallel Cable Transfer in the "Klient" Section, and 
Access Rights set up in the "Server" Section. 

A useful Script command is RUN. General Form:
Run(FileName,Text1,Text2,Delay,Reset)
Example:
Run(C:\TEMP\EXAMPLE.EXE,$LogName,$LogPassword1,1,10)

A useful Command in the SIT.BAT Batch file is:
MODE COM#:96,N,8,1,P     ("#" = 1 or 2)
CTTY COM#

Once you establish a Modem Link, you can go to Terminal Mode, 
and run as if you were at the Keyboard on the Remote Computer.
Have these Batch Commands right after CONNECT.EXE /MS
so that when you make the link, then Exit Connect they run next. 

RASERVER, RACLIENT, MSERVER, FSERVER

RACLIENT does Remote Control of the Remote Computer's Screen 
and Keyboard once a good Modem Link has been established. 
It has the ability to DIAL a Modem Link, but not ANSWER one. 
It also does File Transfers, Compares, and Creates Folders. 
It uses a nice GUI Window File Directory Layout to do this.
This makes it a little more versatile than just Mapped Drives.
It is highly recommended to use if you are transfering files 
using Modems. Using the GUI is faster than the Mapped Drives. 
It calculates a CheckSum for each file Transfered, and there 
is a special "Modem/Settings RASERVER/Use Safe File Transfer" 
that can recover from Transfer Errors that Mapped Drives can't.
It works with KERNEL.COM and RASERVER.COM for low level file
manipulation on both ends of the link with MSERVER ANSWERING, 
then terminating, then running FSERVER with GUI on other end 
of link, showing activity of link. Or, using CONNECT.EXE and 
RASERVER.COM for everything on other end of link. KERNEL.COM and 
RASERVER.COM must run on both sides of the Link. Some of the 
RACLIENT settings may need some adjusting: Screen Refresh Rate 
= 180, Data Block Size = 501 bytes, Repeats = 9 and Reaction = 360. 
Unchecking "Be Colored" reduces Screen Refresh Bandwidth.

RACLIENT FILE COMMANDS:  ("Portal/File Transfer")

ESC     EXIT File Transfer Mode     F4      Compare
Arrows  Up/Down in Columns          F5      Copy
Tab     Local/Remote Sides          F7      Make Folder
Enter   Open Folder                 F8      Delete
Ctrl \  One Level Higher Folder     F10     Settings
Ctrl R  REFRESH                     +       Selection Mask
Alt F1  Change Local Disk           -       Deselection Mask
Alt F2  Change Remote Disk          Shift + Select Entire Folder
Ctrl F1 Display/Set Attributes      Shift - Deselect Entire Folder
Shift Arrows Select/Deselect then move Up/Down

COMMUNICATING WITH MODEMS USING WINDOWS:

Earlier it was stated that the Modem Section of CONNECT! will not 
work with Windows. This is NOT entirely correct. Once you have set 
up Modem Communication and have it functioning properly in DOS, you
can try Windows next. DO NOT PROCEED until you are totally 
satisified with proper setup and fuctionality in DOS first!
The way CONNECT! can work in Windows is with one Computer running 
KERNEL.COM, RASERVER.COM and CONNECT.EXE in Modem ANSWER Mode. 
The Second Computer runs KERNEL.COM, RASERVER.COM and RACLIENT.EXE 
doing Dialing. After the call is Answered, you should see the 
Server's Screen displayed on the Calling Computer. 
Then try "Portal/File Transfer" and see if you get a Remote Listing. 
What DOES NOT seem to work well in Windows is CONNECT.EXE to 
CONNECT.EXE + KERNEL +SSERVER + SKLIENT with the Mapped Drives 
using a Modem Connection. But using RASERVER + RACLIENT to RASERVER +
CONNECT works OK in WIN-WIN, DOS-WIN, or DOS-DOS.  

SPECIAL OPTIONS: "JKRNL/Settings/Settings/Special"

This provides Translation Reference for the "Special" Section 
in the FLM Modules Settings Section. Must be Czech for Compatibility.
Unless you have GOOD REASON, you should leave these at Default Values.
A change to a bad value can cause CONNECT or RACLIENT not to connect. 

MODEM???.FLM Modules:

Cekani na odpoved
Wait for a Answer
CFGWaitOnAnswer, D, 1-2000, 90

Max rozestup prijimanych dat
Receiption Maximum Data Rate
CFGRecvDataRate, D, 1-2000, 18

Max rozestup vysilanych dat
Transmissions Max Data rate
CFGSendDataRate, D 1-2000, 36

Kodovat odesilana data
Encode Transmited Data
CFGDataScramble, L, Ano/Ne (Ano=Yes, Ne=No)

Pocet vyzvaneni
Number of Rings
CFGRingCount, D, 1-100, 2

Vyhrazeny cas
Allotted Time
CFGResrvdTime, D, 0-65535, 600/10800

Automaticka odpoved
Automaticaly Answer
CFGAutoAnswer, L, Ano/Ne (Ano=Yes, Ne=No)

Akce po rozpadu spojeni
Action when Eroded Link
CFGAfterAction, L, Zadna/Reset (Zadna=None, Reset=Reset)

Povolit neprihlasene
No Logging Permitted
CFGNotLogged, L, Ano/Ne (Ano=Yes, Ne=No)

All other *.FLM Modules:

Vyjmout port z BIOSu
Name Port after BIOS
CFGBIOSOut, L, Ne/Ano (Ne=No, Ano=Yes)

Cekani na prijimac
Wait on Receiption
CFGWaitOnRecv, H, 0-$FFFF, $1000

Max rozestup bytu dat
Maxmum Data Byte Rate
CFGDataRate, H, 0-$FFFF, $1000

Max rozestup bytu knotroly
Max Data Byte Control Rate
CFGCtrlRate, H, 0-$FFFF, $4000

Rychlost kontrolnich dat
Baudrate Speed Controler
CFGCtrlSpeed, H, 0-$FFFF, $50


SPECIAL MODEM-TO-MODEM DIRECT CABLE CONSTRUCTION:

To Make a 10DB Padded RJ-11 Phone Cable, insert two 820 Ohm resistors 
in series with one of the wires, and a 220 Ohm resistor connected to 
the junction of the two 820 Ohm resistors and the other end of the 
220 Ohm resistor to the other wire, like this:

Modem1....R1.........R2....Modem2
                |
                R3
                |
Modem1.....................Modem2    where R1,R2=820 Ohms; R3=220 Ohms
 
The recommended value for the amount of DB attenuation is -6 to -20DBv
The formula to calculate  the amount of DB attenuation is:
(10*(LOG10(R3/(R1+R3))))+3 with R1=R2, and R1+R3= Aprox. 1000 Ohms.
Selecting a value of 750 to 1000 Ohms for R1 & R2 sets the Impeadance 
of the line to Aprox 1000 Ohms, which makes the Modem's analog I/O 
circuity happy and terminate properly, reducing echo effects. 

Without the 10DB Pad, you might get errors between the two modems. 
The special Init String lets the Modems ignore the need for a 
Dial Tone or to have to be hooked to a normal Phone Line. 
Depending on the Modems' characteristics, you MAY be able to get 
away WITHOUT EVEN USING an attenuator pad, and just use a straight 
RJ-11 common 6 foot extension cable. Without the attenuator, most 
Modems have enough output and sensitivity to drive a 5000 Foot Line!
So be cautious about overloading modems with a straight 6 foot line. 
A typical Modem has a 1000 Ohm Input/Output Impeadance, 
-10dbmv Output Level (0.8vac), and -9 to -40dbmv receive sensitivity. 

A commonly available female-female RJ-11 adapter is available at many
stores. You can disassemble one of these and put the three resistors
inside of it, making your own -10DB Pad. This is convenient instead of
splicing an RJ-11 Cable.

Alternative Balanced 10DB Pad with Phone Line Compatibility:

Modem1....R1.........R2....Modem2  R1,R2,R3,R4 = 560 Ohms
                |
                R5                 R5 = 270 Ohms
                |+
                C1                 C1,C2 = 10uF @ 50V mini electrolytic
                |-
                C2
                |+
Modem1....R3.........R4....Modem2

NOTE: Capacitors are connected common negatives.
      Use 100 Volt rating for component protection if network 
      will be subject to RINGING Voltages. (70VAC @ 15 HZ)


CONNECT! CABLES:
Connect Shield and Ground 
to Shell each end

7-Wire Serial
10 Meters recommended
30 Meters Possible
10KB/s Standard
20-40KB/s Turbo:

DE9F-DE9F
2-3 (3-Wire)
3-2 (3-Wire)
4-6
5-5 Ground (3-Wire)
6-4
7-8
8-7

DB25-DB25
2-3
3-2
4-5
5-4
6-20
7-7
20-6

DE9 to DB25 Adapter:
1-8 CD
2-3 RD
3-2 TD
4-20 DTR
5-7 Ground
6-6 DSR
7-4 RTS
8-5 CTS
9-22 RI

11-Wire Parallel 4-Bit, DB25M-DB25M
5 Meters recommended,
10 Meters possible. 
70-110 KB/s :

2-15
3-13
4-12
5-10
6-11
10-5
11-6
12-4
13-3
15-2
(18,25)-(18,25) Ground

17-Wire 7,8-Bit Cable:
125-180KB/s

1-15
2-2
3-3
4-4
5-5
6-6
7-7
8-8
9-9
10-17
12-16
13-14
14-13
15-1
16-12
17-10
(18,25)-(18,25)

8-Bit 18-Wire BiDirectional ECP Cable
400KB/s:

1-10
2-2
3-3
4-4
5-5
6-6
7-7
8-8
9-9
10-1
11-14
12-16
13-13
14-11
15-17
16-12
17-15
(18,25)-(18,25)



CONNECT.NFO

CONNECT! 2.0 Program Suite.
Allows Computer-to-Computer Port 
File Transfers over Serial and 
Parallel Cables from simple 3-Wire
10KB/s up to 18-Wire ECP at 400KB/s.
2-Wire Direct Modem-to-Modem Transfers.
Local/Remote Print Queues, Remote Control, 
Modem Dial-Up, and Permissions Support. 
Based on using Mapped Drives for 
Interfacing. Designed for DOS, but 
CAN be run in Windows 9x in special 
Compatibility Mode. Compatible with 
Standard LapLink Serial & Parallel 
Cables, RJ-11 Telephone Extension 
Cable, and 2 other more advanced 
Parallel Cables; All Wiring Diagrams.
A VERY versatile cable transfer program. 
FREEWARE! Written in Borland Pascal 7.
IBM PC AT processor 80286 minimum. 
Written in Czech, but Patches 
included to translate into English. 
Patches must be run under Win32. 


FILE_ID.DIZ

English Patch for 
FORTECH CONNECT! 2.0 
Serial/Parallel Port 
Direct Cable 
File Transfer Program 

Program Download URL's:
http://www.fortech.cz/download/connect.arj
http://www.hw-server.com/docs/spp_ecp/conect/conect2_.exe

Anglicky Zarizovat pro 
FORTECH CONNECT! 2.0 
Seriove/Paralelni Portu 
Primy Kabel
Soubor Prenosu Programu 




# 0 1 2 3 4 5 6 7 8 9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z