The "cookie" sent to Microsoft when requesting the DVD chapters is not reliably linkable back to the client user. As Microsoft has already said, you can clear cookies to remove it. You can also Work Offline to not even make the request in the first place. Did you even read Microsoft's response?
The bulletin I saw on bugtraq said nothing about tracking songs. On top of that, Microsoft disputes the bulletin and issues in it, but the author is blantently ignoring their direct responses to all of his points. this is an extreme exaggeration that seems to be driven by the "fear big old Microosft" camp. It is a feature, not spyware.
Take them to the closest IBM office building to you. Take each drive, assign it a window, and throw really hard. Make sure you attach a printout of this Slashdot story and all the comments. Hilight your comment in red.
All my MP3s and co. are on a 20GB Maxtor 92041U4. The drive is several years old, and has never choked. It is in the same machine as these damned IBM things that keep suiciding.
I'm glad it works for you and all, but I must say that is just retarded. If their product is that flaky or sensitive, they should send a piece of paper with each one that says "THIS PRODUCT IS SO SENSITIVE THAT YOU CAN'T SCREW IT IN AND MUST KEEP 300MPH WINDS BLOWING ABOVE AND BELOW IT AT ALL TIMES. FAILURE TO DO SO WILL RESULT IN RANDOM DATA LOSS, AND WE HERE AT IBM REALLY DON'T CARE ENOUGH TO GIVE YOU A WORKING MODEL IF YOU COMPLAIN."
I, the story poster (even though the name is different), did not have an overclocked machine. The failures I described ran across an ABIT KT7-RAID and an EPoX 8KTA3+. Different controllers, different boards...
I am well aware of that hole and did not cover it. I did, however, point at it and laugh. It was rather tempting to cover it and see what happened. Who knows, maybe it would make the drive magically work?
RMA directly with IBM after the failure. The drives have internal error logs. Get IBM's Disk Fitness Test software over at http://www.storage.ibm.com/ and it'll give you a TRC code that you can use to RMA with. Do it after you hear the clicking noise.
In my experience, erasing the disk doesn't fix the problem. Once you start writing back to the disk, it will return. Erasing the disk just wastes time and seems to also wipe the drive's internal error log.
You describe my exact problem. It is one location on the disk. But I RMA'd twice, and each time Big Blue gave me back another broken 75GXP. You got lucky.
I, being the person who submitted the story, receive the same message in FreeBSD every time I hear the satanic grindings of FreeBSD. It is related to a physical disk location, it seems. It is always the same location in the error messages.
Because United States citizens don't pay their taxes for hte government to produce proprietary licended code. It should be able to be used by all citizens in all circumstances. We all pay for it, businesses, citizens, and even Microsoft. there is no reason we all shouldn't be able to use what we pay for under a public domain license.
Nothing against the GPL, but I find it disgraceful that the United States government is producing code under the GPL. Works produced by the government should be public domain, not GPL. And yes, there is a difference.
Or you could use a non-MSN nameserver, such as running your own. Why depend on the beast when you can do it yourself or find somebody who you trust more to do it?
Slashdot Mirror
The "cookie" sent to Microsoft when requesting the DVD chapters is not reliably linkable back to the client user. As Microsoft has already said, you can clear cookies to remove it. You can also Work Offline to not even make the request in the first place. Did you even read Microsoft's response?
The bulletin I saw on bugtraq said nothing about tracking songs. On top of that, Microsoft disputes the bulletin and issues in it, but the author is blantently ignoring their direct responses to all of his points. this is an extreme exaggeration that seems to be driven by the "fear big old Microosft" camp. It is a feature, not spyware.
I do, because I have a relative that worked for them. I, too, wish they were still in business.
Take them to the closest IBM office building to you. Take each drive, assign it a window, and throw really hard. Make sure you attach a printout of this Slashdot story and all the comments. Hilight your comment in red.
All my MP3s and co. are on a 20GB Maxtor 92041U4. The drive is several years old, and has never choked. It is in the same machine as these damned IBM things that keep suiciding.
I'm glad it works for you and all, but I must say that is just retarded. If their product is that flaky or sensitive, they should send a piece of paper with each one that says "THIS PRODUCT IS SO SENSITIVE THAT YOU CAN'T SCREW IT IN AND MUST KEEP 300MPH WINDS BLOWING ABOVE AND BELOW IT AT ALL TIMES. FAILURE TO DO SO WILL RESULT IN RANDOM DATA LOSS, AND WE HERE AT IBM REALLY DON'T CARE ENOUGH TO GIVE YOU A WORKING MODEL IF YOU COMPLAIN."
I, the story poster (even though the name is different), did not have an overclocked machine. The failures I described ran across an ABIT KT7-RAID and an EPoX 8KTA3+. Different controllers, different boards...
I am well aware of that hole and did not cover it. I did, however, point at it and laugh. It was rather tempting to cover it and see what happened. Who knows, maybe it would make the drive magically work?
I know I shouldn't be baiting a troll, but I don't use Linux. I, the one you are trolling, use FreeBSD.
RMA directly with IBM after the failure. The drives have internal error logs. Get IBM's Disk Fitness Test software over at http://www.storage.ibm.com/ and it'll give you a TRC code that you can use to RMA with. Do it after you hear the clicking noise.
7 out of 6 most likely means that he's had RMA replacement drives die.
In my experience, erasing the disk doesn't fix the problem. Once you start writing back to the disk, it will return. Erasing the disk just wastes time and seems to also wipe the drive's internal error log.
Yes. All of mine came from Hungary. Not sure about the original, but the two RMAs did come from Hungary.
You describe my exact problem. It is one location on the disk. But I RMA'd twice, and each time Big Blue gave me back another broken 75GXP. You got lucky.
I, being the person who submitted the story, receive the same message in FreeBSD every time I hear the satanic grindings of FreeBSD. It is related to a physical disk location, it seems. It is always the same location in the error messages.
The GPL != Public Domain, so I'd say "Proprietary". GNU's Proprietary License.
Because United States citizens don't pay their taxes for hte government to produce proprietary licended code. It should be able to be used by all citizens in all circumstances. We all pay for it, businesses, citizens, and even Microsoft. there is no reason we all shouldn't be able to use what we pay for under a public domain license.
If they don't have a choice, they shouldn't be doing it. Period.
Nothing against the GPL, but I find it disgraceful that the United States government is producing code under the GPL. Works produced by the government should be public domain, not GPL. And yes, there is a difference.
I'll be waiting for an X-Plane junkie to get their hands on the data and make a terrain set out of it.
*waits for the moderators to notice the word FreeBSD and start sucking away the karma*
Or you could use a non-MSN nameserver, such as running your own. Why depend on the beast when you can do it yourself or find somebody who you trust more to do it?
Because the majority of people are computer illiterate and do not distinguish the difference between "computer" and "Microsoft Windows".
What's your address again?
...maybe the seismic activity just makes the monster, or whatever it is, surface.