This part of the technology is led by Volok, or should I say Dr. John, as he likes it to be called. As a veteran PARC member, he understands every detail of computer graphics and even wrote a blanking algorithm on his own when he was in college.

The character-based 'operation' system is not particular about two-dimensional and three-dimensional, such as DOS and godson, they only need to display text, and the specific 'operation' is all done by the processor, and the memory moves lines of commands and text.

In the era of graphical interfaces, it was a disaster, and the appearance of windows made the CPU miserable. The classic mac is like that, all the graphic work is done by our great and sacred 68, hard work, let's pay a little respect to it. The general processing flow is as follows: all graphics are displayed line by line, so the CPU first looks for the address of the window in memory, and then copies the data of each row to the destination display, and repeats this work until the window display is complete.

Therefore, when a window is large, the workload of the CPU increases proportionally, and we will make the CPU repeat this process every time we complete a mobile 'operation', so you can imagine what the effect will be if the CPU is not strong.

Another problem is memory, all the data of the window is first in the memory and then drawn to the monitor, which takes up a lot of resources, which is why the PC with 512k memory does not support the Indos system, and the Mac is as slow as a snail.

The development team led by Warlock borrowed the acceleration principle of the game console, using a special 'door' display chip to accelerate the processing of this part of the graphics data, and combined with the already powerful K32 processor, the workstation was immediately strengthened.

As for the window system studied by MIT, there is a story to tell.

It is said that after Professor Su's threading of the needle, he invested a sum of money for a long time, and "handed over" the development task of the graphic "operation" interface to the MIT laboratory.

Once or twice for a long time can be tolerated, but in 85 years this thing is still grinding and rubbing is a bit wrong, MIT research laboratory does not produce results to ask for money and is particularly ruthless, which makes the long time very unhappy, so I specially went to do an evaluation, but the result made him almost angry crooked nose.

It turns out that in the MIT laboratory, this set of graphical interfaces named x-indo already has a basic form, and to put it mildly, even if it is taken out and sold, it can be regarded as a successful product, but the MIT laboratory is stubbornly holding on to it.

Their reasoning is simple: the main purpose of the X-INDO project is to be implemented perfectly on all machines running Unix, and this version still does not meet this standard and is therefore not suitable for distribution.

After learning the ins and outs for a long time, it suddenly dawned on me that the emotional MIT laboratory does this job, and people do not work exclusively for VS, but also serve DEC, and take precedence over VS.

I said why is it so cheap, feeling that this guy is pulling sponsors everywhere, and the person explained that the difficulty of this project is to develop a standard for a graphical interface that is compatible with all Unix machines and their variants, so it takes a lot of effort to test, and that's how time is consumed.

After listening to MIT's explanation, I wiped my sweat for a long time, obediently, what a great ideal, but we are not the kind of people who have a 'chest' in the world, you can play by yourself.

So in a fit of rage, they asked for a long time to recover their investment, but the people at MIT naturally refused, and asked for the price to pay back on the spot, so they added some money to buy all the technology of this set of semi-finished products.

Later, it became clear that X-indo was not original to MIT, and that they had obtained an experimental 'sexual' window system from Stanford called it, and renamed it X after refining it to be sufficiently distinctive.

With this discovery, Dr. Wollock came forward to find the researchers of the Windows system, and Xu Yili dug to continue the development of the graphical interface.

For a long time, I have completely abandoned MIT's overly idealistic approach, and actually want to be compatible with all unix variants, which is simply ridiculous, and the commercial unix system is five 'flowers' and eight 'doors', and each company always thinks about being incompatible with others for its own interests, how can it be unified?

Therefore, for a long time, the graphics development team of Wollock completely revised the X-window system, and resolutely fought against this sprinkling of compatibility, and everything was optimized for the workstations, EC platforms and 386 that were currently being developed.

After getting all the information of the X window system, I have been working hard for a long time, and I have to admit that this is a special "door" designed for small computers and workstations.

Unlike highly integrated graphics systems like mac and indos, MIT people divide the Windows X system into three parts: the server, the client, and the communication library.

Among them, the server side is equivalent to the display program of the master control hardware, which receives the drawing instructions of the server side to 'operate' the hardware to complete the drawing task and transmits the obtained data to the client. The client does not need to touch the hardware instructions, only needs to request and display.

Therefore, theoretically, as long as the hardware is powerful enough, it can run many servers and clients without interfering with each other, which is quite a bit of a server.

The most surprising thing is that the X Windows system only provides basic system calls, and the first feeling for a long time is that it should be closed and provide a graphical API library, which can be made into a development kit, so that those programmers do not need to use those basic calls step by step, simplifying the programming workload and shortening the development time.

Over time, the Warlock team developed a graphics suite that provided standard building blocks for graphical interfaces such as menus, buttons, and dialogs, as well as a basic Windows Manager, making it easy for all programmers to create a Windows program.

In order to cooperate with the graphics system, a large number of programmers have been mobilized for a long time to port and graphically package existing programs, including the VS-office85 series suite under development.

I've been tired of the 1.0 and 2.0 version naming method for a long time, and it's simple and intuitive to name it after the year, and it's very approachable, and it's been proposed to let everyone vote unanimously at once, so it's so logical to use it on the company's main product, the office series.

VS-office is a money printing machine, and in '84 viesoft alone earned $320 million in revenue, ranking first in the software sales list.

