I smell some Linux idiots...

Linonut <linonut DeleteThis @bellsouth.net> writes:

> 2000? Usually.
> XP? Less often. I've seen more blue screens and network problems on
> XP than I ever saw on NT 4.0; in fact, XP is more like NT 3.5
> as far as stability goes.


I don't believe you. I am accusing you of lying. I used both NT and XP
as development machines for years developing low level DLLs for window
management in C++ and never had these issues you keep referring to.

Come on, fess up - how did you keep getting these BSODs. What were you doing?

--
What part of "I don't know how may there will be the first weeks" was so
unclear and needs explanation? : Peter Köhlmann, COLA.

After takin' a swig o' grog, Hadron Quark belched out this bit o' wisdom:

> Linonut <linonut DeleteThis @bellsouth.net> writes:
>
>> 2000? Usually.
>> XP? Less often. I've seen more blue screens and network problems on
>> XP than I ever saw on NT 4.0; in fact, XP is more like NT 3.5
>> as far as stability goes.
>
> I don't believe you. I am accusing you of lying.

I am not lying. But, why should one care about the accusations of an
unabashed troll?

> I used both NT and XP as development machines for years developing low
> level DLLs for window management in C++ and never had these issues you
> keep referring to.

Good for you. By the way, what do you mean by "low level DLLs for
Window Management"?

> Come on, fess up - how did you keep getting these BSODs. What were you doing?

I've only gotten one, myself. Due to a bad Cisco driver. That same
machine did reboot spontaneously a couple of times, I have no idea why.

I haven't seen /my/ latest XP machine (which, thankfully, I've passed down to
the "new guy") reboot spontaneously or blue screen. But I have seen a
few others' XP boxes BSOD.

And, no, they weren't testing their code when it happened.

I've seen many more spontaneous reboots and BSODs in Windows than I've
seen spontaneous reboots (none) and kernel panics (a couple) in Linux.

Linux is simply more stable, in my experience.

--
"Linux is a cancer!" -- Steve Ballmer, CEO Microsoft

"DFS" <nospam DeleteThis @dfs_.com> writes:

> Kier wrote:
>> On Sat, 05 May 2007 11:19:20 -0500, DFS wrote:
>>
>>> Linonut wrote:
>>>>
>>>> Vista? The word on the street isn't too good.
>>>
>>> hmmmm... I see virtually every OEM preinstalling it and selling it.
>>
>> They don't have amuchchoice. XP is not going to be around much
>> longer. And naturally they'll sell the latest OS.
>
> You made some subliminal revelations here. See if you can figure out what
> they are.
>

LOL.

The "naturally" adds icing to the cake.

--
Used with permission.

Linonut wrote:
> After takin' a swig o' grog, DFS belched out this bit o' wisdom:
>
>>> Extree extree from DFS, read all about it!
>>>
>>> MISCONFIGURED OR FAULTY HARDWARE CAN CAUSE SPONTANEOUS REBOOT!!!!
>>
>> How many times have cola idiots whined that if a 3rd party app takes
>> Windows down it's evidence of Windows inferiority? So what's the
>> difference if it's an app or a piece of hardware?
>
> Oh ... my ... God.

Why so dramatic?



>>> XP? Less often. I've seen more blue screens and network problems
>>> on XP than I ever saw on NT 4.0; in fact, XP is more like NT
>>> 3.5 as far as stability goes.
>>
>> Can you reliably reproduce a BSOD on XP?
>
> Why would I want to?
>
> No, I haven't even tried.

Then XP really isn't as unstable as you intimate it is.



>>> 2003? Not bad. Needs a bit of care.
>>
>> It's a rock.
>
> Not in our experience. It does work pretty well, in general. Win
> 2003's "clustering" is a friggin' joke, though.

How so?



>>> Vista? The word on the street isn't too good.
>>
>> hmmmm... I see virtually every OEM preinstalling it and selling it.
>
> What choice did they have?

It's about time - that's exactly what I've been saying for 3 years!

WCJ wrote:
> High Plains Thumper wrote:
>>> http://www.cafepress.com/saproducts/539539
>>
>> /quote/ Among our broad selection of computer-themed
>> products, such as t- shirts, bumper stickers, coffee mugs,
>> mousepads, and much more, you'll find items like There's no
>> place like 127.0.0.1, Linux: Because rebooting is only for
>> installing hardware, and There are 10 kinds of people: Those
>> who understand binary and those who don't. /-quote/
>>
>> This is good news!
>>
>> It means that the Linux user community has grown to the
>> point that a non-Linux vendor can make money off by selling
>> Linux nick-nacks. We are no longer One Percenters!
>
> (That's my web site you've quoted.) According to my sites'
> stats, *nix makes up 5-10% of my visitors--around 5% without
> counting Mac OSX, 10% with. So, yeah, we're definitely not
> 1-percenters any more!

