Doesn't seem to me that this will do much other than hurt the market, and punish a lot of Microsoft employees who have not necessarily done anything anticompetitive themselves. I can agree with the sentiment previously expressed that it would be great to see which wins in the long run: Closed or open source software. A better solution (originally proposed by RMS, to my knowledge) would be simply leaving the company as it is, keeping its source closed, but merely forcing it to open and publish all of its APIs and standards to the satisfaction of its competitors in markets where it can use its OS dominance to leverage them out. This isn't overly vindictive, and more importantly it gets to the source of the problem: the anticompetitive nature of their monopoly. The OS monopoly is fine for now, Linux, etc. will do what they will all in good time. All that needs to be done is to ensure that that admittedly legitimate monopoly (do you really want to answer Linux-related questions for most people who use Linux? I'd be perfectly happy with Linux just grabbing enough market share to get software and drivers developed for it in a timely manner. Forget world domination.) doesn't keep people out of the browser market, or the office software market. Most posts I've seen seem to be fairly sensible in that they express a certain distaste for this plan. Anyone know if there's a way for us to communicate with the DOJ and give them the benefit of our understanding of the technical issues, and why breaking up M$ isn't necessarily optimal? -RevRigel
Wouldn't this mean that both phone lines and AM radio stations are in violation of part 15 of the FCC rules? The AM radio stations are guilty of causing harmful interference, and the phone companies are guilty of not accepting interference gracefully.
Yeah. I've got an Abit BP6-based machine. The speed of things on my machine was fairly unplayable when there were >25 people on a server, but after typing the magical "r_smp 1" into the console and relaunching the program, it's been completely playable with just my TNT card (30fps or so, seems reasonable given the current state of XF86's lack of DRI).
Slashdot Mirror
Doesn't seem to me that this will do much other than hurt the market, and punish a lot of Microsoft employees who have not necessarily done anything anticompetitive themselves. I can agree with the sentiment previously expressed that it would be great to see which wins in the long run: Closed or open source software. A better solution (originally proposed by RMS, to my knowledge) would be simply leaving the company as it is, keeping its source closed, but merely forcing it to open and publish all of its APIs and standards to the satisfaction of its competitors in markets where it can use its OS dominance to leverage them out. This isn't overly vindictive, and more importantly it gets to the source of the problem: the anticompetitive nature of their monopoly. The OS monopoly is fine for now, Linux, etc. will do what they will all in good time. All that needs to be done is to ensure that that admittedly legitimate monopoly (do you really want to answer Linux-related questions for most people who use Linux? I'd be perfectly happy with Linux just grabbing enough market share to get software and drivers developed for it in a timely manner. Forget world domination.) doesn't keep people out of the browser market, or the office software market. Most posts I've seen seem to be fairly sensible in that they express a certain distaste for this plan. Anyone know if there's a way for us to communicate with the DOJ and give them the benefit of our understanding of the technical issues, and why breaking up M$ isn't necessarily optimal? -RevRigel
My guess would be that it's parity ram. 256 = 32 * 8. 288 = 32 * 9. Extra bit for parity checking and all.
Wouldn't this mean that both phone lines and AM radio stations are in violation of part 15 of the FCC rules? The AM radio stations are guilty of causing harmful interference, and the phone companies are guilty of not accepting interference gracefully.
-Rigel
Yeah. I've got an Abit BP6-based machine. The speed of things on my machine was fairly unplayable when there were >25 people on a server, but after typing the magical "r_smp 1" into the console and relaunching the program, it's been completely playable with just my TNT card (30fps or so, seems reasonable given the current state of XF86's lack of DRI).
-Rigel