Yes. NuTCRACKER Platform applications work with any X server because all X clients and servers speak the same, standard protocol. We have not found a Windows X server that fails to work with Toolkit.

The NuTCRACKER Platform is the runtime component of Toolkit that provides UNIX system-layer emulation in a Win32 environment. MKS Toolkit for Enterprise Developers and MKS Toolkit for Professional Developers include header files, libraries, and other SDK tools that support development and deployment of NuTCRACKER Platform applications and DLLs.

Yes, this is a major advantage of using Toolkit. Please see the "HowTo" in the MKS Toolkit Resource Kit for details and source examples. In addition, see Evolving Applications with COM in the Cross-Platform Developer's Guide.

X Server is a program that provides display and user input services to other programs. In comparison, a file server provides other programs with access to file storage devices. File servers are typically located in a remote location and you use the services of a file server from the machine that you are located at.

Yes, this is easy to do in Toolkit. Refer to Porting Shared Libraries in the Cross-Platform Developer's Guide.

It is possible to retrieve the underlying Win32 handle from the NuTCRACKER Platform with the _NutFdToHandle() API (or donate a handle to the NuTCRACKER Platform with _NutHandleToFd()). It is not possible, however, to share socket handles in this way. Once the NuTCRACKER Platform owns a socket handle, you may not continue to manipulate it with Win32 calls and vice versa. Yes. Toolkit implements FIFOs that are compatible with standard UNIX implementations.

Yes, this is a major advantage of using Toolkit. Please see the "HowTo" in the MKS Toolkit Resource Kit for details and source examples. In addition, see Evolving Applications with COM in the Cross-Platform Developer's Guide.

You could have a byte-ordering problem. The MKS Toolkit Resource Kit contains a port of ONC RPC, including XDR. The XDR functions (and the program RPCGEN) help you encode and decode binary data. The resource kit contains a sample use of XDR to save/retrieve a data structure in a platform neutral form, using the xdrstdio library. Libraries exist for UDP, TCP, memory, and the file system. The Toolkit socket library has implementations of htons(), htonl(), ntohs(), and ntohl().

My targeted platform is Linux with an X server. It may coincidently run on any of the free BSD implementations considering the prerequisite tools should be available for them as well. I will try to make certain that the C code generated does not suffer from any endianness or 32/64 bit issues to ensure it will run on all types of Linux platforms. Any non Unix like OS will most likely require some porting effort, which I can not do personally.

Linking a program causes the following error on Linux: /usr/bin/ld: cannot open -lgmp: No such file or directory

Yes, you have to have some form of X server (unless you're running Windows, of course). It needs an X server for image processing, and for font manipulation. However, if you wish to run in batch mode, you can run with a special, frame-buffer-less X server called Xvfb, which doesn't require a graphics card or mess with your screen: Xvfb :1 -screen 0 10x10x8 -pixdepths 1 & gimp --display :1.0 --no-interface --batch "commands" ..

Some servers have no facility for this; you may be able to adjust your monitor to correct somewhat. Later versions of XFree86 allow these server options: gamma f set gamma value (0.1 < f < 10.0) Default: 1.0 -rgamma f set gamma value for red phase -ggamma f set gamma value for green phase -bgamma f set gamma value for blue phase

Most things we sell will not work with Dells - their proprietary hardware may not work with generic gear. We've found that most USB, Firewire, TV Tuner and memory products we sell, and ALL power supplies and motherboards (without exception), will not work on Dell equipment - the same gear usually works just fine with "generic" PC hardware that we sell, though.

coLinux currently doesn't support running an X server that requires a graphic adapter, because such virtual adapter doesn't exist at the moment. If you want to use X, you can run a Windows X server such as Cygwin/X or Xming, and launch an X session across the virtual network. The reason is that there are limitations enforced by Windows's non-cached memory allocator. This pool is hardcoded to a limit of 256MB and even 128MB on some systems.

This code is probably part of the source to a lisp compiler, which knows how to open-code calls to CAR. However, the interpreter also needs to know how to call CAR, which is what the above defun is doing. This is not recommended in user code... This question is usually motivated by the existence of labels, which is a similar form for binding functions, but also allows mutual recursion between the functions being bound. Given this, it is perhaps natural to question the utility of flet.

Yes, you have to have some form of X server - the GIMP is an X application! It needs an X server for image processing, and for font manipulation. However, if you wish to run in batch mode, you can run with a special, frame-buffer-less X server called Xvfb, which doesn't require a graphics card or mess with your screen: Xvfb :1 -screen 0 10x10x8 -pixdepths 1 & gimp --display :1.0 --no-interface --batch "commands" ..

While the Ayam core functionality (modelling, RIB export) is available everywhere, functionality that is realized through plugins is not available on every platform. This is mainly due to deficiencies in operating system implementations and limited availability of third party software. Aqsis is using two processes when rendering. Ayam can only kill the first one (which is directly spawned by Ayam).

Check the source code to Zinf out on platform X and get it to compile. Once you have it compiling and Zinf is reasonably stable, please send us a set of patches and we will include your changes in the next Zinf distribution. Check out the geek pages for details on this how to check out the source code.

The platform should be fully application-ready, with the processing power and memory to support third-party applications. The system should be standards-based and use standard application programming interfaces like VoiceXML and TAPI.