*** Quoting Jean Parrot to Rich Wonneberger dated 06-16-03 ***
>  RW> It turned out to be the printer cable.
> 
>         Can I say that I doubt it ?

Jean,

Sounds like you just did say it.   :}

*** Quoting Jean Parrot to Rich Wonneberger dated 06-16-03 ***
>         Just for fun, now that you have the software working again, for
>         my curiosity, would you try the first cable once more, just to
>         see ? I just can not follow the setup that would do this and be
>         hardware caused.

If it was my system I would.
I dont understand it my self, but nothing supprises me any more.
I tried deleting the printer and port and re-installing the driver but with
¨the old cable it did the same.  I got the new cable & it did the same
thing.  ¨I deleted the printer & port and re-installed the driver and
it worked.

Not a teckie answer but I azzume it had something to do with the OS and the
¨printer talking to each other.

Rich
I-Net   turtil{at}frontiernet.net


... "Sorry officer, but I was only doing 2400 REALLY! "
---