Sponsored Content
Operating Systems SCO unixware 7.1.0 boot floppy #2 needed if someone has one. Post 302256365 by RDP on Sunday 9th of November 2008 01:44:59 PM
Old 11-09-2008
unixware 7.1.0 boot floppy #2 needed if someone has one.

Hi all,
I'm reinstalling unixware 7.1.0 on another machine for a customer that will replace the existing machine that is now in use. When i go to start the install the second floppy is not recognized. These are the original sco floppies.

I have recreated the boot floppies from the CD and same thing. First one boots fine second it not recognized.

I went to APlawrence's site and used the link to download the images from Caldera's FTP site. Same thing. One is fine and second is not.

Just to test my equipment (floppies and floppy drive) I downloaded the 7.1.1 boot disks and they worked fine. These are the same floppies and the same floppy drive that I used for the 7.1.0 disk images (same version of rawrite) but whenever I try to use the 7.1.0 images it never sees the second disk.

Could there be a bad img on the ftp site? Even if that is true how could the image on the CD be bad?

I originally thought it would be a hardware problem but the 7.1.1 disks boot fine. I've deleted and recreated them 3 times and they always work.

Anybody ever have this issue before?

Does anyone have a working img2 boot disk for 7.1.0 that they could image with rawrite and send me? If so please shoot me a PM.



thanks
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

boot floppy

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

red hat linux installation boot floppy disk

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

Boot Floppy

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

Boot Floppy made in external drive

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

How to install linux in a system without cdrom, usb boot, floppy, other OS?

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

boot floppy for fedora 13

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

UnixWare 2.x needed

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

Boot Floppy with dd and nfs cleint

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

Emergency boot floppy - second hard disk not seen

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

Need emergency boot CD UNIXware 7.1.1 (or 7.1..4)

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
MKRESCUE(8)						      System Manager's Manual						       MKRESCUE(8)

NAME
mkrescue - make rescue floppy or CD SYNOPSIS
/sbin/mkrescue makes a bootable rescue floppy or CD using the default kernel specified in lilo.conf. DESCRIPTION
mkrescue takes its specifation for the kernel from the default image specified in /etc/lilo.conf. If the actual default is an other= spec- ification, then use the first image= specification. Any associated initial ramdisk (initrd=), and append= options will also be used. The root directory will be taken to be the current root. A bootable floppy or CD-image will be created using LILO version 22.5.5 or later. mkrescue normally requires no options, unless a CD-image is desired (--iso). OPTIONS
--append <string> Override any append= options taken from the default image. If there is any doubt about whether the lilo.conf options are correct, then specify no kernel parameters by providing the null string (--append ""). --debug Provide verbose output of the operation of mkrescue, pausing to allow the setting of internal operating parameters to be viewed. <CR> must be hit to proceed from these pauses. --device <device> Make the floppy on a device other than /dev/fd0. The floppy disk will always be made to boot on BIOS device code 0x00 (A: drive), without regard to the drive on which it is created. --fast Use a faster method of creating the boot floppy. This involves first creating a file of --size 1k blocks (default is 1440) mounted using a loopback device, creating the bootable floppy, then copying the entire file to the disk. --fs [ ext2 | msdos | minix ] Specify the type of filesystem to create on the drive. ext2 is the default, but msdos and minix allow slightly more disk sectors for really big kernels. --help Print a short usage synopsis, including a list of command options. --image <label> Specifies the label or alias of the particular image from which the append, initial ramdisk, root, keytable, and kernel information is to be taken. --initrd <filepath> and --kernel <filepath> These options, which must be used together, allow specification of an arbitrary kernel file and initial ramdisk file to be used on the created boot floppy. Be sure you know what you are doing before you use these options. If no inital ramdisk is needed with a particular kernel, then you MUST specify --initrd "", meaning a null pathname. --install [ text | menu ] Allows overriding the default human interface used with the rescue bootloader (configuration file "install=" option). text is the default on 1.2MB and 1.44MB floppy disks, and menu is the default on 2.88MB floppies and HD emulation on CD-R media. --iso Create an ISO-9660 bootable CD image (El Torito Format) suitable for burning to a CD-R or CD-RW. The --device specification defaults to the filename rescue.iso, and the --size defaults to 2880. A utility such as "wodim" may be used to burn the ISO file to a recordable CD medium. With this ISO option, the --size HD option is allowed. --nocompact For faster kernel loading from a floppy, LILO map compaction is normally enabled. This option will disable map compaction by omit- ting the lilo -c switch. --noformat Suppresses creation of a new filesystem on the boot floppy. This option may be used ONLY when you know that the floppy you will be writing upon is formatted with the same filesystem as specified by --fs XXX (default is ext2). --root <device> Specify the root filesystem for the kernel on the boot floppy. The currently mounted root is taken as the default specification. --size [ 1440 | 1200 | 2880 | HD ] The default floppy disk size is 1440, meaning a 1.44MB floppy. When --iso is specified, the default size is 2880. Allowed specifi- cations are 1200, 1440, or 2880, meaning a 1.2MB, 1.44MB or 2.88MB floppy, respectively. No other floppy disk sizes are supported. The HD specification, meaning "hard disk", may only be used with the --iso option, to indicate a 16MB hard disk is to be generated for emulation. This allows for very large kernel/initial ramdisk combinations on CD-R. The hard disk image is created using loop- back devices /dev/loop0 and /dev/loop1, which must be free to utilize this size option. --version Print the version number of mkrescue, then terminate. SEE ALSO
cdrecord(1), dd(1), wodim(1), lilo.conf(5), lilo(8), mkfs(8), mkinitrd(8), mkisofs(8), mount(8) 6 Mar 2011 MKRESCUE(8)
All times are GMT -4. The time now is 08:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy