Discussion Locked

QMS Magicolor printer problems

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,
my network is running under NT 4.0. I have a QMS Magicolor printer installed on a computer and shared. Two users use this printer.
Everything was (more or less) ok, but some day one of the two users could not print anymore. It can normally ping the printer and the computer hosting the printer, but even printing a test page fails. The other computer can still normally print. I tried to delete and reinstall the printer, then restart the hosting computer and then switch off and on the printer (which are usually the little tricks to solve the Magicolor problems) but this time it is inefficient.

SO any suggestion is welcome !!

6 replies

by mancca74

I'm a little unsure about what your problem is but here's a thought.

If your printer is connected to the network with a ip address of its own not to a computer via paralell cable you have to install a crown port driver on the computer from which you want to print. You will have to create a crown port and connect the printer driver to that port.

You can get the neccessary drivers on minoltas home page.

If you have connected the printer to a computer via paralell cable you have to try and uninstall everything and try to set it up from scratch. You even might have to delete all the entries in the registry before setting it up again for it to work properly.

Hope this helps!

by sgt_shultz

check out what port the printer thinks it's attached to? delete and recreate the port? when print jobs go to 'never, never land' (no print, no error msg), i check out the port...also, printer is not currently 'paused', right? hope this helps a little, good luck...

by jna

I wish I could throw it too, but unfortunately it's not up to me!! I had a little hope reading this article. I uninstalled the printer, deleted everything related to it in the registry, reinstalled sp6a, finally reinstalled the printer, but the bloody problem is still there...

This discussion is closed to new replies.