<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100">
    <title>gmane.comp.hardware.trs80.model100</title>
    <link>http://permalink.gmane.org/gmane.comp.hardware.trs80.model100</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29907"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29906"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29905"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29904"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29903"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29902"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29901"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29900"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29899"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29898"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29897"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29896"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29895"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29894"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29893"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29892"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29891"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29890"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29889"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29888"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29907">
    <title>Re: NADSBox ships...</title>
    <link>http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29907</link>
    <description>Hey Rick, is mine one of the ones that hasn't been mailed yet? Just checking, as I'm only three and a half hours drive north of you, and I figured it would be her today as that's how long the other orfers from you took. I've had theft issues with packages sitting on doorsteps before, so I figured I'd check. Call me paranoid! It's like waiting for Santa. Let me know if you have a sec. Thanks!
 
-Jon 

--- On Thu, 12/4/08, Rick Hanson &lt;rick-9mhi4SenqfFAfugRpC6u6w&lt; at &gt;public.gmane.org&gt; wrote:

From: Rick Hanson &lt;rick-9mhi4SenqfFAfugRpC6u6w&lt; at &gt;public.gmane.org&gt;
Subject: Re: NADSBox ships...
To: m100-E4oWkhjlVFm5hqqOCiNUZw&lt; at &gt;public.gmane.org
Date: Thursday, December 4, 2008, 5:05 PM

Oops!  I missed that detail.  I just now renamed the file on the 
development computer to loader.do.  I recommend that when the 
NADSBoxes arrive, place the card in a card reader or USB port on your 
PC and rename that file before using it in your Model "T".

At least 14 people will have it named right ... thanks for the detail 
Brian.  -R</description>
    <dc:creator>Jonathan Rose</dc:creator>
    <dc:date>2008-12-05T04:35:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29906">
    <title>RE: NADSBox ships...</title>
    <link>http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29906</link>
    <description>
On Thu, 4 Dec 2008 18:12:24, Brian Brindle wrote:
 
Great!  The first production NADSBox in use finally after it first started 6 years ago!!! Yeeaaaaaah!
 
 
Thanks, I put a lot of attention into the machining and printing details of the enclosure.  After cuting 6 beta enclosures by hand, I knew I needed a better and quicker solution.  If I had to cut each of them by hand, I would probably still be cutting holes.  :)
 
 
As Rick has already identified, this was a slight oversight when copying files to the SD cards.  Simply rename the LOADER1.DO file to LOADER.DO.
 
 
Yeah, the original plan was to get a factory in China to build a bunch of short, flexible cables.  But most of the factories wanted me to order like 5000 cables minimum, so that idea didn't pan out.  The one place I did locate created a sample cable that was very poor quality and wouldn't make good connection 90% of the time.  Perhaps I can search more when I return to China in a couple of weeks.
 
 
Glad you like it so far and thanks for the f</description>
    <dc:creator>Kenneth Pettit</dc:creator>
    <dc:date>2008-12-05T04:20:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29905">
    <title>RE: A technical question on the m100 file system.</title>
    <link>http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29905</link>
    <description>Didn't we just have this discussion? 

I think instead of hex the easiest way to dump the M100's memory without disturbing RAM 
by loading another program is to set the PC to capture text at 19200bd and on the model T:

OPEN"COM:98N1E"FOR OUTPUT AS 1:FOR I=32768 TO HIMEM:PRINT#1,PEEK(I):NEXT

And then trivially convert the captured file back to text on the PC and search through it for
your lost files.

Of course the NADSBOX should make this even simpler if it is even still necessary.

m
********************************

----------
From: Stephen Adolph[SMTP:twospruces-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org]
Sent: Thursday, December 04, 2008 6:59 PM
To: m100-E4oWkhjlVFm5hqqOCiNUZw&lt; at &gt;public.gmane.org
Subject: Re: A technical question on the m100 file system.

Maybe some of the data is still there, but you would need to dump it
to see what can be saved.  the dump process would need to kinda fancy,
to be able to get all 29k of data out the serial port.

I think that is a whole application on it's own.  requiri</description>
    <dc:creator>M H Stein</dc:creator>
    <dc:date>2008-12-05T03:56:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29904">
    <title>Re: NADSBox ships...</title>
    <link>http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29904</link>
    <description>Oops!  I missed that detail.  I just now renamed the file on the 
development computer to loader.do.  I recommend that when the 
NADSBoxes arrive, place the card in a card reader or USB port on your 
PC and rename that file before using it in your Model "T".

At least 14 people will have it named right ... thanks for the detail 
Brian.  -Rick-


At 03:12 PM 12/4/2008, Brian Brindle wrote:


