05-01-2015
Is the file system floppy disk write protected? Or possibly is the diskette drive dirty enough that it thinks all diskettes are write protected?
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hello guys The company i work for just got a new client, there old datebase is in Unix SCO openserver 5.0.5.
The manager of this new client can login but not as a root , they forgot there own root password. There old IT company never gave it to them and they have no way of getting a hold of them
... (2 Replies)
Discussion started by: josramon
2 Replies
2. SCO
Hi!
Sorry, but I am'not spesialist in SCO OpenServer. I need to add hard disk from SCO Open Server ( "a") in my SCO OpenServer 5.6. I need data from "a". When I added, I see only swap disk, and didn't see root file system. I need to add IDE and SCSI
Please, help me. How right to add disk?... (0 Replies)
Discussion started by: fedir
0 Replies
3. SCO
Hi,
I have an openserver 5.0.0 machine in the office. The sysad of that machine left years ago without leaving the password to anyone.
I was wondering if someone has a copy of the boot / root diskettes (rescue) for this version? Or perhaps if anyone knows a download link / location in the... (0 Replies)
Discussion started by: marcpascual
0 Replies
4. SCO
I would like to expand the size of the root area, currently 800 kb, to a size of 2000 kb. Is that possible to do without loosing any data in the /u area? There is plenty of space available in the /u area. (2 Replies)
Discussion started by: pschnell
2 Replies
5. SCO
I'm "attempting" to install SCO 5.0.7 on an HP ML370 G4 server and am ready to bash the keyboard with head now. I keep getting the error message "WARNING hd: no root disk controller found" when running the bootable install cd.
I have a raid 5 array with an online spare created using 4 36.3 GB... (2 Replies)
Discussion started by: FrictionBurn
2 Replies
6. Solaris
Hi all
I wish to mirror for the root disk, but last time i do, make the server cannot boot up. :p So this time, hope you guys can assist me on it. =)
At the last code, is the step i wish to do. Please help to check and correct me if got any wrong.
root@leo # format </dev/null
Searching for... (17 Replies)
Discussion started by: SmartAntz
17 Replies
7. SCO
DEAR Team,
I need some help in sco open server 5
while booting server beloow message giving server
HTFS no space dev HD 1/42
Thanks
Skb (4 Replies)
Discussion started by: sudhir69
4 Replies
8. Solaris
Hi All
Hope it's okay to post on this sub-forum, couldn't find a better place
I've got a 480R running solaris 8 with veritas volume manager managing all filesystems, including an encapsulated root disk (I believe the root disk is encapsulated as one of the root mirror disks has an entry under... (1 Reply)
Discussion started by: sunnyd76
1 Replies
9. SCO
Hi,
We have an old SCO Openserver 5.0.7 server that I have inherited that currently has two issues that we are trying to resolve.
1. We do not know the root password. I have contacted the old admin, looked for rescue disk and documentation but there appears to be nothing.
I have tried... (1 Reply)
Discussion started by: acerimmer10
1 Replies
FD(4) Kernel Interfaces Manual FD(4)
NAME
fd - floppy disk
DESCRIPTION
The fd* devices refer to the Floppy disk driver using the NEC PD765 floppy disk controller. These diskettes are arrays of 512 byte sec-
tors, although Minix always works with two sectors at a time due to its 1024 byte block size. You can read or write any number of bytes
however, Minix takes care of cutting and pasting incomplete blocks together.
The driver is normally configured for two floppy disk devices fd0 and fd1. It can handle two more, but it is unlikely that the average PC
can.
On the first access to an fd device (by open(2) or mount(2)), the driver will execute a series of read tests to determine the floppy type.
This works ok for all floppy types except the true 360k type, because it is indistinguishable from the 720k type. This only means that the
size of the floppy is not estimated right.
Bits 2-6 of the minor device number may be set to the floppy disk type to make it known to the driver what type of diskette it is reading
or writing. The non-auto devices should be used for formatting, or when one wants to be absolutely sure that the device is accessed right.
These devices exist for drive 0:
type device minor media
0 fd0 0 autodetect
1 pc0 4 360k, 5.25"
2 at0 8 1.2M, 5.25"
3 qd0 12 360k in a 720k, 5.25" drive
4 ps0 16 720k, 3.5"
5 pat0 20 360k in a 1.2M, 5.25" drive
6 qh0 24 720k in a 1.2M, 5.25" drive
7 PS0 28 1.44M, 3.5"
Type 4 may also be used for the rarely seen 720k, 5.25" floppies (type 2 made them obsolete fast.) Note that these "types" only describe
the floppies from a software point of view, type 1 and 4 drives use the same parameters.
If the format bit (bit 7) is set, then the driver interprets write commands as track formatting requests. This is used by the format(1)
command.
If the type bits are set to 28, 29, 30, or 31, then the driver uses a partition table found in sector 0 to partition the floppy. The par-
titions of fd0 may be accessed as fd0a through fd0d. See hd(4) for a description of the partition table, and associated ioctl commands.
FILES
/dev/fd[0-3], /dev/pc[0-3], /dev/at[0-3], /dev/qd[0-3], /dev/ps[0-3], /dev/pat[0-3], /dev/qh[0-3], /dev/PS[0-3], /dev/fd[0-3][a-d]
SEE ALSO
format(1), hd(4), part(8).
BUGS
The driver does not know the size of a 360k diskette in a 360k 5.25" drive, because it uses the 720k parameters for it. So it will happily
try to read past the end making all kinds of interesting noises. It's a good thing these drives are practically obsolete.
The partition table is only read when the drive motor is off and only for an auto or partition device. The driver assumes that a floppy in
a drive with a running motor can't have been replaced all of a sudden.
AUTHOR
Kees J. Bot (kjb@cs.vu.nl)
FD(4)