Quanto And Fhex The New Microprocessor Standard.

Computers and decimal numbers. Working on the Quanto processor has put a problem to the forefront for me to solve. A problem that usually only computer design engineers see. This may shock many of you but the fact is binary computers are actually very clumsy with decimal base radix 10 numbers.

As many of you know, or should know, in decimal division by 10 always produces an exact result but if you do the same thing in binary you'll get an infinity result and not the exact answer! Speaking from personal experience this has always been a very annoying problem.

Computer manufactures also aware of this anomaly invented the floating point math co-processor complete with complex corrector ROM so that correct decimal 10 results will be produced. The problem is this correcting only occurs, as seen with my own experience, to 2 decimal positions. Just right to keep the dollars and change correct but scientific calculations are still left floating in the infinities.

These corrector ROMs add significantly to die complexity of course but another thing is that in order to save on complexity, manufacturers use arithmetic logic units ALUs that are simplified but require sometimes hundreds of clock cycles to complete a single multiply or divide operation. All of this stems from the fact that the native number system of the computer is radix 16 not radix 10 so if you can't beat them then join them! Thus the Quanto solution!

So my package solution to the problem is as follows. The first thing I've done is to expand the hexadecimal number system into a full floating point system, with exponents, that I call fhex. A computer being fully adept to this system can do so with near perfect precision with only some modifications to the integer ALU and with Quanto this will eventually include the ability to perform multiply and divide in a single clock cycle. Thus the math co-processor can be eliminated entirely. What this means is that a computer based on fhex will run rings around a computer using radix 10 floating point even if the fhex system is on a slower clock cycle!

But their is still more to my ultimate solution. What I'm doing is defining an entirely new system of mass and measurement with the simplicity of the metric system yet it is entirely radix 16 and I call it the Fhex Metri System. All of this will be used in building the citadel. So will the outside ever adapt this system? I doubt it because the money people will hate it. It's radix 16 not radix 10!

Another technology that I desire to develop is an entirely new video technology. This is an entirely new hardware configuration in where video memory is directly mapped to display pixels in a way where the antiquated raster scan technology commonly used today can be eliminated. Raster scan technology, for those of you who don't know it, was invented in the ancient television days and was used because the CRT phosphors would only stay lighted for a fraction of a second therefore it was required that the screen be constantly redrawn at a rate of 60 times a second although modern computer systems can support a faster scan rate than this. The problem is that this produces a stroboscopic effect that can cause significant eye strain. It's an effect that I've always hated. 

Quanto and O3S and G@ will not only be different. They will be the best.

Quanto, @on, G@, @3S, @3i! and O3i! are the property of Mescitadel Think Tank and also claims O3S provided none can prove otherwise. What I mean is that the term O3S has been out their for some time but I know of none who actually have a functioning O3S.

Bugs In The Food.

Have you ever thought much about it? How many bugs you eat in a given week. I know. I know. You don't like to think about it. Like the times you open up that bag of getting a little old, flour and find it crawlin' (now listen to the girls scream) or how many bugs are in that bag of corn chips you like so much. But the fact is, you eat 'em, especially if you don't take the time to examine what you eat like when you're in front of the tube, hypnotized.

I live in an agricultural area. This knowledge is a fact of life around here. Stuff that looks like it ain't fit to sell on the shelf or in a basket usually ends up processed into something like ketchup for example. The home for second rate tomatoes.

This points out a problem with food labels. They never tell what the grasshopper content of your chips are and even more importantly how fattening they are. The last time I found an opportunity to tell a guy that he stopped chewin' and dazed off. It was fun. And do I eat em'. Not if I can help it!

Here's a food horror story for you to digest. It was in a true biography about a couple who sailed their boat to Mexico sometime in the 1970's. They went to the meat market and found them spraying Raid on the meat to keep the flies off of it. The couple decided to catch their own fish from then on.

Quanto Quantum Microprocessor Technology.

The best type of micro-processor for use in computers and droids has been a fascination of mine for years. Currently available technologies are not satisfactory, in every aspect, for my logical ambitions. Quanto and O3S (Object Oriented Operating System) and O3i! (Object Oriented Operating Intelligence) are being designed together as a unit and contain many new ideas and some are presented here.

Yes the current Mescitadel Think Tank microprocessor project is now officially called 'Quanto'. The @on project has been dropped and merged into a superior project technology. It is my intension to make Quanto the worlds first functioning quantum processor. Significant advances in architecture have been made and I am very enthused by the results. Even now I'm tooling up for research into this area and I'm preparing the advances that will be required in my vCAD software.

