CT-User
[Top] [All Lists]

[ct-user] CT 9.50 Problem with TIME !!!!

To: <ct-user@contesting.com>
Subject: [ct-user] CT 9.50 Problem with TIME !!!!
From: Oliver Huber" <oe5oho@hotmail.com (Oliver Huber)
Date: Sat, 21 Oct 2000 11:52:01 GMT


hello contester.


i discovered the problem using CT 9.50.001 (i think it is .001)
on 2 computers and linking them together using Siemens Gigaset M101
on approx. 2GHz.

the network is running - logdata and clusterspots are available at
both PCs.

the problem now is TIME!
                   =====

i set date and time under DOS, then start the RUNcomputer. when i do
so CT immediately shows something like 6 or 7h ahead(!) of the DOS
time i just set under DOS!!! (e.g. DOS=12h and CT=18h)

after starting the RUNcomputer i start CT on the 2nd PC (MULTI).

using the CT command SETTIME on the RUN PC doesn´t change the time on
the RUNsystem but i think it did change on the MULTI - as it should,
because the manual somewhere says something like the RUNtime is the
one which is being sent to all other connected stations.
(in my case the RUNtime is a bit wired!).

well, playing with ALT-F command and doing a dummyqso changes the
RUNtime finally so you can adjust the time to match on RUN and MULTI.
(but that´s abnormal!! it should function anyway - but it doesn´t!)

while logging now is possible with the correct times on RUN and MULTI,
the trouble starts again on the MULTIcomputer:
there you can read something like 400minutes, which the RUN according
to CT has to stay on the band where the 1st qso took place from the
RUNstation. of course it is counting down!
on the RUNcomputer the QSY times seem to be correct.
back to the RUNcomputer:
so when the RUNcomputer timer finally says "QSY OK" and one goes to
another band on the RUNstation, then the MULTIcomputer says "band
violation" and marks the QSOs with Red Background. why? because
according to the MULTIstation the RUN should still stay on the
original band!!!

how can it be that CT starts with an offset to normal DOS time????
how can it be that the QSY time (eg 400minutes) corresponds to the
time the RUNstation is offseted somehow?

is this ONE problem or TWO????

it seems to be a TIME problem at least... and it is hard to describe
and i did not take care to write down each bit of info while trying
to get the network run... :-(


i want to use CT´s QSY-timer as i guess the newer versions show the
correct QSYtimes (CT 9.27 didn´t show the correct ones).
but somehow i got a problem :-(((


PLEASE - is there anyone out there who might help me to solve this
problem?!

any tips tricks are welcome AS SOON AS POSSIBLE!!!!


vy 73 de Oliver OE5OHO.


PS: cu in CQWW SSB as OE5T (M/S)




      ... One of the BCC ...
==================================
Visit:  http://www.qsl.net/oe5oho
Email:  oe5oho@hotmail.com
        oe5oho@qsl.net
Packet: oe5oho@oe5xbr.aut.eu


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


<Prev in Thread] Current Thread [Next in Thread>