In 85 years, a rocket plan was deliberately developed for the changing market, and a new GUI-based office series was secretly developed, with the main purpose of completely throwing off those strong competitors under the character system through the update of the graphical 'operation' system.

For example, OrdProfect, this thing is a strong threat to VS-ORD, and users are said to be on par with Office, and other companies have more or less one or two unique skills, after all, the first person to eat crab is the most delicious.

Therefore, through the development of the graphical "operation" system, he has been preparing to reshuffle the application market for a long time, and Joey originally intended to make the graphical version of godson more open and close to programmers, but he has long and undoubtedly vetoed it, and specially added a layer between the core and the application, called API (User Program Interface), which completely cut off the programmer from bypassing the system directly. As a result, the structure of the new system is blurred by other companies, and third-party development of fully compatible programs becomes less sassy.

This trick is learned from Microsoft, and it has been 'very' benevolent for a long time, but it has mastered this new layer, as long as the specific details of this set of APIs are not disclosed, it is impossible for any company to surpass VS company at the application software level in the future.

Of course, all the development tools had to be redesigned and modified, which increased the workload of the programmers at VS Inc., but had to be invested for the sake of future profits and advantages.

It's easy to say, but it's a very difficult process, and it's almost a new challenge for all the members of the VS Research Institute, except for a long time, no one can imagine what the final product will look like, covering software and hardware, and the development team of two or three hundred people is a little larger.

Fortunately, Xu Zhixing has done his best in planning and management, although he is not a technical person in this industry, but he is well aware of the importance of organization and management.

Compared to these crazy people, the technical problems may not constitute an obstacle, and the 'spending' of enough time and money will naturally overcome, and it is rare how to knead these guys together and work together.

This is very busy Xu Zhixing, but it also trained him, so that he can grow into a qualified manager in super speed, he classifies everyone's strengths, and divides them into several departments according to the task, each with its own responsibilities. The long-term is only responsible for the overall framework and development direction, ensuring that the development progress is orderly and fast.

The progress of the research institute is in full swing, and the long-term goal is to release the finished product by the end of 85, but it seems that this goal is too ambitious, and the system may be able to take shape, and the specific application software will not be transplanted until the year of the monkey.

The "kicked" industry is like this, there can be no slackness, otherwise you will find that the world will be turned upside down overnight, because everyone is running wildly.

The same thing plays out in every company, whether it's Intel or Microsoft or IBM, and it's much the same in this regard, especially at this stage in '85.

Intel's most important task at the time was to give birth to the 386, and hundreds of engineers in Santa Tak were busy working on the almost entirely new architecture of the 386.

Different from the previous design model, the chief designer Grove believes that the 286 architecture has many shortcomings and is completely incompetent for future chip development, so he advocates designing a new architecture to be compatible with the software before 286, rather than continuing to improve on the 286.

This is going to kill the development team, and Grove is paranoid and can't be persuaded by anyone, so 386, which could have been born in 84, reversed course halfway and almost started all over again.

In charge of the architecture design is the senior compiler programmer Crawford, who was promoted to the head of the architecture design team by Boss Ge because of his talent for hardware, which is quite similar to Changchang.

Crawford and his team racked their brains to think about Boss Ge's idea, which was not only compatible with previous software, but also had a leap in 'sexuality', which was even more difficult for the old 8086 structure.

After a lot of effort, Crawford finally completed the task, in fact, it was very simple, he designed the 386 processor into three switchable working modes, 8086 mode, 286 mode and 386 mode.

As the name suggests, 8086 mode is used to run 16-bit software, 286 mode is compatible with software optimized for memory management characteristics, and 386 mode is a true high-performance operation mode.

It's a stupid way for him to integrate all the hardware in one go. But what great man said, as long as it can solve the problem, a stupid solution is a good way, and Crawford did it.

In view of the fact that the development of the peripheral control chip of the 286 was released by AMD, Grove was deeply aware of the fact that it could not be developed for the sake of developing microprocessors, so the 386 was positioned as a new microcomputer platform.

Due to the signing of a 10-year 'cross' fork licensing agreement with Changjiu, Grove paid great attention to the development of chipsets on Changjiu's side, and almost "forced" Changjiu to 'get' the development base to the United States.

After all, in the United States, you can communicate with Intel's processor design department faster, and you can understand the architecture of 386 in real time.

Fortunately, Changjiu also attaches great importance to this department, after all, this is the lifeblood of all microcomputer systems, and because of the support and successful experience of Intel, the development progress of the team is very fast, almost equal to the progress of 386.

It is because of these software and hardware cooperation that we have long understood some of the latest technologies applied on the 386, such as CAHCE (High Speed Buffer Memory).

Objectively speaking, all the technologies on the microcomputer are usually converted from the mainframe, and the Cahce technology is no exception. This thing is usually used between the processor and the memory, slower than the processor and faster than the memory, and exists as a buffer for data and commands.

Practice has shown that the difference between the 'sex' performance of a computer without cache technology and a computer with cache technology cannot be calculated, and can even reach a 100% leap in 'sex' performance.

As early as the development of the K32 processor, I have long thought about adding this technology to it, after all, I have been familiar with this process for a long time when designing the mainframe, but it is completely different from the chip used in the microprocessor on the mainframe, this thing is so huge under the process of 4~5 microns, and K32 as the first processor finished product for a long time, adding the cache makes the development risk increase, and it has to be abandoned for a long time.