07-27-2019
This is where a USB floppy drive comes in really handy both to write the BTLD floppies on the Linux box and read them (as BTLD driver(s)) on installation.
Perhaps try to acquire, beg, borrow or steal one of those.
This User Gave Thanks to hicksd8 For This Post:
10 More Discussions You Might Find Interesting
1. SCO
I am facing a problem to install sco 5.0.6 in Dell Power Edge SC1420 which raid controller is ultra 320 scsi raid controller .
how/from where to download the ultra 320 scsi raid controller driver for sco 5.0.6.
Plz help with any idea
karzon (1 Reply)
Discussion started by: karzon
1 Replies
2. SCO
recently we have purchased hp proliant ml350 g5 server and configured raid 5 with hp smartarray p200i sas controller.but i could not found any sas raid controller hp smartarry p200i driver for sco unix 5.0.7 :(.i searched on hp support site,but no use.any one can help. (3 Replies)
Discussion started by: prakrithi
3 Replies
3. UNIX for Dummies Questions & Answers
Trying to install Openserver 6.0 on this server which has an integrated Smart Array P400.
Install halts with the message .......
"Incorrect Disk Partitioning .........................."
I havent yet got to the "divvy" and disk partitioning section of the install section so I am... (2 Replies)
Discussion started by: farmacy
2 Replies
4. 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
5. SCO
This is my first load of SCO OpenServer v5.0.7 on a HP ProLiant ML350 G6. When it asks me to identify the source media it can't find it no matter how I respond. The SCO compatible page says it used the on board SATA DVD-ROM on Port 2 of the embedded SATA controller with "Legacy IDE emulation (as... (8 Replies)
Discussion started by: farmboy
8 Replies
6. SCO
So today I tried to upgrade a customer from a Proliant with an HPSAS controller to an Intel server with a MEGASAS controller.
First, I downloaded the megasas driver from SCO and installed it on the old system.
Then I created a new Microlite Edge emergency boot cd with the new driver on it.
I... (2 Replies)
Discussion started by: jgt
2 Replies
7. Debian
Hello,
I have a few questions about this server.
It has two CPU's 3.20 ghz / 800 mhz / 1MB L2
5120 MB RAM
6 hard disks on HP Smart Array 6i controller (36.4 GB Ultra320 SCSI HD each)
RAID set to RAID 5 (5 discs) with one spare (6th disk)
USB, 2 Ethernet ports, 1 ILO port, 1 SCSI port
... (2 Replies)
Discussion started by: Marcus Aurelius
2 Replies
8. SCO
Installing SCO UNIX 507 on Dell Poweredge T610. It has no floppy so I downloaded the BTLD onto CD from SCO site to load without floppy drive. BTLD loads ok. when i get to the Media to be used, no matter what option i chose i get the error: No controller for device you have chosen. During bootup you... (9 Replies)
Discussion started by: romanglad112
9 Replies
9. SCO
Hello
I'm trying to virtualize an instance of Sco Unix 5.0.5 in VirtualBox (called VM-A) , but sco I have problems set to launch with the new raid controller .
The physical machine has a raid controller adaptec (alad driver) but VirtualBox uses buslogic (blc driver)
What ... (3 Replies)
Discussion started by: flako
3 Replies
10. SCO
Hi all,
A client has an SCO OpenServer Server 6.0, that is running on an HP ProLiant Box and they lost the root password.
Its equipped with a Doal-Core Intel Pentium Processor. They don't have any media or emergency disk anymore.
I tried to boot with the CD Rom, then "Tools", then exit to... (7 Replies)
Discussion started by: thm2222
7 Replies
LEARN ABOUT FREEBSD
fdwrite
FDWRITE(1) BSD General Commands Manual FDWRITE(1)
NAME
fdwrite -- format and write floppy disks
SYNOPSIS
fdwrite [-v] [-y] [-f inputfile] [-d device]
DESCRIPTION
The fdwrite utility formats and writes one and more floppy disks. Any floppy disk device capable of formatting can be used.
The fdwrite utility will ask the user (on /dev/tty) to insert a new floppy and press return. The device will then be opened, and queried for
its parameters, then each track will be formatted, written with data from the inputfile, read back and compared. When the floppy disk is
filled, the process is repeated, with the next disk. This continues until the program is interrupted or EOF is encountered on the inputfile.
The options are as follows:
-v Toggle verbosity on stdout. Default is ``on''. After device is opened first time the format will be printed. During
operation progress will be reported with the number of tracks remaining on the current floppy disk, and the letters I, Z,
F, W, R and C, which indicates completion of Input, Zero-fill, Format Write, Read and Compare of current track respec-
tively.
-y Do not ask for presence of a floppy disk in the drive. This non-interactive flag is useful for shell scripts.
-f inputfile
Input file to read. If none is given, stdin is assumed.
-d device The name of the floppy device to write to. Default is /dev/fd0.
The fdwrite utility actually closes the device while it waits for the user to press return, it is thus quite possible to use the drive for
other purposes at this time and later resume writing with the next floppy.
The parameters returned from device are used for formatting. If custom formatting is needed, please use fdformat(1) instead.
EXAMPLES
The fdwrite utility was planned as a tool to make life easier when writing a set of floppies, one such use could be to write a tar-archive:
tar cf -. | gzip -9 | fdwrite -d /dev/fd0.1720 -v
The main difference from using tar(1)'s multivolume facility is of course the formatting of the floppies, which here is done on the fly, thus
reducing the amount of work for the floppy-jockey.
SEE ALSO
fdformat(1)
HISTORY
The fdwrite utility was written while waiting for ``make world'' to complete. Some of the code was taken from fdformat(1).
AUTHORS
The program has been contributed by Poul-Henning Kamp <phk@FreeBSD.org>.
BUGS
Diagnostics are less than complete at present.
If a floppy is sick, and the inputfile is seekable, it should ask the user to frisbee the disk, insert another, and rewind to the right spot
and continue.
This concept could be extended to cover non-seekable input also by employing a temporary file.
An option (defaulting to zero) should allow the user to ask for retries in case of failure.
At present a suitable tool for reading back a multivolume set of floppies is missing. Programs like tar(1) for instance, will do the job, if
the data has not been compressed. One can always trust dd(1) to help out in this situation of course.
BSD
September 16, 1993 BSD