AlexZ wrote on Yesterday, 15:32:

It happened to me on nForce 3 and Intel SSD. Windows XP froze on boot screen very early and after manual reboot offered safe mode. I selected standard boot and it booted normally. Everything worked fine in Windows once it booted. But after turning the PC off and on it repeated. There may be SSDs that will work fine with nForce 3, but one should be prepared for such issues.

I use Samsung 860 EVO on nForce 4 and it works in SATA-1 mode, not SATA-2 the chipset supports. So this is also an issue but at least it is reliable. This SSD failed to work reliably on AMD SATA controller.

Sorry, I can't help you with that.
My VIA K8T800 (VT8237) always rebooted during the first boot from SSD.
I think I solved the problem today — I installed (on another motherboard it would be ‘moved’, but this is Jetway) a strap resistor on ‘disable autoreboot’.
I don't know how it works — the schematic diagrams say ‘if the BIOS supports this option’.
Half of the motherboards have the resistor set to ‘disable’, while the other half have it set to the opposite position.
But it seems to have worked.

Cand you post pictures ot schematics? This is good news. I could never installed a SSD in KV8 PRO/K8T800 board.

1. We go straight to the benchmarks and, as usual, Code creatures is first
1024*768 no AA, no sound:
1. NF8
2. KU8
3. KV8

VIA is off to a good start with a 3% advantage over the competition; however that 3 % is still well within the 5% which is the limit of error!
2. 1024*768 no AA sound ON:
1. NF8
2. KU8
3. KV8

Please note again the very low impact the sound has on the results! Back on socket A only nforce2 managed such good results in tests with sound while all boards with realtek codecs suffered greatly!
3. 1024*768 AA 4X no sound
1. NF8
2. KU8
3. KV8

4. 1024*768 AA 4X sound ON
1. NF8
2. KU8
3. KV8

VIA is in front however the distance between all 3 platforms is really small!
5. 1280*1024 no sound
A. NF8
B. KU8
C. KV8

nd22 wrote on Today, 04:51:

Cand you post pictures ot schematics? This is good news. I could never installed a SSD in KV8 PRO/K8T800 board.

It's not what you think.
Without switching the SATA mode in the drive itself, the VT8237 A/R will still not see SATA2/3 devices.
Only the “R+” chipset does not have this drawback.
This is a solution to a very strange glitch where, once the SSD has been detected, Windows starts to load. It gets halfway through and then reboots.
Re: How to connect SSD to SATA1 (SandForce based SSD). And a small dirty test.

6. 1280*1024 SOUND ON:
A. NF8
B. KU8
C. KV8

7. and the grand daddy of retro resolutions: 1600*1200
A. NF8
B. KU8
C. KV8

8. final and most demanding settings: 1600*1200 AA 4X sound on:
A. NF8
B. KU8
C. KV8

Despite being the first every single time VIA does not have any decisive advantage in Code creature pro! Also ULI keeps up with the rest of the competition pretty well! Nforce3 is last but 3% slower is nothing extraordinary!

shevalier wrote on Today, 07:40:

It's not what you think. Without switching the SATA mode in the drive itself, the VT8237 A/R will still not see SATA2/3 devices. […]
Show full quote

nd22 wrote on Today, 04:51:

Cand you post pictures ot schematics? This is good news. I could never installed a SSD in KV8 PRO/K8T800 board.

It's not what you think.
Without switching the SATA mode in the drive itself, the VT8237 A/R will still not see SATA2/3 devices.
Only the “R+” chipset does not have this drawback.
This is a solution to a very strange glitch where, once the SSD has been detected, Windows starts to load. It gets halfway through and then reboots.
Re: How to connect SSD to SATA1 (SandForce based SSD). And a small dirty test.

I remember now that I read that; the problem is that the solution requires SSD's wih specific controller which I do not have.

Regarding F.E.A.R. testing.
It's with a NVIDIA's undisable PhysX.
For which you need a PCI-e graphics card no weaker than 8600.
Either a significantly different processor or a resolution of 1024*768

shevalier wrote on Today, 10:32:

Regarding F.E.A.R. testing.
It's a NVIDIA's undisable PhysX.

F.E.A.R. uses Havok physics, which is GPU agnostic.

Nvidia's PhysX is a different thing entirely.

Joseph_Joestar wrote on Today, 10:37:

shevalier wrote on Today, 10:32:

Regarding F.E.A.R. testing.
It's a NVIDIA's undisable PhysX.

F.E.A.R. uses Havok physics, which is GPU agnostic.

Nvidia's PhysX is a different thing entirely.

Exactly, I was wrong.
I watched it very late last night.
Sorry.
The most recent version of the engine uses a DirectX 9 renderer and includes support for the Havok physics model, including the additional "Havok vehicle ...