[WriteLog] LPT CW in WL via UserPort in XP - solving the addressing problem

[W. Wright, W5XD]

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 the file.

For those folks running Windows 95/98, FPORT16.EXE could be run
manually (i.e. you could double click on it from the Windows 
Explorer) but it has gotten to the point that even that is
unadvised. FPORT16.EXE not only is limited to Windows 95/98,
but it also only works if your system BIOS is correctly configured
to say how many and what addresses your LPT ports are on. It
turns out that even Windows 95/98 don't need the BIOS correct,
so most folks haven't set it up. 

FPORT16.EXE cannot be made to work on Windows XP, 2000, or NT
even by UserPort or by direct-io. So its pretty much a lost
cause.

On the final topic, changing WRITELOG.INI to read only is likely
to break WriteLog on ANY system.

Wayne

> -----Original Message-----
> From: Scot Herrick [mailto:scot@k9jy.com]
> Sent: Sunday, August 04, 2002 19:16
> To: w5xd@writelog.com; 'Writelog'
> Subject: RE: [WriteLog] LPT CW in WL via UserPort in XP - solving the
> addressing problem
> 
> 
> 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 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 appropriate addresses, but changes the writelog.ini 
> settings anyway.
> 
> Please do NOT set writelog.ini to read only!
> 
> Wayne
> 
>