jimmsta, on Aug 17 2007, 12:17 AM, said:
I went ahead and created this 'new' DOS... When used, it is essentially what happens when you create a dos-box in Windows 95 - Windows 95 initializes a new DOS session, in protected memory. An actual multi-tasking 32-bit DOS. Of course, the limitations are still present - it seems that the services within VMM32.VXD in windows 95 hold the key to how the kernel gains access to the CPU. I'm certain that such a project IS possible, but it would take YEARS to get it working. And what definition of 'working' do I mean...
It boils down to the aptitude of people, rewriting the kernel is not necessary, that is why we have ntkern written by people who had the foresight before we were directed to migrate to nt5, IMO identifying the driver (obviously not the kernel/ntkern) that can access the registers of dual core cpus is the main stumbling block, parsing this to vmm is secondary, hence dissecting win2ks uni/multicore cpu ability may be helpful, which it is more than capable of doing, although struggling in scheduling hyperthreading. I imagine the information is available for people to do this now, it will probably happen after such people desire to write device drivers for latter day hardware and move on from that.



Help


Back to top









