SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Corel Corp. -- Ignore unavailable to you. Want to Upgrade?


To: Eveline Bernard who wrote (8471)1/7/2000 8:38:00 PM
From: Im-patient  Respond to of 9798
 
Eveline....here's an explanation from the CEO of GOJO...in his own words!...(need RealAudio or compatible...)

biz.yahoo.com

Tom has it a little wrong(GOJO's product is not an emulator(in the CEO's own words))...but yes, GOJO is not exclusive to CORL... But CORL is the only LINUX OS provider who will have it bundled...

Also...GOJO has a patent...bought it...and is sueing CITRIX for a licensing fee...who knows how it will end up...(remember QCOM vs ERICY?(I think it was))

It's all very interesting...



To: Eveline Bernard who wrote (8471)1/7/2000 11:04:00 PM
From: Thomas A Watson  Respond to of 9798
 
Eveline, you are really paying attention. I use the word emulation in a loose way. I believe NCD and Graphon and VMware all have similar operation. A process runs on a msft os computer and allows for the feeding of mouse and keystrokes to an application and the graphic output is the program is fed to a network connection. On the client machine a application runs that takes and feeds the mouse and keyboard to the network and display the graphics returned from the msft application server. So the application is running/executing natively. What you see on the (linux/unix/msft)client looks just like the application would if running native on a msft system. In theory it sounds nice but in practice the piggy nature of msft apps and the fact that in my opinion no one really knows what the msft os actually do completely creates clunk times clank raised to some exponent much larger than 1.

Now gettin any particular msft OS program to run this way with any stability is difficult. So if one creates ones own Linux distribution, one can integrate and test. But the handshaking is tight. So when one is done one's apps may run on other Linuxes. But there are also other layers that add to the complexity. There are different Xservers and there are different Window managers and there are differ modules for the different window managers and all can create small differences in how information is presented. This is why I am against what I loosely call the emulation of an interface.

This is how I mean the corl apps that are not directly ported may only run well on corl Linux which will have a corl selected Xserver and Window manager (kde I think)
Applix apps are directly ported to all OSes and do not operate through interface emulations or simulations.

Software bugs occur at interfaces. Bugs increase quardradically as the number of interfaces increase. All windows api emulation interfaces are guesses as to how they work as there is no source available.

hmmmm Am I confused yet?

this article describes corl/graphon operation kinda.
Corel Linux Will Run Windows Apps pcworld.com

Tom Watson tosiwmee