AppImages > System > jsBudbrainLaufwerksTest


jsBudbrainLaufwerksTest

Screenshot of jsBudbrainLaufwerksTest

Writes a test file to a drive, reads it back, checks every block and deletes it again. Two level meters show the current speed live, two charts record the whole run.

  • Test size from 1024 MB up to 16 GB, or a fixed duration from 5 seconds to 16 minutes
  • Measures the drive itself, not the computer's memory
  • Every block is verified on reading, which helps to uncover drives with a faked capacity
  • Shows when a fast drive runs out of breath and the speed drops
  • Worst, average and best value for writing and reading
  • History of all runs, export as text
  • Never fills a drive: space for the system stays free
  • Light and dark design
  • Available in 47 languages

Compatibility: Uses the C library of the system (may need glibc 2.34 or later)


Usage

jsBudbrainLaufwerksTest is available as an AppImage which means "one app = one file", which you can download and run on your Linux system while you don't need a package manager and nothing gets changed in your system. Awesome!

AppImages are single-file applications that run on most Linux distributions. Download an application, make it executable, and run! No need to install. No system libraries or system preferences are altered. Most AppImages run on recent versions of Arch Linux, CentOS, Debian, Fedora, openSUSE, Red Hat, Ubuntu, and other common desktop distributions.

This AppImage uses the C library of the system and may need glibc 2.34 or later. It does not run on distributions that use a different C library (such as musl on Alpine Linux) or an older glibc.

Running jsBudbrainLaufwerksTest on Linux without installation

Unlike other applications, AppImages do not need to be installed before they can be used. However, they need to be marked as executable before they can be run. This is a Linux security feature.

Beware! AppImages are usually not verified by others. Follow these instructions only if you trust the developer of the software. Use at your own risk!

Download the jsBudbrainLaufwerksTest AppImage and make it executable using your file manager or by entering the following commands in a terminal:

chmod +x ./*.AppImage

Then double-click the AppImage in the file manager to open it.

Sandboxing jsBudbrainLaufwerksTest

If you want to restrict what jsBudbrainLaufwerksTest can do on your system, you can run the AppImage in a sandbox like Firejail. This is entirely optional and currently needs to be configured by the user.

Updating jsBudbrainLaufwerksTest

If you would like to update to a new version, simply download the new jsBudbrainLaufwerksTest AppImage.

The jsBudbrainLaufwerksTest AppImage also can be updated using AppImageUpdate. Using this tool, jsBudbrainLaufwerksTest can be updated by downloading only the portions of the AppImage that have actually changed since the last version.

Integrating AppImages into the system

If you would like to have the executable bit set automatically, and would like to see jsBudbrainLaufwerksTest and other AppImages integrated into the system (menus, icons, file type associations, etc.), then you may want to check the optional appimaged daemon.


Note for application authors

Thanks for distributing jsBudbrainLaufwerksTest in the AppImage format for all common Linux distributions. Great! Here are some ideas on how to make it even better.

Pro Tips for further enhancing the jsBudbrainLaufwerksTest AppImage

Please consider making the jsBudbrainLaufwerksTest AppImage self-contained, so that it does not depend on the C library of the system and runs on more distributions: ship the C library including its loader (ld-linux-*.so.*) and use it to launch the application, or link statically.

Thanks for shipping AppStream metainfo inside your AppImage. Please open a pull request on https://github.com/AppImage/appimage.github.io/blob/master/data/jsBudbrainLaufwerksTest if you have changed it and would like to see this page updated accordingly.

If you would like to see a donation link for the application here, please include one in the AppStream data.

History of this page

Edit the input for this page