The beginning is always the hardest. Although the Mount Everest system is complete, it does not yet meet the standards for market launch.
If the chosen system meets the standards for market launch, there are many software programs that need to be ported over. Without software support, what's the point of this thing?
Just like the BlackBerry system back then, it is indeed very smooth and very secure, but it leaves very little space for installing software, and even less in terms of software support.
Many of them were ported over by themselves, and then an unofficial forum was set up for experts or technicians to make modifications. These were all systems that individuals ported over from other places to support their systems.
The call to action was made, but the software library still couldn't support it, and in the end, it was necessary to open up the JAVA format JAP file to run it.
Putting aside JAVA software, there are already quite a few JAVA games, and almost all mobile phone manufacturers support this camp, so how could there not be many?
Nokia, Sony, Sony Ericsson, Samsung, and Motorola all support JAVA files, making BlackBerry's alternative seem lonely. In the end, it joined in to gain software support.
Xing Baohua isn't worried about software support later on, but rather about support in the early stages. After all, their side is considered original, so they can only do it themselves and let others follow suit. He needs to transfer the software from the Windows system and convert it to JAVA format.
Half of the software was licensed and modified by the company, while the rest was uploaded by technicians themselves. It didn't matter whose software the technicians modified or copied, as long as it didn't crash on the devices and worked, that was fine.
The system testing period was quite chaotic; both hardware and software were in disarray, with various crashes occurring, some caused by software and others by hardware. In short, they were all closely related factors.
Software malfunctions can cause hardware damage or hardware problems, leading to system instability and a series of crashes.
This period of adjustment can only be described as a disaster, a nightmare.
That's how research and development works; without experiencing hardships and failures, how can you know the brightness of the future?
Xiao Tianna, the father of the Mount Everest system, was almost driven crazy by this piece of junk. He and Xing Baohua had put together a rough framework, thinking it would be usable. Back then, it was programmed on an Intel chip, but what about now?
If the chips are useless but they're still being forced into use, who can stand it?
The series of disasters were all caused by Xing Baohua's insistence.
With massive funding, personnel, equipment, and full support, if you still can't make it work, you might as well go home and grow sweet potatoes.
High-tech things are all made by foreigners; we Chinese can't do them, we can't make them. As Mr. Qian said, "If foreigners can do it, so can we Chinese."
Under certain mindsets, the goal is to master certain technologies. Isn't it just about using your brain and playing with electronic technology? Just play around, why worry about money?
He can burn through billions of dollars at will, and once it's gone, he can just go and earn more.
Xiao Tianna found Xing Baohua: "Boss, I feel that the problem is with the chip's performance; it's not compatible with Mount Everest."
"Have you tried the process of elimination? Has the chip ever crashed when running other operating systems? Has it been tested with a pure UNIX system? Has it been tested with a DOS system? What were the results of the operation?"
In short, Xiao Tian couldn't answer the question. He had indeed tested it, and there were no problems using other people's systems, but using his Mount Everest system caused more problems.
This indicates that the problem is not with the chip itself, but rather with incompatibility with Mount Everest.
But Xiaotian's system was modified from the UNIX system, with their own additions.
The core is still UNIX, so there shouldn't be widespread incompatibility. Everything looks normal when the software isn't running, but once a JAP file is added, all sorts of problems arise.
The cause of the problem cannot be found. The parts are normal, but when put together, there is a problem. This kind of difficult problem is indeed hard to solve.
After finishing some work, Xing Baohua went to their laboratory to test the system's operation.
Opening the system package was a real eye-opener, with all sorts of things to add and optimize, leaving me clueless as to where to begin. I have no idea how Xiaotian and his team managed to create it.
Looking at these codes is more of a headache than looking at financial reports. At least looking at the numbers on financial reports means that you've made money, and having money makes you happy.
Looking at the code is really exhausting.
We meticulously reviewed each item, identified any unnecessary additions, and discussed them with the team's technical staff to determine if these additions were necessary.
While streamlining the system, the software should also be streamlined.
Don't just try to fool people; it has to be usable and easy for them to use. Cut the size of any non-professional software in half to make the program extremely small.
Suddenly, Xing Baohua realized that he and his colleagues had fallen into a misconception: they were making computers and laptops, but you couldn't use these things as proper computers and laptops.
Even in the era before he traveled back in time, no company had ever installed mobile low-power chips in a mainframe computer for use.
Even the highest-spec, most advanced mobile low-power chips can't match the performance of a computer from over a decade ago.
This area has been clearly defined long ago, with significant differences between simple and complex commands. Even Microsoft's mobile operating systems differ from their PC systems.
The problem lies in this simple instruction. Once the system becomes complex, it's no wonder it crashes.
Xing Baohua shared some of his ideas with everyone, namely to simplify the operating system to the same level as an embedded machine system, so that it can perfectly run JAVA programs.
If it still can't run, then add an engine module specifically for guiding Java programs.
This means the motherboard design has to be reworked and redesigned. Don't think that adding a module is a simple matter; there are many things to consider.
My dear reader, there's more to this chapter! Please click the next page to continue reading—even more exciting content awaits!
Continue read on readnovelmtl.com
