OpenBCM V1.07b12 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
VE2HAR > MT63     17.03.05 04:12l 132 Lines 5823 Bytes #-7000 (0) @ WW
BID : 21607SENTTO
Read: GUEST
Subj: Re: [MT63] High-speed HF Modem
Path: DB0FHN<DB0MRW<DB0ERF<DB0FBB<DB0FHK<DB0ACC<DB0PKE<DB0RES<ON0AR<VE2PAK<
      W1NGL<VA2HAR<VE2HAR
Sent: 050317/0148z @:VE2HAR.#MTL.QC.CAN.NOAM Laval #:43219 $:21607sentto

 > Karl Larsen's posting, including
>> John Bradley's posting

>     Linux has Open Office which has a Word look-alike.

I haven't seen the latest version of OO, but the versions I've used do odd
things with some Word documents.  I'm running the Codeweavers' Crossover
package with Microsoft Office 2000 for compatibity with those bound to
Windows systems.  While Office itself can be expensive (although I got mine
while I was a student [again] doing my masters' degree recently - I'd never
use it enough to justify the price tag of the non-academic version otherwise),
running it under Linux is a lot safer (virus-wise) and cheaper than running
it under a Redmond OS.

>>Having been involved with emergency managment/planning for many years, the
>>KISS principal still applies: Keep it simple, stupid! So , despite your love
>>of Linux, that should probably stay on your home computer rather than in a
>>command post with many operators of different skills.

Fortunately, it's not necessary to learn how to use Linux to use it in
that kind of environment.  If the system's set up and maintained before
the emergency, it can be totally turn-key during the emergency, and the
user doesn't know/care what OS is running the system.  Putting the
needed programs on a toolbar makes them a click away to even an untrained
user.

>     Linux is cheaper, far more stable, and has far better software for 
> both MT63 and Olivia written for it by Tomi Mannion than Windows does now.
> 
> 
>>With respect to the mode, well I am not convinced that MT63 works better
>>than MFSK under really poor conditions, although the baud rate is higher. I
>>haven'y had the opportunityto try them side by side when conditions are
>>poor, and look forward to that. If OLIVIA ever gets written for windows,
>>that might be the way to go ......
>>

Get back to the KISS principle.  MFSK will out-perform MT63, but requires
a lot more operator intervention.  MT63 can just be left in a monitor
state and watch the monitor for activity.  Olivia is even better in this
regard.  By the way, when the dust finally settles and we are HOPEFULLY
able to used mixed-mode voice and digital modes on HF, it'll be awfully
nice to be able to coordinate things on SSB and kick on 2 kHz MT63 or
something similar to pass a data file.  Not legal in the US now, but
hopefully will be some day.

>     Why wait? Olivia is on Linux right now. I used it today to talk with 
> Txema in Spain! But we did the same thing with MT63 and had 100% perfect 
> copy with both modes in the presents of much packet pest QRM.

It runs well under Windows, too.. just not "pretty" or convenient.  The
waterfall isn't really needed, particularly for fixed-frequency operation.

>     The idea of a station down town somewhere that is used IF there is 
> an emergency is old style thinking. I keep the phone numbers of people 
> that KNOW how to run their OWN equipment and they maintain it while no 
> emergency exists.

Which gets to the comments below...

> 
>>Sorry if I have offended all you Linux lovers, but in the real world ,
>>Windows should rule the emergency computer world...

Sorry to disagree with both Windows and Linux zealots -- but there is
no need to select any operating system to RULE in the emergency
computer world.  Whatever suits the needs -- including performance,
training, reliability, adaptability, and budget -- is what should be used.
An open architecture where any/all OS's can be used is best.  Computers
should be able to interoperate via standard ethernet networks, to allow
file sharing/transfer between systems, and use non-proprietary products
that can be used by different systems with different OS'es without having
to worry if the system can handle some oddball format.

Standardize on protocols and interfaces, not on products, and especially
not on the things that are required to support specific products.  If you
do that, the pieces can be put together 'on the fly' as needed, fitting
into the 'bring your own equipment to the emergency' paradigm.

>     It is high time to replace windows with a stable Unix operating 
> system. That it is free makes it easy to do. This is all written on a 
> Linux computer.

Then do we get to fight about whether we use KDE or Gnome on the
desktop?  It's time to figure out how to make them all work together, so
that it is no longer important what OS is under it all.  Building up
a system that's incompatible with other systems is suicidal, regardless
of if it's based on Linux, FreeBSD, OS/X, Windows, .NOT or whatever.

Which gets back to the questions like "why do we have so many modes?" and
such -- the idea is to have a variety of tools to use when needed, and to
have the expertise needed to not only use them, but to know which one to
use in a particular situation.  Arguing over Pactor vs MT63, Windows vs
Linux, and with how many tones and what bandwidth do we use Olivia can be
counter-productive.  Keeping the discussion focused on learning the
differences -- and the advantages and disadvantages of each -- can be
educational.

-ps



------------------------ Yahoo! Groups Sponsor --------------------~--> 
Tired of hearing the same songs over and over?
Listen to Internet Radio! Skip songs. Click to listen to LAUNCHcast!
http://us.click.yahoo.com/.mKGzA/HARHAA/kkyPAA/CPMolB/TM
--------------------------------------------------------------------~-> 

<<  Try MT63 on 80m - great fun!>>

- The MT63 Reflector -
   MT63@egroups.com

(To unsubscribe. send email to
MT63-unsubscribe@onelist.com)
 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/MT63/

<*> To unsubscribe from this group, send an email to:
    MT63-unsubscribe@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 






Read previous mail | Read next mail


 18.05.2024 18:06:34lGo back Go up