Good morning
Here is a summary of the replies to this question:
> It seems that the older models of 286, 386 and 486 as used
> in contesting are unlikely to be year 2000 compliant.
> Our main contest programs are DOS based, and may also be affected.
> Has anyone studied the ability of CT, TR and NA to work
> accurately in next year's contests? Or do we go back to
> paper logs?
Further comment from ZL1ANJ:
Using CT8, I ran a few sample contacts, and changed the dates
with ALT-F. Changing the date to 31-Dec-1999 went in correctly.
Changing the date to 31-Dec-1990 went in correctly.
Changing the date to 31-Mar-2000 caused the QSO date to remain
at today's date. Same result with 31-Mar-00.
At this time I am thinking of following the suggestions of
rolling back the computer clock. Post contest, prepare the
logfile in ASCII format, and search/replace the old date with
the correct date.
Thanks for the many replies
Martin ZL1ANJ
-------------------------------
The year 1972 has the same calendar as 2000, so it should do the
job for the contesting crowd if all else fails, with the help of
a little search and replace work on the year.
Thanks: Dave K6LL
-------------------------------
DOS will work justfine in the year 2000 - you can
find all the info on the microsoft web page.
Your computer BIOS might not work in after the year 2000.
Thanks: George K5TR
-------------------------------
If you need to do this (roll back the coomputer clock) as a
workaround for some kind of Y2K problem,
then after the contest you should go back and edit the
ZL1ANJ.LOG file with a program like DOS EDIT and correct
the dates with the global substitue feature before submitting it.
Thanks: Trey N5KO
-------------------------------
In your case - contesting - the date information is driven
by the application, CT, NA, etc etc. Best thing to do is
simply set the clock to next year and try it. I have a 1982
vintage true boatanchor PC, 8088 with 512K, no hard drive,
DOS 5, etc. It works like a champ with an ancient
version (pre-386 chip) of CT.
Thanks: Bill N2BC
-------------------------------
I was in the same situation as you here but
finally decided to look for a new CPU and motherboard.
Greg K9IG
-------------------------------
So, did you try to put the date of your PC ahead
into next century?? There then there will be the answer
if your workaround is needed!
(it seems the same old story of putting back the PC date
for that software with expiring date!!)
Thanks: Bob I2WIJ
-------------------------------
Ive played a little with my 486's and looks like things
will work..if not you are right pick any year.
30 seconds with a good text editor and the log to be
submitted could have the proper year universally
replaced..just have to watch QSO # 1990 perhaps...
Thanks: Charles k3ww
-------------------------------
I believe that soon there will be a CT version for win95.
Anyway if you want to change the date, why not going back
to the beginning of the century, back to 1900 and work as
if you were on 2000.
Thanks: Pedro CT1ELP
-------------------------------
The trick is that when setting the date, using the DOS
date command, you have to ignore the format suggestion
it gives you. Enter the year as four digits. After that,
all DOS loggers should be happy.
I have tested TR and it accepts this without any problem.
Thanks: Tree N6TR
-------------------------------
When testing Y2K compliance, its helpful to know the Y2K
limitations of the operating system as well.
MS-DOS 6.22 is "compliant with minor issues".
Microsoft has the details.
Thanks: Terry AB5K
-------------------------------
Since you submit ARRL Logs in ASCII format. You can just
search and replace the year in the .log file and they
will never know!
Thanks: Randy K5ZD
-------------------------------
Suggestion: just set your computer ahead right now
and make some contest entries. If it doesn't handle them,
then setting it back (in time) will be your solution.
Its my view that the year 2000 'problem' has been blown
out of all proportion. I expect a few good belly laughs
and I am sure the media will have a field day.
Thanks: Ron N5IN
-------------------------------
Why not simply set your computer calendar and clock to near
the rollover date/time? Then see if your computer is affected
in any way. Then boot up TRLog and try it and see what you get.
You may be surprised.
Thanks: Dale, kg5u
--------------------------------
--
CQ-Contest on WWW: http://www.contesting.com/_cq-contest/
Administrative requests: cq-contest-REQUEST@contesting.com
|