Comments to the special version of pC/OS 1.00
---------------------------------------------- 

additional to the memory-typ OS_FAR current in the 
original-uC/OS still is the type OS_HUGE in this variation 
implemented, since for example with Intel-CPUs (& devirate) 
the problem of the segmentation of the RAM at areas over 
a 64kB-border away otherwise to the storage access on the 
segment beginning leads. 

Detail: (tested in the SMALL-Model)

NEAR-data	- only within the direct 64kB data-segment 
FAR-data	- over entire storage however not over 64kB segment frontiers away 
HUGE-data 	- over entire storage as linear address area 

There pointers doesn't standardize from the processor is returned, 
the address of an allocated storage area with a size of several kB 
can be returned consequently so: 0x0100: 0xFF58. 
Since becomes with OS_FAR-access of only the offset incremented, 
an access to the elements array[169....] is no more possible, 
since instead the processor on the address 0x0100: 0x0000 for 
the first byte after the segment border grabs etc. 

Through the HUGE-management of pointers within the pC/OS can be used, for 
example, following memory management (Am188ES) consequently: 

0xFFFF : 0xFFFF     ____________________
                   |                    |
                   |     flash-ROM      |    256kB
                   |      (CODE)        |
                    -------------------- 
                   |                    |
                   |                    |
                   |      EE-PROM       |    256kB
                   |   (File-System)    |
                   |                    |
                    -------------------- 
                   |                    |
                   |                    |
                   |        sRAM        |    448kB
                   |                    |
                   |   ( memory Pool )  |
                   |                    |
                   |                    |
                    --------------------
                   |     NEAR data      |    64kB
                   |      segment       |
0x0000 : 0x0000     ====================     INT-vector table

With it can the Arrays for Queue and Pipe also in the SMALL-Model of 
the code through OS_MemAlloc... is positioned within the memory pool 
administered through the Kernel, that can be 64kB bigger. 