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 : How high will Microsoft fly?
MSFT 401.14+1.9%Feb 6 9:30 AM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: DiViT who wrote (59897)7/16/2001 4:18:55 PM
From: Dave  Read Replies (2) of 74651
 
Dave do you really understand what you are talking about?

No, I'm just spouting off random nonsense. How about you?

If Microsoft had removed 'DOS dependency" "years ago" you would have cried foul when all the Legacy DOS based programs ceased to work.

If they did that, and I did cry foul, then I would be confusing "DOS dependency" with "DOS support." They are welcome to remove the crufty old legacy 16-bit code within Windows that DEPENDS on DOS, while leaving SUPPORT for DOS applications intact.

That's what Apple did with Mac OS X, finally removing all emulated 68K code from the operating system, while still supporting legacy applications in an emulated environment (in which many legacy apps actually run much faster than they did in OS 9).

Now I understand that Windows XP will FINALLY be rid of 16-bit code. Yes, I believe will break many 16-bit DLLs and drivers, but it will get rid of the horribly distasteful need for "thunking" between 32-bit and 16-bit code (please correct me if I'm wrong). It's been a long slow ride, but third-party developers who are stuck writing to the Window API deserve this change!

Dave
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext