Intel is initiating a B-2 to L-2 stepping conversion for Intel Core 2 Duo processors E6300 & E6400 (Conroe) and Dual-Core Intel Xeon processors 3040 & 3050 (UP Xeon processors based on Conroe) where they will undergo the following changes:

▪ New S-Spec and MM numbers for the converting products
▪ CPUID will change from 6F6 to 6F2
▪ Extended HALT power specification will reduce from 22 Watts to 12 Watts
▪ Die size optimized for manufacturability
▪ Minor visible difference between the B-2 and L-2 packages
▪ L-2 package is pin compatible with B-2 package

Soljacic realized that the close-range induction taking place inside a transformer--or something similar to it--could potentially transfer energy over longer distances, say, from one end of a room to the other. Instead of irradiating the environment with electromagnetic waves, a power transmitter would fill the space around it with a "non-radiative" electromagnetic field. Energy would only be picked up by gadgets specially designed to "resonate" with the field. Most of the energy not picked up by a receiver would be reabsorbed by the emitter.

Hard|OCP has published an article that discusses nVIDIA's nForce 680i chipset. While this chipset is known to most as the best clocking Intel chipset on the market, some have grown to hate it because of frequent BSODs and errors.

Quadfather compared to Kentsfield

While it has been discussed on the forums a lot already there were no official comparisons between AMDs Quadfather and Intels Kentsfield. So PC watch did exactly that, they compared a 3 GHz Quadfather to a 2.66GHz QX6700. The first major issue found was that the AMD system used up to 80% more energy, not exactly something to ignore. Even though the AMD system didn't score bad, it only won a single benchmark and performed worse or the same at best in every other benchmark.
It seems AMD let their fans down for now. Lets hope they make up to them with their 65nm CPUs. For now, take a look at the results:

Adobe warnt vor einer Schwachstelle in seiner PDF-Lese-Software. Angreifer können über sie bösartigen Code ausführen

Laut Adobe betrifft die Anfälligkeit die Reader-Versionen 7.0.0 bis 7.0.8 [1]. Gleiches gilt für die Acrobat-Ausgaben mit denselben Versionsnummern. Beim neuen Acrobat 8 ist die Lücke hingegen nicht vorhanden. Adobe arbeitet nach eigenen Angaben an einem Patch. Bis dieser erscheint, können sich Anwender mit einem Workaround schützen. Dazu müssen Sie im Ordner «ActiveX» im Pfad «C:\Programme\Adobe\Acrobat 7.0» die Datei «AcroPDF.dll» löschen. Der Nachteil: PDF-Dokumente lassen sich nicht mehr direkt im Internet Explorer öffnen.