Basil Chupin wrote:
Aaron Kulkis wrote:
Basil Chupin wrote:
Aaron Kulkis wrote:
Basil Chupin wrote:
I used Microsoft Office for years, using the printer I mention in
my original post (the Lexmark 4039 plus), and it NEVER even
considered not printing at the first attempt.
Strange
Why 'Strange?
Strange because this is the first time I've come across
such a thing in 25 years of using Unix and 10 years of
using Linux
Gosh, you have been miraculously protected from all the nasties for so
may years! :-) .
Mainly because the methods for an application to print
to a specific printer are so ridiculously simple that
this Open Office bug is the first I've ever been aware
of in all that time.
In many instances Windows works much better than 'Linux'.
If you define "much better" to mean you have a lot of time
to constantly repair things when it auto-destructs part or
all of itself.
No, I do not define "much better" in this way.
I have used Windows XP since it came on the market and I have not had to
"repair" it for more then, say, a couple of times - and this only
because of my own fault.
I've never had to repair a Unix or Linux installation...
And I'm talking thousands of machines, over a course
of over a decade.
The claim that XP "auto-destructs" is nothing more than a one-eyed view
by Linux zealots, and others, who claim that Windows is crap compared to
Linux-based distros.
4 out of 6 Windows XP machines in my infantry company
did exactly that when I was in Baghdad. And I'm talking
on machines on a secure military network, with NOBODY
installing software except me, or commo people from
battalion, as directed at the theater level.
And I've experienced the same thing with every version
of Windows that I've ever had on a personal machine.
Now mind you, I've been programming since 1980, and
can't even remember all the different operating
systems that I've worked on... so unfamiliarity with
computer practices cannot be the blame.
I have a buddy who is a very proficient Windows admin...
he regularly reformats and reinstalls his machines every
6 months..."whether they need it or not" because of
his experiences in the work place...a practice which he
continues to this day.
I don't trust Windows, and the apps associated with it, for all the
reasons mentioned in this and other forums as well as in magazine
articles written by people who know what Windows is all about, but I
would not support your statement in what you state in the above quoted
paragraph.
I find windows to be an absolute pain, both as a
user and as an administrator.
Windows is certainly a "pain" in many ways but as a user it doesn't send
me into an apoplectic state. That it annoys the heck out of me is true
and which is why I switched to a Linux-based distro (SuSe being the
obvious choice after trying out most of the other distros over the years).
I guess it's what you're used to.
I'm used to a system which has definite answers to
everything, and if something works today, it will
work tomorrow, unless *I* change something.
Not being an "administrator" of a Windows-based system I cannot comment
on your experiences with it (as you intimate above) but - to be very
realistic - if administrating a Windows setup was so very bad then
either nobody would be using Windows or the Windows system
administrators are masochists and/or are too stupid to change jobs so as
not to work with Windows.
I would rather administrate 1000 Unix and Linux machines
than to administrate 20 Windows machines.
Or is it a problem with openSuse? Don't know.
I've never had a problem printing from OO on SuSE.
Then you are most fortunate.
Why is OpenOffice such a bitch about printing?
Actually no, that's rather typical for Linux and Unix both.
The only systems I've ever been on in which a printer
suddenly "stopped working" or was unavailable from
an application has been Windows.
Well (and there must be a moral here), I have NEVER has a problem with
printing in Windows - even printing using a NETGEAR print server on the
computers on my home network.
You must be having very good luck.
Typical mean time to failure for a Windows printer
driver installation appears to be 4 months, and that's
on a heavily secured US Department of Defence network...
with the advantage that the US Dept of Defence actually
has access to Windows source code.
"You win some, you lose some", as they say in movies.
I'm not saying that your case does not exist...I'm just
saying that it's far RARER in Linux than in Windows.
If you say so - see above.
I've got lots of experience in both.
If you go the OO forum you will find complaints dated 23 January
2008 about not being able to print.
The above must be a typo for which I apologise - considering that
*today* is 18 January 2008 :-) .
heh.
OK, so there's a bug in the software, which apparently
isn't in the version I'm currently using, and will
probably get tracked down very quickly.
Have you downloaded the latest build, to see if it
works now?
I am using the very latest version of OO (on both 10.2 and 10.3), and
nothing has changed.
But your printer works for everything else?
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
