Posted by Jim Guerber on June 10, 2008 at 16:22:39:
I just read Grant's latest posting under the "Windows 7, don't hold your breath" thread. This stuff is very interesting and speaks to Comet deployment, and future versions of Comet.
As some of you know, we are working on a brand new Comet. One which does not have any 16 bit code in it. We call this Cos32. I want to discuss with you some of the design decisions which we are making.
Given that a typical Comet installation has thousands of programs.
Given that you don't want/dare to mass convert all the programs at once.
Given that the current Comet Runtime is written in 16 bit code.
Given that 64 bit operating systems are around the corner, and will not support 16 bit code.
wait...
Is that really right? Won't someone come along and build a 16 bit x86 interpreter to allow current programs to run???
Anyway...
What should we do? Please give us guidance.
We are building a new Comet that will run recompiled programs. We are trying to provide source compatibility for all of your current programs, but if your source is lost, or you are running emulated Q programs, they won't run with this new runtime.
What are the chances that MS will completely drop support for 16 bit programs?
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.