Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ct\-user\]\s+Safe\s+CT\s+Rev\s+for\s+ARRL\s+DX\?\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ct\-user\]\s+Safe\s+CT\s+Rev\s+for\s+ARRL\s+DX\?\s*$/: 2 ]

Total 2 documents matching your query.

1. [ct-user] Safe CT Rev for ARRL DX? (score: 1): Author: Charlie Ross <ross_family@acm.org> (Charlie Ross); Date: Wed, 19 Jan 2000 07:35:23 -0500; After seeing the messages earlier this month about Y2K problems and the like... Is there a safe/stable CT rev for use in the upcoming ARRL DX contests? --Charlie, NC1N -- ross_family@acm.org -- Charl; /archives//html/CT-User/2000-01/msg00050.html (7,099 bytes)
2. [ct-user] Safe CT Rev for ARRL DX? (score: 1): Author: Jim Reisert AD1C <jjreisert@alum.mit.edu> (Jim Reisert AD1C); Date: Wed, 19 Jan 2000 10:05:06 -0500; CT is not *unsafe* as far as Y2K is concerned - just some of the reports say "19100" instead of "2000". Also there are some issues with ALT-F to edit the date/time of a QSO. There are no known proble; /archives//html/CT-User/2000-01/msg00051.html (7,645 bytes)

Current List: 1 - 2
Page: [1]