<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META content=text/html;charset=iso-8859-1 http-equiv=Content-Type>
<META content='"MSHTML 4.71.1712.3"' name=GENERATOR>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT color=#000000 face=Arial size=2>Ola</FONT></DIV>
<DIV><FONT color=#000000 face=Arial size=2></FONT> </DIV>
<DIV><FONT color=#000000 face=Arial size=2>After seeing the Go32 V1 code I
noticed that the paging mechanism is based on exceptions. This approach means,
that each time RTEMS uses for the first time a page, GO32 <FONT
color=#000000>switches </FONT>to Real Mode, pages the memory, and switch back to
protected mode. Has I understand, this behavior is not consistent with a RTOS
like RTEMS.</FONT></DIV>
<DIV><FONT color=#000000 face=Arial size=2></FONT> </DIV>
<DIV><FONT color=#000000 face=Arial size=2>Is this problem addressed in the new
version ?</FONT></DIV>
<DIV><FONT color=#000000 face=Arial size=2></FONT> </DIV>
<DIV><FONT color=#000000 face=Arial size=2>If in the new version the intention
is to use the Version 2 (<FONT color=#000000>which </FONT>uses a DPMI server),
the problem is still present. Don't you think that is a good idea to have a
small program in DOS that loads the RTEMS and after that is RTEMS that is
responsible of configuring the system and switching to protected mode, maybe
using the code for the FORCE386 BSP?</FONT></DIV>
<DIV><FONT color=#000000 face=Arial size=2></FONT> </DIV>
<DIV><FONT color=#000000 face=Arial size=2>Maybe I'm behind <FONT
color=#000000>scheduling </FONT>and this approach is used in the new
version</FONT></DIV>
<DIV> </DIV>
<DIV><FONT color=#000000 face=Arial size=2>Cumprimentos</FONT></DIV>
<DIV><FONT color=#000000 face=Arial size=2></FONT> </DIV>
<DIV><FONT color=#000000 face=Arial size=2>J. Carlos</FONT></DIV></BODY></HTML>