Remember, the IO is basically a standard pentium class PC with a standard BIOS and a 16MB flash memory card. Please read some of the messages in the "Technical" area on the I-Appliance Discussion Forum BBS, you will find many posts there talking about different OS's and how other installations went.

Booting into Linux is easy, all you need is a recent copy of Penguin (the booter) and a kernel. (Both of which can be found on this site under "Downloads".) Before you can boot into Linux, you will need to turn off Virtual Memory and you may need Mode32 (see the section on Mode32, later). Start up Penguin, select the kernel that you want to boot from in the configuration screen, and then use the boot option from the file menu. If it works, you'll get a message about rarp requests.

You looked at the status web page and your machine was supported. But it just won't boot! Why not? Well, there are a few common problems that cause most of these failures. The most common one is that you're trying to use an ancient kernel that doesn't properly support your hardware. You should always be using the latest kernel, unless you have a really good reason not to. Other common problems are less obvious.

No. (Older dmsdos versions supported it, but this feature has been given up when the CVF-FAT interface was introduced. Well, the documentation always warned ... ) What can I say. You decided to use compressed partitions - now you are experiencing one of their greatest disadvantages. But dmsdos has some special tricks for you in this case. You can..

Either by typing the kernel arguments at the BOOT lilo: prompt, or by adding an ''append='' directive to the /etc/lilo.conf file; for example: At the LILO prompt (example only): BOOT lilo: parport=0x3bc,7 parport=0x3bc,none serial=0x3f8,4 serial=0x2f8,3 If you modify the /etc/lilo.conf file, be sure to run the lilo command to install the new configuration.

The floppy might have bad sectors on it, use a different floppy (one w/o bad sectors). See previous for creating a Linux boot-disk under DOS. See Q. 52 for creating bootdisks. Yes! This card is supported under Linux but the drivers are not currently part of RHL 6.2. You can get the source from here: http://www.scyld.com/network/ethercard.html

If LILO doesn't work, and if the machine has MS-DOS or Microsoft Windows, you may be left with a computer that won't boot. This can also happen on an upgrade to your Linux distribution. Re-installing LILO is the last thing that the installation does. So it is vitally important when installing or upgrading Linux on a dual boot machine, to have a MS-DOS or Windows rescue disk nearby so you can FDISK -MBR. Then you can go about using LOADLIN.EXE instead of LILO.

If you have FreeBSD and Linux on the same disk, just follow LILO's installation instructions for booting a non-Linux operating system. Very briefly, these are: Boot Linux, and add the following lines to /etc/lilo.conf: other=/dev/hda2 table=/dev/hda label=FreeBSD the above assumes that your FreeBSD slice is known to Linux as /dev/hda2; tailor to suit your setup). Then, run lilo as root and you should be done. If FreeBSD resides on another disk, you need to add loader=/boot/chain.

If LILO doesn't work, and if the machine has MS-DOS or Microsoft Windows, you may be left with a computer that won't boot. This can also happen on an upgrade to your Linux distribution. Re-installing LILO is the last thing that the installation does. It is vitally important when installing or upgrading Linux on a dual boot machine, to have a MS-DOS or Windows rescue disk nearby so you can FDISK -MBR. Then you can go about using LOADLIN.EXE instead of LILO.

Most Linux distributions support directly booting a Linux kernel from CD as an alternative to a boot floppy. This requires a bootable CD and ROM BIOS and CD-ROM drive which supporting booting from CD. The latest version of mkisofs supports creating such disks using the El Torito standard for bootable CDs.

ADB) Because it doesn't need one. You can add that feature to the boot loader code, if you want to. The Linux kernel has no graphics primitives, just like any UNIX kernel.

The ADIOS development kit (adk) uses a Makefile which you copy from /mnt/cdrom/adk to /root or whatever directory you want to use. The adk software assumes you have already installed the ADIOS kernel on you linux system. This can be done using the hidden commands from the run options menu, read the notes on how to install ADIOS manually by resizing an existing NTFS partition from http://os.cqu.edu.au/adios/ntfsresizing.html OR You could download the ADIOS kernel source code from http://os.cqu.

