[Oremem/Idamem] Fw: WinLink 2000 Discussion
Virginia Franklin
spudly at pacinfo.com
Fri Aug 27 13:59:20 EDT 2004
Oregon members fyi. I'm not sure if i can forward through the oremem
list or not, so this is a test!
----- Original Message -----
From: aar0zc at bendbroadband.com
To: 'Virginia Franklin'
Sent: Thursday, August 26, 2004 10:32 PM
Subject: WinLink 2000 Discussion
Hi Bob,
I have put together below a synopsis of all the WinLink message traffic that has come my way over the last few days regarding ARMY MARS, NAVY MARS, ARES and other WinLink users. I have all the original traffic on my computer. So if anyone would like to read the original messages, or wish to contact any of the addressees, or look at any of the web resources, I will make the traffic available.
Background
Recently the ARRL has adopted WinLink 2000 for ARES use. In addition ARMY MARS has been using an earlier version of WinLink (V2.9/3.0). This version is now considered to be obsolete in the WinLink community and is no longer supported. It is referred to as WinLink Classic. In addition WinLink supports worldwide maritime operations and is used in other settings.
According to my contacts in ARMY MARS, the DOD and ARMY COMSEC denied certification to WinLink 2000 because it has a built in bridge to the internet. My NAVY MARS contacts say they don't use WinLink because it can not act on priority messages by putting them to the head of any traffic queue. According to WinLink 2000 specialists, the jury is still out on this question. In lieu of WinLink, NAVY MARS uses a homegrown system. I have no knowledge of the situation in AIR FORCE MARS.
My ARMY MARS contacts say that after the last three years of having WinLink 2000 not approved by COMSEC, they want to try again to get WinLink 2000 certified for ARMY MARS use. This involves tests and other matters that will take place this fall. In the meantime, one part of WinLink 2000 is being used and that is Airmail 2000.
Under the impetus of Homeland Security, several agencies, governmental and civilian, are looking at high throughput interoperational digital networking based on advanced Pactor, i.e. Pactor II and III. Two issues that bear on this are the high cost for volunteers to acquire advanced Pactor, and the high bandwidth consumed by Pactor III. (There is currently a program to assist volunteers financially.)
There also seems to be a lot of misinformation about WinLink. And of course, there are those who feel that WinLink threatens whatever pet modes are now being used. In addition, the ARRL is planning to file a petition with the FCC to change the way bandwidth is allocated with a particular emphasis on digital modes.
Summary
The essence of all the above is that times are changing, and in the end there will probably either be common co-operation or eventual marginalization or elimination of some of the players.
What has all this to do with Oregon MARS?
I am not sure yet. Part of the issue may be with the need of moving substantial traffic during sub-audible operating conditions. Only advanced digital modes are capable of doing this to my knowledge. In addition, communication effectiveness is based on getting the most accurate information to decision makers as fast as possible in a standard form. I think digital modes are hard to beat in this context. There use also permits substantial power reduction. Therefore, I endorse the effort being made to get as many Oregon ARMY MARS members as possible qualified in effective digital communication.
On a personal note, I plan to bring up WinLink 2000 and advanced Pactor within the coming weeks so that I can start experimenting with these technologies. While I am experimenting I want to formulate a number of questions, e.g. what is the minimum power for effective communications based on various traffic circuits? How effective is advanced Pactor? What skills do I need to acquire? What changes, if any, do I need to make to my station? What standards should be used? Is additional training material needed?
That is all for now Bob. Please let me know if I can respond to any questions.
Barry
AA7ZC/AARØZC
More information about the Oremem
mailing list