@database Connect.Guide @author "Dirk Tietke" @$VER: Connect V3.0 AmigaGuide-Dokumentation @FONT topaz 8 @help Connect/Help @NODE Main "Connect.Guide: Inhalt" **** Connect Version 3.0 **** ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @{"Program-Description........" LINK "About"} Short Bla bla... @{"How does it work..........." LINK "Connect"} Short Description @{"Installation..............." LINK "Install"} How can I install this thing? @{"Copyright.................." LINK "Copyright"} Where does it come from and how much does it cost? @{"Bugs......................." LINK "fehler"} Nobody is perfect. ;-) @{"Changes...................." LINK "changes"} What's different since last version? @ENDNODE @NODE Connect "Connect.Guide: Short description" One click on the Icon of Connect es it runs quiet in the Background. In the WaitStatus it uses no CPU-Time. You can quit Connect, when you start it again, with Exchange or the Workbench Command BREAK. @ENDNODE @NODE Help "Connect.Guide: Help" Help: ~~~~~ At Problems Tel.: +(49) 481-71648 (ZyXEL) oder +(49) 481-78112 (ISDN) and write to User MC Or call me directly under +(49) 4835-9295. or write to E-Mail an MC@MANIA.PROMETHEUS.DE @ENDNODE @NODE Install "Connect.Guide: Installation" The Installations is fool (oops..., full) easy. Connect can be places in any Directory you want and ConnectPrefs in the same or in the 'Sys:Prefs/' Directory. When ConnectPrefs is started, you can configure different things. The Settings of both Devices could't be totaly different! i.e. my LapTop (damn old thing) can only handle 19200 Baud and my A4000 can handle much more. Also, my Modem is connected to my A4000 with a 7-Wire Cable. The NullModem Cable to the LapTop is only with 3 wires. ---------------------------------------------------------------------------- The Settings for the 1st Device (A4000): Device1...: duart.device Unit......: 0 Baud......: 57600 XOn/XOff......: Off Shared........: Off High Speed....: On RS232 7Wire...: On and the Settings for the 2nd Device (LapTop): Device1...: duart.device Unit......: 1 Baud......: 19200 <- Same BaudRate in the TerminalProgram XOn/XOff......: On <- because, 3 wires. (no RTS-CTS wire) Shared........: Off High Speed....: On RS232 7Wire...: Offs <- so what, only 3 wires ---------------------------------------------------------------------------- Connected with my A2000 and a 7-Wire Cable I used following settings: The Settings for the 1st Device (A4000): Device1...: duart.device Unit......: 0 Baud......: 57600 XOn/XOff......: Off Shared........: Off High Speed....: On RS232 7Wire...: On and the Settings for the 2nd Device (A2000): Device1...: duart.device Unit......: 1 Baud......: 57600 <- Same Baudrate in the Ter TerminalProgram XOn/XOff......: Off Shared........: Off High Speed....: On RS232 7Wire...: On ---------------------------------------------------------------------------- My Configuration of my A4000: Processor: 68040 Takt : 40MHz Memory : 32MByte FastRam, 2 MB Chip, Add : MultiFaceCard II The Baudrate were very good. Also, Connect will use @{b}NO@{ub} CPU-Time when nothing is transfering, it doesn't care if you have an Connect or not. A friend of mine (Hi Simon (Calderone)) tested it with two Amigas. The first one has a 68040 and the otherone has a 68060 CPU. He tested it with CPU-Time of 25% needed and a CPS-Rate of 7000!!!! It's cool, he??? @ENDNODE @NODE About "Connect.Guide: Programdescription" Programdescription: ~~~~~~~~~~~~~~~~~~~ Well, I have a second Amiga and a old Laptop here but only one ISDN-Card. First, to switch always the Modem to the one and then to the other sucks. Also, the LapTop can't handle a Amiga-Isdn-Card. So what to do??? Because I would connect them together with a NullModemCalbe (I got it befor) and I would run my LapTop or A2000 over the first (A4000) Computer. Thought, Done... so after 3 hours I had the prototype of the Program and I began to test. The TestResults were very good. Please see under @{"Installation" LINK "install"}, because there are some results. @ENDNODE @NODE Copyright "Connect.Guide: Copyright" Copyrights: ~~~~~~~~~~~ This Program is TOTALY FREE! Well, if someone thinks, well done, or nice usefull programm, it would be nice to send me some (Present, FanPost, Money, Gold, Diamonds...) Dirk Tietke Neue Anlagen 1o 25767 Bunsoh Germany KtNr: 652456-2o8 Blz : 2oo1oo2o Postgiroamt Hamburg You can get it out of the WuselMania: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ZyXEL: +(49) 481-71648 ISDN : +(49) 481-78112 And who? ~~~~~~~~ E-Mail: MC@MANIA.PROMETHEUS.DE Box : Write To MC or draw in the SupportAreas! Well, do not write to the Sysop, because I am not the Sysop. @ENDNODE @NODE fehler "Connect.Guide: Bugs and Help" When you switch the Gadget of Exchange to 'Inaktiv' or 'Aktiv' than Connect hangs. Well, I will fix this Problem, when I have enough Fun to do that :-) Otherwise.. I don't think this is soooo important.. doesn't it!?!?!? @ENDNODE @NODE Changes "Connect.Guide: Changes" @FONT topaz.font 8 @{JCENTER} .... .:· .::· ··. .::· .:· .: .::· .: ·:.. ..:· .::· .:: :: ··:::::· ::· .::: .:: .. ::: ..... .:::· ::: ::: .· ::::...::. ..::::::::.. .:: :::: :: .:: ..:· ····::::::::... ·:::::·· ··::. .:::· . ::::: .::::: ::· .::· ::: ···   ... ·:· .:: .:::· .:· .::::: :: ::: :::.. ::: .····:. ..:· .:::· .::· :::::: .:: ::: ···::::.. :: . .:· ·:. ..:·· .:::· .:::· ::::: .::: ::: ··::. ::: :·.:· .:: :· .::::.....::::· :::::: ·::· ::: .::· ::: .:·.:: .::: :.·:. .::· :::::: ::::... ..::· :::.::: ::::....::::· :: ·:::. .::: ·:::: ·:::· .:::· ·::::: ::::::::::· .:: ·::::. .::· .:::· ··· ·:::::·· :::: ·::::: ::· xCz .:::· ·:::· · .::· · @{u} @{uu} @{" 2.6 -> 3.0 " LINK "300"} @{" 2.5 -> 2.6 " LINK "206"} @{" 2.3 -> 2.5 " LINK "205"} @{" 2.1 -> 2.3 " LINK "203"} @{" 2.0 -> 2.1 " LINK "201"} @{" 1.0 -> 2.0 " LINK "200"} @{" 0? -> 1.0 " LINK "100"} @ENDNODE @NODE 300 "Changes 3.0" - ConnectPrefs: Changes Gui to Mui @ENDNODE @NODE 203 "Changes 2.3" - ConnectPrefs: XOn/XOff-Gadget will locked, when the RTS-CTS Flag is set and also switched off. - ConnectPrefs: PullDownMenu build in (Save and Open at time without function) - ConnectPrefs: You can select the TaskPri - ConnectPrefs: You can switch a 'Quit-Requester' on for quitting Connect - Connect: When an Error at opening the Device occures, the Error will shown specily (i.e. an other Device has opend -> Message: Device Busy) - Connect: Changed for the new Config - Written an english Guide.File (sorry for my broken and ugly english) @ENDNODE @NODE 100 "Changes 1.00" - This Version was absolutly bullshit. It was the first Version and was at the SerTrans Archive included. @ENDNODE @NODE 200 "Changes 2.0" - Completly new written! @ENDNODE @NODE 201 "Changes 2.1" - Bug: The received Datas are not send correctly to the 2nd Device :-( @ENDNODE @NODE 205 "Changes 2.5" - Localized (please translate if you like to other languages :)) - Monitoring possible, just enter for example: CON:0/0//120/ConnectOutput/... and all what comes thru the devices will shown on the Consolewindow. Also you can enter a File... but WARNING! Monitoring will slow down! So, be careful with this option! To switch of the Monitor, just Clear the StringGadget, where the Entry is in - MEGA Bug at ConnectPrefs: Closebutton is working now ;) - Gadget for CarrierCheck. So if you try to quit Connect, and the CarrierCheck is enabled Connect will ask befor. - Now you can Disable und Enable Connect via Exchange @ENDNODE @NODE 203 "Changes 2.3" - ConnectPrefs: XOn/XOff-Gadget wird gesperrt, sobald das RTS-CTS Flag gesetzt wird und gleichzeitig abgeschaltet. - ConnectPrefs: PullDownMenu eingebaut (Save und Open laufen noch nicht, hatte bisher kein Bock drauf) - ConnectPrefs: TaskPriorität kann eingestellt werden - ConnectPrefs: Es kann eingestellt werden, ob ein Requester vorm Beenden angezeigt werden soll. - Connect: Wenn beim DeviceÖffnen ein Fehler auftritt, wird der Fehler auch genau angezeigt. 'Konnte Device n nicht öffnen' war nicht so der Hit. - Connect: Angepasst auf neue Prefs @ENDNODE @NODE 100 "Changes 1.00" - An die Version kann ich mich nur noch mit Grauen zurueckerinnern. War aber auch die erste Version (lag bei Sertrans dabei) und lief auch nur mit einem Kanal je Device... @ENDNODE @NODE 200 "Changes 2.0" - Komplett neu programmiert! @ENDNODE @NODE 201 "Changes 2.1" - Bug: Die empfangenen Daten wurden nicht richtig zum zweiten Device gesendet :-( @ENDNODE @NODE 206 "Changes 2.6" - Megalittle Bug fixed - Catalogs to Archive added @ENDNODE