Jim Brown
Sep 3rd, 2001, 08:42 AM
Nothing whatsoever to do with VB or even Chit Chat, but it just struck me that there must be a SCO guru out there.
According to our customer, when he tries to add a tcp/ip printer his system complains that the printer (the lpd, that is) should also be a SCO machine. This struck me as unusual because many desktop printers can act as lpds in Unix and MS worlds and they don't have any Unix at all in them, let alone SCO. (As it happens, the printer in question does have a Unix front end, but it's Solaris.) By my reckoning and experience, an lpd is an lpd, as long as it sticks to the rules of lpd-ing.
Then I found a page on SCO's web site that indicated that it's only SCO Admin that would like the printer to be SCO for some adminsitrative reason I think, and so you just ignore the message and carry on adding the printer, including editing printcap like normal.
Can anyone confirm this please? Or alternatively, indicate a different way of adding an lpd in SCO
According to our customer, when he tries to add a tcp/ip printer his system complains that the printer (the lpd, that is) should also be a SCO machine. This struck me as unusual because many desktop printers can act as lpds in Unix and MS worlds and they don't have any Unix at all in them, let alone SCO. (As it happens, the printer in question does have a Unix front end, but it's Solaris.) By my reckoning and experience, an lpd is an lpd, as long as it sticks to the rules of lpd-ing.
Then I found a page on SCO's web site that indicated that it's only SCO Admin that would like the printer to be SCO for some adminsitrative reason I think, and so you just ignore the message and carry on adding the printer, including editing printcap like normal.
Can anyone confirm this please? Or alternatively, indicate a different way of adding an lpd in SCO