1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
|
<html>
<body bgcolor=#ffffff text=#000000 link=#4f4fff vlink=#0000ff alink=#00ff00>
<h1>Choose-OS errors</h1>
Here's a list of some special error conditions and descriptions.
Not all errors are listed here at all.<br>
<dl>
<dt>"<i>xxx <b>and</b> yyy <b>overlap.</b></i>"
<dd>Coordinates of some images/timer on the screen are over each other.
<p>
<dt>"<i><b>Invalid </b>xxx<b>-coordinate for </b>yyy<b>.</b></i>"<br>
"<i><b>Menu X coordinate invalid</b></i>"<br>
"<i><b>Timer coordinates invalid</b></i>"<br>
"<i><b>Invalid coordinates</b></i>"
<dd>A coordinate is out of range.
<p>
<dt>"<i><b>Loading... forced too low.</b></i>"
<dd>The message "<i><b>Loading </b>image_name<b>...</b></i>" was forced too low.
This is caused by coordinates of timer/some image beeing too low.
<p>
<dt>"<i><b>Hole in </b>xxx<b>.</b></i>"
<dd>There's an uncoverable hole (null-block) in a file.
<p>
<dt>"<i>xxx<b>: Not a Choose-OS binary.</b></i>"
<dd>A file doesn't contain a valid Choose-OS header.
<p>
<dt>"<i>xxx<b>: Incorrect version.</b></i>"
<dd>A Choose-OS binary is of incorrect version (i.e. not the same version as the installer)
<p>
<dt>"<i>xxx<b> is too big for a loader.</b></i>"
<dd>Loader module is too big.
<p>
<dt>"<i><b>Maximum number of loaders exceeded.</b></i>"
<dd>You are using too many different OS-specific loaders.
<p>
<dt>"<i><b>What iz thiz? Outta memory????</i></b>"
<dd>Believe me, this cannot happen unless your system really sucks.
<p>
<dt>"<i><b>Invalid harddisk geometry gotten.</b></i>"
<dd>There's something wrong with the harddisk geometry gotten from kernel.
<p>
<dt>"<i><b>Dunno how to handle device </b>xxx<b>.</b></i>"
<dd>A device is not a valid harddisk (IDE,SCSI or XT) or floppy drive.
<p>
<dt>"<i><b>(</b>xxx:yyy<b>): No such device in /dev</b></i>"
<dd>Choose-OS was unable to find a device in /dev.
<p>
<dt>"<i>xxx<b> internal error !!!</b></i>"
<dd>Internal errors are not likely to occur.
<p>
<dt>"<i><b>sizeof(</b>xxx<b>)!=512</b></i>"
<dt>"<i>xxx <b>is of invalid size</b></i>"
<dd>A file is of invalid size.
<p>
<dt>"<i>xxx<b> not compiled in. Please recompile.</b></i>"
<dd>A feature you're trying to use is not compiled in and you must <a href="misc.html#recompile">recompile</a> .
<p>
<dt>"<i>xxx<b>: kernel too big !</b></i>"
<dd>Kernel image is too big (doesn't fit in conventional memory). If it is a bzImage try using
<i>big_linux</i> instead of <i>linux</i>.
<p>
<dt>"<i>xxx<b>: Unknown header format - cannot load high.</b></i>"
<dt>"<i><b>Cannot support initrd - kernel header has unknown format</b></i>"
<dd>A linux kernel has unrecognized header format and therefore certain feature cannot be used. Probably an old kernel.
<p>
<dt>"<i><b>Couldn't find MemTotal in /proc/meminfo</b></i>"
<dd>There's something wrong with your system...
<p>
<dt>"<i><b>Initrd must be loaded above 2M</i></b>"<br>
"<i><b>For bzImage initrd must be loaded above 6M</i></b>"
<dd>You have given an invalid initial ramdisk load address.
<p>
<dt>"<i><b>Error resizing mapfile</b></i>"
<dd>You don't have enough disk space for mapfile?????
<p>
<dt>"<i>xxx <b>might NOT be accesible by thy bios!!!</b></i>"
<dd>With the geometries gotten from kernel the cylinder number for a sector in
a file exceeds 1023 and thus cannot be loaded with bios and may cause the system to be
unbootable. If your bios uses different geometries you may still have a chance.
<p>
<dt>"<i><b>THE SYSTEM MAY BE UNBOOTABLE</b></i>"
<dd>There has been a serious error condition and you might not even be able to boot
your system:
<ol>
<li>Try reinstalling.
<li>If it still doesn't work try changing the files and reinstalling.
<li>Try LILO
<li>Get some help. Do not turn off your computer.
</ol>
</dl>
</body>
</html>
|
