Bug 2388 - Broken file in CDRHi386 distribution: \dosutils\autoboot.bat
Broken file in CDRHi386 distribution: \dosutils\autoboot.bat
Status: CLOSED DUPLICATE of bug 3860
Product: Red Hat Linux
Classification: Retired
Component: aboot (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
: 3257 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 1999-04-27 17:00 EDT by Milan Kerslager
Modified: 2008-05-01 11:37 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-07-09 17:00:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Milan Kerslager 1999-04-27 17:00:14 EDT
Current \dosutils\autoboot.bat looks like this:

loadlin autoboot\vmlinuz

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 16:00:59 EDT
*** 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
(X being the cdrom drive letter).
Entering this at the root seems to run correctly.

------- Additional Comments From jbj@redhat.com  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 17:00:59 EDT
*** This bug has been marked as a duplicate of 3860 ***

Note You need to log in before you can comment on or make changes to this bug.