Marvell SATA Controller

I have a D975XBX2 Intel MB. It has a Marvell 88SE61xx Controller. This is a criminal chipset and is the worst SATA controller ever made with the worst drivers and if I was Pinochet for a day, I would throw the CEO of this company out of a C-130 at 20,000ft for all the hard drives and data loss this chipset causes.

This chipset is criminal.

Why dont Asus, Intel, etc, why dont they just solder 3ware or LSI or any decent non-FAKE-RAID (FRAID) chips on these motherboards? Why would a program manager ever choose an asic that has fake raid, is crap, has crap drivers and sucks?

Conroe vs. Netburst

Conroe vs. Netburst

In response to:

http://badhardware.blogspot.com/2006/03/conroe-roadmap-and-prices.html

Wrong. Why Netburst CPUs are way worse than Conroe:

1) The Conroe has an extra execution unit (4 instead of 3)

2) The pipeline 1/3 the size Netburst CPUs (12/14 stage pipeline vs 30+ of Netburst)

3) The FPU is significantly improved (SSE4, etc)

4) The heat dissipation is lower per unit of work done and lower overall.

5) The caching algorithms used by the Conroe CPUs are drastically improved.

The main bottle neck these days is DRAM refresh cycles and how slow mass storage is, but if you are waiting for things to render or things to encode, the Conroe will be drastically faster.

Check out:

http://www.spec.org/cpu2000/results/

http://www.spec.org/cpu2006/results/

You will see Netburst CPUs doing horrible, AMD single core doing well, AMD dual core doing ok, and Intel Woodcrest and Conroe absolutely killing the competition.

The 4MB cache Conroe CPUs are the ultimate CPU ever to be offered to the public at such a low price point.

I think that buying the E6600 4MB will provide a huge improvement over that piece of junk, hot Netburst.

Intel is throwing out the junk silicon dooming you to a Netburst CPU. Why in god's name would you want to get a new rig with an obsolete piece of junk?

Corel users: Get an E6600 a large fast hard drive like a WD5000YS, and reasonably fast memory.

Post benchmarks if you are going to make performance claims.


------------------

Conroe roadmap and prices
Intel Conroe Prices Core Duo E8000 4MB 3.33GHz 1333MHz Q4 $1199Core Duo EEdition 3.33GHz(L2 4M) 1333MHz Q3 $999Core Duo E6900 4MB 3.20GHz 1066MHz FSB Q4 $969Intel Core Duo E6800 2.93GHz(L2 4M) 1066MHz Q3 $749Intel Core Duo E6700 2.67GHz(L2 4M) 1066MHz Q3 $529Intel Core Duo E6600 2.40GHz(L2 4M) 1066MHz Q3 $315Core Duo E6500 2MB 2.40GHz 1066MHz FSB Q4 $269Intel Core Duo E6400 2.13GHz(L2 2M) 1066MHz Q3 $240Intel Core Duo E6300 2MB 1.86GHz 1066MHz FSB Q3 $209Core Duo E6200 2MB 1.60GHz 1066MHz FSB Q4 $179Core Duo E4200 2MB 1.60GHz 800MHz FSB Q4 $169Intel Celeron D 350, 3.2 GHz ( L2 256K) 533 Mhz NOW $99Now, let compare Core Duo E6900 and Celeron D350.E6900 is better: 2X due to 2 coresE6900 has 2 times higher FSB clock, but can dual cores communicate with memory simulatenously?E6900 has 2 MB L2 per core, thus it is 8 times bigger than at Celeron D 350But E6900 has price 10 times bigger !?Conclusion for Corel user: You will pay 10 times more for the 2 times faster Corel execution.Conclusion for both cores user: When one nice day, when Intel masters Hyper Transport, you will have 4 times more performance for 10 times higher prices. Well, let be correct, when Intel finally make it, E6900 price should be some $500 (Intel will not voluntarily lower its prices) and you will get 4 times more performance for 4 times more money, if you are black mailed with Intel. Otherwise, why to wait, when I can make higher performance boost per $ with purchase of any AMD64? Yes, but E6900 is Intel's next generation processor. Well, after the facts above, it seems me more like Intel's next generation fraud.

------------

Bad Hardware Week is not technically inclined and should not be listened to.

Batch file for clearing all the logs at once in Vista.

