1 |
Alan McKinnon wrote: |
2 |
> On Thursday 01 January 2009 11:02:23 Dale wrote: |
3 |
> |
4 |
>> I just did a reinstall on my rig and it did the exact same thing. I had |
5 |
>> to mask the one it installed and re-emerge the older one that does |
6 |
>> work. Isn't there some way for it to pick the right one? After all, it |
7 |
>> new it was the WRONG one it was installing. Looks to me like it could |
8 |
>> pick the right one. |
9 |
>> |
10 |
> |
11 |
> The software does not have the slightest vaguest foggiest concept of what the |
12 |
> RIGHT and the WRONG drivers are. That's a human being's conclusion. |
13 |
> |
14 |
> It therefore cannot decide. |
15 |
> The devs therefore correctly decided to not even try and decide. |
16 |
> |
17 |
> Unix-like systems demand that the user actually has a clue, is more than a |
18 |
> mere automatonic moron, can and does read information and can and does really |
19 |
> make decisions. And is prepared to live with the results. |
20 |
> |
21 |
> Some Unix people try to get all politically correct and hide this fundamental |
22 |
> fact, but that is just plain wrong. It will never work any other way than how |
23 |
> it is working right now. |
24 |
> |
25 |
> Users that are not prepared to actually think about what they are doing should |
26 |
> switch back to Windows. That system specializes in treating their customers |
27 |
> like complete idiots. |
28 |
> |
29 |
> |
30 |
|
31 |
Not disputing what you say but if it doesn't know what card we are |
32 |
using, why does it warn us that it is not compatible? Exact same thing |
33 |
happened to me a couple weeks ago and it has not happened before that, |
34 |
that I can recall anyway. |
35 |
|
36 |
Dale |
37 |
|
38 |
:-) :-) |