summaryrefslogtreecommitdiffabout
path: root/help/pumpkin.xml
authorMichael Krelin <hacker@klever.net>2006-03-13 21:52:28 (UTC)
committer Michael Krelin <hacker@klever.net>2006-03-13 21:52:28 (UTC)
commit24e693797daef020ece3fa19bb5acce000e37165 (patch) (unidiff)
tree0f2333976f4bc86e8c0b30d0a3e99c8279e435a0 /help/pumpkin.xml
parent05d4b744ffcfd511f7c99969e9e32bf92afdfe4d (diff)
downloadpumpkin-2.7.1.zip
pumpkin-2.7.1.tar.gz
pumpkin-2.7.1.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
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,35 +1,38 @@
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>