Date: Tue, 10 Dec 1996 07:49:56 +0100 (MET) From: Matthias Apitz <guru@softcon.de > Subject: Re: HylaFax

No it can't. You would need Windows 2000/2003 Server. It can however read log files from a Windows NT Server. This happens because no user is logged into the Terminal Services Server at the Server, so the SurfStatsLiveComPlus package has no identity to execute under.

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 .

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.

HylaFAX is intended to run on any UNIX system that supports a particular set of features: FIFO special files, BSD-style sockets and the TCP/IP communication protocols, BSD-style file locking (flock) or equivalent functionality from which it can be emulated (fcntl, lockf), and POSIX 1003.1-style interfaces, including termios for manipulating tty devices. The following systems are known to have these features: AIX v3.x, v4.x BSD/386, FreeBSD, HP-UX 9.x, 10.x IRIX, ISC4.0, Linux, OSF/1 V1.3 and V3.

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.

Which operating system you decide to use should depend on what features you need. For example, if you are already using IIS, ASP, VBScript, Windows Media, Microsoft Access, Microsoft SQL Server, or Visual InterDev, and you don't have the time to learn Unix-based solutions, you'll have to choose a Windows NT or Windows 2000-based host. Just because your desktop is Windows-based doesn't mean you should use a Windows host.

Yes. The Scribe Administrator provides an option in Preferences to set the server as the NT service. Alternatively, you can use InstallScribe-NT.bat script to install Scribe Resident Server as an NT service. This script can be found in the Scribe server installation directory (the default location is C:\Program Files\ScribeAdmin).

Starting with version 2.xx, PunchClock Server can be configured to run as a native Windows service application that works in the background. Click here for detailed instructions. In order for PunchClock Pro to function properly, you need to make sure TCP traffic on port 65439 and 65440 is not being blocked.

There are those that have run the demo on NT4, but the good folks at FASA Interactive say the best bet will be to wait until NT5 is released. Of course that also means you'll need that much more RAM to play.

a) Run Idem and configure your source-destination folders, set menu Log active if you whish a daily report of list of files processed. d) to run the Idem Service, ensure that you follow above considerations about Windows and account rights. run it using a true account with the appropriate rights (something like 'Administrator'). Do not use the default 'LocalSystem' account. This is necessary to be able to replicate files out of the NT box (and this is not our conditions but Microsoft's..

Answer: Yes, we are not limited to running on Windows Server. However, you are limited to the number of socket connections used on Windows NT Workstation, this is a Microsoft limitation. Although this is not enforced by Microsoft.

Our products may run on Windows ME or Windows NT, but we do not support these operating systems: we only support our products on Windows 2000 and Windows XP. You can download the evaluation versions of our products and try them on other versions of the Windows operating systems to see if they work for you.

Sure. Just install it on your Windows NT. And remember to restart your computer no matter Windows NT server or Windows NT workstation to apply system wide changes made by "Nice PDF Creator". Usually, "Nice PDF Creator" should be installed on Windows NT with Service Pack 3 or later installed.

The answer depend on what GRBackPro version you have installed. Version 5.x run on both Windows Workstation and Windows Server. Version 6.x has two different licenses: A Single User license for installation on Windows Workstation and a Server license for installation on a Windows Server. If you backup from a Windows Server edition then a Server license should be used for 4-5 users. If your server handle more users you need a Site license. This license has been created to handle companies.

No. It is not possible to run Terminal Services in Application Server mode on Windows Small Business Server 2003. This is a change from Small Business Server 2000. Running Terminal Services in Application Server mode on a domain controller may present a security risk to your network.

If you have to ask that, you should probably go back to Windows 98. Don't ask about Windows 2000 Server either.

We don't offer a Windows NT dedicated server because we feel that BSDI Unix O/S is a far more robust operating system. See http://www.bsdi.com/info/nt-comparison.html for more details. Please note that most technical questions are answered by an online technical support FAQ located on our web site. See page (home.html). Any other specific technical questions should be directed to support@wylie1.com.

The name of this software package is "HylaFAX", not "hylafax", "Hylafax", or anything else. Also, do not call this software by its old name "FlexFAX" because that name is a trademark of another fax product and the folks that own that trademark are possessive. Please also note that "HylaFAX" is a trademark of Silicon Graphics and it should be treated as such when used in documentation.

HylaFAX is intended to be used with fax modems. Fax modems are not the same as data modems though most contemporary data modems also include support for fax communication. HylaFAX should work with any Class 1, 1.0, 2, 2.0 or 2.1 fax modem. Wherever possible HylaFAX works around known modem problems or restricts modem usage in order to provide a functioning system.

where <version> is found in the file VERSION and <n> is the number recorded in dist/hylfax.alpha. This string is also prominently displayed when you run the configure script to setup the software for compilation and each time the faxq scheduler process is started (look in the file where syslog messages are recorded).

That's hard to answer. Most Class 1, 1.0, 2, 2.0, and 2.1 fax devices will work with HylaFAX with varying levels of success. You can get a relatively good idea of the best hardware to use with HylaFAX via the Hardware Compatibility List or at http://shop.ifax.com.

There are many support options, both free and commercially provided. Please see the Support page for more information.

ASSET was designed for compatibility with the Microsoft Windows NT family of operating systems (NT/2000/XP). Please download the instructions detailing the steps required to install NIST ASSET on Windows NT using the NIST ASSET installer.

All of our servers are UNIX-based (RedHat). We do not operate any servers on the Windows NT platform. [top]

TrayIcon Explorer will run on Windows NT 4.0 and later (previous versions of Windows NT didn't have the system tray).

Yes. You must ensure that all of the appropriate transport services are available to the service. You must also ensure that sufficient information is given in the connection string to start the database.

Yes. OpenCNC runs on Windows NT using the Ardence RTX real-time extension. The result is hard real-time deterministic processing from a single processor and a single operating system. In addition, MDSI is a Microsoft Certified Solution Provider and supports Microsoft Corp.'s Windows Distributed InterNet Applications Architecture for Manufacturing (Windows DNA for Manufacturing). No.

There are several freely available tools on the internet that allow you to set up a Java application as an NT service. See the following links;