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.

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.

No. CLDC specifies the core libraries and virtual machine features for J2ME implementations on resource-constrained devices. A CLDC implementation includes a virtual machine. For instance, KVM is included in the CLDC reference implementation.

There are a number of tools and emulators that are available on the market depending on the developer's needs. Developers can utilize the CLDC reference implementation for basic CLDC development. Many developers also utilize the J2ME Wireless Toolkit to develop applications based on CLDC, MIDP, and other optional packages.

No. Virtual Server 2005 R2 does not support Direct3D. Virtual Server emulates an S3Trio64 video card for 2d video. Virtual machines do not receive additional protection running in a virtualized environment. Each virtual machine is its own entity and needs to be patched individually.

Any application that runs on guest operating systems supported by VMware Server can run in a virtual machine. Customers commonly deploy the following applications within virtual machines: Web and Application Services: Microsoft IIS, Apache, IBM WebSphere, Macromedia ColdFusion, BEA WebLogic Application Server

No. There is a native sanos API. You can develop applications in C using Microsoft Visual Studio. The native sanos API resembles the standard POSIX Unix API, with functions like open(), close() etc. There is also an implementation of the ANSI Standard C library routines. See here for a brief guide to building a simple hello world application in C for sanos.

Use the latest, greatest, fastest JVM you can get your hands on for your platform. The compiler's performance is dependent on the performance of the JVM it is running on, so the faster a JVM you can find to run it on, the shorter your compile times will be. At a minimum you need to use a Java 2 or later JVM to run the compiler (J2SE 1.3 for AspectJ 1.1). We realize that this constraint can be a problem for users who don't currently have a Java 2 JVM available.

Building PXE from source requires JDK 5.0, as PXE sources make some use of generics. JDK 5.0 should be used to run PXE (see Running PXE on 1.4 for additional information regarding JDK 1.4 deployment).

FreeMind works with the virtual machines from Sun, from the version 1.4.0 and higher. FreeMind has been reported to run on the JDK 1.4.2 from Blackdown. FreeMind also works on Linux with Sun Microsystems 64bit JDK version 1.5.0. There is a known issue with official release 0.8.0 of Freemind and Java 6. Encrypted nodes will wipe out your map when trying to save it to disk. Stick to Java 5 (alias 1.5.x) (see bug report) (https://sourceforge.

Most of applications can be installed within of the Virtual Private Server without any modifications. Our customers are using Oracle, DB/2, Weblogic, Websphere and other commerical applications quite succesfully. Applications and services do not have to be aware of Virtuozzo. However, direct access to hardware is not available.

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.

many as the hardware allows, which depends on the amount of available RAM, disk, and system resources—or up to 64 virtual machines.

Ans: Yes, we can... but we should caution you that there are still a lot of old browsers out there that are not Java-enabled. Older AOL browsers, for example, have a devil of a time with Java. We are frankly looking forward to the time when the whole web is fully utilizing the interactive capabilities of the platform-independent language and world of Java. Ans: We have an excellent form script in our CGI Bin, written in perl.

J2SE 1.3 or later is required. We have not tested extensively with the latest 1.5 JVM. So we packaged a 1.4.x JVM with the latest installer of D2K 4.1.1.

J-DSP is a set of Java applets that require a Java virtual machine to run properly. Before launching J-DSP, the courseware will provide you with the opportunity to link to Sun to download the latest Java virtual machine at http://java.com/en/index.jsp (Windows-only). If you are a Mac user you can download a current Java virtual machine directly from Apple at http://docs.info.apple.com/article.html?artnum=120209.

A6) NSIcom CrEme JVM will work. Follow the Software Application Installation Application Note. This may require additional program memory. If so, from the download page, download and install the NP-612S 20M Program Memory Image. Follow the Windows CE Download Instructions.

No, you do not need any Microsoft .NET components to deploy or run your application. Mainsoft for Java EE creates fully compliant Java EE applications that run on any Java EE-enabled server, including Linux, UNIX, and Windows. No. System administrators can install and manage applications created with Mainsoft for Java EE as standard Java EE applications.