There may be several other reasons for that particular output but the only time it has happened to me is when lilo can't find the OS (i.e. it's looking for something in a bootsector that's not there). Perhaps booting to VL with your diskette and then manually editing the /etc/lilo.conf to load in the MBR and to point at the appropriate places for VL and W95 would solve the problems.HTH,Mike

Logged

The plans of the diligent lead to profit...Pro. 21:5 VL64 7.1 RLU 486143

When the first stage loader gets control, it types the letter "L"; when it is ready to transfer control to the second stage loader it types the letter "I". If any error occurs, like a disk read error, it will put out a hexadecimil error code, and then it will re-try the operation. All hex error codes are BIOS return values, except for the lilo-generated 40, 99 and 9A. A partial list of error codes follows:

Thanks for the replies... I already know that both systems works (win95 with the original MBR and VL when it is booted with a diskette and pointed to "root = linux /dev/dhb1/ ro").Would you have any idea why then the lilo record which VL tries to write results in the error 40? I've looked at various posts about editing lilo.configuration file, but it does not seem that there are any variables which control WHERE this lilo boot record will physicall go). It seems that in my case the problem is not so much with "what" is in the lilo boot record but rather "where" BIOS is attempting to seach for the boot record. Any ideas?Thanks.

If you want lilo in the MBR of /dev/hda then you would modify the line /etc/lilo.conf as Joe1962 had indicated but there are other options if you didn't want lilo to be the "master" boot manager. There are several other posts about using other boot managers with Windows and Linux on the forum. One recent such thread discussed bootpart (http://www.vectorlinux.com/forum2/index.php?topic=1073.0). Another is here: http://www.vectorlinux.com/forum2/index.php?topic=487.0. Perhaps these will be of some use to you if you have not already perused those threads. As far as where you BIOS is looking it would seem to have found a broken lilo install and lilo is generating the output that you have received.HTH,Mike

Logged

The plans of the diligent lead to profit...Pro. 21:5 VL64 7.1 RLU 486143

To add a choice to the posts above, you can boot the VL install cd, and there is an option at the install programm to fix lilo. It works for me, but you need to write the MBR in the rigth HD, or as Joe suggested, change your BIOS settings to match the lilo config.

Logged

"There is a concept which corrupts and upsets all others. I refer not to Evil, whose limited realm is that of ethics; I refer to the infinite."Jorge Luis Borges, Avatars of the Tortoise. --Jumalauta!!