OS/2, eCS & ArcaOS - Technical > Programming
OS/2 Architecture Graphic
Martin Iturbide:
Thanks Dave.
I had updated the graphic. I was also advised that SOM does not depend on Presentation Manager, so it should not be a layer up the PM.
Let me know if this is a more adequate one.
Dave Yeo:
Looking better. I notice that you don't have OS/2 Full Screen Session in your graphic, should be beside Presentation Manager as a full screen program can run independent of the PM in its own session and can manipulate the graphics controller independent of the PM. Often they were also the "family class" of programs where the same binary could run under DOS or OS/2.
Examples of using full screen graphics with EMX are the vesa library http://hobbes.nmsu.edu/download/pub/os2/dev/emx/contrib/vesa19.zip and the svga library http://hobbes.nmsu.edu/download/pub/os2/dev/emx/contrib/svgakt19.zip and of course there was/is XFree86 where we could run the exact same X drivers as *nix.
One other point is that some consider the "control program" to be part of the kernel with some of it contained in the kernel and some of it in doscall1.dll. From what I understand, doscall1.dll can be considered part of the kernel depending on your viewpoint.
Martin Iturbide:
Hi Dave
I agreed that I miss a "OS/2 Full Screen Session" component to represent that command line applications can run over it and not over CPI. But does the "OS/2 Full Screen Session" has other name? which are the parts, exe, DLLs of that component?
Thanks for the feedback.
Dave Yeo:
I'm not aware of a better name then "Full Screen Session". The components can be pretty minimal, especially for a text mode application running on a FAT drive, basically the kernel and DOSCALL1.DLL along with the various device drivers and supporting DLLs needed to come up to a command line. Examples are the first couple of install floppies or the util disks that used to be able to be created from system setup.
An example is TEDIT.EXE which depends on DOSCALL1, SESMGR.DLL, KBDCALLS.DLL, NLS.DLL and VIOCALLS.DLL and I guess cmd.exe.
It's nice to also have something to set up the printer spool and a minimal shell such as tshell (also has hints for running in 4MBs of memory) http://hobbes.nmsu.edu/download/pub/os2/util/shell/tshell.zip to allow changing sessions and even DOS support.
Martin Iturbide:
--- Quote from: Dave Yeo on November 25, 2014, 06:47:43 pm ---One other point is that some consider the "control program" to be part of the kernel with some of it contained in the kernel and some of it in doscall1.dll. From what I understand, doscall1.dll can be considered part of the kernel depending on your viewpoint.
--- End quote ---
Opps... I don't have a viewpoint of that :) I'm limited by my knowledge on this subject.
Here goes the updated graphic with the "Fullscreen Session".
Navigation
[0] Message Index
[*] Previous page
Go to full version