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 472.22-1.3%Nov 21 9:30 AM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: sandeep who wrote (45098)5/23/2000 1:31:00 PM
From: SunSpot  Read Replies (1) of 74651
 
Windows 2000 is pretty much based on Windows NT, and making Windows 2000 driver compatible with Windows NT is a choice that Microsoft chose not to take. There might be good reasons for that, but I think it was a bad decision.

Most PnP drivers are still made in the way, that when you insert the device, the OS asks for drivers. Since Windows 2000 Server will mostly be remotely administrated using RDP, and since it is very likely to have two administrators log in at the same time on the same server, which one should get the message that asks for a driver?

Driver compatibility is not only about the VxD itself, it is also about how it is installed.

I wouldn't wonder if PnP changes its behaviour with the next release of Windows 2000, whatever that name it may have.
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext