Some key points from the report (keep in mind this is specifically for the E6500 with the NVIDIA graphics option, but much of this likely applies to the E6400 and/or the Intel integrated graphics option):
1. The problem is NOT an overheating problem - the system simply does not overheat. It is due to premature and overly aggressive attempts at thermal control, invoked at what are NORMAL processor operating temperatures (65-80 Celsius), possibly due to faulty ACPI "passive cooling" parameter definitions and/or control methods. 2. The problem is substantially more pronounced when the system is docked. 3. The problem is aggravated somewhat by the use of dual monitors when docked as opposed to a single monitor. 4. Since the problem is all about temperature, the higher the surrounding ambient temperature in the room, the sooner and the greater the performance loss. 5. The symptoms are much more highly correlated to elevated NVIDIA GPU temperature than elevated CPU core temperatures.
Some miscellaneous corollaries:
1. Any blockage of air inlets or outlets (including, of course, dust) will aggravate the problem. 2. The reason people report shockingly high percent CPU utilization statistics when their system slows down is that the overall capacity of their processor is degraded by the throttling mechanisms. The same processes running on a CPU that is subsequently throttled necessarily will demand a higher percentage of the processor's remaining capacity. 3. The reason some folks report persistent slowness even after installing software to prevent CPU downclocking is that more than one throttling mechanism is in play here. In particular, Software-controlled Clock Modulation (also called On-Demand Clock Modulation) occurs in an almost completely invisible manner, as opposed to performance state changes (which are usually monitored by common utilities). Another often-invisible throttling mechanism is Dynamic FSB Frequency Switching (where the FSB frequency is slashed in half), though if you prevent performance state changes, that takes care of preventing this too (since it's part of state P3). 4. The reason there aren't more complaints (though many are accumulating these days) is that users who experience this problem simply have no way of knowing what the cause is and are likely to blame the wrong thing (Windows, recently installed software, cooling hardware, etc.). Untold masses may be adversely affected by this problem, but nearly all of them wouldn't know it because there's no way for them to tell. Also, the problem is at its worst only when in a docked configuration, which may not be common. 5. The reason complaints are escalating now more than before is that this is the first summer that people have had this system (in the Northern Hemisphere, anyway). I think it's safe to say that ambient temperatures are higher for most E6400/E6500 users now. 6. The problem can be substantially mitigated by pointing an external fan at the system. 7. The problem can also be mitigated by software, such as RMClock, that can override the throttling mechanisms in question, at the expense of negating all passive thermal management (though critical temperature shutdown mechanisms may remain in place).
You are correct in saying the force would be the same. However, due to the difference in densities, equal forces result in different accelerations. Force= mass * acceleration , thus acceleration = Force/mass. If you have 1/2 the mass, you will have twice the acceleration. This acceleration is negative, i.e against gravity. This goes back to what everphilski was saying. The foam slows down more, i.e the delta velocity between the shuttle and the foam > delta velocity between the shuttle and the ice. This is where the kinetic energy comes into play.
If you RTFA, the author was saying that these unmarked and untested DRAM chips can later be marked as if they came from a Tier 1 manufacturer. These chips can then be sold for a premium, yet still less than the Tier 1 price. In that case unmarked and untested = pirated.
Actually, it wouldnt be that much in your back yard. 10,000 barrels of oil @ 55 gallons per barrel = 550,000
If you had a one acre back yard, that would be 27,000 gallons per inch. That would givce you a total of about 21 inches of oil in your backyard, every day. Considering that is the amount saved nationwide, it feels like a drop in the bucket.
Behold: Walk the Plank and Operation Dust Bunny Note: Due to responses by certain detractors, we've updated our legal section (again) to further clarify our stance.
Apparently, this is becoming more and more newsworthy. Security Focus called today and interviewed me. Here is the resulting article: http://securityfocus.com/news/8279
At the start of this year, we (Justin and Clif, Clif and Justin) decided to start a new project. We declared war on illegal file sharing and pirates. The goal was to waste their time and bandwidth while tracking them and how the file moves around.
Results Pages for the Impatient: Walk the Plank Status Page | Dust Bunny Status Page
Walk the Plank, You Pirates!
The first version of this was more-or-less a test to see if it would work. We created a program in C# that would pop-up a message scolding the user. When the program closes, it would "phone home" to our servers, giving us the filename, how long the program ran (run time), and their IP address. We entered the information we collected into a database.
We copied the binary then renamed it to a bunch of warez-like filenames that we found via Jigle.com and searching different P2P networks. We put it up on the Gnutella file sharing network and waited. Within minutes, we had downloads. However, we didn't have entries in the database. The next day we came to the conclusion that people didn't have.NET installed and thus couldn't run the C# binary.
So we rewrote it in C++. Once finished, we replaced all of the C# binaries with the C++ binary. Again within moments, we had downloads and this time we have entries in the database. Goes to show the penetration of.NET.
After about two weeks, we noticed something: The file was spreading without our help. We stopped sharing after we realized this and the file kept propagating, and propagating, and propagating. In no time flat, we wasted over 16 hours of pirate time.
Screenshot: (Top: WTP, Bottom, ODB)
The Next Step: Operation Dust Bunny
The original idea we had went beyond simply logging filename and run time. We wanted to track who got what file from who. So a month after WTP, we wrote Dust Bunny. It was a two-binary system that would read the Pirate ID (PID) encoded in itself, send it to a server, then grab a unique PID returned from the server, and rewrite the ID that is encoded in the binary. Using this information, we could see who got what binary from who.
Written with one person using Visual Studio 2003, another using Dev-C++; one binary in C++, the other in C; and only one person knowing how to code in either language. It was a challenge since the "rabbit" (the GUI program) had to include the "eye" (the program that contacted the server and rewrote the rabbit) for execution. Plus the eye needed an offset that could only be gathered once the rabbit was compiled with eye included. Thanks to TightVNC and a lot of trading of information, we got through it.
Just to be safe, we added a "kill switch" to the eye. If the server returned a special ID number, the eye would delete the rabbit. This way, in case it got out of control as WTP did, we could stop it. Also, if someone renamed it to a filename we didn't like, we could add that filename to the "evil filename list" on the server.
After it was completed, we replaced all the binaries with the new version. Once again, they started to be downloaded instantly. The next day, we already had redistributions -- someone downloaded a copy from someone other then us. We could tell since we were logging the PIDs. It didn't take long until we had multi-branch trees of pirates.
We decided after one month time of sharing Dust Bunny, we'd stop and let it propagate on it's own. That marker was around March 9th, 2004.
Current Status
By now, WTP has racked up over 62 hours in wasted pirate time. Dust Bunny is well on its way with 20 hours. Dust Bunny has around 3,500 unique pirates and over 6,200 ex
Here are the instructions:
This SWIPE tool allows you to crack a 2D barcode. Ever noticed the barcode on the backside of your license? Ever wondered what information it stores or why it is even there? Use our online application or the stand-alone program and put an end to the mystery! It is your data, so shouldn't you have a look? Learn more about the 2D barcode and your driver's license.
WHAT YOU NEED TO BEGIN
1. Check to see if your driver's license has a 2D barcode. Currently 39 states use the 2D barcode to encode personal information on the backside of drivers' licenses. Look for a band of black and white squares in a random pattern.
This thing here is a 2D barcode.
2. Make a digital image of your driver's license barcode. You can either use a scanner or a digital camera to create this image. The image you create must be a color GIF file or a very high quality JPEG without compression artifacts. The image file size should be roughly 500k to 1.5MB and can not be larger than 2MB. The license image should be 1000-1500 pixels wide and make sure it is rightside up. For good results, this image must be in sharp focus with high contrast.
Based on recent use, our Toolkit participants are getting better results with scanned images than images taken with a digital camera. If you use a digital camera, be sure to point the camera directly at the barcode and the license is level in respect to the lens.
3. Decide if you want to use the online application or stand-alone program to decode your barcode. We have made two versions of our barcode decoder: an online version and a stand-alone program. They both will return the same results; the only difference is the stand-alone program allows you to decode locally on your hard drive. The online version is a little bit easier to use, but you will have to upload your barcode image to our server.
Note: We are not archiving any image files for future use. We will, however, keep track of the different kinds of information each state encodes on its drivers' licenses. This research will be made available to our SWIPE Toolkit visitors. No specific data or identifying information will ever be stored on our server.
Now it is time to decode! Please contact us if you have any problems or questions.
Thank you SO much for this tip. I've been having many problems with my Deskjet 970. I just cleaned that ribbon and there was an AMAZING amount of ink on it. Now it runs like new!
I live in Emmaus, PA and our local power company, PPL (Pennsylvania Power and Light) has been testing broadband over powerline here for a few months. My friend has it and he finds it very convenient. He gets 1.5mb 2-way for about 30 bucks a month. Of course this is just a pilot program. I just can't wait till I can get in on the action. (According to him, PPL called random people in the Emmaus area to try out the system.) This is wonderful because here in Emmaus, there is no DSL or 2-way cable modems because of the monopoly the cable company(service Electric) has over everything.
The only link I could find on PPL's pilot program was here
Quoted below:
PPL, PA
Al Richenbacher, Manager of PPL's Market Development Group, reported on PPL's test of PLC in Emmaus, PA, working with Main.net. They chose Main.net due to their extensive track record of trials in Europe, and the ability of Main.net to pass their PLC signal through the transformer. I confirmed this during Q and A--Main.net can pass their signal through a transformer rather than couple around it.
If the trial goes well, PPL would look to go to commercial deployment in 2003.
PPL is also considering partnering with Amperion, to provide MV backhaul. This would primarily be to service business customers with bandwidths of T1 and below.
PPL is currently in the middle of developing their own back office (billing, provisioning, etc), to service their PLC offerings.
Al would not reveal their total cost per customer on the trials, but stated that it appeared to be favorable when compared to DSL and cable.
Initial penetration is expected to be less than 10%. But, with a smart build strategy Al stated that this would be enough to pass break even.
PPL has an internal group that works with the state regulatory commission. Conversations so far have only been preliminary but the reaction from the commission has been positive and encouraging.
Flourinert is a whole bunch of fun. You can actually buy it for about 200 bucks a gallon. A few people have tried overclocking their computers by immersing their computers in the stuff. Check it out here and here
ITworld has more info on the laptop. To answer those who say this laptop will spring a leak:
"The solution can last for more than five years, the flexible tube can circulate the solution over 20,000 times and the pump works for more than 44,000 hours, the statement said."
And even if it does spring a leak:
"Plastic panels separate these water-cooling elements from high-voltage areas, in case of a solution leak from the cooling system. The Tokyo company also offers a three-year guarantee service for the product."
Laser pointer holography was originaly developed by Frank DeFreitas. His web site http://www.holoworld.com/holo/diode.html has many pictures of his work. Quite a marvel. You should buy his book. It is very informative. It's about 17 bucks from Amazon.com Its very helpful and takes you step by step in the process and a bit into the history of holograms etc. I'be had great success with his process. It's a bit harder to find his holographic plates, and this isn't exactly the cheapest thing in the world. The plates cost me US$60 for five or six! But the results are great. You CAN'T use this for any kind of forgery because the holograms are on a glass substrate. I suppose it is possible to put it on plastic somehow. But beats me on how to do it.
Performance is only meaningfully increased if using RAID 0. Sure, with RAID 5 you get some increase, but the processing power to determine the parity can slow you down if you dont have a dedicated card to do so.
Slashdot Mirror
Here's a post on Dell's forums describing the issue
From the link:
Some key points from the report (keep in mind this is specifically for the E6500 with the NVIDIA graphics option, but much of this likely applies to the E6400 and/or the Intel integrated graphics option):
1. The problem is NOT an overheating problem - the system simply does not overheat. It is due to premature and overly aggressive attempts at thermal control, invoked at what are NORMAL processor operating temperatures (65-80 Celsius), possibly due to faulty ACPI "passive cooling" parameter definitions and/or control methods.
2. The problem is substantially more pronounced when the system is docked.
3. The problem is aggravated somewhat by the use of dual monitors when docked as opposed to a single monitor.
4. Since the problem is all about temperature, the higher the surrounding ambient temperature in the room, the sooner and the greater the performance loss.
5. The symptoms are much more highly correlated to elevated NVIDIA GPU temperature than elevated CPU core temperatures.
Some miscellaneous corollaries:
1. Any blockage of air inlets or outlets (including, of course, dust) will aggravate the problem.
2. The reason people report shockingly high percent CPU utilization statistics when their system slows down is that the overall capacity of their processor is degraded by the throttling mechanisms. The same processes running on a CPU that is subsequently throttled necessarily will demand a higher percentage of the processor's remaining capacity.
3. The reason some folks report persistent slowness even after installing software to prevent CPU downclocking is that more than one throttling mechanism is in play here. In particular, Software-controlled Clock Modulation (also called On-Demand Clock Modulation) occurs in an almost completely invisible manner, as opposed to performance state changes (which are usually monitored by common utilities). Another often-invisible throttling mechanism is Dynamic FSB Frequency Switching (where the FSB frequency is slashed in half), though if you prevent performance state changes, that takes care of preventing this too (since it's part of state P3).
4. The reason there aren't more complaints (though many are accumulating these days) is that users who experience this problem simply have no way of knowing what the cause is and are likely to blame the wrong thing (Windows, recently installed software, cooling hardware, etc.). Untold masses may be adversely affected by this problem, but nearly all of them wouldn't know it because there's no way for them to tell. Also, the problem is at its worst only when in a docked configuration, which may not be common.
5. The reason complaints are escalating now more than before is that this is the first summer that people have had this system (in the Northern Hemisphere, anyway). I think it's safe to say that ambient temperatures are higher for most E6400/E6500 users now.
6. The problem can be substantially mitigated by pointing an external fan at the system.
7. The problem can also be mitigated by software, such as RMClock, that can override the throttling mechanisms in question, at the expense of negating all passive thermal management (though critical temperature shutdown mechanisms may remain in place).
I think that this video says it all then... http://www.youtube.com/watch?v=B-m6JDYRFvk
According to Brad Fitzpatrick's(of LiveJounral fame) blog, He's working on Perl support.
You are correct in saying the force would be the same. However, due to the difference in densities, equal forces result in different accelerations. Force= mass * acceleration , thus acceleration = Force/mass. If you have 1/2 the mass, you will have twice the acceleration. This acceleration is negative, i.e against gravity. This goes back to what everphilski was saying. The foam slows down more, i.e the delta velocity between the shuttle and the foam > delta velocity between the shuttle and the ice. This is where the kinetic energy comes into play.
Part 2 Continued here:
h t_be_giants_1.php/
http://www.gearlog.com/2007/08/interview_they_mig
There are some better pictures at engaget:
r izr-z8-a-symbian-kick-slider-with-hsdpa
http://www.engadget.com/2007/02/12/motorolas-moto
Looks like someone found one on Comm ave in Boston and put it up on ebay
r tising-Bomb_W0QQitemZ130075321405QQihZ003QQcategor yZ363QQssPageNameZWDVWQQrdZ1QQcmdZViewItem
http://cgi.ebay.com/Mooninites-Ignignokt-LED-Adve
If you RTFA, the author was saying that these unmarked and untested DRAM chips can later be marked as if they came from a Tier 1 manufacturer. These chips can then be sold for a premium, yet still less than the Tier 1 price. In that case unmarked and untested = pirated.
If you had a one acre back yard, that would be 27,000 gallons per inch. That would givce you a total of about 21 inches of oil in your backyard, every day. Considering that is the amount saved nationwide, it feels like a drop in the bucket.
If you want to play hl2 without going through steam, make a shortcut to "c:\(install path)\hl2.exe" -steam
This allows you to run hl2 without going through steam at all.
Behold: Walk the Plank and Operation Dust Bunny
.NET installed and thus couldn't run the C# binary.
.NET.
Note: Due to responses by certain detractors, we've updated our legal section (again) to further clarify our stance.
Apparently, this is becoming more and more newsworthy. Security Focus called today and interviewed me. Here is the resulting article: http://securityfocus.com/news/8279
At the start of this year, we (Justin and Clif, Clif and Justin) decided to start a new project. We declared war on illegal file sharing and pirates. The goal was to waste their time and bandwidth while tracking them and how the file moves around.
Results Pages for the Impatient: Walk the Plank Status Page | Dust Bunny Status Page
Walk the Plank, You Pirates!
The first version of this was more-or-less a test to see if it would work. We created a program in C# that would pop-up a message scolding the user. When the program closes, it would "phone home" to our servers, giving us the filename, how long the program ran (run time), and their IP address. We entered the information we collected into a database.
We copied the binary then renamed it to a bunch of warez-like filenames that we found via Jigle.com and searching different P2P networks. We put it up on the Gnutella file sharing network and waited. Within minutes, we had downloads. However, we didn't have entries in the database. The next day we came to the conclusion that people didn't have
So we rewrote it in C++. Once finished, we replaced all of the C# binaries with the C++ binary. Again within moments, we had downloads and this time we have entries in the database. Goes to show the penetration of
After about two weeks, we noticed something: The file was spreading without our help. We stopped sharing after we realized this and the file kept propagating, and propagating, and propagating. In no time flat, we wasted over 16 hours of pirate time.
Screenshot: (Top: WTP, Bottom, ODB)
The Next Step: Operation Dust Bunny
The original idea we had went beyond simply logging filename and run time. We wanted to track who got what file from who. So a month after WTP, we wrote Dust Bunny. It was a two-binary system that would read the Pirate ID (PID) encoded in itself, send it to a server, then grab a unique PID returned from the server, and rewrite the ID that is encoded in the binary. Using this information, we could see who got what binary from who.
Written with one person using Visual Studio 2003, another using Dev-C++; one binary in C++, the other in C; and only one person knowing how to code in either language. It was a challenge since the "rabbit" (the GUI program) had to include the "eye" (the program that contacted the server and rewrote the rabbit) for execution. Plus the eye needed an offset that could only be gathered once the rabbit was compiled with eye included. Thanks to TightVNC and a lot of trading of information, we got through it.
Just to be safe, we added a "kill switch" to the eye. If the server returned a special ID number, the eye would delete the rabbit. This way, in case it got out of control as WTP did, we could stop it. Also, if someone renamed it to a filename we didn't like, we could add that filename to the "evil filename list" on the server.
After it was completed, we replaced all the binaries with the new version. Once again, they started to be downloaded instantly. The next day, we already had redistributions -- someone downloaded a copy from someone other then us. We could tell since we were logging the PIDs. It didn't take long until we had multi-branch trees of pirates.
We decided after one month time of sharing Dust Bunny, we'd stop and let it propagate on it's own. That marker was around March 9th, 2004.
Current Status
By now, WTP has racked up over 62 hours in wasted pirate time. Dust Bunny is well on its way with 20 hours. Dust Bunny has around 3,500 unique pirates and over 6,200 ex
Here are the instructions: This SWIPE tool allows you to crack a 2D barcode. Ever noticed the barcode on the backside of your license? Ever wondered what information it stores or why it is even there? Use our online application or the stand-alone program and put an end to the mystery! It is your data, so shouldn't you have a look? Learn more about the 2D barcode and your driver's license.
WHAT YOU NEED TO BEGIN
1. Check to see if your driver's license has a 2D barcode. Currently 39 states use the 2D barcode to encode personal information on the backside of drivers' licenses. Look for a band of black and white squares in a random pattern.
This thing here is a 2D barcode.
2. Make a digital image of your driver's license barcode. You can either use a scanner or a digital camera to create this image. The image you create must be a color GIF file or a very high quality JPEG without compression artifacts. The image file size should be roughly 500k to 1.5MB and can not be larger than 2MB. The license image should be 1000-1500 pixels wide and make sure it is rightside up. For good results, this image must be in sharp focus with high contrast.
Based on recent use, our Toolkit participants are getting better results with scanned images than images taken with a digital camera. If you use a digital camera, be sure to point the camera directly at the barcode and the license is level in respect to the lens.
3. Decide if you want to use the online application or stand-alone program to decode your barcode. We have made two versions of our barcode decoder: an online version and a stand-alone program. They both will return the same results; the only difference is the stand-alone program allows you to decode locally on your hard drive. The online version is a little bit easier to use, but you will have to upload your barcode image to our server.
Note: We are not archiving any image files for future use. We will, however, keep track of the different kinds of information each state encodes on its drivers' licenses. This research will be made available to our SWIPE Toolkit visitors. No specific data or identifying information will ever be stored on our server.
Now it is time to decode! Please contact us if you have any problems or questions.
Thank you SO much for this tip. I've been having many problems with my Deskjet 970. I just cleaned that ribbon and there was an AMAZING amount of ink on it. Now it runs like new!
The only link I could find on PPL's pilot program was here
Quoted below:
PPL, PA
Al Richenbacher, Manager of PPL's Market Development Group, reported on
PPL's test of PLC in Emmaus, PA, working with Main.net. They chose
Main.net due to their extensive track record of trials in Europe, and the
ability of Main.net to pass their PLC signal through the transformer. I
confirmed this during Q and A--Main.net can pass their signal through a
transformer rather than couple around it.
If the trial goes well, PPL would look to go to commercial deployment in
2003.
PPL is also considering partnering with Amperion, to provide MV backhaul.
This would primarily be to service business customers with bandwidths of
T1 and below.
PPL is currently in the middle of developing their own back office
(billing, provisioning, etc), to service their PLC offerings.
Al would not reveal their total cost per customer on the trials, but
stated that it appeared to be favorable when compared to DSL and cable.
Initial penetration is expected to be less than 10%. But, with a smart
build strategy Al stated that this would be enough to pass break even.
PPL has an internal group that works with the state regulatory commission.
Conversations so far have only been preliminary but the reaction from the
commission has been positive and encouraging.
Here's the article: http://www.nwfusion.com/news/2002/1125bethisrael.h tml
Flourinert is a whole bunch of fun. You can actually buy it for about 200 bucks a gallon. A few people have tried overclocking their computers by immersing their computers in the stuff. Check it out here and here
Sorry about that.. It didnt take my post as HTML Here's the link to the mirror of the pictures: www.waikontt.com/shuttle.asp
View my mirror of the pictures here
"The solution can last for more than five years, the flexible tube can circulate the solution over 20,000 times and the pump works for more than 44,000 hours, the statement said."
And even if it does spring a leak:
"Plastic panels separate these water-cooling elements from high-voltage areas, in case of a solution leak from the cooling system. The Tokyo company also offers a three-year guarantee service for the product."
Sounds good to me!
Here is more information on this laptop. It's in japanese, but the pictures speak a thousand words.
Laser pointer holography was originaly developed by Frank DeFreitas. His web site http://www.holoworld.com/holo/diode.html has many pictures of his work. Quite a marvel. You should buy his book. It is very informative. It's about 17 bucks from Amazon.com Its very helpful and takes you step by step in the process and a bit into the history of holograms etc. I'be had great success with his process. It's a bit harder to find his holographic plates, and this isn't exactly the cheapest thing in the world. The plates cost me US$60 for five or six! But the results are great. You CAN'T use this for any kind of forgery because the holograms are on a glass substrate. I suppose it is possible to put it on plastic somehow. But beats me on how to do it.
W-S
www.lehigh.edu/~wsc2/terror.htm
oopsy my bad. I'm sorry my mistake. It's friday. Gimmi a break
Performance is only meaningfully increased if using RAID 0. Sure, with RAID 5 you get some increase, but the processing power to determine the parity can slow you down if you dont have a dedicated card to do so.
That uses a hard drive.