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.

No. While Casper can be used to clone all versions of Windows Vista, Windows XP, 2000, ME, 98, and 95, it does not support cloning Windows NT 3.x or 4.x platforms. Not officially. Future Systems Solutions does not support the use of Casper on Windows 2000 Server or Windows 2000 Advanced Server.

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.

Yes. However, due to the specific nature of GoBack, if you want to copy to a hard disk protected by GoBack, or copy to a drive that contains a GoBack history file, you must disable protection on the hard disk first. You must also disable protection before creating or removing a drive on a hard disk protected by GoBack. If you use GoBack, please consult the Casper Tech Edition help for additional information.

No. The PowerCam 2.0 Digital Camera requires a USB power connection and Windows NT does not support USB.

For some applications specific vocabularies are available. For others it simply emulates keystrokes. Others take full advantage of the API when available.

WORKMATE has been written specifically for the 32 bit Windows operating systems (ie Windows 95/98/NT). To run on Windows 3.1 or Windows for Workgroups you need Saturn Datalink our 16 bit program..

Depends. It does not run under Windows NT/2000/XP, and it does not resize NTFS partitions, but it can move Windows NT/2000/XP partitions and it does not damage your Windows NT/2000/XP installation.

Yes. However, Windows NT, Windows for Workgroups, and Windows 95 all include a DPMI host, DOSX.EXE, with several serious bugs, some of which are difficult to work around. As a result we could not warranty operation of DOS/4G under any early versions of these operating systems. We have worked around some of these problems in version 2.0 of DOS/4G and would be interested in hearing whether or not you experience problems running your DOS/4G programs under these environments.

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.

It should however run Windows emulators that include x86 CPU emulators such as Twin, as well as Windows itself under whole-PC emulators such as Bochs. In either case however you will need to run another operating system, such as GNU/Linux, and emulation will likely be fairly slow. And of course there is the slight possibility that Microsoft will port Windows NT to the F1, but I wouldn't hold my breath. ;-)

Answer: The Corporate Voice Room may be compatible with Windows NT version 4.0 only. However, the Corporate Voice Room works best with Microsoft Windows 2000 and XP.

All TracePlus applications are compatible with Windows NT 4.0 Workstation or Server running either Service Pack 5 or Service Pack 6a. We do not support any other Service Packs. TracePlus does not support Windows NT 4.0 with no service pack installed. With the release of Windows XP SP2 and Windows 2003 Server SP1, Microsoft introduced a feature called Data Execution Prevention (also known as DEP).

Solaris PC NetLink 2.0 software is compatible with SP4, and testing has shown that Solaris PC NetLink software also works fine with Windows NT Server 4.0 (with SP5 and SP6) with Windows NT default Registry settings.

Actually (and unfortunately) yes. The old-style NTCONFIG.POL files can, indeed, affect both Windows 2000 and Windows XP workstations. And, as always, use with care, because these policies are considered preferences which “tattoo” the registry, where (by and large) Group Policy settings do not tattoo. (See the FAQ “What is the difference between Policies and Preferences?”) There is a single password policy which all users in the domain must embrace.

Answer: Most software that runs under NT 4.0 will run under Windows 2000; however there have been some software packages that do not run under Windows 2000. Some software requires power user or administrator privileges to run, and some require that they be run from the account that they were installed from. Both Beams Division and the TOC group has tested various software packages under Windows 2000. Beams Division's results are at http://www-bdnew.fnal.gov/network/w2k-software.

Yes. PowerArchiver 2006 9.64 and greater will work great in Windows Vista. PowerArchiver 2007 has been designed with full support for Vista and has received Windows logo certification.

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

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.

Generally, reactivating Windows is not necessary, but it should not be a problem either way. The Windows activation process is actually tied to several components on the system. Microsoft has a Technical Market Bulletin on Windows Product Activation (WPA) that explains how it works. Basically, WPA generates a hash based on approximately 10 different hardware items. While this includes the serial number of the hard disk, this is only one component of the hash key.

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.