http://www.direct-io.com/
Here is a copy of the message about troubleshooting from the wl reflector.
-bmb
Troubleshooting Checklist for Writelog, XP, and Direct I/O:
1. Make sure that you actually have writel32.exe in the security tab,
and that the path is correct to the program. This is especially
important if you change the location of the program, as it will not work
if the path is wrong.
2. Rename the file fport16.exe to fport16.old in the program directory
where you installed writelog. This is required because fport16.exe
forces writelog to use the wrong addresses for the lpt ports.
3. Use ONLY the I/O address 378-37F for direct I/O in the control
panel.
4. Edit writelog.ini in the windows subdirectory (usually c:\windows)
and correct the addresses. In a typical XP system you will have only
LPT1 so you can elminate LPT2, LPT3 and set LPT1 as follows: LPT1 :=
0x378
5. Make sure the cable is correct assembled. If it used to work with
your ME or 98 system, it should be ok when you get your XP system
working. If not test it if you can. I used a 10K resistor to the LPT
pin on the cable and to the base of a 2N2222, with the emitter grounded
and the collector tied to the key input. The schematics that come from
writelog will work just fine.
6. If you system is an HP system, it may come with an ECP functional
port. This enhanced functionality is for bidirectional communication
over the LPT port. It can and should be turned off. To access Bios and
shut it off you reboot, when the blue HP screen comes up hold down F1
key and you will get "Entering Setup". At that point look at the menus
and you will see a topic (that is usually NOT visible until you scroll
down the bottom of the screen) I/O Configuration. Select this, and you
will find an LPT Port functionality entry. Change this from ECP to
Standard LPT, save the chages, boot up.
7. A few helpful reminders:
a. Writelog DOES NOT delete the writelog.ini file if you do a clean
install. You need to do this by hand.
b. Although you are used to not having to reboot when making
changes to I/O and networking, I found that
sometimes Direct I/O doesn't propagate changes in configuration
unless you reboot.
c. The control panel can show you the status of Direct I/O if you
view the hidden I/O and look in non plug and play.
d. The Port selection in the control panel can show you the
resources used by LPT1. This should only show 378-37F,
since XP does not need interrupts for LPT1. DO NOT CHANGE ANY
SETTINGS HERE. Use only the SETUP/BIOS
e. DO NOT CHANGE THE settings for Direct I/O operation (ie leave it
on automatic, especially do not set BOOT!)
If you do, you will get the XP Blue Screen of Death (first
time I ever saw it). If this happens, reboot to the last
good configuration and it will go away.
f. Close and restart writelog each time you make a change to the
I/O configuration. These changes do not
propagate to running programs. When the LPT1 line has
checkable boxes under setup/ports you have been
successful. After you get here, exit windows, shut everything
off, and do a cold start to make sure that
it's all correctly on the disk! When you come back from a
dead start and it still works you are successful.
g. REMEMBER TO PLUG IN THE CABLE before attempting to test the
rig. Believe it or not, I spent an hour or more
pulling out my hair over the fact that despite my knowledge
and experience in this stuff, and an otherwise
perfect configuration, THE CABLE WAS UNPLUGGED. It's amazing
how software actually still requires
hardware to do something! The cable had fallen out while
doing something else. Guess that's what those
little screws are really for!!
Remember, there are three places where LPT1 must be appear correctly:
a. In writelog.ini (starts out wrong, will be made wrong by
fport16.exe if you don't rename it etc.)
b. In direct i/o control panel (you set this)
c. In the resources tab of the system/hardware control panel (you
check this)
Remember, ECP must be changed to LPT in BIOS/SETUP.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of FireBrick
Sent: Wednesday, February 20, 2002 01:29 PM
To: DXBase List
Subject: [DXBase] xp and lpt
This issue of printer ports no longer working as cw interface ports has been
reported on the Writelog reflector.
The fix is a 3rd party driver that allows programs to utilize the printer
port as they did in win9x.
As I only use com ports for my interfaces I never dloaded it or saved it.
But you can find the location if you peruse the Writelog archives.
As for what we are going to do in the future? I think it's in the
manufacturers court to adapt their equipment to the new technology of USB or
Firewire.
Even new machines are now sold with only 1 serial port. ISA slots are almost
impossible to find in any modern motherboard.
Like the dinosaurs....adapt or die.
------------------------------------------------------------
Newspaper Headline: Typhoon Rips through Cemetery; Hundreds Dead
------------------------------------------------------------
Bill H. in Chicagoland
[EMAIL PROTECTED]
_______________________________________________
DXBase Reflector - Please visit us on the web at www.dxbase.com
- - - - - - - - - - - - - - - - - - - - - - -
To UNSUBSCRIBE please visit:
http://mailman.qth.net/mailman/listinfo/dxbase
