On Windows, where Allegro CL processes are implemented with native operating system threads, a single Lisp thread and any number of foreign threads independent of the Lisp heap may run at the same time on different processors. [A "foreign thread" is an ACL process that has made a foreign call and released the heap or an independent thread started by a call to a foreign library function. See this for more information.

The number of virtual machines running per host depends on several things, including physical memory, processor, and workload running in the guest. With Virtual Server 2005 R2, you define the amount of memory available to a virtual machine, and that memory allocation can be altered to reflect the needs of the virtual machine.

The current version of Allegro CL is 8.1 on all supported platforms. This version was released in August, 2007. Or, 8.1 was released 8/1/2007.

Raster3D is distributed as source code (mostly Fortran, with a few C routines), so it should run on anything that has Fortran and C compilers installed. You wouldn't believe how many strange compilers are out there, however, so I can only promise smooth installation on machine configurations which I have tested myself. That means mostly unix boxes, including those from DEC/Compaq/HP (DU4, Tru64), SGI (Irix), and IBM (AIX). The source distribution builds smoothly under linux.

Yes, there is a mailing list for Allegro CL users. It is accessed through the address allegro-cl@franz.com. To be added to or deleted from this list, send mail to allegro-cl-request@franz.com. Franz periodically makes announcements on this mailing list, but its main purpose is to allow members of the Allegro CL (both Unix and Windows) to communicate with each other, sharing ideas, complaints and code. Note: the mailing list address used to be allegro-cl@cs.berkeley.

Our documentation is updated online after release as needed. The updated documentation is available on the Franz Inc. Web and versions are available for downloading. See http://www.franz.com/support/documentation/ for both online documentation and downloadable updates. For each released version of Allegro CL, we compose a list of current operating system levels on which we have tested and on which we know our product will work. This list is also located in installation.

The fundamental issue with Allegro CL working on a new operating system versions is whether the operating system has any fundamental issues that break Allegro CL. Typically, when the operating system is a natural progression from one which we currently support, we will take specific steps to resolve incompatibilities. Incompatibilities most often occur when an operating system vendor changes the signal-handling interface, usually to be more Posix compliant. The change can break Allegro CL.

Updating patches is a two-step process. First, a user typically calls the function (sys:update-allegro) to download all available patches, exits all lisps, then runs update.exe. Both of these operations result in the creation or modification of files in the Allegro directory. Windows Vista has a security model that disallows installation of files into c:\Program Files\ if you do not have Administrator priviledges, which is where Allegro CL is installed by default.

Mapping from Lisp threads to native operating system thread library. On Linux this means 'NPTL'. On Windows this is the WIN32 library. Making the compiler and library of Lisp code written for the implementation SMP "thread safe". By "thread safe", we mean the orderly updating of global resources. For example, two threads adding to a hash table, changing a symbol's value or defining a method on a generic function.

Each instance of the engine is uniquely identified, and as such you do not want to copy the config from one folder to another. Simply install a new instance of the program into a different directory. Register it with your email address, and it will be up and running using your hyperthreaded or second processor. Note: It should be noted that when running two instances TSC on a dual processor machine you should not attempt to have them both in your start up file because both will not auto start.

It will run, but only if you use a stripped down version (less features compiled in), and have almost NO drivers, etc loaded into memory. TNOS must exist in conventional memory, and on processors earlier than a 386, you had no support in the CPU for altering memory maps to maximize the conventional memory. I ran TNOS on a 286 for several years, I just needed a good "shoehorn" to get in what features I needed." So there you go.

Why have a single, dual processor machine when you can have multiple redundant servers. Server Load balancing provides us the abililty to scale your website when you need that extra horsepower, it is that simple.

Yes. CLDC-based applications can execute in other Java Virtual Machines, provided that the required CLDC libraries, profiles, and/or optional packages are also available.

If the operating system you are interested in running Allegro CL on is the same lineage and the underlying architecture is the same as one which we have already listed as supported, the best question to ask us is

We can answer this question "yes" or "no", which will tell you as the customer whether we have any negative experiences with the operating system version. (The information here may also provide the answer.) If the operating system is very new, the answer to this question might more likely be "no", because the assumption is that the new version is compatible, unless and until it proves otherwise. Other questions that you might ask, if you know that your operating system is very new, are

This is a known bug in Mac OS X. Programs which catch Unix-style signals and handle them will still result in "crash" reports being generated erroneously by the CrashReporter. See http://developer.apple.com/technotes/tn2004/tn2123.html#SECLIMITATIONS and note close to the end of the page under the heading "CrashReporter Limitations", specifically the bug labelled 2941263. It looks from the page as though this CrashReporter has only started in MacOSX 10.

Because it simplifies the command line by storing any or all of the following in the regestry [HKEY_LOCAL_MACHINE \ SOFTWARE \ Public Domain \ Blat]. SMTP Server Address Sender's Address Number of times to retry sending Port number to use (ie, if not the SMTP default of 25) The -q switch which "supresses *all* output" Blat -install smtphost.bar.com foo@bar.com // Sets host and userid Blat -install smtphost.bar.com foo // Sets host and userid Blat -install smtphost.bar.

No. While the SSL module fasl file was included in the Express, it was not intended that the SSL interface be available in the Express Edition. If you have the need for an SSL interface, we gladly urge you to contact us at info@franz.com for an evaluation of our Professional or Enterprise Editions. Section 19.4.

R is being developed for the Unix, Windows and Mac families of operating systems. Support for Mac OS Classic ended with R 1.7.1. The current version of R will configure and build under a number of common Unix platforms including cpu-linux-gnu for the i386, alpha, arm, hppa, ia64, m68k, mips/mipsel, powerpc, s390, sparc (e.g., http://buildd.debian.org/build.php?&pkg=r-base), and x86_64 CPUs, powerpc-apple-darwin, mips-sgi-irix, rs6000-ibm-aix, and sparc-sun-solaris.