</description>
    <dc:creator>Rick Hanson</dc:creator>
    <dc:date>2008-12-05T01:05:00</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29903">
    <title>Re: NADSBox ships...</title>
    <link>http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29903</link>
    <description>That's great news, Brian.  I mailed 26 of the 40 units on Tuesday.  I 
have 8 in process ... 4 waiting for me to finish TS-DOS ROMs that 
were ordered at the same time, and 4 that just need finish packing 
and shipping.  Only 6 remain unpaid, unpacked and unshipped.  It will 
all work out over time.  I'm keeping the pressure on to push through 
all the remaining orders.  My only block is my day business taking 
most of the time each day.  We'll get there... -Rick-


At 12:40 PM 12/4/2008, Brian Brindle wrote:


</description>
    <dc:creator>Rick Hanson</dc:creator>
    <dc:date>2008-12-05T00:54:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29902">
    <title>Re: A technical question on the m100 file system.</title>
    <link>http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29902</link>
    <description>Ok, thanks for the input. Most of my stuff is in very small files (poetry for example), so the whole file might only take up 2-6k. I'm wondering if there is not some kind of way to dump the contents of the memory to, say, the new NADSbox via the text-&gt;SD feature. 
 
Guess I've got some more tinkering to do :-)

Thanks again for the input!
--- On Thu, 12/4/08, Stephen Adolph &lt;twospruces-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt; wrote:

From: Stephen Adolph &lt;twospruces-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt;
Subject: Re: A technical question on the m100 file system.
To: m100-E4oWkhjlVFm5hqqOCiNUZw&lt; at &gt;public.gmane.org
Date: Thursday, December 4, 2008, 3:59 PM

Maybe some of the data is still there, but you would need to dump it
to see what can be saved.  the dump process would need to kinda fancy,
to be able to get all 29k of data out the serial port.

I think that is a whole application on it's own.  requiring ram.  Some
of the TS roms had a cold boot recovery function.  that might be a
better way to go.

One ca</description>
    <dc:creator>Jonathan Rose</dc:creator>
    <dc:date>2008-12-05T00:51:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29901">
    <title>Re: A technical question on the m100 file system.</title>
    <link>http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29901</link>
    <description>Maybe some of the data is still there, but you would need to dump it
to see what can be saved.  the dump process would need to kinda fancy,
to be able to get all 29k of data out the serial port.

I think that is a whole application on it's own.  requiring ram.  Some
of the TS roms had a cold boot recovery function.  that might be a
better way to go.

One can imagine a scenario where that technique can work, where you
rebuild a file, but I think it is a little tricky since there is a
file system interaction.

Simplest would be dump all ram to serial port and see what you can do
with it externally.

You would have to dump ram using hex encoding or something, to get
around the control characters.
..Steve



On Thu, Dec 4, 2008 at 4:25 PM, Jonathan Rose &lt;ipaq1945-/E1597aS9LQAvxtiuMwx3w&lt; at &gt;public.gmane.org&gt; wrote:

</description>
    <dc:creator>Stephen Adolph</dc:creator>
    <dc:date>2008-12-04T23:59:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29900">
    <title>Re: NADSBox ships...</title>
    <link>http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29900</link>
    <description>Mine hasn't made it to texas yet.

Lee

On Thu, Dec 4, 2008 at 5:12 PM, Brian Brindle &lt;bbrindle-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt; wrote:




</description>
    <dc:creator>Lee Kelley</dc:creator>
    <dc:date>2008-12-04T23:47:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29899">
    <title>Re: WP2s</title>
    <link>http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29899</link>
    <description>Hello sir:


There is no WP2-specific variant of TEENY.  Consequently, TEENY.EXE does not
recognize an attached WP2 laptop.

Keeper of the Primordial Bit (mother of all bits),  -= Ron Wiesen =-

----- Original Message ----- 
From: &lt;coxon.spencer-rieW9WUcm8FFJ04o6PK0Fg&lt; at &gt;public.gmane.org&gt;
To: &lt;m100-E4oWkhjlVFm5hqqOCiNUZw&lt; at &gt;public.gmane.org&gt;
Sent: Thursday, December 04, 2008 8:35 PM
Subject: WP2s




</description>
    <dc:creator>Ron Wiesen</dc:creator>
    <dc:date>2008-12-04T23:28:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29898">
    <title>Re: NADSBox ships...</title>
    <link>http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29898</link>
    <description>Just got home and unwrapped my NADSBox!

The quality of this devices is far better than I expected. The case on
this thing is down right beautiful! The devices was very well packaged
and even contained 2 AA batteries, and the coolest little SD card I've
ever seen. The whole built in USB port on the SD card had me confused
for a few seconds.

