64bit virtual drive
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 1581
Linux Virtual Server 1.21
Linux Virtual Server is a load-balancing and server clustering system for Linux. more>>
The Linux Virtual Server is a highly scalable and highly available server built on a cluster of real servers, with the load balancer running on the Linux operating system.
The architecture of the server cluster is fully transparent to end users, and the users interact as if it were a single high-performance virtual server.
The basic goal of the Linux Virtual Server Project is to:
- Build a high-performance and highly available server for Linux using clustering technology, which provides good scalability, reliability and serviceability.
<<lessThe architecture of the server cluster is fully transparent to end users, and the users interact as if it were a single high-performance virtual server.
The basic goal of the Linux Virtual Server Project is to:
- Build a high-performance and highly available server for Linux using clustering technology, which provides good scalability, reliability and serviceability.
Download (0.03MB)
Added: 2005-04-06 License: GPL (GNU General Public License) Price:
1673 downloads
The 64 bit Virtual CPU Project 0.0.23
The 64 bit Virtual CPU Project is a project to create 64-bit virtual CPU. more>>
This is a project to create 64-bit virtual CPU, create a 64 bit assembler for the CPU and then port C to it, and then create scripts to port GNU/Linux to it.
The aim is to run 64-bit Linux on common 8/16/32 bit CPUs in applications where speed is not an issue.
Enhancements:
- Added C code intended tor a PIC Preliminary documentation More updates to Gambas program
<<lessThe aim is to run 64-bit Linux on common 8/16/32 bit CPUs in applications where speed is not an issue.
Enhancements:
- Added C code intended tor a PIC Preliminary documentation More updates to Gambas program
Download (0.67MB)
Added: 2005-07-06 License: GPL (GNU General Public License) Price:
1600 downloads
Virtual Drum Machine 0.3
Virtual Drum Machine is a simple drum machine. more>>
Virtual Drum Machine is a simple drum machine.
It works for little endian/linux kind of machines. You may let it work on others machines, but you probably will get troubles with it.
You definitely need oss (or maybe alsa) for sound output, and a posix-like operating system. To let it work on a big endian machine should be painful.
You write a rhythm, then you compile it, then you are able to play it to your sound card or save it to a file.
The Virtual Drum Machine is made of
- the Rhythm Compiler,
- the runtime library.
The Virtual Drum Machine is in the public domain. Who needs a license? money makers? Protection against robbery? let me laugh... Read any text of law, you will see where the robbers reside.
A simple file would look like :
void main_rhythm(void)
{
tempo = 120;
- a
. b
. b
.
- a
.b
- a
.
. b
. b
- a c
. b
}
Install:
Do a "./configure" in the drums directory, then "make", then "make install", it should be alright. You can listen to some examples in the examples/ directory.
Who yo use it?
Write a rhythm. Compile it with "rc". Run the produced program. You are done.
See the examples/ directory to get the point.
When you run an example, try "-h" to get the available options.
It should be self-explanatory.
The rhythm compiler has several options. By running "rc --help", all should be clear.
Technical Details:
The compiler will parse the input file line by line.
If a line starts with "*" or "." (not counting leading white spaces), the whole line is seen as a rhythm line, and is transformed into C code. If not, it is passed as is to the C file.
Beware! You MUST NOT start any C code line by "*" or "."!
You can create as much functions as you want, write any C code you want. But remember that a line starting by "*" or "." is seen as a rhythm line and is translated by "rc" into C code.
You must provide a "void main_rhythm(void)" function, that will be called by the library. It is the starting point of your rhythm. It can be "void main_rhythm(int argc, char *argv[])" too, with common meaning for those parameters (non-C coders will have trouble with the Virtual Drum Machine).
You can change the tempo (ex. "tempo=100;") or the volume (ex "vol=0.4;") at any time. Each sample comes with its own volume and panning (ex. "a.vol = 0.1;" "a.pan=-0.8;"). Volumes range from 0 to what you want. 1 is for the normal volume. Panning ranges from -1 (left) to 1 (right). 0 is center. All values are double. You can use "volume" instead of "vol", and "panning" instead of "pan". There is no global panning, if you want all left, set all samples to left.
To run in stereo mode, dont forget "-s" when running the generated program. It is mono by default.
You absolutely need to compile and run the examples, and read them to get the point out of it!
The "rc.conf" file contains configuration informations. You specify the sample by "sample" followed by its name (the one you will use in your rhythm files), then the file that will be played. The name of the sample must start by a letter, followed by letters and/or numbers (it must be a valid C identifier, without "_" though). The configuration file contains the install directory, used by "rc" to compile your rhythms. Take a look at the one that is provided to see how to use it.
The sound files are simple wav files. They all should be of the same rate, which can be specified to the generated program, using the "-f" option (44100 is the default). (The library only handles very basic wav files, if yours dont work, you probably will have to modify the library for the program to handle it.)
When you add a sample, you must modify "rc.conf" for the changes to appear. The samples are hard-linked to the produced program, so if you change "sample a /some/dir/file1.wav" by "sample a /one/other/dir/file2.wav" in the configuration file, the previously generated programs will still use "/some/dir/file1.wav". You will have to compile them again to take the changes into account.
Enhancements:
- The code has been modified to let gcc 4 compile it.
<<lessIt works for little endian/linux kind of machines. You may let it work on others machines, but you probably will get troubles with it.
You definitely need oss (or maybe alsa) for sound output, and a posix-like operating system. To let it work on a big endian machine should be painful.
You write a rhythm, then you compile it, then you are able to play it to your sound card or save it to a file.
The Virtual Drum Machine is made of
- the Rhythm Compiler,
- the runtime library.
The Virtual Drum Machine is in the public domain. Who needs a license? money makers? Protection against robbery? let me laugh... Read any text of law, you will see where the robbers reside.
A simple file would look like :
void main_rhythm(void)
{
tempo = 120;
- a
. b
. b
.
- a
.b
- a
.
. b
. b
- a c
. b
}
Install:
Do a "./configure" in the drums directory, then "make", then "make install", it should be alright. You can listen to some examples in the examples/ directory.
Who yo use it?
Write a rhythm. Compile it with "rc". Run the produced program. You are done.
See the examples/ directory to get the point.
When you run an example, try "-h" to get the available options.
It should be self-explanatory.
The rhythm compiler has several options. By running "rc --help", all should be clear.
Technical Details:
The compiler will parse the input file line by line.
If a line starts with "*" or "." (not counting leading white spaces), the whole line is seen as a rhythm line, and is transformed into C code. If not, it is passed as is to the C file.
Beware! You MUST NOT start any C code line by "*" or "."!
You can create as much functions as you want, write any C code you want. But remember that a line starting by "*" or "." is seen as a rhythm line and is translated by "rc" into C code.
You must provide a "void main_rhythm(void)" function, that will be called by the library. It is the starting point of your rhythm. It can be "void main_rhythm(int argc, char *argv[])" too, with common meaning for those parameters (non-C coders will have trouble with the Virtual Drum Machine).
You can change the tempo (ex. "tempo=100;") or the volume (ex "vol=0.4;") at any time. Each sample comes with its own volume and panning (ex. "a.vol = 0.1;" "a.pan=-0.8;"). Volumes range from 0 to what you want. 1 is for the normal volume. Panning ranges from -1 (left) to 1 (right). 0 is center. All values are double. You can use "volume" instead of "vol", and "panning" instead of "pan". There is no global panning, if you want all left, set all samples to left.
To run in stereo mode, dont forget "-s" when running the generated program. It is mono by default.
You absolutely need to compile and run the examples, and read them to get the point out of it!
The "rc.conf" file contains configuration informations. You specify the sample by "sample" followed by its name (the one you will use in your rhythm files), then the file that will be played. The name of the sample must start by a letter, followed by letters and/or numbers (it must be a valid C identifier, without "_" though). The configuration file contains the install directory, used by "rc" to compile your rhythms. Take a look at the one that is provided to see how to use it.
The sound files are simple wav files. They all should be of the same rate, which can be specified to the generated program, using the "-f" option (44100 is the default). (The library only handles very basic wav files, if yours dont work, you probably will have to modify the library for the program to handle it.)
When you add a sample, you must modify "rc.conf" for the changes to appear. The samples are hard-linked to the produced program, so if you change "sample a /some/dir/file1.wav" by "sample a /one/other/dir/file2.wav" in the configuration file, the previously generated programs will still use "/some/dir/file1.wav". You will have to compile them again to take the changes into account.
Enhancements:
- The code has been modified to let gcc 4 compile it.
Download (0.67MB)
Added: 2006-02-08 License: Public Domain Price:
943 downloads
NVM Virtual Machine 2.0
NVM Virtual Machine is a small, fast, extensible and portable virtual machine. more>> <<less
Download (0.28MB)
Added: 2007-04-27 License: GPL (GNU General Public License) Price:
546 downloads
Virtual Cron 0.1
Virtual Cron is a PHP library that can check whether it is time to run a periodical task. more>>
Virtual Cron is a PHP library that can check whether it is time to run a periodical task. The class can be used to check whether it is time to run a task that must run from time to time.
It creates a control file to keep track the last time the task was scheduled.
The class can check the control file last modification time to determined whether it passed a given period of time since the last time the task was run.
If the given interval time has passed since the last run, the class recreates the control file and returns true to inform the application that is time to run the task again.
<<lessIt creates a control file to keep track the last time the task was scheduled.
The class can check the control file last modification time to determined whether it passed a given period of time since the last time the task was run.
If the given interval time has passed since the last run, the class recreates the control file and returns true to inform the application that is time to run the task again.
Download (MB)
Added: 2007-04-24 License: LGPL (GNU Lesser General Public License) Price:
924 downloads
Kool Virtual Decks 0.0.0b
Kool Virtual Decks project is a professional double CD player emulator like Virtual Turn Tables. more>>
Kool Virtual Decks project is a professional double CD player emulator like Virtual Turn Tables, BPM Studio or any other as you know.
The idea is that you can mix two songs like a DJ would make in his/her dual cd player or in his/her turntables.
Well this program is just a preview, and idea. It doesnt work yet.
If you want to join to this project or if you have any suggestion please e-mail me.
<<lessThe idea is that you can mix two songs like a DJ would make in his/her dual cd player or in his/her turntables.
Well this program is just a preview, and idea. It doesnt work yet.
If you want to join to this project or if you have any suggestion please e-mail me.
Download (0.26MB)
Added: 2006-10-09 License: GPL (GNU General Public License) Price:
1118 downloads
Virtual Ring Buffer 0.5.0
Virtual Ring Buffer (VRB) is an implementation of a character FIFO ring buffer. more>>
Virtual Ring Buffer (VRB) is an implementation of a character FIFO ring buffer. Virtual Ring Buffer provides direct access to the buffer so the calling program can construct output data in place, or parse input data in place, without the extra step of copying data to or from a calling program provided buffer area.
In order to facilitate this direct access, VRB makes sure that all references to buffer locations for either output or input is always a single contiguous block of memory so that the calling program does not have to deal with split buffer spaces every time the cycling of data reaches the end of the buffer and wraps around to the beginning.
Thus, the calling program is free to use any number of tools available which do not have to be aware that they are operating directly in a ring buffer. In the latest version, VRB also provides a buffer overflow protection mechanism so that buffer overflow bugs force the program to be trapped by the operating system if accessed pointers wander beyond the range of address space managed by VRB. This feature can be disabled if desired, since it occupies 2 extra pages of address space.
VRB does all this without adding any copying overhead of its own. This ability is achieved by placing a mirror image memory map immediately after the buffer that is a reference to exactly the same memory as the buffer itself. Thus a reference to the memory location immediately past the last location in the buffer accesses the same physical RAM as the beginning of the buffer.
Thus a pointer near the end of the buffer that has a length that would otherwise have to wrap around will instead extend into the mirror image space to get the same result, but without any special handling by the program.
Installation:
First extract the source where you wish to store it. One of these commands might be used within the desired directory after the tar files has been downloaded there:
bunzip2 < vrb-0.5.0.tar.bz2 | tar -xpf -
gunzip < vrb-0.5.0.tar.gz | tar -xpf -
A subdirectory called vrb-0.5.0 is created. Execute these command to change into that directory and compile the source (changing the prefix if desired):
cd vrb-0.5.0
./Configure --prefix=/usr/local
make clean
make install
Note that unlike most other source packages using a configuration system, the configure command name is capitalized. The above commands will not install the man pages at this time. To install the man pages, simply copy them to the desired location, such as:
cp -p vrb/man/man3/*.3 /usr/local/man/man3
Usage:
VRBs basic approach designed into its API is that the calling program asks for the address and length of either the empty space where output data can be placed, or the data space where input data is present (previously placed there). These steps are implemented by macros for maximum speed, and are separate for address and length. The calling program then accesses that data directly in the buffer via that address (and length).
Once the data handling is complete, the calling program decides how much of that data it has inserted into empty space, or taken from data space, and calls VRB functions to indicate the which, which updates pointers (but does not copy any data). There are also functions available to assist in doing read/write I/O. Once the man pages are installed, the command man vrb is the starting point.
Enhancements:
- A vrb_empty function was added.
- Dead code in vrb_take was cleaned up.
- A poll loop was implemented in vbuf. vbuf now uses getopt.
- Buffer size calculation and data type/format were fixed in vbuf.
<<lessIn order to facilitate this direct access, VRB makes sure that all references to buffer locations for either output or input is always a single contiguous block of memory so that the calling program does not have to deal with split buffer spaces every time the cycling of data reaches the end of the buffer and wraps around to the beginning.
Thus, the calling program is free to use any number of tools available which do not have to be aware that they are operating directly in a ring buffer. In the latest version, VRB also provides a buffer overflow protection mechanism so that buffer overflow bugs force the program to be trapped by the operating system if accessed pointers wander beyond the range of address space managed by VRB. This feature can be disabled if desired, since it occupies 2 extra pages of address space.
VRB does all this without adding any copying overhead of its own. This ability is achieved by placing a mirror image memory map immediately after the buffer that is a reference to exactly the same memory as the buffer itself. Thus a reference to the memory location immediately past the last location in the buffer accesses the same physical RAM as the beginning of the buffer.
Thus a pointer near the end of the buffer that has a length that would otherwise have to wrap around will instead extend into the mirror image space to get the same result, but without any special handling by the program.
Installation:
First extract the source where you wish to store it. One of these commands might be used within the desired directory after the tar files has been downloaded there:
bunzip2 < vrb-0.5.0.tar.bz2 | tar -xpf -
gunzip < vrb-0.5.0.tar.gz | tar -xpf -
A subdirectory called vrb-0.5.0 is created. Execute these command to change into that directory and compile the source (changing the prefix if desired):
cd vrb-0.5.0
./Configure --prefix=/usr/local
make clean
make install
Note that unlike most other source packages using a configuration system, the configure command name is capitalized. The above commands will not install the man pages at this time. To install the man pages, simply copy them to the desired location, such as:
cp -p vrb/man/man3/*.3 /usr/local/man/man3
Usage:
VRBs basic approach designed into its API is that the calling program asks for the address and length of either the empty space where output data can be placed, or the data space where input data is present (previously placed there). These steps are implemented by macros for maximum speed, and are separate for address and length. The calling program then accesses that data directly in the buffer via that address (and length).
Once the data handling is complete, the calling program decides how much of that data it has inserted into empty space, or taken from data space, and calls VRB functions to indicate the which, which updates pointers (but does not copy any data). There are also functions available to assist in doing read/write I/O. Once the man pages are installed, the command man vrb is the starting point.
Enhancements:
- A vrb_empty function was added.
- Dead code in vrb_take was cleaned up.
- A poll loop was implemented in vbuf. vbuf now uses getopt.
- Buffer size calculation and data type/format were fixed in vbuf.
Download (0.047MB)
Added: 2006-03-07 License: LGPL (GNU Lesser General Public License) Price:
1330 downloads
High Level Virtual Machine 0.1
High Level Virtual Machine is a toolkit for developing virtual machines for dynamic languages. more>>
High Level Virtual Machine is a toolkit for developing virtual machines for dynamic languages.
The High Level Virtual Machine is:
- Based on LLVM (Low Level Virtual Machine). LLVM is HLVMs sister project. HLVM gains tremendous capability from LLVM in the areas of code generation, bytecode storage, runtime execution, etc.
- Aimed at supporting dynamic languages such as Ruby, Python, Perl, Jython, Haskell, Prolog, etc.
- A complete compiler developers toolkit for creating new languages easily. To write a new compiler, language designers simply write a plugin that describes the language to HLVM and how to translate the grammar productions into HLVMs comprehensive Abstract Syntax Tree (AST). After that, HLVM handles all aspects of code generation, bytecode storage, XML translation, JIT execution or interpretation, and native compilation.
- A language interoperability framework. Because all front end compilers generate code in the same AST, they can interoperate. Use of the runtime library for common constructs (e.g. "string") allow even complex data types to be shared between languages. Users of HLVM can write complex programs in multiple languages and be assured the result can be executed efficiently.
- A code management system including code revisioning, interface versioning, automated recompilation, separation of workspaces, etc.
- Currently under development. Project started April 20th, 2006. Stay tuned to this web site for future developments.
<<lessThe High Level Virtual Machine is:
- Based on LLVM (Low Level Virtual Machine). LLVM is HLVMs sister project. HLVM gains tremendous capability from LLVM in the areas of code generation, bytecode storage, runtime execution, etc.
- Aimed at supporting dynamic languages such as Ruby, Python, Perl, Jython, Haskell, Prolog, etc.
- A complete compiler developers toolkit for creating new languages easily. To write a new compiler, language designers simply write a plugin that describes the language to HLVM and how to translate the grammar productions into HLVMs comprehensive Abstract Syntax Tree (AST). After that, HLVM handles all aspects of code generation, bytecode storage, XML translation, JIT execution or interpretation, and native compilation.
- A language interoperability framework. Because all front end compilers generate code in the same AST, they can interoperate. Use of the runtime library for common constructs (e.g. "string") allow even complex data types to be shared between languages. Users of HLVM can write complex programs in multiple languages and be assured the result can be executed efficiently.
- A code management system including code revisioning, interface versioning, automated recompilation, separation of workspaces, etc.
- Currently under development. Project started April 20th, 2006. Stay tuned to this web site for future developments.
Download (0.12MB)
Added: 2006-06-15 License: LGPL (GNU Lesser General Public License) Price:
1227 downloads
Virtual server monitor 0.5
Virtual server monitor (vsmon) is a monitoring tool for Linux-VServer. more>>
Virtual server monitor (vsmon) is a monitoring tool for Linux-VServer that gives a system administrator a global view of all vservers running on his park.
For now, it does not offer control over the vservers life cycle (e.g. provisioning, start, stop, and restart operations). To use vsmon, you must deploy one backend on each vserver host and one frontend, preferably in its own vserver.
Enhancements:
- The frontend was reworked to display a summary of all hosts.
- An owner can be assigned to each vserver.
- The backend can be used on hosts without Linux-VServers, and it no longer obtains IP addresses.
- The libdnet dependency was removed.
- The parsing of /proc/"pid"/stat now works for kernel 2.6.18.
- A Nagios plugin was added, which enables the use of the vsmon backend to monitor a host disk, memory, and swap.
- The plugin monitors all mount points according to an "intelligent" algorithm, which determines warning and critical thresolds as a function of the total size of the partition.
<<lessFor now, it does not offer control over the vservers life cycle (e.g. provisioning, start, stop, and restart operations). To use vsmon, you must deploy one backend on each vserver host and one frontend, preferably in its own vserver.
Enhancements:
- The frontend was reworked to display a summary of all hosts.
- An owner can be assigned to each vserver.
- The backend can be used on hosts without Linux-VServers, and it no longer obtains IP addresses.
- The libdnet dependency was removed.
- The parsing of /proc/"pid"/stat now works for kernel 2.6.18.
- A Nagios plugin was added, which enables the use of the vsmon backend to monitor a host disk, memory, and swap.
- The plugin monitors all mount points according to an "intelligent" algorithm, which determines warning and critical thresolds as a function of the total size of the partition.
Download (MB)
Added: 2007-01-16 License: GPL (GNU General Public License) Price:
1015 downloads
Virtual Universe Client 0.72
Virtual Universe is a 3D cyberspace which offers more possibilities than just chat. more>>
The "Virtual Universe" is a 3D cyberspace which offers more possibilities than just chat: it is a combination of the Web, chat, and instant messaging within a realistic, three-dimensional cyberspace.
The "Virtual Universe" is a virtual reality environment which runs on top of the Internet.
Main features:
- chat with each other
- see the chat-partner as a virtual, three-dimensional person
- interact and communicate
- be creative in many ways
- create own worlds for any desired subject
Enhancements:
- A lighting bug in .COB/.SCN loader has been fixed.
<<lessThe "Virtual Universe" is a virtual reality environment which runs on top of the Internet.
Main features:
- chat with each other
- see the chat-partner as a virtual, three-dimensional person
- interact and communicate
- be creative in many ways
- create own worlds for any desired subject
Enhancements:
- A lighting bug in .COB/.SCN loader has been fixed.
Download (16.8MB)
Added: 2007-01-08 License: Freeware Price:
1020 downloads
C# Java Virtual Machine 1.0.1
C# Java Virtual Machine is a tiny implementation of the Java VM, including simple native classes. more>>
C# Java Virtual Machine is a tiny implementation of the Java VM, including simple native classes. This project is written using the C# language. The VM is very easily expandable by writing additional native or Java classes.
Enhancements:
- The DbConnection class, which provides a connection to MS SQL or PostgreSQL using ADO.NET, was added.
- The Syst.MachineName method, which returns the machine name, was added.
- String.startsWith and String.endsWith functions were added.
- Some comments for VM.cs were written.
<<lessEnhancements:
- The DbConnection class, which provides a connection to MS SQL or PostgreSQL using ADO.NET, was added.
- The Syst.MachineName method, which returns the machine name, was added.
- String.startsWith and String.endsWith functions were added.
- Some comments for VM.cs were written.
Download (0.40MB)
Added: 2007-05-25 License: GPL (GNU General Public License) Price:
884 downloads
joeq virtual machine 20030812
joeq virtual machine is a language-independent Java virtual machine implemented in Java. more>>
Joeq is a virtual machine and compiler infrastructure designed to facilitate research in virtual machine technologies such as Just-In-Time and Ahead-Of-Time compilation, advanced garbage collection techniques, distributed computation, sophisticated scheduling algorithms, and advanced run time techniques.
Joeq is entirely implemented in Java, leading to reliability, portability, maintainability, and efficiency. It is also language-independent, so code from any supported language can be seamlessly compiled, linked, and executed -- all dynamically.
Each component of the virtual machine is written to be independent with a general but well-defined interface, making it easy to experiment with new ideas.
Joeq is released as open source software, and is being used as a framework by researchers on five continents on topics ranging from automatic distributed virtual machines to whole-program pointer analysis.
Joeq is a virtual machine and compiler infrastructure designed to be a platform for research in compilation and virtual machine technologies. We had three main goals in designing the system. First and foremost, we wanted the system to be flexible. We are interested in a variety of compiler and virtual machine research topics, and we wanted a system that would not be specific to researching a particular area.
For example, we have interest in both static and dynamic compilation techniques, and in both type-safe and unsafe languages. We wanted a system that would be as open and general as possible, without sacrificing usability or performance.
Second, we wanted the system to be easy to experiment with. As its primary focus is research, it should be straightforward to prototype new ideas in the framework. With this in mind, we tried to make the system as modular as possible, so that each component is easily replaceable. Learning from our experience with Jalapeno, another virtual machine written in Java, we decided to implement the entire system in Java.
This makes it easy to quickly implement and prototype new ideas, and features like garbage collection and exception tracebacks ease debugging and improve productivity. Java, being a dynamic language, is also a good consumer for many of our dynamic compilation techniques; the fact that our dynamic compiler can compile the code of the virtual machine itself means that it can dynamically optimize the virtual machine code with respect to the application that is running on it. Javas object-oriented nature also facilitates modularity of the design and implementation.
Third, we wanted the system to be useful to a wide audience. The fact that the system is written in Java means that much of the system can be used on any platform that has an implementation of a Java virtual machine. The fact that Joeq supports popular input languages like Java, C, C++, Fortran, and even x86 binary code increases the scope of input programs. We released the system on the SourceForge web site as open source under the Library GNU Public License.
It has been picked up by researchers on five continents for various purposes, among them: automatic extraction of component interfaces, static whole-program pointer analysis, context-sensitive call graph construction, automatic distributed computation, versioned type systems for operating systems, sophisticated profiling of applications, advanced dynamic compilation techniques, system checkpointing, anomaly detection, secure execution platforms and autonomous systems. In addition, Joeq is now used as the basis of the Advanced Compilation Techniques class taught at Stanford University.
Joeq supports two modes of operation: native execution and hosted execution. In native execution, the Joeq code runs directly on the hardware. It uses its own run-time routines, thread package, garbage collector, etc. In hosted execution, the Joeq code runs on top of another virtual machine. Operations to access objects are translated into calls into the reflection library of the host virtual machine.
The user code that executes is identical, and only a small amount of functionality involving unsafe operations is not available when running in hosted execution mode. Hosted execution is useful for debugging purposes and when the underlying machine architecture is not yet directly supported by Joeq. We also use hosted execution mode to bootstrap the system and perform checkpointing, a technique for optimizing application startup times.
Joeq system consists of seven major parts:
- Front-end: Handles the loading and parsing of input files, such as Java class files, SUIF files, and binary object files.
- Compiler: A framework for performing analyses and optimizations on code. This includes the intermediate representation (IR) of our compiler.
- Back-end: Converts the compilers intermediate representation into native, executable code. This code can be output to an object file or written into memory to be executed. In addition, it generates metadata about the generated code, such as garbage collection maps and exception handling information.
- Interpreter: Directly interprets the various forms of compiler intermediate representations.
- Memory Manager: Organizes and manages memory. Joeq supports both explicitly-managed and garbage-collected memory.
- Dynamic: Provides profile data to the code analysis and optimization component, makes compilation policy decisions, and drives the dynamic compiler.
- Run-time Support: Provides runtime support for introspection, thread scheduling, synchronization, exception handling, interfacing to external code, and language-specific features such as dynamic type checking.
<<lessJoeq is entirely implemented in Java, leading to reliability, portability, maintainability, and efficiency. It is also language-independent, so code from any supported language can be seamlessly compiled, linked, and executed -- all dynamically.
Each component of the virtual machine is written to be independent with a general but well-defined interface, making it easy to experiment with new ideas.
Joeq is released as open source software, and is being used as a framework by researchers on five continents on topics ranging from automatic distributed virtual machines to whole-program pointer analysis.
Joeq is a virtual machine and compiler infrastructure designed to be a platform for research in compilation and virtual machine technologies. We had three main goals in designing the system. First and foremost, we wanted the system to be flexible. We are interested in a variety of compiler and virtual machine research topics, and we wanted a system that would not be specific to researching a particular area.
For example, we have interest in both static and dynamic compilation techniques, and in both type-safe and unsafe languages. We wanted a system that would be as open and general as possible, without sacrificing usability or performance.
Second, we wanted the system to be easy to experiment with. As its primary focus is research, it should be straightforward to prototype new ideas in the framework. With this in mind, we tried to make the system as modular as possible, so that each component is easily replaceable. Learning from our experience with Jalapeno, another virtual machine written in Java, we decided to implement the entire system in Java.
This makes it easy to quickly implement and prototype new ideas, and features like garbage collection and exception tracebacks ease debugging and improve productivity. Java, being a dynamic language, is also a good consumer for many of our dynamic compilation techniques; the fact that our dynamic compiler can compile the code of the virtual machine itself means that it can dynamically optimize the virtual machine code with respect to the application that is running on it. Javas object-oriented nature also facilitates modularity of the design and implementation.
Third, we wanted the system to be useful to a wide audience. The fact that the system is written in Java means that much of the system can be used on any platform that has an implementation of a Java virtual machine. The fact that Joeq supports popular input languages like Java, C, C++, Fortran, and even x86 binary code increases the scope of input programs. We released the system on the SourceForge web site as open source under the Library GNU Public License.
It has been picked up by researchers on five continents for various purposes, among them: automatic extraction of component interfaces, static whole-program pointer analysis, context-sensitive call graph construction, automatic distributed computation, versioned type systems for operating systems, sophisticated profiling of applications, advanced dynamic compilation techniques, system checkpointing, anomaly detection, secure execution platforms and autonomous systems. In addition, Joeq is now used as the basis of the Advanced Compilation Techniques class taught at Stanford University.
Joeq supports two modes of operation: native execution and hosted execution. In native execution, the Joeq code runs directly on the hardware. It uses its own run-time routines, thread package, garbage collector, etc. In hosted execution, the Joeq code runs on top of another virtual machine. Operations to access objects are translated into calls into the reflection library of the host virtual machine.
The user code that executes is identical, and only a small amount of functionality involving unsafe operations is not available when running in hosted execution mode. Hosted execution is useful for debugging purposes and when the underlying machine architecture is not yet directly supported by Joeq. We also use hosted execution mode to bootstrap the system and perform checkpointing, a technique for optimizing application startup times.
Joeq system consists of seven major parts:
- Front-end: Handles the loading and parsing of input files, such as Java class files, SUIF files, and binary object files.
- Compiler: A framework for performing analyses and optimizations on code. This includes the intermediate representation (IR) of our compiler.
- Back-end: Converts the compilers intermediate representation into native, executable code. This code can be output to an object file or written into memory to be executed. In addition, it generates metadata about the generated code, such as garbage collection maps and exception handling information.
- Interpreter: Directly interprets the various forms of compiler intermediate representations.
- Memory Manager: Organizes and manages memory. Joeq supports both explicitly-managed and garbage-collected memory.
- Dynamic: Provides profile data to the code analysis and optimization component, makes compilation policy decisions, and drives the dynamic compiler.
- Run-time Support: Provides runtime support for introspection, thread scheduling, synchronization, exception handling, interfacing to external code, and language-specific features such as dynamic type checking.
Download (1.0MB)
Added: 2005-04-22 License: LGPL (GNU Lesser General Public License) Price:
1645 downloads
Php Gmail Drive 0.3.2
PhpGmailDrive (PGD) turns your Gmail account into a Web based file server. more>>
PhpGmailDrive is a new type of file sharing utility. Unlike typical file servers (say xDrive) it uses Gmail as backend file server. You can enjoy it simply by hosting a small PHP script in your web site without any database.
Gmail file space is more than 2GB, so you can imagine you already have such a big space on internet. However, you will require a Gmail account (If you dont have any Gmail address, go GmailSwap or ask your friends.).
PGD automatically connects Gmail server and fetches list of all attached files and generate downloadable links in a tree like view. If you are looking for a file server to upload your music or notes without any hassle, PGD is ideal for you. Technically speaking PGD is wrapper of Gmailer .
Thought there is no need to know hecks of PHP or Gmailer. Just you have to check that your PHP hosting service provider has curl extension of PHP to handle HTTP/HTTPS traffic.
Main features:
- Successfully connects to Gmail and only grabs list of Attachments in Gmail messages.
- List of attachments are displayed with inbuilt Javascript engine. You can customize output to any other formats.
- 100% compliant to GMAILFS. So you can upload with Windows Gmail Shell extension or Linux GmailFS utilities..
- Supports Multiple Gmail accounts in the same script .
- Supports all browsers.
- Total size is less than 100 KB.
<<lessGmail file space is more than 2GB, so you can imagine you already have such a big space on internet. However, you will require a Gmail account (If you dont have any Gmail address, go GmailSwap or ask your friends.).
PGD automatically connects Gmail server and fetches list of all attached files and generate downloadable links in a tree like view. If you are looking for a file server to upload your music or notes without any hassle, PGD is ideal for you. Technically speaking PGD is wrapper of Gmailer .
Thought there is no need to know hecks of PHP or Gmailer. Just you have to check that your PHP hosting service provider has curl extension of PHP to handle HTTP/HTTPS traffic.
Main features:
- Successfully connects to Gmail and only grabs list of Attachments in Gmail messages.
- List of attachments are displayed with inbuilt Javascript engine. You can customize output to any other formats.
- 100% compliant to GMAILFS. So you can upload with Windows Gmail Shell extension or Linux GmailFS utilities..
- Supports Multiple Gmail accounts in the same script .
- Supports all browsers.
- Total size is less than 100 KB.
Download (0.069MB)
Added: 2005-07-08 License: LGPL (GNU Lesser General Public License) Price:
1576 downloads
Virtual Data Center 1.04-11
The Virtual Data Center (VDC) is a digital library system more>>
The Virtual Data Center (VDC) is a digital library system "in a box" for numeric data.
The VDC is a web application which provides everything necessary to maintain and disseminate collections of research studies: including facilities for the storage, archiving, cataloging, translation, and dissemination of each collection.
It includes on-line analysis, powered by the R Statistical environment. It also provides extensive support for distributed and federated collections including: location-independent naming of objects, distributed authentication and access control, federated metadata harvesting, remote repository caching, and distributed virtual
<<lessThe VDC is a web application which provides everything necessary to maintain and disseminate collections of research studies: including facilities for the storage, archiving, cataloging, translation, and dissemination of each collection.
It includes on-line analysis, powered by the R Statistical environment. It also provides extensive support for distributed and federated collections including: location-independent naming of objects, distributed authentication and access control, federated metadata harvesting, remote repository caching, and distributed virtual
Download (14.5MB)
Added: 2006-04-18 License: GPL (GNU General Public License) Price:
1287 downloads
Virtual Tomcat 0.1
Virtual Tomcat is a set of scripts designed to ease administration tasks involved with hosting multiple JVM instances. more>>
Virtual Tomcat project is a set of scripts designed to ease administration tasks involved with hosting multiple JVM instances and domains using Apache Tomcat and HTTPd.
The system (which uses jsvc to spawn instances) allows users to deploy their own applets from within their home directories, as well as allowing full access to /manager and /admin applets.
<<lessThe system (which uses jsvc to spawn instances) allows users to deploy their own applets from within their home directories, as well as allowing full access to /manager and /admin applets.
Download (0.015MB)
Added: 2006-04-17 License: BSD License Price:
736 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above 64bit virtual drive search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
