Re: [CAD_CAM_EDM_DRO] Re: Compters without printer port

>> The most likely explanation to me is that the BOB looks like some sort
>> of EPP or ECP device, but when the driver can't get it to reset or
>> initialize, it disables the port. This might make sense when the
>> expected use of a parallel port is to communicate with things like
>> printers and scanners. It may also be an issue if the thing connected
>> to the interrupt input is in the "wrong" state while Windows is booting.
>>
> Certainly in my own case, the BOB is specifically deigned to draw almost no
> current. Some breakout boards that hang opto isolators directly on the parallel
> port will not work with ITX and other 'set top' style motherboards, so I've gone
> for a low current buffer as the very first stage.
>
> The fact that W2k boots fine and XP doesn't point to an initialization problem
> with windows rather than any hardware problem. ANd as I say - leave the cable
> out - start XP - plug in. Then no problem either.
>

Sure, that's compatible with my explanation. The XP driver may be more
paranoid than the 2k driver when it has problems initializing external
hardware, or can't determine what the hardware is.

It's likely that one (or more) of the inputs that end up in the status
register is the problem. These are pins 10-13 and 15 on the port
connector. You might try disconnecting each of those and rebooting. At
some point the machine will boot up, and you can start reconnecting them
(leaving the last one disconnected). You should be able to find out
which of the inputs is the problem.

This is all assuming that I'm right ;)

- Steve