Click to See Complete Forum and Search --> : Booting BigSlack


Xprotocol
08-02-2001, 06:06 PM
I downloaded BigSlack because I wanted to be able to run Linux without repartitioning or formating to optimize space and better work with Windows. Anyways, I have an ASUS A7V motherboard which comes with four IDE ports. The ATA-100's are where I hook-up my HD's. Well, these ports use a Promise Ultra ATA 100 controller which stops most Linux distros from seeing my HD's by default. Now, when ever I boot BigSlack I get a Kernal Panic error as well as a VFS error that it can't find device on 8:04. Now, the 8:04 referes to the 4th partition on a SCSI drive, so I just changed some data around in the linux.bat file and all that happened was the number changed to 3:something. I boot BigSlack by rebooting into DOS mode, browsing to the linux directory on my C: drive, and typing linux which executes the linux.bat file. Here is the only executed line of code from this file, the rest is REMed out:\linux\loadlin \linux\vmlinuz root=/dev/hda1 rw vga=791 Now, BigSlack thinks hda1 is where my copy of BigSlack is. Well, it is and it isn't. Linux sees hda1 as my CD-ROM drive which is not using the promise controller. But hda1 should technically refer to the first HD on my system. Is there anyway I can edit the contents of the linux.bat file so that BigSlack knows where it is? Here's some output about my first HD that BigSlack gave when trying to boot:ide0
0x1f0-0x1f7, 0x3f6
0xd800-0xd807
Thanks for your help.