[ct-user] SS + 9.46.002

[David Robbins]

this is a common problem with networked ct for ss and other contests
where serial numbers are shared across bands.  you must work in exactly
the right sequence or the numbers get out of sync.  i think we worked it
out once that you must use the insert key to send the report and once
you send it you must log the qso.  you can not wipe it or they will be
out of sync.  another basic problem is that ct does not save the serial
number in the .bin file, the serial numbers are created on the fly from
the order of the qso's in the file.  so you can not do fix_mine on any
contest with serial numbers or they will be out of sync.  I think we
made it about an hour one time trying to do m/s ss with networked
computers before they were messed up, and its almost impossible to fix
later without lots of manual editing.

Dallas Carter wrote:
> 
> Yes the bin file is hosed too, also the ASCII log files.  73  Dallas W3PP
> 
> ----------
> From:   Doug Brandon[SMTP:dab@home.com]
> Sent:   Monday, November 08, 1999 1:54 PM
> To:     ct-user@contesting.com
> Subject:        Re: [ct-user] SS + 9.46.002
> 
>  >Used CT this weekend 2 computers/2 radios - anyone else out there have
>  >problems with sequence numbers in multi computer setup?
> 
> I do single op 2 radio, but I haven't gotten around to checking out the
> 2-radio software support, so I just use two computers networked
> together.  I used 9.45 this weekend, but remember seeing this weird
> behavior in earlier versions also.
> 
> If you log a QSO on computer #1, the QSO data gets sent to computer #2, but
> computer #2 doesn't update its "send this #" value until a new QSO is
> logged on computer #2.  CT *should* update its "send this #" value when a
> new QSO is received over the network.  I had to do a lot of manual exchange
> sending because of this.  Also, if you happen to press ALT-W to wipe the
> contents of the current QSO entry while the second computer is "out of
> sync", it will show the wrong QSO # on the screen.  The wrong # will also
> scroll up the screen as you continue to log QSOs.  Hopefully the wrong
> number isn't stored in the .BIN file (I got home late and haven't done a
> WRITELOG yet).  I made note entries whenever this happened so I could
> manually fix the .LOG file afterwards if necessary.
> 
>     73 de Doug, N6RT
> 
> /*---------------------------------------------------------------------*/
>    Doug Brandon         http://members.home.com/dab         dab@home.com
> 
> --
> Submissions:              ct-user@contesting.com
> Administrative requests:  ct-user-REQUEST@contesting.com
> WWW:                      http://www.k1ea.com/
> Questions:                owner-ct-user@contesting.com
> 
> --
> Submissions:              ct-user@contesting.com
> Administrative requests:  ct-user-REQUEST@contesting.com
> WWW:                      http://www.k1ea.com/
> Questions:                owner-ct-user@contesting.com

-- 
David Robbins K1TTT (ex KY1H)
k1ttt@berkshire.net   or   robbins@berkshire.net
http://www.berkshire.net/~robbins/k1ttt.html

--
Submissions:              ct-user@contesting.com
Administrative requests:  ct-user-REQUEST@contesting.com
WWW:                      http://www.k1ea.com/
Questions:                owner-ct-user@contesting.com