Free windows nt software for linux

Winamp::Control is a Perl module to control winamp (over the network).

SYNOPSIS

use Winamp::Control;

use IO::Extended qw(printfln);

my $winamp = Winamp::Control->new( host => $opts{host}, port => $opts{port} );

if( my $ver = $winamp->getversion )
{
printfln Connected to Winamp (Ver: %s), $ver;

printfln Currently playing: %s , $winamp->getcurrenttitle() if $winamp->isplaying();

println "Current playlist:nt", join "nt", $winamp->getplaylisttitle();
}

Winamp::Control is a perl module for controlling Winamp (www.winamp.com) over a network or local. It requires the httpQ winamp-plugin written by Kosta Arvanitis (see prerequisites) installed on the computer playing the music (It is called "server" and will receive the commands). Perl clients doesnt need it, because the clients are communicating via http (and they are not restricted to any operating-system).

picoSQL project is the first Italian Open Source relational database management system.
The project of picoSQL was born in 1995. It was an ODBC driver for COBOL indexed files. It consisted of a DLL written in C++ on Windows 3.1 operating system. In the beginning the main effort was made in order to obtain a good compatibity with existing front-end (mainly the MS-Access, MS-Query and VisualBasic) and in order to see COBOL files as a normalized relational DB.
The obtained success concurs to develop ulteriorly the product, refining the query optimizer and implementing an extended SQL, to exclusion of the DDL (Data Description Language). A later version, called PicoDB, were devoloped on UNIX system in client/server architecture.
PicoSql is released under GPL license; it derives from PicoDB (that remains a Picosoft proprietary product) with the addition of some SQL-DDL statement (CREATE/DROP TABLE(INDEX) and excluding COBOL files compatibility). The C/C++ library that allow the database access from C/C++ programs using the ODBC 2.5 API is released under LGPL license; this allows to link the library with programs that are not under GPL.
PicoSQL can be used from Windows applications (like MS-ACCESS, MS-Query, VB etc.) in client/server modality using the ODBC driver picoSQLNet. It can moreover be used from appropriate Java programs through the JDBC driver comprised in the distribution. Finally it can be used from programs written in C and C++ through its set of ODBC 2.5 compliant API.
PicoSQL lacks at the moment of some common characteristics to the most common RDBMS (like the schema and catalogue concepts and the management of the user permissions who can be obtained anyway using the permissions of the host operating system) but they are just these lacks to make it particularly simple to install and to use and fast in the logons and the queries.
Installation:
The installation is particularly simple: if you have the binary distribution, is sufficient to extract the compressed files in one directory ( under Windows NT/2000/XP) and execute:
startTestDb.sh (Unix/Linux)
PicoSQL consists fundamentally in a program, picosqld, to activate through inetd (or xinetd) or picoserv. In such a way it becomes a net service binded to a port, that is to a entire number comprised between 1 and 65535; this number (as an example 6789) must always be specified on the command line of picosqld. As an example:
picosqld 6789
For the activation with inetd (or xinetd), you must see the relative documentation. picoserv is a simple program that replaces inetd, mainly for scopes of test or debugging: its usage is the following:
picoserv [-f] commandLine portNumber
In our case the activation of picosqld can be obtained with the following command line:
picoserv "picosqld 6789" 6789
To notice as the port number is specified two times, as an argument of picosqld and as an argument of picoserv.
When picosqld receive a connection request, it reads a configuration file to find the necessary informations. This file is a text file on Unix/Linux systems.
# Unix/Lunixthe file read for configuration is
$HOME/.picosql.ini
or, if this file is missing
/etc/picosql.ini
The file consists of sections and parameters. A section begins with the name of the section in square brackets and continues until the next section begins. Sections contain attributes of the form
name=value
The file is line-based - that is, each newline-terminated line represents either a comment, a section name or a parameter. Section and parameter names are not case sensitive. Only the first equals sign in a parameter is significant. Any line beginning with a semicolon (;) or a hash (#) character is ignored, as are lines containing only whitespace. Each section corresponds to a database and comprises information like user, password and DB location. In the following example there are two database declared, the former called picoSqlTest, is accessible by anyone while the latter, called rubrica is accessible only by user pico giving the appropriate password.
[picoSqlTest]
DataDirectory=/home/test.db
[rubrica]
DataDirectory=/home/rubrica.db
User=pico
Password=soft
PicoOdbcTrace=NO
SuspensiveLock=YES
; for picosql client only
server=localhost
port=6789
Enhancements:
- This version fixes a problem on authentication and a bug when the connection fails.

Bochs is a highly portable open source IA-32 (x86) PC emulator written in C++, that runs on most popular platforms. Bochs project includes emulation of the Intel x86 CPU, common I/O devices, and a custom BIOS.

Currently, Bochs can be compiled to emulate a 386, 486, Pentium, Pentium Pro or AMD64 CPU, including optional MMX, SSE, SSE2 and 3DNow! instructions.

Bochs is capable of running most Operating Systems inside the emulation including Linux, Windows 95, DOS, and Windows NT 4. Bochs was written by Kevin Lawton and is currently maintained by this project.

Bochs can be compiled and used in a variety of modes, some which are still in development. The typical use of bochs is to provide complete x86 PC emulation, including the x86 processor, hardware devices, and memory.

This allows you to run OSs and software within the emulator on your workstation, much like you have a machine inside of a machine. For instance, lets say your workstation is a Unix/X11 workstation, but you want to run Win95 applications.

Bochs will allow you to run Win 95 and associated software on your Unix/X11 workstation, displaying a window on your workstation, simulating a monitor on a PC.

Need a Type 3 JDBC Driver for MS Access or SQL Server? Think RmiJdbc!
RmiJdbc project is a client/server JDBC Driver that relies on Java RMI.
All JDBC classes (like Connection, ResultSet, etc...) are distributed as RMI objects, so that you can distribute as you like the access to any database supporting the JDBC API.
In fact, RmiJdbc is just a bridge to allow remote access to JDBC drivers.
Why RmiJdbc?
- You develop a client/server application with databases on Windows (NT)? Use RmiJdbc along with the JDBC/ODBC Bridge, your Windows (NT) databases become remotely accessible in Java.
- You implement a JDBC Driver? Just implement the JDBC classes locally, dont bother with remote access!
- You need serializable JDBC classes? Here they are.
Enhancements:
- Add features/limitations/changes here

VIPS is a free image processing system. It aims to be about half-way between Photoshop and Excel: it is very bad at retouching photographs, but very handy for the many other imaging tasks that programs like Photoshop get used for.
It is good with large images (images larger than the amount of RAM in your machine), and for working with colour. Here is a recent publication on VIPS.
VIPS comes in two main parts: libvips is the image-processing library and nip2 is the graphical user-interface.
Both work on Unix (with convenient packages for Gentoo, Debian, Ubuntu and FreeBSD), Windows (NT, 2k and XP only) and Macintosh (OS 10.2 and later). The VIPS library is licensed under the LGPL and and the user-interfaces are licensed under the GPL.
VIPS has been used and developed in the EU projects VASARI, MARC, VISEUM, ACOHIR, CRISATEL, ARTISTE and MUSA. The Department of Electronics and Computer Science at the University of Southampton use it as an image processing framework in research projects.
Its used at The National Gallery, London for most of their imaging research. VIPS is also used in a number of other labs, museums and galleries around the world (including MOMA, the Louvre and BStGS), mostly for infra-red reflectogram mosaic assembly. IIPimage use it to manipulate very large images.
Enhancements:
- A major new release after almost 3 years work: faster, more scaleable, image metadata support, lower memory use, more image file formats, integrated matrix and plot display, background recalculation, many new operations.

With WAppFTP_Client3 you can transfer Files from your local system to a remote host (Unix or Windows 2000/NT), or from a remote Host to your local system. You will be able to create directories, delete directories/files, change the name of directories/files and show Files (a simple Editor is included).
WAppFTP_Client2 uses a graphical Interface (like the Windows Explorer) to do all the above named actions.
Drag and Drop support is now included. That means you can copy Files to the remote Host, just by dragging them into the Remote Systems Window and drop them there.
Main features:
- Secure FTP connections are possible with version 3.0
- Up- and download whole directory hirarchies
- Launch an application with a double mouse click at a appropriate file
- Build (or extract) jar archives with the include jar builder via drag and drop

Fnkdat provides an interface for determining common directory names in UNIX and Win32 applications.
Appications organize files differently on different platforms. On Win32 systems, an application is generally installed by a user and it is usually (more-or-less) installed entirely under a single tree. For example, the game OmniHype might be installed in the directory C:Program FilesOmniHype.
Its maps or data may be in C:Program FilesOmniHypemaps, and the system configuration might be C:Program FilesOmniHypeconfig.dat. Information specific to the user straczynski (such as keyboard/mouse settings) might be stored under G:Documents and SettingsStraczynskiApplication DataOmniHype in Windows NT and its derivatives, and under C:Program FilesOmniHypeusersstraczynski in Windows 95 and its derivatives.
On a UNIX system the story is completely different. An application may be compiled by a user or a packager, and file locations (at least one of them, anyway) are often defined at compile-time. The application is then installed by a user or a system administrator, relative to a prefix (such as /usr/). Following the above example, the binary for the game OmniHype may be installed as /usr/bin/omnihype. Its maps or data may be in /usr/share/omnihype/maps/. The system configuration may be /etc/omnihype.conf, and information specific to the user straczynski may be stored under ~straczynski/.omnihype/.
fnkdat is an attempt to cope with these differences.
Usage:
fnkdat is implemented as a single function. The source is released under a GUILE style license and may be statically linked to both public and commercial software. The license text, links to the source, and a couple tutorials are listed below.
Enhancements:
- A patch that fixes a compiler warning was applied.