#JetDiret & Win95
4 messages in this thread
I'm not quite sure that Microsoft doesn't support DLC in Windows 95. The
german Beta Version (March 95, 4.00.347) includes a detailed installation guide
for
a Real Mode DLC-Driver, but newer revisions might be different…
Two files are required (msdlc.exe and netdlc.inf), and both shell be
available via download service or CompuServe. (There are – of course – no
such files until now).
The old WfW 3.11-drivers do run with Windows95, but the protocol can't be
installed. By editing the protocol.ini the driver can be configured – and even
a
status is available with the HP-network-ports-monitor and a test page can be
printed (exciting!). Important: "saps=3" in the [msdlc$] section.
Printers can be connected to HP-Network-Ports. But printing out of any
application
causes a system hang (not exciting).
Perhaps there is a possibility to install the WfW 3.11-driver by creating a
netdlc.inf-file which commits Windows95-settings.
But I don't know how such a file should look like.
Did anyone try it?
Thanks for reply.
I have now successfully installed JetDirect with NE2000 card on peer basis with
no server involved. This can be accomplished without DLC, as I was advised by
CompuServe. JetDirect can understand Win95 without DLC.
However, I have run into a new problem I am debugging. That is that I am only
able to connect one machine on the server-less network to the JetDirect. When
I add a second machine with the exact same hardware and software configuration
to the chain, only one of the PC's can see the printer. Whichever one grabs it
first prevents the other machine from seeing the printer on the network.
Comments anyone?
Alan,
When you say that only one computer can see the direct mode printer, what does
the other computer do? Does the network printer folder show up? Do you see
other printers? Do you get any error messages?
-Rob
-Robert A. Miller
Thanks for reply.
The "other" PC (which can be either one of the two depending on which grabs the
printer) can find no network printer either in the network neighborhood or in
the JetAdmin window. As you may know, after installing JetAdmin printer, you
have color-coded printer icon at bottom right. One PC has green, the other
red. If I boot in opposite order, the situation is reversed. It's as if each
is set up ok by itself, but if they both try to find a network printer, one
steals it.
I hope we can solve this because it's creating havoc at the office.
I am actually in Germany this week, but would like to continue the dialog so I
can solve immediately on return. Please advise further.
Regards.
P.S. Either PC can see and print to a local LPT1 with no difficulty.