Last updated on 2015/2559 9 28, a full moon day;     map;

Approx. 12+ maps available to read;

Bitmapped *.bmp;

CLM (Collaborative Linkage Map);

Sys . Domain;

map     map;

mapping all nuclear plants as dots on screen surface in the Internet;
mapping all nuclear powered of civilizations ... ;

this DOMAIN 's one of the policies: since 2011, this DOMAIN has mapped all nuclear plants as dots on screen surface in the Internet, and civilizations' all nuclear power must be demolished, ended, finished, in 21st century; alternative solution will be: power from Fusion plants (e.g. Solar, Tidal, Wind, ... ); this DOMAIN has been developed for peaceful and tranquil purpose only, therefore, NOT Laser focus (e.g. motor way laser, wormhole way laser) onto any nuclear plant yet from its Satellite DNS System; if demonstration is necessary to prove (e.g. laser focus, and then pinpoint, and then launch), and then IT will be consecutive nuclear explosions one-after-another in our earth for sure i.e. beyond Manmade Global Weather ... ; all civilizations should change power from nuclear to fusion;

MCM (Multi Context Map);

Sys . Domain;

Memory mapped: *.pq;

Network drives mapped: Unformatted disk (s) must be formatted first e.g. $p$g; formatted disk (s) provides file systems to be used; partition to the disks prompts limit volume and provide identity, e.g. C: , D: , ..., as identities of drives [drive letters], and each property informs available storage space, and type of file system; Depending on OS setup (e.g. size), drives can be categorized such as SHARED, NOT SHARED, SYSTEM, and etc. OS implements directories on the networked drives, and mapping of drives provides available and allowable paths to work in a workgroup, inside a domain, through a forest, and etc. Basically, network drives can be mapped and utilized as Absolute Path, and Relative Path, WHERE relative path does not define drive letters, protocol used, and etc. , on the other hand, absolute path defines drive letter, protocol used, and etc. IFF hardware, also see: super capacitor; IFF software also see: 12 alphanumeric;

PBM Any map: *.pnm;

PBM Gray map: *.pgm;

PBM Pixmap: *.ppm;

Register map: Before understanding WHAT is register map, memory must be understood; To understand memory, memory space must be understood e.g. 0 ~ ((210) -1) similar to 0 ~ 1023 similar to 100x000h ~ 0x03FFh; WHY memory space? because Harvard architecture is faster than von Neumann architecture, because in Harvard architecture, microcontroller (e.g. Hitachi chip, NEC chip, Sharp chip, SONY chip, ... ) has been divided into data-memory and program-memory, and each memory uses each bus; Because, von Neumann architecture uses one bus for both data-memory and program-memory; After understanding memory space, WHICH partitioned space (a.k.a. bank, 2 banks, for example in assembly language, programmer commonly set register status (TRUE) by using opcode (opcode a.k.a. mnemonic address) MOVE among banks) must be understood; Such memory space switching provides interrupt-vector, therefore 2 banks with 2 available addresses may have 2 interrupt-vectors, 4 banks with 4 available addresses may have 4 interrupt-vectors, 8 banks with 8 available addresses may have 8 interrupt-vectors, and so on ... ; WHEN return address is saved, accordance with program-counter's set location in memory, software program execution run time continues ... ; The most difficult for programmers is engineering compiler (s); To program a compiler, advance programmers must understand hardware thoroughly;


X Bitmap: *.xbm;

X Pixmap: *.xpm;

Note: notice that some *map* are in file/FS, and some are not.