By the time you hit the printer driver (on your computer) the printer's hardware has been abstracted out of the picture. Or that would be my guess. Another way to put it - why would the printer driver know anything about what's inside the printer.
And if that's not clear then try this: "You don't need to know how a car works to drive one". Enough. If you want to control stepping motors I would pull them from the printer and start over.
This looks like a good place to start: galilmc.com/learning/tutorials.php If that's too commercial then try this: cs.uiowa.edu/~jones/step/ here's a paper from mit: dspace.mit.edu/bitstream/handle/1721.1/4... Wow, that one's over 30 years old and uses a PDP11. Never mind that one. Then try this for the basics: en.wikipedia.org/wiki/Stepper_motor I think you get the idea - there's plenty out there.
--- Say, a better place to pull a stepping motor *and* the circuit that drives it is from an old floppy drive. Why? Because the computer to drive interface contain lines to "step" the read/write head in and out.
You pulse these control lines and the head moves. I think that's exactly what you are after - isn't it?
I would connect a micro-controller to the steppers or the stepper controller inside the printer and talk to the micro-controller directly. Writing drivers can be more difficult and can be a pain to debug. Steppers are fairly easy to drive too If you really want to go that direction, you might want to see if there are any open source linux drivers.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.