For those who may have tried UserPort without instant success, there's one more wrinkle to consider before giving up. If your Setup/Ports dialog doesn't show what you expect, some cut and try experim
Author: Steve Baron - KB3MM" <SteveBaron@StarLinX.com (Steve Baron - KB3MM)
Date: Thu, 1 Aug 2002 14:29:01 -0000
Those INI files entries are populated by FPORT16.exe. Just rename the file and make your own entries. means manual 378-37F, was XP LPT of Athlon back in
Thanks, Steve. After following your suggestion, and getting Setup / Ports corrected from my revisions to INI, I then renamed FPORT16.exe back to its original. Not sure what else it does, but it did n
Its a good idea on XP systems to rename (or delete) FPORT16.EXE. It attempts to read the BIOS settings for LPT addresses in a way that only works on Windows 95/98. Otherwise it fails to read appropri
Wayne, Just curious - would this also apply to Windows NT, and Windows 2000? Thanks...Scot, K9JY See K9JY's WriteLog User Support Site at: http://www.k9jy.com mailto:scot@k9jy.com Its a good idea on
Yes, not running FPORT16.EXE is a good idea on XP, Windows 2000, and Windows NT. As of WriteLog version 10.34, FPORT16.EXE is never run automatically, so its no longer necessary to delete or rename t
Hi there, for an upcoming M/M operation I am just playing around with Writelog ... I had zero problems so far on WIN98 and WIN2000 but now to WIN XP... Playing around on a WIN XP machine and having p
FWIW, I had more consistent results with the dlportio driver than with UserPort. I wrote up what worked for me at http://www.qsl.net/n1eu/n1mm/MMKeying.htm 73, Barry N1EU ____________________________