XPost: comp.os.linux.advocacy, comp.sys.mac.advocacy   
   From: hhitman86@pacbell.net   
      
   On 6/24/2010 7:51 PM, Justin wrote:   
   > On 06/24/2010 09:31 PM, XX wrote:   
   >> "Justin" wrote in message   
   >> news:i00pjr$s5g$2@news.eternal-september.org...   
   >>> On 06/24/2010 06:38 PM, Rotten Apple wrote:   
   >>>> "ray" wrote in message   
   >>>> news:88i1ulF8dtU8@mid.individual.net...   
   >>>>> On Thu, 24 Jun 2010 23:10:31 +0200, Hadron wrote:   
   >>>>>   
   >>>>>> ray writes:   
   >>>>>>   
   >>>>>>> On Thu, 24 Jun 2010 15:43:39 -0400, Justin wrote:   
   >>>>>>>   
   >>>>>>>> Here is yet another failure for Windows 7. Here's the Readers'   
   >>>>>>>> Digest   
   >>>>>>>> version of whats going on. The Win7 drivers aren't fully compatible   
   >>>>>>>> with the Wireless 802.11. So it works fine without any   
   >>>>>>>> encryption but   
   >>>>>>>> the instant I secure the network - "Windows 7 was unable to connect   
   >>>>>>>> to   
   >>>>>>>> the network." I installed Ubuntu on the machine - worked like a   
   >>>>>>>> champ   
   >>>>>>>> - WPA2 personal and all.   
   >>>>>>>>   
   >>>>>>>> So, how about if one of you Microsoft trolls explain how this is   
   >>>>>>>> actually a design feature or is somehow my fault. Remember I have   
   >>>>>>>> 10+   
   >>>>>>>> years of IT experience I know how to solve driver problems. The   
   >>>>>>>> fact   
   >>>>>>>> that there are no Win 7 drivers for this wireless adapter is all   
   >>>>>>>> Microsoft's fault. I guess Microsoft just doesn't have the   
   >>>>>>>> resources   
   >>>>>>>> or brainpower to fix this little problem. Oh well. The laptop is my   
   >>>>>>>> brother's. He told me to spec out a new laptop for him. A Macbook   
   >>>>>>>> Pro.   
   >>>>>>>   
   >>>>>>> That would be yet another example of MS planned obsolescence. They'd   
   >>>>>>> rather have you get your win7 up on a new computer - they are hardly   
   >>>>>>> interested in backwards compatibility.   
   >>>>>>   
   >>>>>>   
   >>>>>> What happened to it all being the maker of the HW in question's   
   >>>>>> fault.   
   >>>>>>   
   >>>>>> You know and I know Raytard that that story is a crock of shit.   
   >>>>>   
   >>>>> One can ask whose 'fault' it is. Obviously MS does not develop drivers   
   >>>>> for anything they leave it to the manufacturer - so from that point of   
   >>>>> view, it is the manufacturers fault. One can also ask if MS SHOULD   
   >>>>> supply   
   >>>>> drivers - in which case it is their fault. And obviously, MS could   
   >>>>> provide 'hooks' to enable older drivers - but they have no interest in   
   >>>>> backwards compatibility.   
   >>>>   
   >>>> Why aren't you wondering why no manufacturer or model number has been   
   >>>> named   
   >>>> in spite of the questions being asked several times?   
   >>>>   
   >>>   
   >>> C120x - see previous post, kiddo.   
   >>   
   >> Now that was a long Google search. A long waste of time.   
   >>   
   >>   
   >   
   > That makes alot of sense.   
   > The fact is, Linux was working trouble free on the same machine Windows   
   > simply couldn't cut it.   
   > Therefore Windows 7 is flawed.   
      
        It was just a driver issue. If that's the case, then all   
   OSes are flawed. I had a Foxconn wireless adapter and can't get   
   a Linux distro to work with it. You can't blame this driver   
   issue on Windows 7.   
      
   John   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)