TRIM beta test...32BIT windows looks 100%, 64Bit windows now 90%+ OK.UPDATE 28-05-09 Wiper 0525 uploaded for test

[Tony]

So i have approval for a public beta test, here are the facts you need to know.

I tested this app on a Gigabyte X48-DQ6 and Vista 64, after TRIMMING the drive on reboot the OS was corrupt. I did this 4 times ...each time with a fresh install.


Wiper has moved to over 90% safe for windows 64bit users along with totally safe for 32bit users, a new version has just been uploaded, give it a try let me know what you find here in this thread. Be cautious still, i have designated this new build still under beta test. There may still be no XP64 support, i do not have the OS here to test.

Conditions of use:

You must understand using this application carries risks, BE REALLY CAUTIOUS with Vista 64 or Windows 7 64. Hence if you download and try this software you except there is risk and agree that you may end up having to fresh install the OS there after.
Its beta, and carries all the risks that beta software does. If you see any drive issues i suggest you reflash the drive to 1.10 and fall away from testing.

The application ONLY works with FW1.10...1275 does not work. Its also single drive only...NO RAID

Use this thread to talk about your findings, any issues and any further suggestions.

MD5 checksum Wiper.exe : FE28C8FD68ACC03293546D242A57BD4C

UPDATE 22-4-2009

New version for test..wiper.exe 0422

more info on corruption issue:

The reason why user data got corrupted was some device drivers (eg. Intel Matrix Storage) sent only 28bit LBA address to SSD while Wiper sent 48bit LBA address. Complete solution is not implemented yet, but this version has some avoidance code... In other words, performance may not be restored, but user data will be more likely to be preserved.

Again this is released for test as Beta Only...its the next build on from the previous release.

May 28th UPDATE

new Wiper 0525...again under beta test.


Not sure on changelog although it has been built off 0422 so it should be a move in the right direction.

[Dalla]

I´ll give it a shot, using XP 32 and Vertex 30 GB

[KryptoNyte]

Are there any specific instructions or limitations to use (RAID), Tony, or just extract it and run it from the windows desktop?

Edit: Okay, I see "don't use in RAID" from another thread.

[Tony]

OOps no raid, single drive only.. i will add that to the top post

[Tony]

its a click and run affair...it looks for vertex, finds it and TRIMS it. You will see it creates a HUGE file on the SSD when TRIMMING then deletes it when finished

[KryptoNyte]

Understood. Thanks, Tony.

[devsk]

its a click and run affair...it looks for vertex, finds it and TRIMS it. You will see it creates a HUGE file on the SSD when TRIMMING then deletes it when finished

So, questions, questions:

1. This means it is trimming Windows drives (C:, D: whatever) and not the disk? what happens to other partitions that Windows 32 bit doesn't see? Do those partitions remain fragmented?

2. Does this work for single drive as a non-member RAID?

[Amozz]

So, questions, questions:

1. This means it is trimming Windows drives (C:, D: whatever) and not the disk?

Yes, after what I can understand from how it works, that's right. It allocates all available free space on the logical disk, sends TRIM for all sectors occupied by this file, and finely deletes the file. It's the safe and easy way to do it.

And that's lead to the most probably reason for this errors on w64 - one or more cast with the wrong integer type. Perhaps in the assembly part?

what happens to other partitions that Windows 32 bit doesn't see? Do those partitions remain fragmented?

Probably yes. To TRIM an FS unknown to Windows, the wiper must know the FS well, or include a windows driver for it.

[win7-64]

Booted into vista 64 sp1 from a non ssd hardrive and tried the wiper program again (had not worked before corrupting my windows 7 64 installation when i ran it from within windows installed on the vertex drive) and it seems to have worked. Both drives where on ide mode when the program was run and the wiper tool was working as it looked like it was creating a large file on the vertex then it deleted it when finished.

Rebooted and went back into the vertex windows 7 64 installation in raid mode non-member disk and no corruption, it booted fine with all the files intact as far as i can see.

So as long as it's its not run from a 64bit os which is installed on the vertex but from another drive it seems to work.

[BobF]

Booted into vista 64 sp1 from a non ssd hardrive and tried the wiper program again (had not worked before corrupting my windows 7 64 installation when i ran it from within windows installed on the vertex drive) and it seems to have worked. Both drives where on ide mode when the program was run and the wiper tool was working as it looked like it was creating a large file on the vertex then it deleted it when finished.

Rebooted and went back into the vertex windows 7 64 installation in raid mode non-member disk and no corruption, it booted fine with all the files intact as far as i can see.

So as long as it's its not run from a 64bit os which is installed on the vertex but from another drive it seems to work.

Just tried what you say, booted into my Win7 dual boot system on a HDD, and trimmed my Vista64 60GB Vertex and data 128 GB Vertex. Trim wiper seemed to run OK this time, but when I ran chkdsk afterwards, the data Vertex had all sorts of problems that it didn't have before, and the Vista64 Vertex stopped running chkdsk and had to be killed. I did then get chkdsk to run on it, and it again had all sorts of errors that weren't there before.

So it didn't work for me.

Bob F

[amjl2000]

You don't mention XP64... have just put this on my drive, and tried the wiper.. get 'error message from system: The parameter is incorrect.'

This is with and without nVidia southbridge drivers on my mobo.
It hasn't broken anything though

[Tony]

so no XP64 ...I will make note.I don't own the OS so can't tests it.

[Binary Poet]

Works like a champ on a Vertex 120 running in a Asus G1 laptop (ICH7 controller) with Vista 32......

Completed in about 12 seconds with the drive 25% full

I have run it 3 times and rebooted after, fine every time...

Good Job Tony......

[Tony]

Works like a champ on a Vertex 120 running in a Asus G1 laptop (ICH7 controller) with Vista 32......

Completed in about 12 seconds with the drive 25% full

I have run it 3 times and rebooted after, fine every time...

Good Job Tony......

BP, glad you added the edit...i had no issues with V32 either, the system actually felt really snappy after the first use.
I actually dropped it into my start folder, every time the test PC booted the drive is trimmed.

[Tony]

Remember guys my issues were when I rebooted.