I am trying to install eCS 2.1 on my ASUS L3000D laptop.
After rebooting from the hard disk, I got the message "SYS 1475: The file OS2BOOT
cannot be found"
Airboot 1.07 boots Win XP well. On the Italian newsgroup they said that Airboot 1.07 is faulty...
Thank you for your help.
Usually, this occurs when some aspect of the partitioning scheme being used is not properly accessible by the mini file system drivers incorporated into the kernel, or when OS2BOOT or OS2LOADR are not in the location they are expected to be in.
In the case of the first, it means correcting something in the MBR/AirBoot stuff, or correcting something in the partitioning scheme. For both/either, dfSEE can be helpful.
In the case of the second, if the program is available (and I haven't checked my eCS 2.1, so I don't know), booting off the CD and running SYSINSTX BOOTDRIVE: may resolve the issue (inotherwords, you'd run something like this from a cmdline session started from the install CD...
"SYSINSTX C:")
Generally, it was located on the installed bootable partition (ie, Drive C or wherever you installed) in \OS2\INSTALL\BOOTDISK - as well as on the install CD/CDs someplace.
The only other things I can think of are the following (this is all pre-coffee senility, so excuse any errors):
- the drive is partitioned to something too large to boot off of. This is probably not likely, unless some backleveled drive/LVM/kernl support is in use. But,
previously you would be limited to a 500GB
DRIVE for your boot drive (yes, drive - not partition) or a drive where only 500GB was partitionable - otherwise OS/2 and eCS will not boot. Again though, that limitation has supposedly been removed
- The boot partition is HPFS and is either near or larger than the 64GB limitation imposed by HPFS. I never ever use an HPFS partition over 50GB - doing so can cause all sorts of issues, this occasionally being one of them (including, oddly, sometimes on a system that has worked for ages).
- The IDE/SATA driver has the wrong switches being used for the chipset (or isn't fully compatible) - this will create the following scenario: (1) the mini-FS driver WILL start the boot process and run OS2LOADR & OS2BOOT - BUT, when it does the handoff to the IDE/SATA drivers and the "real" file system drivers (ie: HPFS.IFS and/or JFS.IFS), then suddenly things go wrong, because the driver/fs driver combination isn't accessing the disk correctly. Keep in mind, certain things like OS2LOADR are actually needed beyond the boot process, and OS2BOOT is needed up to and
during boot for the kernel handoff.
Hope that helps point you in the correct direction
Rob