Search:

Trying figure out what causes low GFlops, v0.9.5?

I have 4 SSD in RAID0 on ICH10 (X58 chipset board) with OROM 11.5.0.1414 and IRST 11.5.0.1207 installed. Windows 7 U x64 SP1.

I have been trying the procedure outlined here, but it does not appear...

I asked about the TRIM for RAID under Windows 7 on TechNet.

The reply was that it works for ATA devices, but not for SCSI devices.

SCSI devices use UnMap, which Windows 7 cannot use.

As the...

True.

Still, I wish there was a definitive way to determine whether TRIM is or is not working on my RAID0 array.

You are correct, Sentential said 'enabled', not 'working', my bad.

I got a little excited...

Excellent news!

How did you determine TRIM was working?

Yes, but I have only seen the drivers, not the full installation package.

Thanks for that, I was using CDI 4.3.0a.

Yes, it does show the individual drives, and under Standard, reports ATA8-ACS | ATA8-ACS version 6.

EDIT:

Drives are ADATA S599.

I did see that in the ASU thread, but I see no difference on my rig.

Also CDI does not show my array.

EDIT:

To follow up on your edit, I have read that because the RST 11.5.0.1149 makes...

Were you able to make any determination?

From my limited searching on the Internet, and the limited amount of information on the subject, it is my understanding there is no reliable way to...

@Anvil,

I just noticed that.

Anyway, I went back to RST 11.1.0.1006, and got a better result:

http://i291.photobucket.com/albums/ll305/Arctucas/AnvilRC15-21-12.jpg

I wil give the RST...

Dropped off significantly from BETA 11

http://i291.photobucket.com/albums/ll305/Arctucas/Anvilbench5-19-12.jpg

Thanks for the update.

@Anvil,

I wanted to check with you regarding when we might expect to see the next version?

Thanks, and keep up the good work.

I believe it must be some specific incompatibility unique to my system that the benchmark is having trouble with, since every other application I have used that identifies the motherboard does so...

@Anvil,

Thank you for continuing development of this application.

I am still getting the wrong socket listed, however.
...

Primo:

http://i291.photobucket.com/albums/ll305/Arctucas/CDMramdisk1-6-12.jpg


QSoft:

http://i291.photobucket.com/albums/ll305/Arctucas/CDMramdiskQSoft1-6-12.jpg

New screenshot, fresh install done yesterday, after secure erase was run on each SSD:

http://i291.photobucket.com/albums/ll305/Arctucas/Volume0_240GB_1GB-20111223-1236.png

I am not sure about...

4x ADATA S599 RAID0

http://i291.photobucket.com/albums/ll305/Arctucas/Volume0_240GB_1GB-20111217-2146.png


Excellent application.

I only wonder why it is showing my motherboard as Socket...

I did manage to figure out a way to make Kombustor use both cards; rename the MSIKombustor.exe (whichever DX version I want to use) to Heaven.exe.

Thanks for the replies.

OK, I set Kombustor to match my screen resolution (1920x1200), checked the Fullscreen box, and it still only uses the primary GPU.

I understand, I had never heard that term until now.

"re roll"?

EDIT:

FurMark (1.9.0) also only uses the primary unless I rename it to etqw.

When running Kombustor, it appears to only be using the primary gpu, even though I have SLI enabled.

How may I get Kombustor to utilize both cards?

@joshy,

You have PM.