Bug 2388

Summary: Broken file in CDRHi386 distribution: \dosutils\autoboot.bat
Product: [Retired] Red Hat Linux Reporter: Milan Kerslager <milan.kerslager>
Component: abootAssignee: David Lawrence <dkl>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0CC: jsfhome, milan.kerslager, phil
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-07-09 21:00:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Milan Kerslager 1999-04-27 21:00:14 UTC 
Current \dosutils\autoboot.bat looks like this:

loadlin autoboot\vmlinuz
initrd=..\misc\src\trees\initrd.img

This sould be initrd=autoboot\initrd.img

Anyway file ..\misc\src\trees\initrd.img does not exist.
In directory ..\misc\src\trees you now have only files
initrd-local.img and initrd-network.img.
Comment 1 Jeff Johnson 1999-06-19 20:00:59 UTC 
*** Bug 3257 has been marked as a duplicate of this bug. ***

On installing after booting off the CDROM, I had found that
the AUTOBOOT.BAT INITRD.IMG is pointing to the wrong
directory. The directory it should be pointing to is as
follows:
X:\DOSUTILS\AUTOBOOT\INITRD.IMG.
(X being the cdrom drive letter).
Entering this at the root seems to run correctly.


------- Additional Comments From jbj  06/19/99 14:56 -------


*** Bug 3584 has been marked as a duplicate of this bug. ***

Trying to start up manually from DOS, I invoked the AUTOBOOT
script from the \DOSTOOLS directory, and LOADLIN failed to
find the appropriate kernel and ramdisk image.  Looking
around, I found apparently the only kernel and ramdisk image
on the CD, but they were in different directories than the
batch file was referencing.  Manually running loadlin with
the different paths allowed me to boot and install normally.
Comment 2 Jeff Johnson 1999-07-09 21:00:59 UTC 
*** This bug has been marked as a duplicate of 3860 ***