author | Michael Krelin <hacker@klever.net> | 2006-03-13 21:52:28 (UTC) |
---|---|---|
committer | Michael Krelin <hacker@klever.net> | 2006-03-13 21:52:28 (UTC) |
commit | 24e693797daef020ece3fa19bb5acce000e37165 (patch) (side-by-side diff) | |
tree | 0f2333976f4bc86e8c0b30d0a3e99c8279e435a0 /help/pumpkin.xml | |
parent | 05d4b744ffcfd511f7c99969e9e32bf92afdfe4d (diff) | |
download | pumpkin-24e693797daef020ece3fa19bb5acce000e37165.zip pumpkin-24e693797daef020ece3fa19bb5acce000e37165.tar.gz pumpkin-24e693797daef020ece3fa19bb5acce000e37165.tar.bz2 |
Prepared bugfix release 2.7.12.7.1
git-svn-id: http://svn.klever.net/kin/pumpkin/trunk@150 fe716a7a-6dde-0310-88d9-d003556173a8
-rw-r--r-- | help/pumpkin.xml | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/help/pumpkin.xml b/help/pumpkin.xml index 369d5d7..c966fbd 100644 --- a/help/pumpkin.xml +++ b/help/pumpkin.xml @@ -1,59 +1,62 @@ <?xml version="1.0"?>
<winhelp>
<topic id="About" title="About PumpKIN" keywords="about">
<heading scroll="no">About <kin>PumpKIN</kin></heading>
<p><kin>PumpKIN</kin> is a program designed to send and receive files over the net while having <kin href="http://kin.klever.net/T42/">T42</kin> or <product>Wintalk</product> session running using <term>TFTP</term> (<rfc num="1350"/>) protocol. It includes full-functional <term>TFTP</term> server/client so it may be useful for maintaining <a href="http://www.cisco.com/">CISCO</a> routers and other network equipment.</p>
<p/>
<p><b><i>Enjoy!</i></b></p>
<license years="1997-2006"/>
<credist/>
</topic>
<topic id="News" title="What's New">
+ <newsfor version="2.7.1" date="March 13th, 2006">
+ <ni>Bugfix release</ni>
+ </newsfor>
<newsfor version="2.7" date="February 28th, 2006">
<ni>Access lists based on request IP address and TFTP opcode for automating access policy</ni>
<ni>Possibility to start/stop TFTP server, while keeping client functionality intact</ni>
<ni>Logging to file</ni>
<ni>Resizable main window</ni>
</newsfor>
<newsfor version="2.6" date="August 6th, 2005">
<ni>more robust solution to the backslash/slash dilemma</ni>
<ni>A bit more elaborate error reporting</ni>
<ni>Fixed uninstall procedure so that it works on XP</ni>
</newsfor>
<newsfor version="2.5" date="July 11th, 2004">
<ni>Change of <a href="#About">license</a> and opening the source.</ni>
<ni>Minor cosmetic changes</ni>
</newsfor>
<newsfor version="2.0" date="June 13th, 1998">
<ni>Sounds customization. Now you can customize <kin>PumpKIN</kin> bells and whistles or turn them off completely.</ni>
<ni>Previous version of <kin>PumpKIN</kin> had a bug causing it to misbehave when you're requesting file from remote <term>tftp</term> server using <b>IP Address</b> (as opposed to <b>hostname</b>).</ni>
<ni>Typo causing <kin>PumpKIN</kin> to log outgoing request in reverse (i.e. <i>Requesting 'hostname' from 'filename'</i>) fixed.</ni>
<ni>Something else that you may not notice and I can not remember.</ni>
</newsfor>
<newsfor version="1.5" date="February 12th, 1998">
<ni>Transfer resumes. No checking on file contents is done, so it's up to you to decide whether you want to start transmission from the beginning or resume unfinished transfer.</ni>
<ni>Support for <b>block size</b>, <b>trasnfer size</b> and <b>transfer timeout</b> options as described in <rfc num="1782"/>, <rfc num="1783"/> and <rfc num="1784"/>. I'm not sure if there are any other <term>TFTP</term> implementations supporting this, but at least it makes sense if you use <kin>PumpKIN</kin> on both ends.</ni>
<ni>New Install program</ni>
</newsfor>
</topic>
<topic id="Using" title="Using PumpKIN">
<heading scroll="no">Using <kin>PumpKIN</kin></heading>
<p>This is a simple program for file exchange between two parties. It allows you to send files over the network to your party while having a <kin href="http://kin.klever.net/T42/">T42</kin> or <product>Wintalk</product> conversation. It uses open sessions to determine IP address of your party. Also you may use it as a <term>TFTP</term> client/server by itself. To get/put files from/to <term>TFTP</term> server you need to enter host name/IP address manually in the <a href="#Request">Request Dialog</a>.</p>
<p>To Abort transfer(s) currently in progress - select transfer(s) you want to terminate in the list and click <b>Abort xfer</b> button.</p>
<p>You may want to hide <kin>PumpKIN</kin> window and leave it as a tray icon only. Just click the <image source="pumpkin.bmp"/> icon in the tray or simply close the window.</p>
<p>Use <a href="#Options">Options</a> button to set <kin>PumpKIN</kin> options.</p>
<p>You can start and stop <kin>PumpKIN</kin>'s <term>TFTP</term> server by checking and unchecking the <b>Server is running</b> checkbox in the lower right corner of main <kin>PumpKIN</kin> window.</p>
</topic>
<topic id="ConfirmRRQ" title="Confirm Read Request Dialog">
<heading scroll="no">Confirm Read Request Dialog</heading>
<p>When the file is requested from your <term>TFTP</term> server you may choose to <b>Grant Access</b> to this file or to <b>Deny Access</b>. If you hesitate to answer for <a href="#ConfirmationTimeout"><b>Confirmation timeout</b></a> (<i>default - 30 seconds</i>) <kin>PumpKIN</kin> defaults to denial of all requests.</p>
</topic>
<topic id="ConfirmWRQ" title="Confirm Write Request Dialog">
<heading scroll="no">Confirm Write Request Dialog</heading>
<p>Whenever your party sends you a file you have always a choice to accept it or not. You can also save the file under a different name by choosing the <b>Rename</b> option. If you already have file with such name you may chose to <b>resume</b> transfer. No checking on file contents is done. This option may or may not work depending on remote implementation of protocol. It does work if you use <kin>PumpKIN</kin> on both ends. If you are still unsure for <a href="#ConfirmationTimeOut"><b>Confirmation timeout</b></a> (<i>default - 30 seconds</i>) <kin>PumpKIN</kin> will make safe decision for you (deny).</p>
</topic>
<topic id="Request" title="Request Dialog">
<heading scroll="no">Request Dialog</heading>
<p>Request dialog is aimed to let you form read or write request. You may set the following options:</p>
<ul>
<li><b>Local File</b> - You can change the name of the file you're sending (or destination in case you're receiving) right here. You may also use <b>Browse</b> button to select the file.</li>
|