> It could *be* a solution. Despite your bias, it may be that the router has> always been "broken" and your previous desktop software was, by chance and> luck, working anyway. It such a situation, an upgrade might "break" things> because of timing issues, not code changes, and the proper solution is to> fix the router.>> I'm not saying that's what is happening here. In fact, I doubt that is the> case. However, just because the combination of Xv1 and Y works and Xv2 and> Y doesn't work does not imply that Xv2 is broken.>
I know, just look at HTML 4.1 and IE 6 vs. IE 7. IE 7 became[relatively] standards compliant, and that broke a lot of websites.
But in this case neither KDE 3 nor KDE 4 are broken, rather thefunctionality for network printing seems to have not yet been written.
> What I think is happening here is that KDE 4 dropped a lot of KDE 3's> printing infrastructure. IME, KDE 4 *seems* to depend on a working, local> CUPS setup. In one of your other messsages you said:>
I do have a local, working CUPS. However, due to the router's stupiddesign of using an EXE file to configure Windows instead of giving theuser the configuration details, I do not know the correct IP addressformat to use, nor the protocol to use. KDE 3.5.10 did manage to scanand find this info, therefore I was hopeful that I could go throughthe old config files and extract this info.
>>In KDE 3.5.0 I could enter the IP address of the router as the address>>of the print server and the printer worked fine. Not so in KDE 4.2.2.>> (Are you sure it was 3.5.0; I bet it was actually 3.5.6 or above.)>
It was KDE 3.5.10, I left out the 1 character.
> You should be able to configure a print queue on your local cupsd to print> to a remote lpd or cupsd print queue. Most likely, there is an lpd or cupsd> running on your router. You should be able to browse to> http://localhost:631 to set this up. When it asks for the printer / server> IP, you can use the IP of the router.
The IP of the router must be in one of the following formats:http://192.168.0.1:631/ipp/http://192.168.0.1:631/ipp/port1ipp://192.168.0.1/ipp/ipp://192.168.0.1/ipp/port1lpd://192.168.0.1/queuesocket://192.168.0.1socket://192.168.0.1:9100
Additionally, I have these protocols to choose from:AppSocket/HP JetDirectBackend Error HandlerHal printing backendHP Fax (HPLIP)HP Printer (HPLIP)Internet Printing Protocol (http)Internet Printing Protocol (ipp)LPD/LPR Host or PrinterSCSI PrinterWindows Printer via SAMBA
You mention LPD so I will now try that protocol with all the possibleIP address configurations.
I should note that I already received a letter from D-Link trying toassist, so I sent to them the list of addresses and protocols as wellto ask. I also made note that I am surprised that this information isnot in the literature provided with the router. I await their secondresponse.
-- Dotan Cohen
http://what-is-what.comhttp://gibberish.co.il___________________________________________________This message is from the kde mailing list.Account management: https://mail.kde.org/mailman/listinfo/kde.Archives: http://lists.kde.org/.More info: http://www.kde.org/faq.html.
