Annotated edit history of
fdflush(8) version 1, including all changes.
View license author blame.
Rev |
Author |
# |
Line |
1 |
perry |
1 |
FDFLUSH |
|
|
2 |
!!!FDFLUSH |
|
|
3 |
NAME |
|
|
4 |
SYNOPSIS |
|
|
5 |
DESCRIPTION |
|
|
6 |
OPTIONS |
|
|
7 |
BUGS |
|
|
8 |
FILES |
|
|
9 |
AUTHOR |
|
|
10 |
---- |
|
|
11 |
!!NAME |
|
|
12 |
|
|
|
13 |
|
|
|
14 |
fdflush - force floppy disk drive to detect disk change |
|
|
15 |
!!SYNOPSIS |
|
|
16 |
|
|
|
17 |
|
|
|
18 |
__fdflush__ [[device] |
|
|
19 |
!!DESCRIPTION |
|
|
20 |
|
|
|
21 |
|
|
|
22 |
__Fdflush__ is a band-aid for a common PC hardware |
|
|
23 |
problem. Many PC floppy disk drives can't detect when the |
|
|
24 |
disk has been changed. The symptom of this problem is that |
|
|
25 |
when a disk is changed, the drive will continue to read |
|
|
26 |
buffered data from the previous disk rather than new data |
|
|
27 |
from the disk presently in the drive. Running ''fdflush'' |
|
|
28 |
makes the system believe the disk-change switch has been |
|
|
29 |
actuated, and the system discards the buffered blocks in |
|
|
30 |
response to this information. If you have one of these |
|
|
31 |
slightly-broken disk drives, you'll have to run |
|
|
32 |
''fdflush'' every time you change a disk. |
|
|
33 |
!!OPTIONS |
|
|
34 |
|
|
|
35 |
|
|
|
36 |
''device'' |
|
|
37 |
|
|
|
38 |
|
|
|
39 |
The name of the floppy disk device, in the form ''/dev/fd1 |
|
|
40 |
.'' The default is ''/dev/fd0 .'' |
|
|
41 |
!!BUGS |
|
|
42 |
|
|
|
43 |
|
|
|
44 |
They're in your hardware. Try swapping in another floppy |
|
|
45 |
drive to see if this problem goes away. |
|
|
46 |
!!FILES |
|
|
47 |
|
|
|
48 |
|
|
|
49 |
/dev/fd''N'' floppy disk device. |
|
|
50 |
!!AUTHOR |
|
|
51 |
|
|
|
52 |
|
|
|
53 |
Bruce Perens ''Bruce@Pixar.com .'' |
|
|
54 |
---- |
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.