As some may know researchers in the field regard the quantum processor as the ultimate in computer execution science having the potential to be an order of magnitude faster than any current processor concept. A quantum processor is known solely for the electrical physics of its operation. A significant variety of descriptions exist being the fact that it is said that nobody really knows how to build a quantum processor. But this is about to change seeing how I have devised a workable quantum processor concept.

The typical Quanto processor will contain multiple cores with cache and will support multitasking and sundry proprietary security features. Each core will have 10 ($16) general registers, some have a specific purpose and the rest are general purpose, and an ALU that supports the fhex number system however radix 10 numbers will require the support of a software emulator.  The registers themselves are sized by opcodes according to needs.

It's instruction set is redesigned to be logically improved. The usual addressing modes will be supported along with these 2 extra types. It will support both BP(base pointer) and IP(instruction pointer) indirect with index. It will also have specialized cache control loop instructions.

As to the requirement of O3S it will support floating memory segmentation and access restriction logical protocols and a register will serve as BP. The memory model itself will be flat. Eventually the data/prefetch memory buss itself will be an impressive 400 ($1024) bits wide! Or in other words 80 ($128) bytes wide! The reason why is because memory buss contention sets a practical limit as to how many cores can share it. This helps to alleviate this problem. Also this means that video rendering speeds will be very impressive. Fast enough for artificial intelligence recognition protocols. However it is my intention to make the first implementations of the device like a 10($16) bit MCU with real world interface capability such as a A/D and D/A converter and other useful functions.

As you can probably surmise Quanto will be a computer system on a chip. It is designed to boot O3S and O3i! from internal ROM for security reasons. O3S implementations will support typical PC style application development methods of course. G@ is my new programming language especially made for this use and is a more logical solution to application programming.

In addition their are two new concepts that I intend to employ in the Quanto processor. First I'm developing the theoretical basis for an entirely new digital switching device that I call a Logister. This is a new concept quantum gate electronic device that I intend to use as a replacement for the transistor in all of my digital designs because of its superior performance characteristics. According to my calculations Quanto should achieve a clock frequency greater than 100 GHz and it will not require the use of cooling fans.

And also in the chip manufacturing industry you'll here of them speak of the limits of small they can achieve and they explain it as the physics of the transistor no longer hold at that small of a size and it no longer functions properly. Sometimes this explanation can vary slightly. The point I'm making is this. I have discovered what is happening and I have the solution for it. The logister will come into the new frontier of small and when I say this I mean quantum computer small. I'm also working on the concept for a new thin film integrated circuit manufacturing technique.

Another device that I'm currently conceptualizing is an entirely new high capacity persistent memory device. It consists of a passive cube in which the surface is covered in micro electronics intended to access the cube in a 3 dimensional manner. It will be a rugged device as opposed to the hard disk drive which although the capacities are quite high, they are simply too fragile for the uses I require.

Their will be two types of boot ROM in Quanto. OTP (1 time programmable) and flash both of which must be programmed by connecting an external JTAG like device. In addition attempting to reprogram an OTP device will destroy it for security reasons. Whether one is surfing the intra-net or has droids one wants to be certain of the loyalty of their machines.

Quanto, @on, G@, @3S, @3i! and O3i! are the property of the Mescitadel Think Tank and also claims O3S provided none can prove otherwise. What I mean is that the term O3S has been out their for some time but I know of none who actually have a functioning O3S computer operating system. O3i! (Object Oriented Operating Intelligence) is the primary artificial intelligence project of the Mescitadel Think Tank.

$ denotes a radix 10 number and its absence denotes a fhex radix $16 number.

G@ Language and Compiler Software Technology.

G@ is a highly efficient programming language that I've been working on for a long time now. My work in developing the @on micro processor has put forward the requirement that I develop programming software for it and this in turn has driven me to examine general programming software logic.

The first thing I considered of course is the C++ software I'm using now. I acquired this software in 1997 and I admit I still don't know everything about it. Yes I write fully functional software with it yet their is some tricks I still don't know and the reason why is because the documentation is so huge and bewilderingly complex that I just haven't read it all. 

This brings up an advantage for G@. In G@ one person can master any imaginable programming job and get it done while this same job would take a team of programmers in another language. Productivity is the word and this will come from having the simplest and most reliable programming experience anywhere. How you might ask? It is called vision and genius.

