|
PureBytes Links
Trading Reference Links
|
Because WinNT employs preemptive multi-tasking, it does a reasonably good job of
handling ill-behaved 16-bit apps as long as each is run in a separate virtual
machine. When run in the same virtual machine (default), Omega's apps will lock
everything else out in the virtual machine until it is finished doing whatever
it's doing. Since both the Omega charting and server apps must run within the
same virtual machine, a workspace load operation will lock out the server, even
under WinNT.
Earl
-----Original Message-----
From: dcountach <countach@xxxxxxxxxxxxxxxx>
To: omega-list@xxxxxxxxxx <omega-list@xxxxxxxxxx>
Date: Sunday, August 23, 1998 12:33 PM
Subject: Re: data reception during LOAD WORKSPACE
>Doesn't Windows NT (and OS/2 :-) prevent the problem of apps hogging the
>CPU ??
>
>donc
>
>
>>Subject: Re: data reception during LOAD WORKSPACE
>> Date: Sat, 22 Aug 1998 05:59:53 -0600
>> From: "Earl Adamy" <eadamy@xxxxxxxxxx>
>> To: "List-omega" <omega-list@xxxxxxxxxx>
>>
>>Windows in it's various incarnations starting with 3.0 incorporated a "Yield"
>>event which allowed a programmer to yield a long running task to the operating
>>system so that the Os could allow other tasks to run. It did not take a rocket
>>scientist to build apps which did not hog the CPU (as TS/SC does when loading)
>>nor did it take a rocket scientist to simulate threading which allowed related
>>tasks to proceed. Later versions of Windows have facilitated the building of
>>truly threaded apps. Omega programs have been generally ill-behaved and in the
>>social world would be considered selfish. Perhaps they will properly thread
>>operations in TS5. In any event, more memory should reduce load time,
>>alternatively a faster processor.
>>
>>Earl
>
|