Vista has quite a large number of log files. Sometimes its nice for troubleshooting to wipe out all the logs and create a problem to see that problems manifestations in the logs. The following in a batch file will do this.

wevtutil cl "Application"
wevtutil cl "DFS Replication"
wevtutil cl "HardwareEvents"
wevtutil cl "Internet Explorer"
wevtutil cl "Key Management Service"
wevtutil cl "Security"
wevtutil cl "System"
wevtutil cl "EndpointMapper"
wevtutil cl "ForwardedEvents"
wevtutil cl "Microsoft-Windows-ADSI/Debug"
wevtutil cl "Microsoft-Windows-AltTab/Diagnostic"
wevtutil cl "Microsoft-Windows-Backup"
wevtutil cl "Microsoft-Windows-Bits-Client/Analytic"
wevtutil cl "Microsoft-Windows-Bits-Client/Operational"
wevtutil cl "Microsoft-Windows-CAPI2/Operational"
wevtutil cl "Microsoft-Windows-CertificateServicesClient-CredentialRoaming/Operational"
wevtutil cl "Microsoft-Windows-CodeIntegrity/Operational"
wevtutil cl "Microsoft-Windows-CodeIntegrity/Verbose"
wevtutil cl "Microsoft-Windows-COM/Analytic"
wevtutil cl "Microsoft-Windows-CorruptedFileRecovery-Client/Operational"
wevtutil cl "Microsoft-Windows-CorruptedFileRecovery-Server/Operational"
wevtutil cl "Microsoft-Windows-CredUI/Diagnostic"
wevtutil cl "Microsoft-Windows-DateTimeControlPanel/Analytic"
wevtutil cl "Microsoft-Windows-DateTimeControlPanel/Debug"
wevtutil cl "Microsoft-Windows-DateTimeControlPanel/Operational"
wevtutil cl "Microsoft-Windows-DCLocator/Debug"
wevtutil cl "Microsoft-Windows-Diagnosis-DPS/Analytic"
wevtutil cl "Microsoft-Windows-Diagnosis-DPS/Debug"
wevtutil cl "Microsoft-Windows-Diagnosis-DPS/Operational"
wevtutil cl "Microsoft-Windows-Diagnosis-MSDT/Debug"
wevtutil cl "Microsoft-Windows-Diagnosis-MSDT/Operational"
wevtutil cl "Microsoft-Windows-Diagnosis-PLA/Debug"
wevtutil cl "Microsoft-Windows-Diagnosis-PLA/Operational"
wevtutil cl "Microsoft-Windows-Diagnosis-WDI/Debug"
wevtutil cl "Microsoft-Windows-Diagnostics-Networking/Debug"
wevtutil cl "Microsoft-Windows-Diagnostics-Networking/Operational"
wevtutil cl "Microsoft-Windows-Diagnostics-Performance/Diagnostic"
wevtutil cl "Microsoft-Windows-Diagnostics-Performance/Diagnostic/Loopback"
wevtutil cl "Microsoft-Windows-Diagnostics-Performance/Operational"
wevtutil cl "Microsoft-Windows-DiskDiagnostic/Operational"
wevtutil cl "Microsoft-Windows-DiskDiagnosticDataCollector/Operational"
wevtutil cl "Microsoft-Windows-DiskDiagnosticResolver/Operational"
wevtutil cl "Microsoft-Windows-DriverFrameworks-UserMode/Operational"
wevtutil cl "Microsoft-Windows-DxgKrnl/Diagnostic"
wevtutil cl "Microsoft-Windows-EFS/Debug"
wevtutil cl "Microsoft-Windows-EventCollector/Debug"
wevtutil cl "Microsoft-Windows-EventCollector/Operational"
wevtutil cl "Microsoft-Windows-Eventlog-ForwardPlugin/Debug"
wevtutil cl "Microsoft-Windows-EventLog-WMIProvider/Debug"
wevtutil cl "Microsoft-Windows-EventLog/Analytic"
wevtutil cl "Microsoft-Windows-EventLog/Debug"
wevtutil cl "Microsoft-Windows-FileInfoMinifilter/Operational"
wevtutil cl "Microsoft-Windows-Firewall-CPL/Diagnostic"
wevtutil cl "Microsoft-Windows-Forwarding/Operational"
wevtutil cl "Microsoft-Windows-FunctionDiscoveryHost/Tracing"
wevtutil cl "Microsoft-Windows-GroupPolicy/Operational"
wevtutil cl "Microsoft-Windows-Help/Operational"
wevtutil cl "Microsoft-Windows-HotStart/Diagnostic"
wevtutil cl "Microsoft-Windows-HttpService/Trace"
wevtutil cl "Microsoft-Windows-International/Operational"
wevtutil cl "Microsoft-Windows-IPSEC-SRV/Diagnostic"
wevtutil cl "Microsoft-Windows-Kernel-Acpi/Diagnostic"
wevtutil cl "Microsoft-Windows-Kernel-BootDiagnostics/Diagnostic"
wevtutil cl "Microsoft-Windows-Kernel-PnP/Diagnostic"
wevtutil cl "Microsoft-Windows-Kernel-Power/Diagnostic"
wevtutil cl "Microsoft-Windows-Kernel-Prefetch/Diagnostic"
wevtutil cl "Microsoft-Windows-Kernel-Process/Analytic"
wevtutil cl "Microsoft-Windows-Kernel-Registry/Analytic"
wevtutil cl "Microsoft-Windows-Kernel-WDI/Analytic"
wevtutil cl "Microsoft-Windows-Kernel-WDI/Debug"
wevtutil cl "Microsoft-Windows-Kernel-WDI/Operational"
wevtutil cl "Microsoft-Windows-Kernel-WHEA"
wevtutil cl "Microsoft-Windows-LanguagePackSetup/Analytic"
wevtutil cl "Microsoft-Windows-LanguagePackSetup/Debug"
wevtutil cl "Microsoft-Windows-LanguagePackSetup/Operational"
wevtutil cl "Microsoft-Windows-LDAP-Client/Debug"
wevtutil cl "Microsoft-Windows-MeetingSpace/Operational"
wevtutil cl "Microsoft-Windows-MemoryDiagnostics-Results/Debug"
wevtutil cl "Microsoft-Windows-mobsync/Diagnostic"
wevtutil cl "Microsoft-Windows-MPS-CLNT/Diagnostic"
wevtutil cl "Microsoft-Windows-MPS-DRV/Diagnostic"
wevtutil cl "Microsoft-Windows-MPS-SRV/Diagnostic"
wevtutil cl "Microsoft-Windows-MUI/Operational"
wevtutil cl "Microsoft-Windows-NetworkAccessProtection/Operational"
wevtutil cl "Microsoft-Windows-OfflineFiles/Analytic"
wevtutil cl "Microsoft-Windows-OfflineFiles/Debug"
wevtutil cl "Microsoft-Windows-OfflineFiles/Operational"
wevtutil cl "Microsoft-Windows-OfflineFiles/SyncLog"
wevtutil cl "Microsoft-Windows-PowerCfg/Diagnostic"
wevtutil cl "Microsoft-Windows-PowerCpl/Diagnostic"
wevtutil cl "Microsoft-Windows-PrintSpooler/Aux-Analytic"
wevtutil cl "Microsoft-Windows-PrintSpooler/Core-Analytic"
wevtutil cl "Microsoft-Windows-PrintSpooler/Core-Debug"
wevtutil cl "Microsoft-Windows-PrintSpooler/ISV-Analytic"
wevtutil cl "Microsoft-Windows-Program-Compatibility-Assistant/Operational"
wevtutil cl "Microsoft-Windows-QoS-Pacer/Debug"
wevtutil cl "Microsoft-Windows-QoS-qWAVE/Debug"
wevtutil cl "Microsoft-Windows-ReadyBoost/Operational"
wevtutil cl "Microsoft-Windows-ReliabilityAnalysisComponent/Operational"
wevtutil cl "Microsoft-Windows-RemoteAssistance/Admin"
wevtutil cl "Microsoft-Windows-RemoteAssistance/Operational"
wevtutil cl "Microsoft-Windows-RemoteAssistance/Tracing"
wevtutil cl "Microsoft-Windows-Resource-Exhaustion-Detector/Operational"
wevtutil cl "Microsoft-Windows-Resource-Exhaustion-Resolver/Operational"
wevtutil cl "Microsoft-Windows-Resource-Leak-Diagnostic/Operational"
wevtutil cl "Microsoft-Windows-ResourcePublication/Tracing"
wevtutil cl "Microsoft-Windows-RestartManager/Operational"
wevtutil cl "Microsoft-Windows-RPC/Debug"
wevtutil cl "Microsoft-Windows-RPC/EEInfo"
wevtutil cl "Microsoft-Windows-Security-Licensing-SLC/Perf"
wevtutil cl "Microsoft-Windows-Sens/Debug"
wevtutil cl "Microsoft-Windows-ServiceReportingApi/Debug"
wevtutil cl "Microsoft-Windows-Services-Svchost/Diagnostic"
wevtutil cl "Microsoft-Windows-Services/Diagnostic"
wevtutil cl "Microsoft-Windows-Shell-AuthUI-Common/Diagnostic"
wevtutil cl "Microsoft-Windows-Shell-AuthUI-CredUI/Diagnostic"
wevtutil cl "Microsoft-Windows-Shell-AuthUI-Logon/Diagnostic"
wevtutil cl "Microsoft-Windows-Shell-AuthUI-PasswordProvider/BootAnim"
wevtutil cl "Microsoft-Windows-Shell-AuthUI-PasswordProvider/Diagnostic"
wevtutil cl "Microsoft-Windows-Shell-AuthUI-Shutdown/Diagnostic"
wevtutil cl "Microsoft-Windows-Shell-DefaultPrograms/Diagnostic"
wevtutil cl "Microsoft-Windows-Shell-Shwebsvc"
wevtutil cl "Microsoft-Windows-Shell-ZipFolder/Diagnostic"
wevtutil cl "Microsoft-Windows-Speech-UserExperience/Diagnostic"
wevtutil cl "Microsoft-Windows-stobject/Diagnostic"
wevtutil cl "Microsoft-Windows-Subsys-Csr/Operational"
wevtutil cl "Microsoft-Windows-Subsys-SMSS/Operational"
wevtutil cl "Microsoft-Windows-SystemHealthAgent/Diagnostic"
wevtutil cl "Microsoft-Windows-TaskScheduler/Debug"
wevtutil cl "Microsoft-Windows-TaskScheduler/Diagnostic"
wevtutil cl "Microsoft-Windows-TaskScheduler/Operational"
wevtutil cl "Microsoft-Windows-TerminalServices-PnPDevices/Admin"
wevtutil cl "Microsoft-Windows-TerminalServices-PnPDevices/Analytic"
wevtutil cl "Microsoft-Windows-TerminalServices-PnPDevices/Debug"
wevtutil cl "Microsoft-Windows-TerminalServices-PnPDevices/Operational"
wevtutil cl "Microsoft-Windows-TerminalServices-RemoteConnectionManager/Analytic"
wevtutil cl "Microsoft-Windows-TerminalServices-RemoteConnectionManager/Debug"
wevtutil cl "Microsoft-Windows-TerminalServices-RemoteConnectionManager/Operational"
wevtutil cl "Microsoft-Windows-UAC-FileVirtualization/Operational"
wevtutil cl "Microsoft-Windows-UAC/Operational"
wevtutil cl "Microsoft-Windows-User-Loader/Analytic"
wevtutil cl "Microsoft-Windows-VolumeSnapshot-Driver/Operational"
wevtutil cl "Microsoft-Windows-WindowsUpdateClient/Operational"
wevtutil cl "Microsoft-Windows-WinINet/Analytic"
wevtutil cl "Microsoft-Windows-Wininit/Diagnostic"
wevtutil cl "Microsoft-Windows-Winlogon/Diagnostic"
wevtutil cl "Microsoft-Windows-Winlogon/Operational"
wevtutil cl "Microsoft-Windows-WinRM/Analytic"
wevtutil cl "Microsoft-Windows-WinRM/Debug"
wevtutil cl "Microsoft-Windows-Winsock-AFD/Operational"
wevtutil cl "Microsoft-Windows-Winsock-WS2HELP/Operational"
wevtutil cl "Microsoft-Windows-Winsrv/Analytic"
wevtutil cl "Microsoft-Windows-Wired-AutoConfig/Operational"
wevtutil cl "Microsoft-Windows-WLAN-AutoConfig/Operational"
wevtutil cl "Microsoft-Windows-WMI-Activity/Trace"
wevtutil cl "Microsoft-Windows-WSC-SRV/Diagnostic"
wevtutil cl "Microsoft-Windows-WUSA/Debug"
wevtutil cl "Setup"