Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TRLog\]\s+Windows\s+Me\s+Clarification\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TRLog\]\s+Windows\s+Me\s+Clarification\s*$/: 3 ]

Total 3 documents matching your query.

1. [TRLog] Windows Me Clarification (score: 1): Author: matt@qrq.com (Matthew George); Date: Tue, 10 Oct 2000 21:39:09 -0600; TRLog works fine running in Windows ME (full screen command shell)... I have been on beta versions of Windows ME with no problems since March (running TRLog). I have been using the release version of; /archives//html/TRLog/2000-10/msg00028.html (7,839 bytes)
2. [TRLog] Windows Me Clarification (score: 1): Author: Hank.Lonberg@Harrisgrp.com (Lonberg, Hank); Date: Wed, 11 Oct 2000 07:21:02 -0700; Same is true here on both laptops and desktops have always run TR in Dos window with full automation including TR Cw keying and Parallel port voice keyer signals with external paddle connection. Neve; /archives//html/TRLog/2000-10/msg00029.html (8,477 bytes)
3. [TRLog] Windows Me Clarification (score: 1): Author: bsmall@buffalo.edu (Bruce M. Small); Date: Wed, 11 Oct 2000 18:31:03 -0400; Some people have trouble with CW keying when running in a DOS Window. Like me. I cannot key from the parallel port in that circumstance, although the serial port works fine. When running under DOS it; /archives//html/TRLog/2000-10/msg00030.html (7,391 bytes)

Current List: 1 - 3
Page: [1]