Install CD Issue

Oh yeah, i forgot to include, i am using the i386 release.

Forgot to say, if this clears things up: It happens right after i hit any button (but memtest86+) on the CD menu.

I'm not too sure how to edit bug contents, but i just used everest, and the chipset from that is said to be:
ATI Radeon Xpress 200/1100/1150

http://lkml.org/lkml/2006/10/21/194

and maybe

http://lkml.org/lkml/2006/9/21/104

Those sources might help (but all other people getting this error only occurs on ancient computers...)

http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/7126aa46fde16a9e/b5ba1bc1d5e0fe5a%23b5ba1bc1d5e0fe5a

http://groups.google.com/group/linux.kernel/browse_thread/thread/e270d5b1a1974edc/d0f11e2e82370700%23d0f11e2e82370700

Same things but with different responses...

I don't know if this has anything to do with it:

http://www.ravenbrook.com/project/mps/master/code/protlii3.c

[startcode]
/* Interrupt number 14 is Page Fault. */
#define TRAPNO_PAGE_FAULT 14
[endcode]

or maybe this?
http://www.greenend.org.uk/rjk/2002/02/lostinterrupt.html

[startquote]
Interrupts have numbers: on a normal PC, interrupt number 14 is used by the first IDE bus (/dev/hda and /dev/hdb) and interrupt 15 by the second IDE bus (/dev/hdc and /dev/hdd). So when the kernel receives interrupt 14 it only checks the first IDE bus; when it receives interrupt 15 it only checks the second.
[/endquote]

Most other sources say its a pagefault
[startquote]
......(interrupt 14) is triggered when the processor attempts to access a page, which is marked as not-present.
[/endquote]

From http://www.delorie.com/djgpp/doc/ug/interrupts/inthandlers2.html

[startquote]
       So, what seems to be the problem? Well, the problem can be the demand paging itself. If, during the process, the paging unit determines that the required page table or the page itself is externally stored (swapped), then the i386 issues an interrupt 14 (0eh). Normally, this offers no trouble whatsoever as the operating system (or in our case the DPMI host) can load the respective page or page table into memory and resume its operation. However, this should not be done during the execution of an interrupt handler because DOS is a non-reentrant operating system. If an interrupt handler, any other functions it invokes or any variable it touches is swapped out then a page fault (exception 14) might be issued and your program goes to the little fishes...

       The solution, as you may have guessed, is to 'lock' the memory regions that must be available, telling the DPMI host to keep them in active memory at all times. This can be done with the Djgpp library functions '_go32_dpmi_lock_code()' and '_go32_dpmi_lock_data()'. How do you use them? It depends on the circumstances.
[/endquote]

In conclusion, I really don't know whats going on and i'm hoping a developer can sort this out for me.

Ubuntu works fine now, it seems that my BIOS was out of date and a simple BIOS update made ubuntu work. (Maybe this shouldn't be rejected? because of other people who may be using old BIOSes)