Quote: "It does sound like [censor] what I'm saying doesn't it? I didn't quite word it properly - a large majority of motherbaords with Cryix processors use the AV protection [and these specific Cyrix-based (processor) boards have buggy AV]. If you turned it off, fair enough."
No such thing a s 'Cyrix-based board'.. they run on (Super) Socket 7, which most of the time support is only given because it's an x86 processor. Bios don't technically support them unless they're SiS, but then you get into the whole fact that until recent SiS Chipsets were worth [censored] all. Too buggy and slow for anything really worthwhile. God did I remember those early MMX years with those horrible boards.
Quote: "Oh... ok. So you are trying to say the (working) Linux drivers that came with my IBM InfoPrint printer are illegal? (Which specify 'Any functioning UNIX/GNU/LINUX platform..' as system requirements)"
Unless you are using an IBM machine, yes. Read the GPL.
They're identical to EULAs not that Linux owners will ever admit that; basically tell you what you can and can't do with the source.
Quote: "[quote]I'm not exactly an 'old-hand' at Linux (2+ years so far) but ending your reply with something like that doesn't really inspire confidence - if you burst in attempted insults etc. (implication) then how can you be expected to survive with Linux? Linux isn't like Windows [yet]
and is all about perserverence (sp?). "
Doesn't that defeat the object of Linux? To be an alternative?[/quote]
Why yes, yes it would.
In-fact the whole Linux community as it stands 100% defeats the point in the operating system; the fanboyism about this change is just stupid.
Linux was designe to be small, portable, and easily adapted for your needs. It was never designed for home users, or as 'an alternative' to Windows. Leave that to Apple and Amiga (yes they ARE still going), Linux is for cost effective business solutions on custom systems where applications of widescale Operating Systems would be too much and the integration of Unix would cost to much to be worth while.
Quote: "All of those reasons apply to any large project with lots of people working on it. How do you think Microsoft do it?"
Microsoft has a share knowlage and bug database, allowing every employee to give advice on a problem that is found in order to help. Generall bugs are often fixxed far quicker internally but having a complete database of problems, plus past problems and solutions allow debuggers to do thier job very quickler and efficiently.
Microsoft have recently opened this technology up to the public as TheGameCreators have been noticing recently after being accepted into the Longhorn Developer/Beta Program. It is by far one of the best systems you can think of for any development team, no matter the size. You are effectively given in a consise space the combined programming knowlage of thousands upon thousands of seasoned professionals.
Wiki, and CVS logs don't even come close.
Check it out, as I believe it's currently mainly available publically for the .NET 2.0 and Visual Studio 2005 platforms.
Quote: "Raven I've been installing Linux on my machines since around 1996-97, and the only hardware problem I've ever had was a refresh issue on my IBM ThinkPad (which was solved by editing a config file using a monitor) and getting support for my wireless LinkSys USB receiver was very difficult. Other than that, I've NEVER had a problem with any hardware. And pretty much any distro I've tried (and I've tried many) have help guides all the way through install. Even installing Fedora Core through text-mode was simple in itself"
Yeah, the thing is more the hardware being used more often.
A large majority of people who use Linux are using basically mid-low range current technology.
This is the market mainly catered for because these are the machines being used. Because there is no such thing as a 'Beta' program from Linux, you only get feedback from those actively involved in development.
It's pretty much like, say TGC have several machines in thier office. Each of them have either ATI or NVIDIA cards.. so they start making a shader engine and test it internally.
The only experience they will have is with those two manufacturers. Let's say that one of the new users to DB/P tries shaders on thier S3 card. Because it wasn't in development, and the large population of the community doesn't have any of these cards... more often than not a bug will occure because of small incompatibilities.
As the user is new, they'll just decide they'll probably either decided 'DB/P isn't work my time as it doesn't work.' or they will ask on the forums at which point most people or atleast the one's that are listend to will be like 'well it works on my computer', at which point the said newbie again will get fed up and leave it alone.
It's the same deal with Linux. As it's designed be a small minority around a small very specific group of computers often developing purely to standards.. this causes issues.
Microsoft on the other hand don't, mainly because they lay down the framework; and the companies themselves are told to make thier own hardware compatible. Yet the support back'n'forth for this makes it possible and easy for them to achieve this.
While Cyrix is an IBM, the built it around thier x86 Standard, not Intels.
The problem here is much like when your trying to run things in a browser. Like Cascade Sheets; While sure Explorer and Mozilla have support for the full range of the commands, Mozilla impliments it in a way that combines all of your classes together like
Table Class -> Row Class > Link Class
Where-as Explorer only displays the base class and makes changes based on bottom up.
Link Class -> Row Class -> Table Class
this simple flip of the rendering; while using the same keyword causes very different results.
In a web-browser this just means incorrect rendering, but imagine that with your processor. It'll crash, quite spectacularly.
I mean why do you think Windows automatically wants you to report any error that happens? Just for kicks?
It's so a solution can be provided if it is a common error, and if it's new they'll know that X Hardware using X Util trying X Operationg = Crash.
They can adapt thier systems. This is just something Linux doesn't have or even have the community with which to support.
But given what Linux is ment for, why would they ever need such a thing?