SOURCES TELL the INQUIRER that Nvidia is preparing a fresh onslaught against its chipset competitors next year, with PCI Express the major prong for its all-out AMD attack. During next year, Nvidia plans to introduce a total of three different PCI Express chipsets for the Athlon64/Opteron microprocessors, taking advantage of the faster throughout the bus provides.

The first plank of its PCI Express onslaught will be a chipset tentatively called Crush 3GIO, which will take advantage of the increased graphics capabilities of PCI Express. 3GIO was the former codename for PCI Express. Plans for this chipset are well underway – it is expected to sample in the fourth quarter of this year and be available in the first quarter of next year. It supports a hypertransport interface to the Athlon64. The Crush K8-04 is a high end PCI Express chipset that is being prepared on a similar schedule. It will support four Serial ATA ports, four ATA-133 ports, ADMA, NV RAID, four PCI 2.3 slots , 24 bit 7.1 surround audio and Gigabit Ethernet. Vendors are pinning high hopes on what they describe as "2004 PCs", using PCI Express.

View: The full story
News source: The Inq

Changelog:
Diskeeper build 430 adds support for Windows Server 2003, and includes performance and reliability improvements to the boot-time defragmentation engines.

Please Note: On a small number of Windows XP systems, running a boot-time defragmentation may result in a Windows message being displayed after the post-defragmentation reboot indicating that the system did not start up properly. This is sometimes followed by a CHKDSK operation, which finds no disk errors. We are investigating the cause of this message, but at this time no system that has displayed this startup screen or run a post-defragmentation CHKDSK has demonstrated any problems. You can simply use the default "Start Windows Normally" option, or let the timer time-out. Your system will then boot up normally.

Also Note: The Diskeeper NTFS boot-time engines have been modified in this build to verify they have exclusive access to the volume being defragmented. This change ensures that no other drivers or services can modify the volume while the boot-time defragmentation is running. If the volume cannot be locked, an error message appears describing this and the boot-time defragmentation will not run.


There are no additional comments
Advertisement


Commenting has either been disabled on this article or you are not logged in. Click here to login or register, its free!

Note: Anonymous commenting is disabled in order to keep the quality of responses to a high standard.


Scroll to the Top
....
My Preferences
....
Communicating with server
Loading
Please Wait...
....
Loading
 X 
....