I'm not sure about that. "Will fix" seems to imply the errata could be fixed in silicon or microcode, while "Will not fix" means it won't get fixed at all.
A workaround isn't considered as a FIX, WONTFIX is wontfix even with published workarounds (including microcode). WONTFIX means that the error won't be fixed at the silicon level, which is the subject of errata papers.
Can you tell me how did you manage to run DOS apps without a working BIOS?
Duh? he didn't, read what he wrote, he poped in a working bios, booted to dos, switched out the good chip and in the corrupted one, and flashed the corrupted bios from dos.
That's hotflash/hotswap, and it's been a standard flashing practice for motherboards for years, for everyone who doesn't own a flashing bench at least.
It's extremely common to do it for borked motherboard though, that's called "hotflash" and people have been doing it for years.
It's not noteworthy, you just have to be careful and you're done.
On a side note, other people have flashing benches for that kind of purposes, they just pop out the flash rom, pop in the bench, imprint the chip, pop it back in the motherboard. But flashing benches are for true electronics nerds, or guys who hack around with bios and stuff all day long and will corrupt a bios or two every week
Thing is, a laptop chip doesn't mean you're using a laptop. For example, I'm currently planning to buy a core-duo based desktop machine, because even though it doesn't have the power of an A64 the fact that it runs extremely cool and still has good performances make it perfect for an extremely silent machine.
Put a Core Duo in a good box (think Antec P180), with a high quality PSU (e.g. Seasonic S12), a massive tower cooler such as Thermalright's brand new HR-01, throw in an underclocked Nexus120 just for the security, a pair of silent drives (3"5 single platter or, even better, notebook drives) and a passively cooled CG and you get yourself a completely silent box that couldn't overheat if it's life was on the line.
Well, just to show you it probably hasn't changed much since I left, here's a post from the Triton website (Triton's been one of the top-10 guilds of EQ ever since... the guild was born basically) talking about the very latest Everquest extension (or not, they probably have released another one since october, SoE seems to release an expansion every 4 month now, used to be once a year... doesn't matter much though, they just keep the price fix and span the same content over 3 extensions instead of one, means more $$$). You can see by his comment about the Bloodeye encounter how interresting the fight seemed.
Everquest used to be the most popular MMORPG. It was more or less the first full-3D MMO (along with Asheron's Call, but AC never reached EQ's fame). Starting with the first extension (Ruins of Kunark), so-called Raid targets started to develop for "high end" players (the ones that'd play 6h/day 7d/week at least on average): big monsters, requiring military-like organization, teams of ~30 players, and LOTS of time (and skill). This was reinfoirced by the second extension (Scars of Velious) with more content geared towards high-end players, as well as complete zones requiring a raiding guild to even get the ability to enter it. The 3 "final" zones of the extension (Plane of Growth, Temple of Veeshan and Sleeper's Tomb) all took multiple hours of fight from start to end, even though the players rapidly began to "cheat" the game "especially in sleeper's tomb, setting teleporting bots near the end of the zone, in order to avoid 3-4 hours of cleaning every time).
Next came Luclin, which was more or less the worst: 2 very high end zones (Ssra Temple and Vex Thal, the latter being only available after a very long, time consuming quest, and requiring to beat the boss of Ssra temple), heaps of monsters with mountains of hit points and very few shortcuts (some of the boss monsters in Vex Thal used to take more than an hour each to beat, from the time you started hitting on it to the fall of the monster), in fact Vex Thal itself was usually done in 2 to 3 days (6-10 hours raid each day)
Then came Planes of Power, which saw much less "huge-ass HPs" mobs, but more event-driven things... that in the end took about as long, and it had 10 times the number of boss mobs Luclin had. Not only that, but even the short events were a pain (a single error and you'd have been preparing for 3 hours for nothing, thank you drive through, come back next week... and i'm not joking here), most of them were buggy and unreliable at first, the top tier guilds spend a year "debugging" the various scripts before being allowed to reach the final zone of the expansion.
I got done playing soon after my guild beat PoTime (disc: I wasn't in a top tier guild, so that was in mid-2004) because it was just taking too much time, and wasn't fun anymore (to me), but I'm pretty sure the high end hasn't changed much (may be slightly funnier, but it's no less time consuming)
When I stopped playing, I had a/play of 160 days over about 4 years I think (160 days as in 160*24h with the character logged in the game), I know some people who had been averaging that kind of/played every year since the release of EQ (had a guildmate with 500 days of/play)...
There, you have it, that is EQ's insanity. And we even liked it.
And BTW, that "problem" which you speak of was "fixed" in the latest version, so saying they don't care about it is just uninformed flamebait.
Failed, only one issue has been fixed (DHT flag), and it's been fixed 13 days ago while the issue has been known to the dev team since April 2005 at least.
BitComet incorrectly uses DHT on private torrents/trackers, even ignoring BitComet's user's settings NOT to if the tracker briefly goes down!
BitComet deliberately misreports upload and download amounts to trackers and seeds in order to get the "lion's share" of upload bandwidth from seeders.
(Others have said that using super-seed as a seeder often takes >200% of the torrent's size to create other seeds due to BitComet's cheating-by-default.)
BitComet disconnects and reconnects to download more than is fair via optimistic unchoke -- (which is meant to give new arrivals something to share. Sadly, Azereus is reported to do this too. Automatically droping working connections is hostile activity -- it creates lots of churn which costs extra bandwidth for trackers and peers alike.
BitComet seems to favor uploading to other BitComet clients, even when getting faster download speeds from other clients. The most extreme case was a private tracker/torrent on a huge college lan with "100mbps" connections -- the person who did this could download at >5mbps if using BitComet but only ~5-15 KB/sec if using Torrent.
The only item fixed so far is #1 DHT flag, it's supposed to be fixed in version 0.61 released 13 days ago, the failure to respect the DHT flag has been known since March 2005...
Simple: Luddle is either a genius, an ET or very dedicated to his software.
Probably a bit of all, and the fact that it's coded in C++/Win32 with custom libraries (and the final executable is run through a packer to further reduce it's size by 50%, even though that slightly bumps the RAM usage)
You are right, but then again a windows client relies on the win32 api doesn't it.
But doesn't load half the files of the computer into ram when it starts.
uTorrent takes 5Mb of RAM estate running full speed with 20+ torrents loaded in... BitTornado, using wxPython, hogs 25Mb/instance (== 25Mb/torrent, for it launches an instance per file) and a well loaded azureus will "optimize" at least 150Mb of your ram...
Used to be mine too, but the RAM usage growing linearly with the torrents (25Mb/torrent ain't nothing to spit at) and the fact that no release actually works well past 0.3.7 made me switch to uTorrent. I find the interface clunkier and more annoying to configure on a per-torrent basis, but not having 500Mb swallowed by 25 instances of BitTornado running is actually worth it.
Even if it is fixed (is it really?) it's extremely far from the only gripe people have against bitcomet, and the abuses bitcomet makes of the BT protocol and functions.
I don't know which BitComet fagboi modded parent as troll, but what he's saying is the plain and simple truth, BitComet is "broken" (cheating), the dev team doesn't care and won't fix it, and it has been banned from several private trackers from not respecting any DHT flag, prioritizing BitComet clients over others, abusing the optimistic unchoke process and spamming (DoS-like) other clients and trackers.
Sorry, I have 2Gb RAM and I still prefer Torrent by far and large, you just can't beat Teh Snappy and 5Mb of RAM estate that also provides most of azureus' features.
And I'd add that, for all meanings and purposes, the Web (regardless of it's "versioning") is a wonderfully universal medium: thanks to a pair of assistive technologies, it's possible for blind, paralytics, deafs people,... to access informations in a much easier, much pleasant way.
These assistive technologies don't always work well with some javascript stuff. Accessibility is important, and the baseline of accessibility is the base text-only medium, without all the bells and whistles but with the content and the basic services.
Even when it's a slower, longer, more cumbersome to use the service, page or application, it's still orders of magnitude better than not being able to reach the service at all.
Slashdot Mirror
A workaround isn't considered as a FIX, WONTFIX is wontfix even with published workarounds (including microcode). WONTFIX means that the error won't be fixed at the silicon level, which is the subject of errata papers.
Duh? he didn't, read what he wrote, he poped in a working bios, booted to dos, switched out the good chip and in the corrupted one, and flashed the corrupted bios from dos.
That's hotflash/hotswap, and it's been a standard flashing practice for motherboards for years, for everyone who doesn't own a flashing bench at least.
It's extremely common to do it for borked motherboard though, that's called "hotflash" and people have been doing it for years.
It's not noteworthy, you just have to be careful and you're done.
On a side note, other people have flashing benches for that kind of purposes, they just pop out the flash rom, pop in the bench, imprint the chip, pop it back in the motherboard. But flashing benches are for true electronics nerds, or guys who hack around with bios and stuff all day long and will corrupt a bios or two every week
Thing is, a laptop chip doesn't mean you're using a laptop. For example, I'm currently planning to buy a core-duo based desktop machine, because even though it doesn't have the power of an A64 the fact that it runs extremely cool and still has good performances make it perfect for an extremely silent machine.
Put a Core Duo in a good box (think Antec P180), with a high quality PSU (e.g. Seasonic S12), a massive tower cooler such as Thermalright's brand new HR-01, throw in an underclocked Nexus120 just for the security, a pair of silent drives (3"5 single platter or, even better, notebook drives) and a passively cooled CG and you get yourself a completely silent box that couldn't overheat if it's life was on the line.
Maybe the fact that some fanbois manage to find excuse for blizzard having problems others managed to solve years ago?
Well, just to show you it probably hasn't changed much since I left, here's a post from the Triton website (Triton's been one of the top-10 guilds of EQ ever since... the guild was born basically) talking about the very latest Everquest extension (or not, they probably have released another one since october, SoE seems to release an expansion every 4 month now, used to be once a year... doesn't matter much though, they just keep the price fix and span the same content over 3 extensions instead of one, means more $$$). You can see by his comment about the Bloodeye encounter how interresting the fight seemed.
Next came Luclin, which was more or less the worst: 2 very high end zones (Ssra Temple and Vex Thal, the latter being only available after a very long, time consuming quest, and requiring to beat the boss of Ssra temple), heaps of monsters with mountains of hit points and very few shortcuts (some of the boss monsters in Vex Thal used to take more than an hour each to beat, from the time you started hitting on it to the fall of the monster), in fact Vex Thal itself was usually done in 2 to 3 days (6-10 hours raid each day)
Then came Planes of Power, which saw much less "huge-ass HPs" mobs, but more event-driven things... that in the end took about as long, and it had 10 times the number of boss mobs Luclin had. Not only that, but even the short events were a pain (a single error and you'd have been preparing for 3 hours for nothing, thank you drive through, come back next week... and i'm not joking here), most of them were buggy and unreliable at first, the top tier guilds spend a year "debugging" the various scripts before being allowed to reach the final zone of the expansion.
I got done playing soon after my guild beat PoTime (disc: I wasn't in a top tier guild, so that was in mid-2004) because it was just taking too much time, and wasn't fun anymore (to me), but I'm pretty sure the high end hasn't changed much (may be slightly funnier, but it's no less time consuming)
When I stopped playing, I had a /play of 160 days over about 4 years I think (160 days as in 160*24h with the character logged in the game), I know some people who had been averaging that kind of /played every year since the release of EQ (had a guildmate with 500 days of /play)...
There, you have it, that is EQ's insanity. And we even liked it.
Had you ever played Everquest in a mid-high end guild, during the Luclin+ era, you too would consider that 40 man raid for 6 hours IS casual.
Sounds like the fucking Sleeper Event in Everquest, but with less coolness and more suckage, to me...
TFA tells me that AQ stands for "Ahn'Qiraj"
I think Azureus has PHE now, at least in the last betas (seems to be flawed though), and Ludde's currently implementing a PHE in uTorrent
No, the issue is that the Turions are NOT equally good, and clearly not better.
And that's a shame, for I'd really wish to stay with AMD.
Failed, only one issue has been fixed (DHT flag), and it's been fixed 13 days ago while the issue has been known to the dev team since April 2005 at least.
BitComet cheats:
BitComet incorrectly uses DHT on private torrents/trackers, even ignoring BitComet's user's settings NOT to if the tracker briefly goes down!
BitComet deliberately misreports upload and download amounts to trackers and seeds in order to get the "lion's share" of upload bandwidth from seeders.
(Others have said that using super-seed as a seeder often takes >200% of the torrent's size to create other seeds due to BitComet's cheating-by-default.)
BitComet disconnects and reconnects to download more than is fair via optimistic unchoke -- (which is meant to give new arrivals something to share. Sadly, Azereus is reported to do this too. Automatically droping working connections is hostile activity -- it creates lots of churn which costs extra bandwidth for trackers and peers alike.
BitComet seems to favor uploading to other BitComet clients, even when getting faster download speeds from other clients. The most extreme case was a private tracker/torrent on a huge college lan with "100mbps" connections -- the person who did this could download at >5mbps if using BitComet but only ~5-15 KB/sec if using Torrent.
The only item fixed so far is #1 DHT flag, it's supposed to be fixed in version 0.61 released 13 days ago, the failure to respect the DHT flag has been known since March 2005...
Simple: Luddle is either a genius, an ET or very dedicated to his software.
Probably a bit of all, and the fact that it's coded in C++/Win32 with custom libraries (and the final executable is run through a packer to further reduce it's size by 50%, even though that slightly bumps the RAM usage)
But doesn't load half the files of the computer into ram when it starts.
uTorrent takes 5Mb of RAM estate running full speed with 20+ torrents loaded in... BitTornado, using wxPython, hogs 25Mb/instance (== 25Mb/torrent, for it launches an instance per file) and a well loaded azureus will "optimize" at least 150Mb of your ram...
Used to be mine too, but the RAM usage growing linearly with the torrents (25Mb/torrent ain't nothing to spit at) and the fact that no release actually works well past 0.3.7 made me switch to uTorrent. I find the interface clunkier and more annoying to configure on a per-torrent basis, but not having 500Mb swallowed by 25 instances of BitTornado running is actually worth it.
Even if it is fixed (is it really?) it's extremely far from the only gripe people have against bitcomet, and the abuses bitcomet makes of the BT protocol and functions.
I don't know which BitComet fagboi modded parent as troll, but what he's saying is the plain and simple truth, BitComet is "broken" (cheating), the dev team doesn't care and won't fix it, and it has been banned from several private trackers from not respecting any DHT flag, prioritizing BitComet clients over others, abusing the optimistic unchoke process and spamming (DoS-like) other clients and trackers.
or are comparing to Torrent, currently taking up 3,612K with rougly the same load as your azureus (slightly lower)
but Torrent uses 5Mb of ram when doing the same job...
Sorry, I have 2Gb RAM and I still prefer Torrent by far and large, you just can't beat Teh Snappy and 5Mb of RAM estate that also provides most of azureus' features.
Serious business
And I'd add that, for all meanings and purposes, the Web (regardless of it's "versioning") is a wonderfully universal medium: thanks to a pair of assistive technologies, it's possible for blind, paralytics, deafs people, ... to access informations in a much easier, much pleasant way.
These assistive technologies don't always work well with some javascript stuff. Accessibility is important, and the baseline of accessibility is the base text-only medium, without all the bells and whistles but with the content and the basic services.
Even when it's a slower, longer, more cumbersome to use the service, page or application, it's still orders of magnitude better than not being able to reach the service at all.