summaryrefslogtreecommitdiffabout
path: root/help/pumpkin.xml
Unidiff
Diffstat (limited to 'help/pumpkin.xml') (more/less context) (ignore whitespace changes)
-rw-r--r--help/pumpkin.xml3
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 @@
1<?xml version="1.0"?> 1<?xml version="1.0"?>
2<winhelp> 2<winhelp>
3 <topic id="About" title="About PumpKIN" keywords="about"> 3 <topic id="About" title="About PumpKIN" keywords="about">
4 <heading scroll="no">About <kin>PumpKIN</kin></heading> 4 <heading scroll="no">About <kin>PumpKIN</kin></heading>
5 <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> 5 <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>
6 <p/> 6 <p/>
7 <p><b><i>Enjoy!</i></b></p> 7 <p><b><i>Enjoy!</i></b></p>
8 <license years="1997-2006"/> 8 <license years="1997-2006"/>
9 <credist/> 9 <credist/>
10 </topic> 10 </topic>
11 <topic id="News" title="What's New"> 11 <topic id="News" title="What's New">
12 <newsfor version="2.7.1" date="March 13th, 2006">
13 <ni>Bugfix release</ni>
14 </newsfor>
12 <newsfor version="2.7" date="February 28th, 2006"> 15 <newsfor version="2.7" date="February 28th, 2006">
13 <ni>Access lists based on request IP address and TFTP opcode for automating access policy</ni> 16 <ni>Access lists based on request IP address and TFTP opcode for automating access policy</ni>
14 <ni>Possibility to start/stop TFTP server, while keeping client functionality intact</ni> 17 <ni>Possibility to start/stop TFTP server, while keeping client functionality intact</ni>
15 <ni>Logging to file</ni> 18 <ni>Logging to file</ni>
16 <ni>Resizable main window</ni> 19 <ni>Resizable main window</ni>
17 </newsfor> 20 </newsfor>
18 <newsfor version="2.6" date="August 6th, 2005"> 21 <newsfor version="2.6" date="August 6th, 2005">
19 <ni>more robust solution to the backslash/slash dilemma</ni> 22 <ni>more robust solution to the backslash/slash dilemma</ni>
20 <ni>A bit more elaborate error reporting</ni> 23 <ni>A bit more elaborate error reporting</ni>
21 <ni>Fixed uninstall procedure so that it works on XP</ni> 24 <ni>Fixed uninstall procedure so that it works on XP</ni>
22 </newsfor> 25 </newsfor>
23 <newsfor version="2.5" date="July 11th, 2004"> 26 <newsfor version="2.5" date="July 11th, 2004">
24 <ni>Change of <a href="#About">license</a> and opening the source.</ni> 27 <ni>Change of <a href="#About">license</a> and opening the source.</ni>
25 <ni>Minor cosmetic changes</ni> 28 <ni>Minor cosmetic changes</ni>
26 </newsfor> 29 </newsfor>
27 <newsfor version="2.0" date="June 13th, 1998"> 30 <newsfor version="2.0" date="June 13th, 1998">
28 <ni>Sounds customization. Now you can customize <kin>PumpKIN</kin> bells and whistles or turn them off completely.</ni> 31 <ni>Sounds customization. Now you can customize <kin>PumpKIN</kin> bells and whistles or turn them off completely.</ni>
29 <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> 32 <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>
30 <ni>Typo causing <kin>PumpKIN</kin> to log outgoing request in reverse (i.e. <i>Requesting 'hostname' from 'filename'</i>) fixed.</ni> 33 <ni>Typo causing <kin>PumpKIN</kin> to log outgoing request in reverse (i.e. <i>Requesting 'hostname' from 'filename'</i>) fixed.</ni>
31 <ni>Something else that you may not notice and I can not remember.</ni> 34 <ni>Something else that you may not notice and I can not remember.</ni>
32 </newsfor> 35 </newsfor>
33 <newsfor version="1.5" date="February 12th, 1998"> 36 <newsfor version="1.5" date="February 12th, 1998">
34 <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> 37 <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>
35 <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> 38 <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>
36 <ni>New Install program</ni> 39 <ni>New Install program</ni>
37 </newsfor> 40 </newsfor>
38 </topic> 41 </topic>
39 <topic id="Using" title="Using PumpKIN"> 42 <topic id="Using" title="Using PumpKIN">
40 <heading scroll="no">Using <kin>PumpKIN</kin></heading> 43 <heading scroll="no">Using <kin>PumpKIN</kin></heading>
41 <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> 44 <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>
42 <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> 45 <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>
43 <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> 46 <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>
44 <p>Use <a href="#Options">Options</a> button to set <kin>PumpKIN</kin> options.</p> 47 <p>Use <a href="#Options">Options</a> button to set <kin>PumpKIN</kin> options.</p>
45 <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> 48 <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>
46 </topic> 49 </topic>
47 <topic id="ConfirmRRQ" title="Confirm Read Request Dialog"> 50 <topic id="ConfirmRRQ" title="Confirm Read Request Dialog">
48 <heading scroll="no">Confirm Read Request Dialog</heading> 51 <heading scroll="no">Confirm Read Request Dialog</heading>
49 <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> 52 <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>
50 </topic> 53 </topic>
51 <topic id="ConfirmWRQ" title="Confirm Write Request Dialog"> 54 <topic id="ConfirmWRQ" title="Confirm Write Request Dialog">
52 <heading scroll="no">Confirm Write Request Dialog</heading> 55 <heading scroll="no">Confirm Write Request Dialog</heading>
53 <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> 56 <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>
54 </topic> 57 </topic>
55 <topic id="Request" title="Request Dialog"> 58 <topic id="Request" title="Request Dialog">
56 <heading scroll="no">Request Dialog</heading> 59 <heading scroll="no">Request Dialog</heading>
57 <p>Request dialog is aimed to let you form read or write request. You may set the following options:</p> 60 <p>Request dialog is aimed to let you form read or write request. You may set the following options:</p>
58 <ul> 61 <ul>
59 <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> 62 <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>