Glad to meet you. I'd never expect the proprietor of the site to
reply, but this is good. Not being 1%'ers any more, I guess that
means we are no longer outlaws.

--
Rafael

Rafael wrote:
> WCJ wrote:
>> High Plains Thumper wrote:
>>>> http://www.cafepress.com/saproducts/539539
>>>
>>> /quote/ Among our broad selection of computer-themed
>>> products, such as t- shirts, bumper stickers, coffee mugs,
>>> mousepads, and much more, you'll find items like There's no
>>> place like 127.0.0.1, Linux: Because rebooting is only for
>>> installing hardware, and There are 10 kinds of people: Those
>>> who understand binary and those who don't. /-quote/
>>>
>>> This is good news!
>>>
>>> It means that the Linux user community has grown to the
>>> point that a non-Linux vendor can make money off by selling
>>> Linux nick-nacks. We are no longer One Percenters!
>>
>> (That's my web site you've quoted.) According to my sites'
>> stats, *nix makes up 5-10% of my visitors--around 5% without
>> counting Mac OSX, 10% with. So, yeah, we're definitely not
>> 1-percenters any more!

> Glad to meet you. I'd never expect the proprietor of the site to
> reply, but this is good. Not being 1%'ers any more, I guess that
> means we are no longer outlaws.

Thanks--nice to meet you, too. I only came here as a result of
following an entry in my site logs--I wondered what was being said about
us in c.o.l.a., and laughed my ass off when I saw the windoze troll's
comments. I guess he has a serious case of OS envy, what with all the
rebooting he has to do, paying for bloated crash-prone software, etc. Oh
well, whatever makes him happy!

--

Unless you're a hemorrhoid, get off my ass
http://www.cafepress.com/saproducts.30997994

DFS <nospam DeleteThis @dfs_.com> wrote:
>
> You let me know when OpenOffice Calc will handle this useful Excel VB
> functionality that lets me add custom colors to a sheet.
>
> dim cTxt as String
> cTxt = "Dark Walnut"
> cTxt = Application.WorksheetFunction.VLookup(cTxt,
> Worksheets("ProductStandards").Range(colorRange), 2)
> objProducts.Cells(1, 3).Font.Color = RGB(CLng("&H" & Left(cTxt, 2)),
> CLng("&H" & Mid(cTxt, 3, 2)), CLng("&H" & Right(cTxt, 2)))

OpenOffice is built around a component object model with open interfaces.
Basically every document attribute is accessible via that interface, so
I can write the equivalent of your above script in a pile of different
languages. The openoffice.org website has the following to say about it:

The Scripting Framework allows OpenOffice.org users to write and
run macros in multiple languages including OpenOffice.org Basic,
Python, Java, BeanShell and JavaScript. These macros can then be
assigned to menus, toolbars, keyboard shortcuts, events and
embedded objects.

If you are bringing over VB scripts, then OO Basic is probably the
easiest conversion, but I personally would probably pick something
like Java or JavaScript for anything written from scratch. Colors
can be set by manipulating the CharColor attribute, and there is
an RGB function like the one you use. The implementation is trivial
and left as an exercise for the student.

Later,

Thad

thad01.TakeThisOut@tux.glaci.remove-this.com wrote:
> DFS <nospam.TakeThisOut@dfs_.com> wrote:
>>
>> You let me know when OpenOffice Calc will handle this useful Excel VB
>> functionality that lets me add custom colors to a sheet.
>>
>> dim cTxt as String
>> cTxt = "Dark Walnut"
>> cTxt = Application.WorksheetFunction.VLookup(cTxt,
>> Worksheets("ProductStandards").Range(colorRange), 2)
>> objProducts.Cells(1, 3).Font.Color = RGB(CLng("&H" & Left(cTxt, 2)),
>> CLng("&H" & Mid(cTxt, 3, 2)), CLng("&H" & Right(cTxt, 2)))
>
> OpenOffice is built around a component object model with open
> interfaces. Basically every document attribute is accessible via that
> interface, so I can write the equivalent of your above script in a
> pile of different languages.

So they say - for brevity's sake, just one language will do.

And in case it's not clear, the 3rd statement returns a HEX value from a
lookup table, and the 4th statement extracts the RGB values and applies them
to the stated property of the specific cell(s) - in this case the font color
attribute of cell C1.

And in case you weren't aware (you cola guys have blind spots when it comes
to MS technologies):
http://schmidt.devlib.org/java/libraries-excel.html
http://www.answermysearches.com/generate-an-excel-formatted-file-right...-python