Popped it in - set my terminal to 98N1D and flipped the switch. I was
greeted with the license acceptance screen and typed accept. The
command prompt access via term is very useful and well done. In my
opinion the devices is worth the cost just to be able to type text
files on an SD card.  Now keep in mind I haven't read the directions
to this thing yet but found BOOTST.DO on the card. I used type to
display the file and saved it as bootsts.do. I then loaded that in
BASIC and saved as a BA file. Of course I forgot to remove the command
prompt from my bootsts.do file so this didn't work. Edited bootsts.do
and removed the &gt; from the end saved as a BA file fired it up and..</description>
    <dc:creator>Brian Brindle</dc:creator>
    <dc:date>2008-12-04T23:12:24</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29897">
    <title>Tandy WP-2 on eBay</title>
    <link>http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29897</link>
    <description>There's a WP-2 on eBay right now. The seller says it works, but that it has
some problems.

 

Item #  320321305752

</description>
    <dc:creator>Jim Tiner</dc:creator>
    <dc:date>2008-12-04T22:42:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29896">
    <title>Re: Ohhh.... Dear....</title>
    <link>http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29896</link>
    <description>
I heard it called Trash-DOS long before I heard the whole computer get called the Trash-80.  For good reasons, too, like how it, upon discovering that the file you were storing was too large to fit in the space available on the disk, would cheerfully continue writing it over track 0, rendering the disk unreadable.  I liked DOSPLUS.  It had features that MS-DOS never got.


      

</description>
    <dc:creator>Mike Warns</dc:creator>
    <dc:date>2008-12-04T22:29:40</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29895">
    <title>Re: Ohhh.... Dear....</title>
    <link>http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29895</link>
    <description>

TRS-80 is Trash-80. Even my freind Kurt Dekker used to call it that. Radio
Shacks computers just never had a very good reputation, and even the Model
100  has that pesky tendency to cold start. Don't run from the "Trash-80"
term, it is a familiar, term of endearment.



Nice! He's dreaming a bit, but maybe he'll get the $300. But what is the
CueCat doing there??
</description>
    <dc:creator>Peter Vollan</dc:creator>
    <dc:date>2008-12-04T22:08:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29894">
    <title>Re: WP2s</title>
    <link>http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29894</link>
    <description>
What are you using to convert? I think I made a Perl script at some point...

</description>
    <dc:creator>John R. Hogerhuis</dc:creator>
    <dc:date>2008-12-04T22:03:34</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29893">
    <title>Re: WP2s</title>
    <link>http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29893</link>
    <description>I love my WP2!  In Windows XP I have had success using LaddieCon.exe
(available from www.bitchin100.com) for all my Model T and WP2 transfers.
Subsequently, you still need to run your file through the converter to get
it into decent plain text, but getting it onto your computer is half the
battle!

-Eric

On Thu, Dec 4, 2008 at 12:35 PM, &lt;coxon.spencer-rieW9WUcm8FFJ04o6PK0Fg&lt; at &gt;public.gmane.org&gt; wrote:

</description>
    <dc:creator>Eric Nakano</dc:creator>
    <dc:date>2008-12-04T21:54:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29892">
    <title>Re: Club 100 Website Provides Nuts &amp; Bolts Technical Information -- Was: Re: A technical question on the m100 file system.</title>
    <link>http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29892</link>
    <description>Thanks Ron, I have actually used the files on the M-100 at Club 100 on several occasions. I know I can look them up, of course, but it's more fun to tinker first. It's kind of how I learn. I do the same thing with cars. I fiddle around for a bit, and then I go look it up. When I do that, I tend to remember things forever. I tend to go crosseyed if I try to read first without tinkering, and it doesn't 'sink in'. 
 
Thank you for the excellent idea about personalizing a copy of the memory map though!That's a fantastic idea. It never occured to me to make my own. I've also toyed with the idea of taking all the important stuff from all over the web and condensing it into a 'Model 100 Bible', so to speak, where it's all formatted in a printible format (either pdf of publisher) so that you could print out one big book and have everything you would ever need in one place. At least, it sounded like a good idea to me. 
 
Thanks so much for the detailed response!

--- On Thu, 12/4/08, Ron Wiesen &lt;ronw-q0bwPPp</description>
    <dc:creator>Jonathan Rose</dc:creator>
    <dc:date>2008-12-04T21:37:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29891">
    <title>Re: A technical question on the m100 file system.</title>
    <link>http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29891</link>
    <description>Thanks Steve! That makes sense. So there is no easy way to 'undelete' a file, since the pointers get moved around, huh? Here's the reason I'm asking:
 
I'm a writer, and there have been three seperate occasions where the M-100's memory got corrupted (using UR-2/VIEW60 mainly), and I lost some work. My idea was to write this program that logs (in a .do file I could print) what the addresses of the different files were in memory, so if something 'went wrong'. I could dump the contents of RAM into a .do file, and salvage the writing after transfering it to the PC or NADSbox.
 
