dkrahmer / mediatester Goto Github PK

This posible?

I had spent about 5 days waiting for this program to test a 14tb drive. It filled up, and then spent a few days testing, it was nearly done. And then it showed a failure, and I couldn't do a quick re-test, as all the written data had disappeared!

MediaTester.exe version: 0.4.1.0.

Suggestions (assuming they can easily be achieved by a single person.)

Hello.

• Actual access type to the device: solely achieved upon temporary file; it would be worth to enrich this access support by the options as logical drive and as physical device.
• Adding a real-time drive map, so the progress during the operations can be followed, and the locations of faulty blocks visualized.

Do not hesitate to close if those suggestions are not decent.

I have been using the drive but wanted to wipe it and decided to check it's supposed size of 1tb was genuine and ran it through with Media Tester which checked the size with writing and reading randomly over the drive. After which I just got the No Media message from windows. Has this been noted before?

Thanks for this great tool.
Since large HDDs can take a while to test it would be great to pause testing and resume it on another day.

3 of the VirusTotal vendors detect malware in the recently downloaded executable and show access to IP addresses with questionable reputations.

My PC crashed while the program was running. I am looking into the system logs. I see the WER... tmp files mentioned in the VirusTotal details were created and then deleted shortly before the crash.

Is it possible your exe has been compromised?

OS: Windows | edition: 11; version: 21H2. MediaTester.exe version: 0.4.1.0.

Hello. A unique item is displayed by the rolling menu. Nevertheless several items would be expected to be displayed since this is the very purpose of the rolling menu.

I tried to test the hard disk of the computer, but the speed seems to be a little slow, and there is no pressure on the CPU and the hard disk.

I'm testing multiple SD cards. Insert card, test, eject card, insert next card--I can't convince it that the new card is of a different size than the old one. Easy enough to close and reopen but it should either detect the media change or at least not use cached data when you click the button to expand the drive list.

Reference:

Hello. At About, the presence of the URL is useful; it would be even more if it could be as link instead of text. The mention Help, as part of (Click Help to view), is non-existent in the present UI. Thus the target it refers to, must be elsewhere.

Just received a new Kingston High Endurance 256GB card from a reputable shop, and figured I'd write ~33GB of data to it (set to 33000000000 bytes in UI) just as a quick sanity check without immediately filling it to the brim.

No issues while verifying the individual blocks, but I got a weird "First failing byte: -1" error at the end:
MediaTesterResults_2024-01-24_12-15-23_FAIL.txt

Tried again with 1GB (1000000000 bytes), same thing:
MediaTesterResults_2024-01-24_12-19-15_FAIL.txt

Tested a random 8GB Memory Stick Pro Duo I had laying around with both a fresh exFAT and FAT32 format, and it did the same thing both times. Was fine when I tested the full capacity, so I'm guessing this is a bug?

Also, bonus round: Setting 1000 bytes on the 256GB card led to some different weirdness, with the test going for about half a minute (way longer than expected) and the "Remaining" field going negative. Log:
MediaTesterResults_2024-01-24_12-20-03_FAIL.txt

(also got the same error in the end)

The 256GB card was tested with its factory exFAT formatting, and has now gone into service -- I can't run further tests on it if required, but let me know if I can provide any other info. Version was v0.4.1.0, Windows 10 x64 22H2.

OS: Windows | edition: 11; version: 21H2. MediaTester.exe version: 0.4.1.0.

Hello. Attempts to execute this program invariably fail, producing the application error code 0xc0000135.

This is feature request.

It would be nice to have for checking when the performance started to degrade. Useful for both "Write and verify" and "Verify" operations.

total size: 537gb (all available) write avg 13,445MB/sec Written 30GB Elapsed 00:45:00 Remaining: 1.08.00.00?

I unzipped the latest MediaTester-master.zip and loaded MediaTester.sln in Visual Studio 2019.
I did a rebuild of the solution and a build afterwards. I got the error message '
The "Fody.WeavingTask" task was not given a value for the required parameter "SolutionDir".
' twice, at line 53 of Fody.targets, both on project MediaTester and on project MediaTesterCli.
Can you help me find out if I am doing something wrong?

Can I translate into Spanish?