The Microsoft NT DDK includes two NDIS protocol driver samples. In addition, an updated NT 4.0 Packet driver sample is available on the Microsoft website.

The PCAUSA SNTRANS project is an example NDIS 3.1 PROTOCOL virtual device driver for Windows 95. SNTRANS is written in the 'C' programming language specifically for VtoolsD for VxD framework, and provides a basic empty shell for developing your own protocol driver. SNTRANS is functional only to the extent that it registers the SNTRANS protocol and automatically binds to one MAC adapter, and unbinds when the driver is unloaded. No other functionality is provided in the sample.

The Microsoft Windows NT DDK team has a sample NDIS Intermediate (IM) Driver named "ImSamp" on their website at: The Microsoft NT 5.0 Beta 2 DDK includes a different NDIS IM Driver sample "PassThru" under the directory: January 6, 1999 - Andrew Zabolotny <bit@eltech.ru> has contributed a paper that includes his instructions on how to adapt a intermediate driver that works with network cards to make it work with RAS. Click the link below to view Mr. Zabolotny's paper.

Windows NT (both the Workstation and Server) is a 32-bit Operating System. It is a preemptive, multi-tasking Operating System, which means that the Operating System controls allocation of CPU time, not the applications, stopping one application from hanging the OS. NT supports multiple CPU's giving true Multi-tasking, using symmetrical multiprocessing, meaning the processors share all tasks, as opposed to asymmetrical multiprocessing, where the OS uses one CPU and the applications another.

Windows NT series systems are designed for sharing resource. Form the original design, NT does not support USB interface so you cannot install any USB device under Windows NT system.

There is no special PCMCIA driver needed for Windows NT. PCMCIA sockets are ready to use after Windows NT 4.0 and the latest service pak are installed. If your machine is configured to dual boot with Windows 98 and Windows NT 4.0, you will have to power off the machine and go directly into Windows NT 4.0 in order to use the PCMCIA socket. You'll received the above error message if restarting without powering off.

Insert the midiLink driver disk into drive A. Or type the drive or directory to locate the driver files.

This OS is currently not supported. Trying to install Windows ME with a Verite graphics card may result in a system crash.

There are obvious similarities: both provide functions to send and receive packets and to submit NDIS requests to a NDIS adapter driver. Both employ a DLL as an intermediary between the Win32 application on a companion NDIS protocol driver. Rawether is simple to understand and use. Developers who have successfully used Rawether include both experienced network software developers as well as those who do not have a deep understanding of NDIS or Windows device drivers.

I unzipped WD503REG.ZIP and entered the password, but the installation process stopped and I received the following error message:

When I installed Windows NT on my PC9 on the first reboot, it rebooted to Invalid Page Fault in the NTOSKERNEL.EXE error "Blue Screen of Death" memory error screen.

We've included the driver for Inmos B004-compatible boards into our Windows Server Package (both full and lite versions). However, it is not our own - we've just made a few modifications to one provided by Jari Salminen. Developing the NT driver is a very complex task, anyway. You have to be very familiar with Microsoft DDK (Device Development Kit), if you know what I mean...

Miniport Drivers replace platform-specific functionality with platform-independent "wrapper" functions. The writer of a "legacy" driver is free to use whatever functionality is available to develop a device driver. The penalty for this freedom is that the resulting driver is limited in that it can only be used on the operating system that provides the selected features.

The following links should take you directly to Dell's User Guide site for the listed models. I have the links set-up to open in a New Window. Please let me know of any dead links and additional models to include. I will try to keep this up-to-date.

Answer: CTC Parker Technical Support strongly recommends that you do not attempt to install a Windows operating system on a PowerStation. We recommend that you send it to CTC Parker for reprogramming and that, in the future, you purchase the PowerStation with the desired operating system factory installed. Question: When I installed Windows NT on my PC9 on the first reboot, it rebooted to Invalid Page Fault in the NTOSKERNEL.EXE error "Blue Screen of Death" memory error screen.

No. The Windows 98 upgrade is only designed to upgrade from Windows 95. Installing Windows 98 over Windows NT will be considered as downgrading. To upgrade Windows NT 4.0, you will need to upgrade to Windows NT 5.0.

No, and it's somewhat unlikely that anybody would undertake a port. Read Bart Schaefer's excellent summary of the problems. Excerpt: "I've seriously looked at porting it to NT, yes. The problems are pretty severe."

Version 4.0 of Windows NT Workstation does not support ENERGY STAR features that can be activated through the Control Panel. In some computer models, ENERGY STAR features can be activated though the computer's set-up initiative, or bios. You should contact computer support staff for assistance if you're not familiar with bios settings. This FAQ page was modifed from www.energystar.gov/powermanagement, a webpage developed by the Cadmus Group.

Yes. Reinstall in the same directory to make sure that the WINHELP.INI file and registry get updated. Try any or all of the following: reinstall; download the latest help file from our download page; delete the .gid file associated with the help file. STATISTICA's scrollsheet files use the same extension (.scr) as Windows screen saver files do. If you change the default action of double-clicking .

Windows NT ships with NTBACKUP.EXE which is suitable for backing up most installations however its features are quite basic, for the larger more complex installations one of the following may be worth a look

No. While Casper Tech Edition can be used to clone all versions of Windows Vista, XP, 2000, ME, 98, and 95, it does not support cloning Windows NT 3.x or 4.x platforms. Not officially. While Casper Tech Edition can be used to clone a Windows 2000 Server or Windows 2000 Advanced Server system, such use is not officially supported by Future Systems Solutions. Yes. Casper Tech Edition supports all versions of Windows XP Professional, including the x64 (64-bit) Edition.

Windows NT comes with an RPC which interoperates with DCE RPC. Windows 95 apparently provides this interface as well. However, it is not quite the same as DCE. The wire-level protocol is the same as DCE RPC, so applications running on NT can communicate with DCE applications on other platforms. However, the application source code is not instantly portable. Microsoft changed the format of procedure names and moved the status result from a parameter to the function value.

Answer: Only the Development software can be run in Windows NT. Windows NT has a limited DOS shell and it will not support Interact runtime with any device drivers other than the DEMO driver.

It is possible to load NDIS 3.0 NDIS MAC drivers (and make them work) on Windows 2000, but Windows 2000 is the last release that it will support them. Microsoft is killing Full NIC driver support after Windows 2000.

Yes with all Windows XP based systems you must have Administrator rights in order to install the system level print driver.

Under UNIX, there's a PGP command line utility (pgpe) which does the encryption. However, under NT, PGP 5 is GUI based only. PGP 6.5.1 brings back the command line, but I haven't got it to work in conjunction with Soupermail yet. All is not lost though, as you can use the DOS version of PGP 5 under NT. A couple of caveats; Use an up to date version of perl. Activestate build 509 hung when calling PGP 5, build 518 seemed fine.

Windows NT 4.0 ships a utility called IMAGECFG.EXE in the support\debug folder of the Windows NT 4.0 CD-ROM (it does not ship with Windows 2000).