loadlin questions with RH7.1

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: Kevin Brown
Date:  
Subject: loadlin questions with RH7.1
Yes I was initiating the command from within c:\linux. Guess I should have said
that, heheh. I also tried the full path and it still gave that same error.
Doing this worked fine for RH6.2 to install. I didn't see any updates for
images on the VAlinux mirror, but it could be possible that there is something
wrong with them and since I can't get into RHs Ftp server I can't verify if the
mirror was up to date or not.

> > OK, downloaded the ISO for cd one from the local mirror that a plugger was so
> > kind to set up (sorry, don't remember your name, but thanks). Since I can only
> > have one peripheral plugged into my laptop at a time (cdrom or floppy or second
> > battery) I usually copy the files from the dosutils directory onto my c:\linux.
> > Then edit autoboot.bat to point to the right location (and verify the \ instead
> > of / for paths). I run autoboot.bat and loadlin spits back "not an Image file"
> > ...
> >
> > Autoboot.bat initially said:
> > loadlin autoboot\vmlinuz initrd=autoboot\initrd.img
> >
> > both files exist and comparing the sizes of them to the one on VAlinux's mirror
> > shows them to be the same size. I tried various things like:
> >
> > loadlin autoboot\initrd.img
> > loadlin autoboot\vmlinuz
> > loadlin autoboot\boot.img --> (copied from the images directory)
>
> Your default directory is c:\linux when you issue the loadlin command,
> right? If not, add "cd c:\linux" to autoboot.bat before loadlin.
>
> I found a couple messages suggesting you need to include the full path
> name, as in:
>
> loadlin c:\linux\autoboot\vmlinuz initrd=c:\linux\autoboot\initrd.img
>
> That makes sense (to me) in a goofy, DOS-like way. If loadlin was
> reading the directory instead of the image, it should say "not an image
> file". I can't seem to find the source for loadlin.exe - must sleep...
> If that doesn't work I'd try to get the source to find out exactly what
> prompts that message.