2 Loadlin Boot Questions

[nightsky]

Installed on old win98se Slackware12 am booting successfully with Loadlin, Linux.bat:
@echo off

smartdrv /C
c:\loadlin\loadlin c:\loadlin\vmlinuz root=/dev/hdg2 ro vga=3
intrid=diskimage

1. Is the intrid=diskimage necessary because of the large size of new kernels, ie. hugesmp.s 2.6.21,5?
I was readiing about latest loadlin and am not sure if the manual said I needed intrid because of large new kernels or intrid is written into loadlin.exe?

2. Suddenly a Loadlin+win95+win98+winme.pdb file appeared on my desktop. When I tried to view its context w/Notepad it was all code or gibberish, don't know wish? Can I delete this file?

Anyway I am up an running but using this intrid to boot if i don't have to use it might damage fiiles or system?

[kilgoretrout]

I haven't used loadlin in so long I've forgotten most of what I once knew about it. In general, however, an initrd is used to load modules necessary to complete a boot up, typically filesystem support and device support for hard drives on sata, scsi and other interfaces.

Modern kernels can have device support built into the kernel or have the support in the form of loadable kernel modules. However, in order to load these modules you have to be able to mount the root fileystem which is where these modules reside. The usual strategy followed by most distros is to compile a kernel with a ton of module support for a wide range of devices but have limited "built in" kernel support for devices. Now to get all your hardware detected during a boot, you need to be able to detect the hard drive where the root filesystem is located and you need to have support for the filesytem used. Since a lot of this stuff is typically module only supported you need to have a way to load the needed modules without mounting and reading them from the root filesystem. That's the purpose of an initrd. It gives you the modules needed to mount your root filesystem so you can load the other driver modules.
The slackware kernel is large because of the it was compiled with module support for a huge amount of hardware. The install routine detects your hardware and determines which modules need to be loaded. It also determines what needs to be in your initrd so the root filesytem can be mounted.

[nightsky]

Thank you kilogoretrout. Loadlin 16C is pretty gd, but I just did not understand the manual with all the parameters to pass stuff to slackware during bootup, ergo all the confusion. I just do not like messing with Windows MBR. I just want to rumage around in slackware till I learn how to run command line, edit, compile, and general usage. If I crash slackware I don't have to worry about windows, I can just reinstall slackware again and start over, each time I am a little ahead if I don't let too much time go by and forget everything I learned from previous install. lolol Thanks much.

[nightsky]

Update for those of u browsing for information... Loadlin is booting my slackware12 from win98se DOS.bat just fine. Initrid is only required with certain kernels