thanks tony
so even my suspicion it COULD have been microsoft supplying this broken code POSSIBLY to cause linux trouble was paranoid...
thats at least something i could imagine as possible tho, but even that didnt make much sense... so it was ami after all who forgot to update the tables, ok....
its still interesting though WHY ami uses seperate tables and tries to pin down what OS you use and then provide a specific table...
I guess they only meant good and wanted to be able to provide optimized tables for different OSes, but then they didnt keep all the tables up to date...
so yeah, after all there seems to be no evil whatsoever in this, its just a glitch...
actually, the only evil in all this is some people causing a few big companies a big headache and bad press without getting their facts straight.
ill check with our bios engineers now and will see if we can ping ami about updating the table or fix it ourselves.
thanksOriginally Posted by Knight
Thank you Tony and Saaya. It is sad to see a community like this turn into a war zone over an innocent glitch. Thank you two for keeping cool with all this bickering.
yeah its sad to see how fast discussions go from topic based to opinion based and then just low level barking and grunting at each other :/
Reply With Quote
Bookmarks