Path: news1.icaen!news.uiowa.edu!iagnet.net!199.0.154.56!ais.net!uunet!in5.uu.net!munnari.OZ.AU!news.mel.connect.com.au!news.labyrinth.net.au!news.alphalink.com.au!not-for-mail From: "Lazy Bone" Newsgroups: alt.c64,comp.sys.amiga.emulations,comp.sys.amiga.programmer,comp.sys.amstrad.8bit,comp.sys.apple2,comp.sys.atari.8bit,comp.sys.cbm,comp.sys.m6809,comp.sys.msx,comp.sys.oric,comp.sys.sinclair,comp.sys.tandy Subject: Codename GENOS (was Codename G-OS) Mail 3 Date: 8 Oct 97 19:41:05 -0900 Organization: Badly Configured Clients, Inc. Lines: 153 Message-ID: <343BE1D1.MD-0.198.zhulien@alphalink.com.au> NNTP-Posting-Host: ppp28-5-3.alphalink.com.au Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Newsreader: MicroDot-II/AmigaOS 0.198 Xref: news1.icaen comp.sys.amiga.emulations:59952 comp.sys.amiga.programmer:118788 comp.sys.amstrad.8bit:8921 comp.sys.apple2:125755 comp.sys.atari.8bit:48937 comp.sys.cbm:77267 comp.sys.m6809:3322 comp.sys.msx:5037 comp.sys.oric:725 comp.sys.sinclair:46726 comp.sys.tandy:22144 Hi everyone. G-OS now GENOS ============== I mentioned in the previous mail that someone pointed out the similarity between the name 'Codename G-OS' and the product 'GEOS'. Because no similarity was intended, the name for or generic OS, will be now called 'Codename GENOS' until a better name can be found. If you have a suggestion, let us all know. MAILING List and Feedback ========================= Most email software when replying to emails has the facility to 'reply to all recipients' - that means if you receive this from me (which was sent to approx 10 people), you can also email them all and share your ideas with everyone. This should work well. I will send updated mailing lists as I think worthwhile. VML (Virtual Machine Language) ============================== Several people mailed me their concern regarding the speed that a PCode system would be like on an 8 bit CPU. Here is the now intended solution for Codename GENOS. Codename GENOS and it's Applications will be written in VML. The development of this VML has just started and will be based around common instruction types that are commonly shared by CPUs. It is hoped that most common instructions will have a one to one relation with the native target CPU's machine language. Of course there will be some instructions that will infact have to be coded as a 'routine' on the target computer. I currently believe this will give an almost full performance on EVERY target platform. As mentioned before, I had a suggestion from one of you that during the installation of an application should be when the JIT is invoked. This is way it will probably be. Why translate the code from VML to native code EVERY time an application is run? The users wouldn't even be aware there was a VML behind the scenes. We will achieve full speed and full portability - no 'runtime' code will be interpreted. HAL (Hardware Abstraction Layer) ================================ The HAL is a very important portion of this OS. The OS could exist with no HAL, but it wouldn't be able to handle input/output and still be portable if the HAL wasn't there. The OS needs input/output so, the HAL will contain a set of standard documented routines which MUST be implemented on EACH target platform. The HAL's implementation will start of simple, with text output, command line input and some sort of secondary storage support. From here, it will progress to bitmapped graphics (for systems that support this), communications etc... Remember, not all computers have human input devices, the target system could be an embedded system, or PLC (programmable logic controller). Intended Applicaton Development Process ======================================= Initially development of applications will have to be done in one of two ways. Either with a hex editor (to created VML software), or with the assistance of utilities we will all have to write on another system to cross compile or cross assemble. Perhaps a Small C compiler of another system (ie: MSDOS, MacOS, CP/M) could be adapted to generate VML. Eventually a VML assembler and other language compilers will then be written from scratch in VML so they can then be portable. If anyone would like volunteer to be part of this sub-development team, ie: perhaps convert GCC to generate VML, please let us know. Development Plan ================ This is the development plan as it stands currently. 1. Codename GENOS Awareness and Advertising (in progress) 2. Resource gathering (in progress) 3. Website (main one AND lots and lots of mirrors) 4. Mailing List (implemented) 5. IRC Channel 6. VML Specification (in progress) 7. Resource Allocation (in progress) 8. HAL Design 9. VML to Native code translator (cross platform version) 10. Initial HAL implementation 11. Development of simple command line shell (for testing) 12. Design of OS (to be written in VML) 13. Development of VML assembler (written in VML) 14. Development of VML 3GL (written in VML) 15. ... Commercial Again? ================= I had some people email me saying that a commercial project for redundant computers will fail. Why? Remember, it will likely be commercial, but FREE! Also, only the INITIAL target computers will be 8bit. Later targets might be current Alpha, Intel or PPC CPUs. If the project takes off - ie: people actually use the OS, then we may actually see a common future platform (ie: JAVA is not very platform independant cause it need too much resources for 8 bit computers). And also an 'efficient' OS for the faster CPUs. Resources Needed ================ All forms of resources are needed for this project. 1. Systems Analysts/Programmers to design and implement the HAL on each platform 2. Application Programmers to code programs in VML Assembler or a 3GL 3. Web page designers to design, implement and maintain websites 4. Administrators to maintain the mailing list, IRC channel 5. Beta testers to test everything 6. Artists to create cool advertising (on the web) 7. Brainstormers to give us suggestions Names Needed ============ As mentioned before, Codename GENOS really needs a proper name. Also this programming effort should have a name too - for promotion and identity. Until Next Time Regards Julian Cassin