> The openoffice.org website has the following to say about it:
>
> The Scripting Framework allows OpenOffice.org users to write and
> run macros in multiple languages including OpenOffice.org Basic,
> Python, Java, BeanShell and JavaScript. These macros can then be
> assigned to menus, toolbars, keyboard shortcuts, events and
> embedded objects.
>
> If you are bringing over VB scripts, then OO Basic is probably the
> easiest conversion, but I personally would probably pick something
> like Java or JavaScript for anything written from scratch. Colors
> can be set by manipulating the CharColor attribute

OpenOffice.org Help for CharColor: "No Topics found"



>, and there is an RGB function like the one you use. The implementation
> is trivial and left as an exercise for the student.

And still no cola "advocates" can step up and write any simple OO Calc
scripts in OOBasic, or any language for that matter?

DFS <nospam.RemoveThis@dfs_.com> wrote:
>
> How many times have cola idiots whined that if a 3rd party app takes Windows
> down it's evidence of Windows inferiority? So what's the difference if it's
> an app or a piece of hardware?

The difference is that an app should never take down the OS, the OS
should be able to handle that and only crash that one app. That is
in fact the case with apps on Linux.

Drivers are another story. Having more direct access to the kernel,
they have more ability to crash the system. Linux has gotten pretty
good at minimizing even those risks, and many things that used to
cause a kernel panic now only generate an oops and things keep
chugging along.

Windows seems to suffer from more stability problems because MS
took the approach of vertically integrating many of their components
and tying more stuff right into the kernel layer then Linux (which
has a more modular, layered approach). Recent Windows versions
have moved away from that, pushing much of the driver work back up
into the user process space, which hopefully will improve stability,
but it is likely to hurt performance some.

Thad

DFS <nospam RemoveThis @dfs_.com> wrote:
>
> Can you reliably reproduce a BSOD on XP?

Do I get to write my own driver? > Seriously though, reliable
BSODs are the easiest to catch and thus the first to be fixed. Its
those intermittent seemingly random ones that hang around forever
and cause the most trouble. Maybe if Windows was open source, a
wider pool of developers would have a better chance of catching
the bugs and fixing them.

Its no accident that Linux has a reputation for stability.

Thad

thad01.RemoveThis@tux.glaci.remove-this.com wrote:
> DFS <nospam.RemoveThis@dfs_.com> wrote:
>>
>> Can you reliably reproduce a BSOD on XP?
>
> Do I get to write my own driver? > Seriously though, reliable
> BSODs are the easiest to catch and thus the first to be fixed. Its
> those intermittent seemingly random ones that hang around forever
> and cause the most trouble. Maybe if Windows was open source, a
> wider pool of developers would have a better chance of catching
> the bugs and fixing them.

Careful what you wish for: if Windows was open source there would be no
Microsoft - and cola would have no reason to live.



> Its no accident that Linux has a reputation for stability.

I think there's very little relationship between open source and stability.
KNode and Konqueror are some of the least stable apps I've ever used, and I
used to make OpenOffice crash easily.

DFS wrote:

> But why does the nVidia driver

Yes, my nVidia Nx6600 works great on opensuse 10.2

thanks for asking

--
http://you-read-it-here-first.com
Get a 3% t-shirt:
http://dyo.customink.com/cink/r.jsp?E=jabailo%40texeme.com&F=3percent3
Be Clear:
http://dyo.customink.com/cink/r.jsp?E=jabailo%40texeme.com&F=straight1

On Sun, 06 May 2007 02:11:00 +0000, thad01 wrote:

> DFS <nospam DeleteThis @dfs_.com> wrote:
>>
>> How many times have cola idiots whined that if a 3rd party app takes
>> Windows down it's evidence of Windows inferiority? So what's the
>> difference if it's an app or a piece of hardware?
>
> The difference is that an app should never take down the OS, the OS
> should be able to handle that and only crash that one app. That is in
> fact the case with apps on Linux.

AFAIK this has been explained time & again to the dolt. He's either got a
memory loss, or it doesn't sink in to begin with.

> Drivers are another story. Having more direct access to the kernel,
> they have more ability to crash the system. Linux has gotten pretty
> good at minimizing even those risks, and many things that used to cause
> a kernel panic now only generate an oops and things keep chugging along.
>
> Windows seems to suffer from more stability problems because MS took the
> approach of vertically integrating many of their components and tying
> more stuff right into the kernel layer then Linux (which has a more
> modular, layered approach). Recent Windows versions have moved away
> from that, pushing much of the driver work back up into the user process
> space, which hopefully will improve stability, but it is likely to hurt
> performance some.