In the message from Steve Harrison........
>
>The instructions in the CT manual (V8, at least) on the use of MERGE are
>very clear and unambigous; MERGE works as advertised. Your old first file was
>saved under FD94.OLD. Your second file was not touched and is still there undr
>the old name (FD94.ST2, in your case). The new file with the merged logs is
>there under the original first file's name (FD94.BIN).
>
Though I do not mean to slam Steve, as I mentioned many times to Ken
via the CT BBS and in person, the MERGE documentation is NOT clear!
But like he said, if you C:\> MERGE FD94(.bin) FD94.ST2
merge interprets that as MERGE FD94(.bin) FD94(.BIN)
meaning that nothing in FD94.ST2 ends up in the new file FD94.BIN
The point he was trying to make was not about what files are
preserved, but that command-line-arguments are only processed for
the filename... not the extension. MERGE assumes .bin! (or did)
>I have no idea about version 9 programs since I haven't bought V9 yet.
>73, Steve KO0U/4 <sharrison@sysplan.com>
>
The DOCS speak nothing of station configuration information... only of
QSOs. And I believe there was at one time an issue versus which
station config ended up in the .bin
If I could have a wish list implementation for CT, I would have the
.bin only contain qso information and that station1, station2, com
port and onther config information stored in a seperate file...
that way when you do a merge on the fly during a multiop, you
wouldn't have to reconfig the second station all the time....
(or do two merges one merge sta1.bin sta2.bin and vice-versa..)
(You would also eliminate the need for a log clearing program..)
73 de Luigi
--
John L. Luigi Giasi, AA1AA jlgiasi@umassmed.ummed.edu
System Programmer/Administrator aa1aa@ummed.edu
Information Resources Division
Univ. of Mass. Medical Center (508) 856-UNIX
Worcester, MA 01655 FAX: (508) 856-2440
"Laurence A. Canter and Marsha S. Seigel of CSLAW wasted more human
and computer resources than Robert T. Morris. OBEY NETIQUETTE!"
|