Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+LPT\s+problem\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+LPT\s+problem\s*$/: 3 ]

Total 3 documents matching your query.

1. [WriteLog] LPT problem (score: 1): Author: "Alan Maenchen" <ad6e@inreach.com>; Date: Wed, 11 Jan 2006 21:32:23 -0800; I've been using WL for years, and this is something new for me. Comfuser is a 2GHz thingamabob with 2 com ports and one LPT on the motherboard (one of the last available!) running W2K pro. I've used; /archives//html/WriteLog/2006-01/msg00099.html (6,762 bytes)
2. Re: [WriteLog] LPT problem (score: 1): Author: Bill Turner <dezrat1242@ispwest.com>; Date: Thu, 12 Jan 2006 07:29:46 -0800; ORIGINAL MESSAGE: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In a situation like this with any program, not just WriteLog, I would go to control panel and uninstall the com and lpt ports, then; /archives//html/WriteLog/2006-01/msg00100.html (8,213 bytes)
3. [WriteLog] LPT problem (score: 1): Author: "Peter Barron" <ve3pn@igs.net>; Date: Fri, 13 Jan 2006 04:56:41 -0000; If Bills suggestion doesn't jive (this usually fixes a lot of things) check the writelog.ini entry for something like [Ports] LPT1=0x378 Where the =0x the address for your LPT port Sometimes this can; /archives//html/WriteLog/2006-01/msg00104.html (7,249 bytes)

Current List: 1 - 3
Page: [1]