Originally G@ had its start being very similar to C++ and was meant to be used on the @on processor. But better ideas influenced its evolution to the point that G@ is significantly different from any other programming language out there. I've even changed the visual appearance of windowed software by reengineering the view structure for software such as the multiple document interface. I do feel I have better ideas on such things as anybody else however doing this is a requirement because Microsoft Corporation has patents and copyrights on virtually every aspect of appearance and function of Windows software and they aggressively defend them.

Here are some key G@ points. First I removed the requirement for matching {}'s which can be a source of some very aggravating bugs and replaced it with a more fool proof formating system. I removed the ';' line terminator and replaced it with the requirement that all compile lines begin with '*'. This allowed me to restructure comment tokens since any line without a starting '*' won't be compiled thus it is a comment. The G@ universal document editor can supply '*' formatting in a smart way. Their are other format differences and I'll explain them at a later date.

More importantly however todays multi cored computers demand improved memory efficiency. I accomplished this by reengineering the software logic typical in the use of variables and function calls and virtual pointers. I've even reengineered thread logic for superior performance with the goal of having multiple cores concurrently executing within a single process. I've also reengineered memory heap logic and mass storage methods and their relationship to executables.

In G@ you have greater access to cpu registers and can even define them as variables all towards the superior performance advantage of G@. I have incorporated improved access visibility within a program and such is governed solely by syntax and not a scope restrictive wall. I'm currently improving the language structure in a way that will produce more logical constructs. Their will be functions, function objects and networks of objects that will make program logic logical and maximize execution performance.

@on, G@, @3S, @3i! and O3i! are the property of Mescitadel Think Tank and also claims O3S provided none can prove otherwise. What I mean is that the term O3S has been out their for some time but I know of none who actually have a functioning O3S.

O3S Dock Software Technology.

O3S (Object Oriented Operating System) is the future in computer software and development in this technology is progressing splendidly and it is vital in making the vCAD Micro Lithograph a practical reality. Being object oriented is not entirely unique to O3S since popular OSi on the market take an object oriented approach on the surface. But how it works underneath is where the superiority of O3S begins to show plus the fact that this supports the concept of executable docking.

In O3S the typical application is of the type *run* and I say it this way because O3S does not use .EXTsions in media files and also of note I use media instead of disk to indicate a storage device and the reason why is because a flash device is not a disk. Well anyway their is another type of executable that is of the type *dock* which is not usually a stand alone application because it is intended to add functionality to an application in a modular way. This is the very nature of the object oriented approach to computing.

Here's an example. Take the typical document processor of O3S that uses the universal document interface which is a stand alone application. Universal document is of course a full word processor with a full bitmap background for any type of image containment and when run under Windows it is of the file type .udoc. But in O3S you can take a G@ programming system toolbar and dock it onto the universal document processor and viola! You have a full G@ programming system with compiler and all the tools.

Universal Document under O3S is capable of accepting many such docks and this shows actually how this concept can be used to manage clutter allowing you to detach and remove docks that you aren't using. This is an important point especially for vCAD which is being designed to have many such docks and uses the universal document interface. Such docks can include those for electronics and components. My current research interests center around micro electronics and I expect that to remain so for several years, and I hope to report significant advances over the next year.

It is my intention to make my very first vCAD Micro Lithograph manufacturing project the etching of PC boards for the mounting of electronic components instead of the usual chemical etching process now widely used. Then I intend to concentrate on electronics and the @on processor which I can say will likely consume the next 10 to maybe even 15 years of my development time. I intend to document and publish these as I go.

Yes universal document is the base data container for vCAD because it can contain a 3D object. This is clearly useful because the component and textual descripti are both in a common document. As for the dock object itself it has full access to all the required data fields in document processor. On the software technical side of things when a dock is compiled it has dependencies that must be included from the dock target run executable so that this data can be found. This of course creates a useful security barrier that occurs with the O3S requirement that all executables have an embedded passkey or they will not execute.

Universal Document Processor is a fully functional software system and is updated regularly. I'm currently coding G@ code editing improvements. O3S is currently under development and the process define stage is nearly complete and x86_64 boot loader development has commenced. G@ is also under development and while nearly complete it is going through a structural revision. A newly engineered software object base system that will significantly accelerate the development and completion of software from this time forward, is now fully functional and on-line.

@on, G@, @3S, @3i! and O3i! are the property of Mescitadel Think Tank and also claims O3S provided none can prove otherwise. What I mean is that the term O3S has been out their for some time but I know of none who actually have a functioning O3S.