If you can switch back to WIN7, my suggestion would be to do so.
If you can switch back to WIN7, my suggestion would be to do so.
From: Rogier F. van Vlissingen <vliscony@gmail.com>
Date: Tue, May 17, 2016 at 6:05 AM
Subject: [libreoffice-users] HP Officejet Pro 8630 overprinting lines in LO
on Win 10
To: users@global.libreoffice.orgSince switching to Windows 10, I've had to abandon LibreOffice, since my
printer inexplicably overprints lines in LO. This never happened in Win7.Anybody have any suggestions?
At some point I am going to Linux Mint 17.3, but I will need to keep at
least one machine running Win10...
Go mint and virtualize win10
Namasté _/\_
Agreed on virtualization, you may want to run Win 7 inside Linux to avoid your problems.
If you don't want Win 10, use the tricks documented on the net to keep win 10 outside.
VirtualBox is a good start for example but you need some extra RAM for Windows if you don't have it.
Thanks for all the suggestions.
All of them are too much effort, if need be I can do the PDF work around.
For now what this means is I'll work with MSO, which I dislike intensely,
but it can't be helped. I foresee in future running my main machine under
Linux Mint entirely, and keeping a Win10 machine just for limited jobs
where I absolutely must have it. This is all too much.
If LO can't make a mainstream printer like this work, that is pretty
devastating.
*Rogier Fentener van Vlissingen
<http://t.sidekickopen52.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJN7t5XX4Rs8XWW8r4QYz1px7xYW5v_Sgz56dJpLf29LVkq02?t=http%3A%2F%2Fviz.me%2Fvliscony%2Ft%2F7&si=4817575424294912&pi=cb0b1d7c-ff80-4f89-aa71-8becc08c0128>*
*About Me
<http://t.sidekickopen52.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJN7t5XX4Rs8XWW8r4QYz1px7xYW5v_Sgz56dJpLf29LVkq02?t=http%3A%2F%2Fabout.me%2Fvliscony&si=4817575424294912&pi=cb0b1d7c-ff80-4f89-aa71-8becc08c0128>
*Schedule
a phonecall here
<http://t.sidekickopen52.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJN7t5XX4Rs8XWW8r4QYz1px7xYW5v_Sgz56dJpLf29LVkq02?t=https%3A%2F%2Fcalendly.com%2Fdabxdssinc%2F15min&si=4817575424294912&pi=cb0b1d7c-ff80-4f89-aa71-8becc08c0128>
You cite LO as the culprit yet the problem occurred after changing to
Win10. I suggest you verify if the HP driver is at the correct version for
Win10. Maybe use the 'DriverTalent' program to check all your drivers.
http://download.cnet.com/Driver-Talent/3000-2094_4-76219521.html
Have the latest, but will check with HP....
*Rogier Fentener van Vlissingen
<http://t.sidekickopen52.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJN7t5XX4Rs8XWW8r4QYz1px7xYW5v_Sgz56dJpLf29LVkq02?t=http%3A%2F%2Fviz.me%2Fvliscony%2Ft%2F7&si=4817575424294912&pi=ba55486d-42c8-47e5-9028-9b32a4dcd4c8>*
*About Me
<http://t.sidekickopen52.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJN7t5XX4Rs8XWW8r4QYz1px7xYW5v_Sgz56dJpLf29LVkq02?t=http%3A%2F%2Fabout.me%2Fvliscony&si=4817575424294912&pi=ba55486d-42c8-47e5-9028-9b32a4dcd4c8>
*Schedule
a phonecall here
<http://t.sidekickopen52.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJN7t5XX4Rs8XWW8r4QYz1px7xYW5v_Sgz56dJpLf29LVkq02?t=https%3A%2F%2Fcalendly.com%2Fdabxdssinc%2F15min&si=4817575424294912&pi=ba55486d-42c8-47e5-9028-9b32a4dcd4c8>