mirror of
https://github.com/davidgiven/fluxengine.git
synced 2025-10-31 11:17:01 -07:00
Rename test bulktransport to test bandwidth; avoid watchdog failures while the
bandwidth test is running.
This commit is contained in:
@@ -51,7 +51,7 @@ In order to do anything useful, you have to plug it in to a floppy disk drive (o
|
||||
rpm for a 3.5" disk, or 360 rpm for a 5.25" disk. If it doesn't, please
|
||||
[get in touch](https://github.com/davidgiven/fluxengine/issues/new).
|
||||
|
||||
7. Do `fluxengine test bulktransport` from the shell. It'll measure your USB
|
||||
7. Do `fluxengine test bandwidth` from the shell. It'll measure your USB
|
||||
bandwidth. Ideally you should be getting above 900kB/s. FluxEngine needs
|
||||
about 850kB/s, so if you're getting less than this, try a different USB
|
||||
port.
|
||||
@@ -241,9 +241,9 @@ directory.
|
||||
- `fluxengine seek`: moves the head. Mainly useful for finding out whether
|
||||
your drive can seek to track 82. (Mine can't.)
|
||||
|
||||
- `fluxengine test bulktransport`: measures your USB throughput. You need
|
||||
about 600kB/s for FluxEngine to work. You don't need a disk in the drive
|
||||
for this one.
|
||||
- `fluxengine test bandwidth`: measures your USB throughput. You need about
|
||||
600kB/s for FluxEngine to work for DD disks, and 900 to 950kB/s for HD
|
||||
disks. You don't need a disk in the drive for this one.
|
||||
|
||||
- `fluxengine test voltages`: measures your FDD bus signal voltages, which
|
||||
is useful for testing for termination issues.
|
||||
|
||||
Reference in New Issue
Block a user