re: Arctic Silver, I wouldn't dump huge blobs on your traces, but it is practically non-conductive. That was the big deal with it in the first place...previous metal-based compounds were really conductive, whereas non-conductive silica-based compounds weren't very effective.
My install was a little messy, too, and there's a light dusting of AS2 on my Athlon traces (like you say, it's nigh-impossible to wipe off without submerging the chip in isopropyl). I haven't gotten any clock/voltage/instability issues from it, so I'm pretty sure I'm not shorting anything.
Reverse engineering isn't illegal, but code copying is. The whole reason you do a heavily documented double-blind is so that chunks of code will -inevitably- appear the same. With documentation, you can claim coincidence, or that it was a necessity of the algorithm.
If the bnetd guys didn't keep docs (or if they reverse-engineered from a disassembly...that isn't legal, btw, since object code is as protected as source...their credibility is going to be severely impacted. If they did duplicate a bug that's not immediately reflected in the packet handling, I'd say they're pretty well screwed.
Slashdot Mirror
They don't work for keyboards, unfortunately, or at least the one that came with my logitech mouse doesn't. I assume they're a commodity item.
Nice setup.
re: Arctic Silver, I wouldn't dump huge blobs on your traces, but it is practically non-conductive. That was the big deal with it in the first place...previous metal-based compounds were really conductive, whereas non-conductive silica-based compounds weren't very effective.
My install was a little messy, too, and there's a light dusting of AS2 on my Athlon traces (like you say, it's nigh-impossible to wipe off without submerging the chip in isopropyl). I haven't gotten any clock/voltage/instability issues from it, so I'm pretty sure I'm not shorting anything.
Geo
Reverse engineering isn't illegal, but code copying is. The whole reason you do a heavily documented double-blind is so that chunks of code will -inevitably- appear the same. With documentation, you can claim coincidence, or that it was a necessity of the algorithm.
If the bnetd guys didn't keep docs (or if they reverse-engineered from a disassembly...that isn't legal, btw, since object code is as protected as source...their credibility is going to be severely impacted. If they did duplicate a bug that's not immediately reflected in the packet handling, I'd say they're pretty well screwed.
Add
user_pref("middlemouse.contentLoadURL", false);
to user.js in your profile directory. The bit the other guy posted with "openNewWindow" disables the wrong bit of functionality.
Geo
And probably very limited support, of the type they provide on their other entry-level compiler packages.
Geo
...is the special dog noise package!
C: "woof woof WOOF woof WOOF WOOF WOOF!"
SA: "What's that, Lassie?"
C: "woof woof WOOF WOOF woof WOOF WOOF woof!"
SA: "It's timmyh? And he's portscanning from the WELL?"