Yes you can. But if your hard disk is small it won't give you what you expect. You'd better choose the best operating system and work only on it. Don't ask which operating system !

Refer to the section "Making Installation Diskettes" from the RedHat Linux Installation manual at http://www.redhat.com/support/manuals/RHL-7.1-Manual/install-guide/

Yes, you can define two different run level for this (under SysVInit) in /etc/inittab. One run level includes the ISDN processes, where the other one does not.

Install LILO at the start of your Linux boot partition instead of in the Master Boot Record. You can then boot LILO from BootEasy. If you are running Windows® 95 and Linux this is recommended anyway, to make it simpler to get Linux booting again if you should need to reinstall Windows 95 (which is a Jealous Operating System, and will bear no other Operating Systems in the Master Boot Record).

EasyBCD can hook into an existing GRUB installation without any user intervention - just point it and it'll do the rest. If you're GRUB isn't already properly configured though, take a look at this sample configuration file for just about everything you could need. Nope. EasyBCD is a very special and unique application in that it doesn't even touch your bootsector or MBR, yet it's still the most powerful bootloader on the planet! Vista installs the "BCD Bootloader" to your MBR and Bootsector.

The best way to learn how to do those things is choose a distro that comes with a bootloader, and then read their documentation.

Format the partition under OS/2, either with FAT or HPFS. This is so that OS/2 knows about the partition being formatted. (This step is not necessary with OS/2 'warp' 3.0.) Boot Linux, and create a file system on the partition using mkfs -t ext2 or mke2fs. At this point you may, if you like, use Linux's fdisk to change the code of the new partition to type 83 (Linux Native)-this may help some automated installation scripts find the right partition to use.

DISCLAIMER: Messing around with boot loader issues can make your harddisks unbootable. Please make backups before doing so. Please install a new boot loader only when you really now what you do. We reject any responsibility for damages that may occur on your system. GRUB - the GRand Unified Bootloader - needs to access some files in order to run. Its best you place them on a small - 50MB is enough even for further extensions - FAT 16/32 partition.

Format the partition under OS/2, either with FAT or HPFS. This is so that OS/2 knows about the partition being formatted. (This step is not necessary with OS/2 'warp' 3.0.) Boot Linux, and create a file system on the partition using mkfs -t ext2 or mke2fs. At this point you may, if you like, use Linux's fdisk to change the code of the new partition to type 83 (Linux Native)—this may help some automated installation scripts find the right partition to use.

Yes, and this is only a bit more complicated. You'll need to read the bits on installing, later. Still, follow the steps above to make sure that Linux will work for you in the first place.

Add something like this to your /etc/lilo.conf file under linux and rerun /sbin/lilo. Note that Solaris *MUST* be the active partition, on either the primary or another another hard drive. To use LILO with Solaris on the primary partition, install LILO in the MBR and mark the solaris partition as active. In this example Solaris is on your second hard drive (hence the "loader" line): other = /dev/hdb1 loader = /boot/chain.

Starting with Unattended 4.0, we are shipping a Linux boot disk in addition to the DOS boot disk. Note that this is not for installing Linux; we are simply booting a custom diskless Linux system to initiate the installation of Windows. The Linux boot disk is quite mature now, and it works a lot like the DOS boot disk. It runs the same Perl code, in fact, which we think is kind of neat. At present, it only supports booting from CD-ROM (using the linuxboot/linuxboot.

Yes, and if it does not work for you, we are very interested in fixing it. The boot disk uses Linux kernel 2.6, which is still maturing. One common problem is with ACPI support in Linux, which is under very active development. If the boot disk has trouble with your hardware, try booting with ACPI support disabled. Hold down the Shift key while booting, which will present a boot: prompt. Then type unattended acpi=off and press Enter.