06-09-2009
I'm sorry to say that I did not get it to work. I tried the boot img's from the SCO site and some other sites. I ended up installing the 7.1.1 version of the OS. I believe that I used their original license info for the 7.1.1 but i could have used the 7.1.1 license info. The customer that loaned me the 7.1.1 disks no longer has that server. At this point if SCO complains then i can have them fix their own boot disks.
I'm not sure is this is a media problem with the disks or the boot floppies. I was never able to get another copy of 7.1.0 to test with.
sorry I could not give you better news.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
hello ,
i have sun sparc machine with sunos2.7 , the machine has a cdrom but no floppy drive , it is networked with windows machine , from where i can use ftp and telnet.
can i use floppy drive of windows machine and create a boot image(of unix) on that drive, using ftp?
thanx
raju (4 Replies)
Discussion started by: raju
4 Replies
2. UNIX for Dummies Questions & Answers
Hi,
My dear friends,
I am trying to install red hat linux. I have downloaded its disc1. On the instructions page, the next stage is to make the boot disk, so that I can boot from the floppy. However, I am unable to locate the boot image iso file. I tried on google, but I got a few files which... (3 Replies)
Discussion started by: linuxpenguin
3 Replies
3. AIX
Dear Sirs,
I would like to make a Boot Floppy for the RS6k F30. Somebody can help me?
Spart (1 Reply)
Discussion started by: spartiate
1 Replies
4. Ubuntu
there is probably another post about this, i just can't find it on unix.com or google. basically, i am trying to make a boot floppy via CLI/terminal. the problem is that i use an external drive. when i do the first couple of steps, i get rejected. when i do the mounting and unmounting, all the... (4 Replies)
Discussion started by: Texasone
4 Replies
5. Linux
Hello to everyone,
I am new to linux and I want to move to this system after bad experiences with windows.
I have also a particular problem. An old laptop is probably able to handle just linux at this point of its life.
The cdrom is gone, the bios doesn't have usb boot support, there is no... (6 Replies)
Discussion started by: highkftj
6 Replies
6. Red Hat
Is there a way to create a boot floppy for a fedora 13 system? Rescue disk image from the official boot.iso is too big. (1 Reply)
Discussion started by: druidmatrix
1 Replies
7. SCO
Anyone here using Unixware 2.x? I want to try some binary testing on this system regarding DG/UX binaries. (4 Replies)
Discussion started by: dgux
4 Replies
8. IP Networking
hi
I'm looking for absolutly a minimal Unix or Linux installed on just 1 boot floppy with dd and nfs client. (3 Replies)
Discussion started by: ccc
3 Replies
9. SCO
OS = Openserver 5.0.5
Ran 'mkdev fd' and made emergency boot floppy (boot and root). Choose custom kernel, not generic.
However kernel on the 1.44 floppy did not see both hard disks, it only saw the first one (SCSI id 0), and not SCSI id 1 (second disk)
Q. Is this a limitation of emergency... (5 Replies)
Discussion started by: grips03
5 Replies
10. SCO
In my previous thread post (which is also the most recent on this SCO forum), I mentioned that we have an HP DL380G5 server running SCO Unixware 7.11
which has unable to boot with error “FATAL BOOT ERROR: Can't load stage 3”.
..
Unfortunately no media is available for the machine and I think the... (1 Reply)
Discussion started by: BernP
1 Replies
LEARN ABOUT HPUX
bootconf
bootconf(4) Kernel Interfaces Manual bootconf(4)
NAME
bootconf - boot device configuration table
DESCRIPTION
The file contains the address and disk layout type of the system's boot devices or lif volumes. It is used by the and HP-UX kernel control
scripts (fileset to determine how and where to update the initial boot loader. Normally the kernel's script queries the system's hardware
and creates the file. In rare cases when either the system configuration cannot be automatically determined or additional and/or alternate
boot devices should be automatically updated, the administrator must edit the file manually.
There is one line in the file for each boot device. Each line contains the following blank-separated fields in the order shown:
disk type A flag indicating how the file system(s) on the disk are laid out. The flag must be one of the following:
Indicates that the root disk is in LVM or VERITAS Volume Manager
(VxVM) format. If LVM or VxVM mirrors are used, then each of the "mirrors" must have its own line in the file.
Indicates that the root disk is in the
"whole disk" format with no partitions, but boot and swap space are reserved outside the file system.
device file The absolute path of the device special file that accesses the physical device where the boot area is located. For LVM root
disks, the device special file is the physical volume(s) returned by the command. For "whole disks" this is the device file
that references the entire disk.
Blank lines are permitted. Any line beginning with a is considered to be a comment.
DIAGNOSTICS
The Software Distributor log file contains diagnostic messages under the fileset if the file is incorrect. Most of the messages are self-
explanatory; a few warrant additional explanation:
If there are no other messages about
the file is probably empty. Otherwise, the file is not in the proper format, and the other messages will explain what the problem
is.
The specified device file does not point to a disk where there is a
lif which contains the file
Some character other than
or is in the first field of a line.
As of release 10.0, the boot areas in
must all be on the same type of disk layout.
There are characters after the
device file specification.
EXAMPLES
The boot area is on an LVM root disk:
l /dev/disk/disk7_p2
The boot area is on a whole disk layout:
w /dev/disk/disk7
WARNINGS
All of the boot devices in the file must have the same disk layout.
AUTHOR
was developed by the Hewlett-Packard Company.
FILES
SEE ALSO
mediainit(1), hpux(1M), hpux.efi(1M), mkboot(1M), vgdisplay(1M), lif(4), intro(7).
documentation.
bootconf(4)