Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.
Course Of The Month
7 days, 2 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
if no win2k specific drivers, which to try: nt4 or win98?
Posted on 2000-02-25
In the absence of drivers written specifically for windows 2000, which drivers should I try first: the win98 or the nt4 drivers (to see whether they work)?
As I understand it, win98 introduced a new driver model that's _supposed_ to be native (but maybe non-preferred) for win2000 as well, so that in theory a driver written to the new standard should support both win98 and win2000.
However, I'm also under the impression that windows 2000 can deal with nt4 drivers the same way that win98 can deal with win95 drivers. Sometimes.
Assuming that I'm right on both counts (I could be dead wrong), should I try the win98 driver first, on the assumption that it will either work better than the nt4 driver (because it was written to support the new standard and thus be supported natively) or die a horrible death (if it was written for win95 and just happens to be supported by win98 in backwards-compatibility mode).
I suspect that even if it's true about 98 drivers, the vast majority of so-called "win98" drivers are really just written to the win95 driver model.
Of course, there's also the possibility that even drivers nominally written to the new spec (in theory) might not work, because the author(s) took shortcuts that win98 didn't notice, but win2k will notice and scream loudly about.
Of course, there's also the spectre that even drivers nominally written to the new spec (in theory) might not work, because the author(s) took shortcuts that win98 didn't notice, but win2k will notice and scream loudly about.
Still, I'd like to find out a definitive answer for this... Lots of people have been asking me, and I really hate not knowing for sure.
As I understand it, win98 introduced a new driver model that's _supposed_ to be native (but maybe non-preferred) for win2000 as well, so that in theory a driver written to the new standard should support both win98 and win2000.
However, I'm also under the impression that windows 2000 can deal with nt4 drivers the same way that win98 can deal with win95 drivers. Sometimes.
Assuming that I'm right on both counts (I could be dead wrong), should I try the win98 driver first, on the assumption that it will either work better than the nt4 driver (because it was written to support the new standard and thus be supported natively) or die a horrible death (if it was written for win95 and just happens to be supported by win98 in backwards-compatibility mode).
I suspect that even if it's true about 98 drivers, the vast majority of so-called "win98" drivers are really just written to the win95 driver model.
Of course, there's also the possibility that even drivers nominally written to the new spec (in theory) might not work, because the author(s) took shortcuts that win98 didn't notice, but win2k will notice and scream loudly about.
Of course, there's also the spectre that even drivers nominally written to the new spec (in theory) might not work, because the author(s) took shortcuts that win98 didn't notice, but win2k will notice and scream loudly about.
Still, I'd like to find out a definitive answer for this... Lots of people have been asking me, and I really hate not knowing for sure.
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
4
-
3
8 Comments
Do not use Win9x drivers. Period. Win2k, as you know, is based on the NT kernel. And because of this, it uses the NT HAL, or NT Hardware Abastraction Layer. This means that you must use NT drivers on your Win2k box, or, of course, drivers specifically written for Win2k.
Win98, Win98SE, Win95 drivers are all more or less the same. None interact with the HAL, instead, they interact directly with the hardware itself. This won't work in NT because of security, and therefor won't work in Win2K.
If Win2K drivers don't exists (chances are they will soon) use NT4 drivers only. Using Win9x drivers will result in unpredicable outcomes.
Win98, Win98SE, Win95 drivers are all more or less the same. None interact with the HAL, instead, they interact directly with the hardware itself. This won't work in NT because of security, and therefor won't work in Win2K.
If Win2K drivers don't exists (chances are they will soon) use NT4 drivers only. Using Win9x drivers will result in unpredicable outcomes.
Always use NT4 drivers first. If that don't work then you can try to install W98 drivers but I know (from betatesting) that 99% of the w98 drivers will not work...
So stay with the NT4 drivers and ask (seek) for W2K drivers
Mario
So stay with the NT4 drivers and ask (seek) for W2K drivers
Mario
Do not try Win98 drivers... this is bad advice. Most likely, your system either won't boot or will crash soon after.
Win9x drivers are NOT for Win2k. Do NOT use them.
Win9x drivers are NOT for Win2k. Do NOT use them.
In the beta-doc there was a advise to use the W98 drivers if something don't work. But I say that 99% don't work.
Mario
Mario
Where in the beta documentation does it say this? Perhaps I am looking in the wrong place, but the only section on drivers states to only use the NT4 drivers, if available, otherwise wait for Win2k drivers to come out.
At any rate, in my experience, using Win98 drivers results in stuff breaking. If it does indeed say to use Win98 drivers in the docs, I still think they should be avoided, even if it means not having a functioning peice of hardware.
If you don't avoid it, you will no doubt sacrifice stability.
At any rate, in my experience, using Win98 drivers results in stuff breaking. If it does indeed say to use Win98 drivers in the docs, I still think they should be avoided, even if it means not having a functioning peice of hardware.
If you don't avoid it, you will no doubt sacrifice stability.
OK, I finally had a few hours to kill on Saturday morning and managed to find the defininitive answer in the MSDN knowledge base.
See: "Surveying the New Win32 Driver Model for Windows 98 and Windows NT 5.0"
http://msdn.microsoft.com/library/periodic/period97/wdm1211.htm
(Yay! I KNEW I wasn't hallucinating & that it was for real, even if most of my friends thought I was crazy...)
In a nutshell, it basically says that a flawlessly-executed Windows 2000 driver can also work under Windows 98 *** IF *** the developer implements everything perfectly, takes no shortcuts, provides an occasional alternate method within the driver to be used by Win98, and gets really lucky.
While this might imply that a really progressive forward-looking developer might conceivably have written such a driver months ago and released it as a "Windows 98" driver, the odds of that actually happening in real-world corporate America is pretty slim (I'm a developer myself, although I don't do drivers, and god knows how many holy wars I've had over the issue of "elegant and flawless vs. good enough to sell")
Thus, as a practical matter, the fallback strategy looks like:
1. Win2000-certified
2. Win2000 beta, unless it has a bug bad enough to render it unusable
3. Win NT4 certified
4. NT 4 uncertified
5. Win98 certified -- but light a few candles & sacrifice a chicken first :-)
See: "Surveying the New Win32 Driver Model for Windows 98 and Windows NT 5.0"
http://msdn.microsoft.com/library/periodic/period97/wdm1211.htm
(Yay! I KNEW I wasn't hallucinating & that it was for real, even if most of my friends thought I was crazy...)
In a nutshell, it basically says that a flawlessly-executed Windows 2000 driver can also work under Windows 98 *** IF *** the developer implements everything perfectly, takes no shortcuts, provides an occasional alternate method within the driver to be used by Win98, and gets really lucky.
While this might imply that a really progressive forward-looking developer might conceivably have written such a driver months ago and released it as a "Windows 98" driver, the odds of that actually happening in real-world corporate America is pretty slim (I'm a developer myself, although I don't do drivers, and god knows how many holy wars I've had over the issue of "elegant and flawless vs. good enough to sell")
Thus, as a practical matter, the fallback strategy looks like:
1. Win2000-certified
2. Win2000 beta, unless it has a bug bad enough to render it unusable
3. Win NT4 certified
4. NT 4 uncertified
5. Win98 certified -- but light a few candles & sacrifice a chicken first :-)
Featured Post
Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Suggested Solutions
| Title | # Comments | Views | Activity |
|---|---|---|---|
| How to migrate DHCP sever on Windows 2003 to Windows 2008 | 4 | 520 | |
| Windows 2000 Kerberos problem | 5 | 355 | |
| Windows Explorer and WinZXip | 4 | 541 | |
| Software to report on NTFS folder permissions? | 2 | 502 |
NTFS file system has been developed by Microsoft that is widely used by Windows NT operating system and its advanced versions. It is the mostly used over FAT file system as it provides superior features like reliability, security, storage, efficienc…
A big percent of today’s marketing activity is performed through the online environment. The marketing strategies that have existed a decade ago no longer relate to what’s happening today. We’re currently facing a revolutionary era, called the digit…
Suggested Courses
Course of the Month7 days, 2 hours left to enroll
734 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.