Is this in any way feasible? Assuming a file was deleted or 'messed up', and no new files were created (so the file's RAM was not overwritten), could I still scan the previous RAM location and get the file back, or is it more complicated than that? I've seen utilities to dump ALL of the ram (in case of a cold start), but I was looking for something smaller, quicker, and more easily useable. 
 
In other words, if I knew that my story f</description>
    <dc:creator>Jonathan Rose</dc:creator>
    <dc:date>2008-12-04T21:25:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29890">
    <title>Bitchin100 also provides free space for documentation</title>
    <link>http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29890</link>
    <description>Good info and it looks like your private stash is even better :-) .

The "private copy" thing is why I created the Bitchin100 DocGarden wiki.

Wikis are easy for anyone to edit.

So for my own documents and tidbits I get off the list, I prefer a 
public copy that is a living document open to the community to improve.

http://bitchin100.com/wiki/index.php?title=Model_T_DocGarden

It keeps a version history so if someone puts something wrong it is 
fairly easy to recover the prior state. Haven't had a problem with 
"tragedy of the commons" yet but so far I am the main contributor to the 
DocGarden.

</description>
    <dc:creator>John R. Hogerhuis</dc:creator>
    <dc:date>2008-12-04T21:19:13</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29889">
    <title>Re: WP2s</title>
    <link>http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29889</link>
    <description>What you need is laddiecon, which you can find on the bitchin' 100 site.The WP-2 works just fine with it, and the WP 2's built in file transfer utility is already installed. It's been quite awhile since I used mine, as I prefer the Model 100s, but you basically start up the command line program on the PC side and set it to the correct serial port, and then start up the file transfer software on the WP-2. Select disk, as laddiecon (like Desklink and Teeny) emulates the TPDD protocol, and you should be able to load and save files with ease between the two computers. Very easy!

--- On Thu, 12/4/08, coxon.spencer-rieW9WUcm8FFJ04o6PK0Fg&lt; at &gt;public.gmane.org &lt;coxon.spencer-rieW9WUcm8FFJ04o6PK0Fg&lt; at &gt;public.gmane.org&gt; wrote:

From: coxon.spencer-rieW9WUcm8FFJ04o6PK0Fg&lt; at &gt;public.gmane.org &lt;coxon.spencer-rieW9WUcm8FFJ04o6PK0Fg&lt; at &gt;public.gmane.org&gt;
Subject: WP2s
To: m100-E4oWkhjlVFm5hqqOCiNUZw&lt; at &gt;public.gmane.org
Date: Thursday, December 4, 2008, 12:35 PM

They may not have the nostalgic factor of the Model 100 -- but I think they 
a</description>
    <dc:creator>Jonathan Rose</dc:creator>
    <dc:date>2008-12-04T21:15:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29888">
    <title>Re: NADSBox ships...</title>
    <link>http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29888</link>
    <description>Hello Brian:

It takes a #%!! of a man to entrust his wife with the safekeeping of his
NADSBox &lt;wink&gt;,

73 to KG4NIQ de WD8PNL,  -= Ron Wiesen =-

----- Original Message ----- 
From: "Brian Brindle" &lt;bbrindle-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt;
To: &lt;m100-E4oWkhjlVFm5hqqOCiNUZw&lt; at &gt;public.gmane.org&gt;
Sent: Thursday, December 04, 2008 8:40 PM
Subject: Re: NADSBox ships...


Ken on developing a great product! It's one thing &gt; to blow hot air on the
list (as I am wont to do) it's another thing to &gt; put in the hours and "just
ship it."&gt; &gt; Great work, man.Thanks John.  I am anxious to here what everyone
else thinks of the device also.  It certainly has been a long time coming.Ken


</description>
    <dc:creator>Ron Wiesen</dc:creator>
    <dc:date>2008-12-04T21:18:13</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29887">
    <title>Re: WP2s</title>
    <link>http://permalink.gmane.org/gmane.comp.hardware.trs80.model100/29887</link>
    <description>
Well, good news: this is a 100% solved problem.

The WP-2 works with LaddieCon.exe from DISKETTE on the FILES menu (it 
also works with DLPlus, and DLPilot).

You can find LaddieCon.exe at http://bitchin100.com

Also, WP-2 works with NADSBox. I tested this feature.

One thing you will want to do is convert to .DA file rather than .DO 
before you transfer the file. On the WP-2, DO format is a binary format.

</description>
    <dc:creator>John R. Hogerhuis</dc:creator>
    <dc:date>2008-12-04T21:09:40</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.hardware.trs80.model100">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.hardware.trs80.model100</link>
  </textinput>
</rdf:RDF>
