>You may have the strobe the wrong way round. Outputting zero makes >the strobe high (i.e inactive). I know this because my old printer >didn't work when we first tried it, and it turned out that the reason >was because the Sam initially sets strobe active (naughty!) and the >printer therefore pretended to be always busy. Typing OUT 233,0 when >the Sam was first switched on solved the problem.
Right... :) >Also, note that the EDDAC sets the busy signal to 'not busy', so you can >tell if one is connected by setting the data register to 0 (or something >harmless) and wiggling the strobe. A real printer will become busy, but >the EDDAC will not. Eek! I'd hate to do it that way - for one, it'd print stuff out all over the place... (well, I suppose if you output a null, you might get away with it... but I wouldn't like to try!) >I can't remember whether you can tell that the interface is connected in the >first place, but I think probably not. Naaah.. don't think so. You can check for the Comms part of it - but not for the parallel part. Pity really. Simon -!- Mains Hum: A sine of the times??? +- Email:[EMAIL PROTECTED] ---- Fidonet: 2:250/124.2 (Simon Cooke) -+ | Snail:1 Dovey Close, Astley, Tyldesley, Manchester, M29 7NP, UK | | Tel: (01942) 886084 Fax: (01942) 886084 (ring voice first to confirm!)| +- WWW: http://jumper.mcc.ac.uk/~simonc ----------------------------------+
