<html><body><span style="font-family:Verdana; color:#000000; font-size:10pt;">Personally, I have always thought that a single do all program would be a wonderful thing. However, as I've begun to play with different programs for different uses such as Winlink, OutpostPM, D*RATS, APRS, etc... It has become very clear to me that separate programs for different protocols is the way to go.<br><br>I would like to see a way to push a message from D*RATS onto Packet or Winlink, but really that could be done easily by copy and paste functionality. So, I don't think it is needed natively.<br><br>The only thing I would really like to see right now is a way to use OutpostPM and Winlink on the same TNC/Radio simulataneously. But, that is for another discussion (unless someone that has done this can pm me offline.)<br><br>Thanks!<br><br>Eric M. Gildersleeve ~ KD7CAO<br>
316 Fry St., #212<br>
Denton, TX 76201<br>
<br>
Mobile: 360.304.0904<br>
E-Mail: <a href="mailto:eric@4gildersleeve.us" mce_href="mailto:eric@4gildersleeve.us">eric@4gildersleeve.us</a><br>
Website: <a href="http://www.4gildersleeve.us/" mce_href="http://www.4gildersleeve.us/">http://www.4gildersleeve.us/</a><br>
<br>
<br><br>
<blockquote webmail="1" style="border-left: 2px solid blue; margin-left: 8px; padding-left: 8px; font-size: 10pt; color: black; font-family: verdana;">
<div >
-------- Original Message --------<br>
Subject: Re: [drats_users] TNC Port Support<br>
From: Dan Smith <dsmith@danplanet.com><br>
Date: Thu, May 28, 2009 2:45 pm<br>
To: Discussion of D-RATS <drats_users@lists.danplanet.com><br>
<br>
> Why don't we get the TNC to do that work? That is after all what it<br>
> does.<br>
<br>
Because D-RATS is, at the end of the day, intended for D-STAR which<br>
doesn't have that same concept. I don't really want to change the<br>
significant part of the protocol stack that would be required to<br>
depend on AX.25 or the TNC to do the heavy lifting. Besides, from<br>
what I understand of how TNCs work, they don't do any of the more<br>
advanced things that D-RATS does, such as use a sliding window for the<br>
stream.<br>
<br>
I didn't intend to push D-RATS into the packet realm, but rather just<br>
provide a way to use a TNC instead of (or alongside) a D-STAR radio<br>
for the purposes of bringing in new users without a cost of entry.<br>
<br>
> Otherwise you'll have to speak KISS etc to a TNC and if you can<br>
> speak KISS then the TNC could not be a TNC at all but rather a copy<br>
> of FBB or JNOS or ... on the end of a virtual comm port.<br>
<br>
I'd much rather leave the standard packet and AX.25 stuff to things<br>
like FBB or JNOS. Leo has expressed some interest in bridging with<br>
OpenBCM for integration with the messages. I think it's probably best<br>
to not drag D-RATS into the packet realm, but rather provide<br>
interfaces to the entities that already rule that world.<br>
<br>
Is that reasonable?<br>
<br>
-- <br>
Dan Smith<br>
dsmith#danplanet.com, s/#/@/<br>
<a href="http://www.danplanet.com" target="_blank" mce_href="http://www.danplanet.com">www.danplanet.com</a><br>
KK7DS<br>
_______________________________________________<br>
drats_users mailing list<br>
drats_users@lists.danplanet.com<br>
<a href="http://lists.danplanet.com/mailman/listinfo/drats_users" target="_blank" mce_href="http://lists.danplanet.com/mailman/listinfo/drats_users">http://lists.danplanet.com/mailman/listinfo/drats_users</a><br>
</div>
</blockquote></span></body></html>