Administrace komentářů

As explained earlier, many components in the boot sequence can produce rather cryptic error messages. This is mainly for reasons of restricted space, and possibly to avoid problems producing national language variants. Messages are generally of the form SYSxxxx, where xxxx is a standard OS/2 error number. If a working OS/2 system is available, simply type the command: HELP SYSxxxx

or just: HELP xxxx at a command prompt, obviously replacing the xxxx with the appropriate number. Many of the more common boot time error messages are explained here.

SYS01462 The partition table on the startup drive is incorrect. Generally, this means either that more than one partition is marked active, or one of the partitions has a status byte with a value other than 00H or 80H, which are the only legal values.

SYS01463 The operating system cannot be loaded from the startup drive. This is caused by a disk read error, while reading the boot sector of the active partition.

SYS01464 The operating system is missing from the startup drive. A valid boot sector for a partition should contain the values 055H and 0AAH in its last two bytes, in that order. This is a simple validation check, intended to prevent attempts to boot from a corrupt or unformatted partition. This message is generated if the validation check for these two bytes fails.

SYS01475 The file OS2BOOT cannot be found. OS2BOOT is the second stage boot program, and it must be present on a bootable partition; it may be a hidden file. This message appears if the directory entry for OS2BOOT cannot be found in the root directory of the boot drive.

SYS02025 A disk-read error occurred. This means exactly what it says. There was an error (generally hardware) while attempting to read the disk during the loading of OS2BOOT, the second stage boot program.

SYS02027 Insert a system diskette and restart the system. This is merely an advisory message.