Quote:
|
It fired off a report to MS, but that doesn't help me very much.
|
whoa. 'hey mr micro$oft support, i ran into connectivity problems while trying to p2p some pirated 'ware. can u help me?'
hell, i'd never use xp unless i absolutely cannot avoid it (at which time m$ will hopefully have lost off from its standing on the desktop os market and linux will have matured even more) - it's far too proprietary (making greyware programming like p2p clients tough) and far too insecure (if i would share illegal stuff, which i, of course, don't, i'd avoid at all costs the worst stoolpigeon of all os'es round... think about it: just because it's flashy and because the marketing dept has a huge budget, xp is not a good, in fact possibly the worst os to run p2p on - the firewall stinks and is a bitch to replace by a decent one (by which i do not refer to zone alarm - far too hackable and virii-targeted 4 yours truly), the system's tendency to loudmouth about to whoever it may concern about all sorts of activity on your box, including such of the more shady type, precludes it to be used by any security-conscious (or conscious in general, for a crime is crime is a cime, no matter how much you may think it justified 'morally') p2p'er.
insofar, as to answer the original question:
get a decent os ;-)
and about 'flock':
we all know tht dotnet is m$' attempt to blow away java from the desktop market. now, what can we expect? another greedy monopoly scheme, another m$ development with huge security holes, in all probability a vm kernel that now and then squeezes off a little data packet to whoever paid m$ for getting prime user data, just like it's implemented in nearly any m$ app to date.
sorry, folks: using dotnet for a p2p prog (and even if it's just the gui) is nearly as stupid as using ie components (which is why i wont go fasttrack). imho it's more than that: it's talk one way, walk another - who's going to benefit from p2p'ers using m$-code dependent progs?
microsoft is.
see?