amiga hardware for sale
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 1526
Hardware Monitor applet 1.4
The Hardware Monitor applet is a small program for the Gnome panel. more>>
Hardware Monitor applet is a small program for the Gnome panel which tries to be a beautiful all-round solution to hardware monitoring.
It also tries to be user-friendly and generally nice and sensible, integrating pleasantly with the rest of your Gnome desktop.
Main features:
- A graphical view where each monitor is represented by a (time, measurement) colored curve
- A bar-plot view with a horizontal bar per monitor
- A column view with a column (time, measurement) diagram for each monitor
- A textual view which simply lists the monitors and the currently measured values
- A flame view which produces spiffy flames, the sizes of which are determined by the values of the monitored device
And the applet supports monitoring the following hardware characteristics:
- CPU usage (all CPUs, or one at the time) - niced background processes such as SETI@home are automatically ignored
- Memory usage - cache and buffers are automatically ignored
- Swap usage
- Load average
- Disk usage (or disk space free)
- Network throughput (Ethernet, wireless, modem, serial link), either incoming or outgoing or both
- Temperatures from internal sensors (e.g. system board and CPU temperatures)
- Fan speeds from internal sensors
- To avoid eating CPU time when it is scarce, the applet lowers its priority.
<<lessIt also tries to be user-friendly and generally nice and sensible, integrating pleasantly with the rest of your Gnome desktop.
Main features:
- A graphical view where each monitor is represented by a (time, measurement) colored curve
- A bar-plot view with a horizontal bar per monitor
- A column view with a column (time, measurement) diagram for each monitor
- A textual view which simply lists the monitors and the currently measured values
- A flame view which produces spiffy flames, the sizes of which are determined by the values of the monitored device
And the applet supports monitoring the following hardware characteristics:
- CPU usage (all CPUs, or one at the time) - niced background processes such as SETI@home are automatically ignored
- Memory usage - cache and buffers are automatically ignored
- Swap usage
- Load average
- Disk usage (or disk space free)
- Network throughput (Ethernet, wireless, modem, serial link), either incoming or outgoing or both
- Temperatures from internal sensors (e.g. system board and CPU temperatures)
- Fan speeds from internal sensors
- To avoid eating CPU time when it is scarce, the applet lowers its priority.
Download (0.30MB)
Added: 2007-01-17 License: GPL (GNU General Public License) Price:
601 downloads
X Hardware Monitor 1.0
X Hardware Monitor is monitor hardware indicators for temperature, voltage etc... of a running system with a graphical panel. more>>
X Hardware Monitor is a hardware monitor that shows indicators for temperature, voltage, fan speed etc, of a running system with a graphical panel.
The default configuration allows to monitor up to 3 temperatures, 3 fan speeds and 6 voltages. This tool is more particularly adequate for bi-processor systems.
<<lessThe default configuration allows to monitor up to 3 temperatures, 3 fan speeds and 6 voltages. This tool is more particularly adequate for bi-processor systems.
Download (0.015MB)
Added: 2005-09-22 License: Freeware Price:
1496 downloads
Hardware Monitor 1.4
Hardware Monitor is a multi-purpose, beautiful system-monitoring applet. more>>
Hardware Monitor is a multi-purpose, beautiful system-monitoring applet.
The Hardware Monitor applet is an applet for the GNOME panel which tries to be a beautiful all-around solution to system monitoring. It also strives to be user-friendly and generally nice and sensible, integrating pleasantly with the rest of your GNOME desktop.
Includes different viewers, including a flame effect, allows multiple devices to be monitored in the samme applet, uses smooth updating, polished graphs, clean HIG-compliant interface.
Main features:
- A graphical view where each monitor is represented by a (time, measurement) colored curve
- A bar-plot view with a horizontal bar per monitor
- A column view with a column (time, measurement) diagram for each monitor
- A textual view which simply lists the monitors and the currently measured values
- A flame view which produces spiffy flames, the sizes of which are determined by the values of the monitored device
And the applet supports monitoring the following hardware characteristics:
- CPU usage (all CPUs, or one at the time) - niced background processes such as SETI@home are automatically ignored
- Memory usage - cache and buffers are automatically ignored
- Swap usage
- Load average
- Disk usage (or disk space free)
- Network throughput (Ethernet, wireless, modem, serial link), either incoming or outgoing or both
- Temperatures from internal sensors (e.g. system board and CPU temperatures)
- Fan speeds from internal sensors
<<lessThe Hardware Monitor applet is an applet for the GNOME panel which tries to be a beautiful all-around solution to system monitoring. It also strives to be user-friendly and generally nice and sensible, integrating pleasantly with the rest of your GNOME desktop.
Includes different viewers, including a flame effect, allows multiple devices to be monitored in the samme applet, uses smooth updating, polished graphs, clean HIG-compliant interface.
Main features:
- A graphical view where each monitor is represented by a (time, measurement) colored curve
- A bar-plot view with a horizontal bar per monitor
- A column view with a column (time, measurement) diagram for each monitor
- A textual view which simply lists the monitors and the currently measured values
- A flame view which produces spiffy flames, the sizes of which are determined by the values of the monitored device
And the applet supports monitoring the following hardware characteristics:
- CPU usage (all CPUs, or one at the time) - niced background processes such as SETI@home are automatically ignored
- Memory usage - cache and buffers are automatically ignored
- Swap usage
- Load average
- Disk usage (or disk space free)
- Network throughput (Ethernet, wireless, modem, serial link), either incoming or outgoing or both
- Temperatures from internal sensors (e.g. system board and CPU temperatures)
- Fan speeds from internal sensors
Download (0.29MB)
Added: 2007-01-13 License: GPL (GNU General Public License) Price:
1037 downloads
Hardware 4 Linux 0.9.3
Hardware 4 Linux project contains a set of tools to report Linux-compatible hardware to hardware4linux.info. more>>
Hardware 4 Linux project contains a set of tools to report Linux-compatible hardware to hardware4linux.info.
Enhancements:
- This release anonymizes dmidecode output, collects OS version files instead of calling osinfo, collects audio codec files, adds a README, and collects PCI modules.
<<lessEnhancements:
- This release anonymizes dmidecode output, collects OS version files instead of calling osinfo, collects audio codec files, adds a README, and collects PCI modules.
Download (MB)
Added: 2007-08-11 License: GPL (GNU General Public License) Price:
494 downloads
AVI Player for XMMS 1.2.3
AVI Player for XMMS is an AVI player plug-in for XMMS to play Windows AVI, DivX ;-), and ASF files. more>>
The AVI player is a plug-in for XMMS, giving it the ability to play Windows AVI (including DivX ;-)) and ASF files on your Linux or FreeBSD box.
You can simply add movies to your playlist and the plug-in will call aviplay to play the movie files. Many aviplay options are supported, such as fullscreen playback and true hardware acceleration on XFree86 4.x.x.
Enhancements:
- Included a stripped version of avifile 0.53.5 that compiles staticly into the plugin. This will make avi-xmms work no matter what avifile version you have installed on the system.
- Added wma and wmv support.
<<lessYou can simply add movies to your playlist and the plug-in will call aviplay to play the movie files. Many aviplay options are supported, such as fullscreen playback and true hardware acceleration on XFree86 4.x.x.
Enhancements:
- Included a stripped version of avifile 0.53.5 that compiles staticly into the plugin. This will make avi-xmms work no matter what avifile version you have installed on the system.
- Added wma and wmv support.
Download (0.68MB)
Added: 2005-08-15 License: GPL (GNU General Public License) Price:
1606 downloads
Hardware lister B.02.11.01
Hardware Lister is a small tool to provide detailed information on the hardware configuration of the machine. more>>
lshw (Hardware Lister) is a small tool to provide detailed information on the hardware configuration of the machine.
Hardware lister can report exact memory configuration, firmware version, CPU version and speed, cache configuration, bus speed, mainboard configuration, etc. On DMI-capable x86 or EFI (IA-64) systems and on some PowerPC machines (PowerMac G4 is known to work).
Information can be output in plain text, XML or HTML.
It currently supports DMI (x86 and EFI only), OpenFirmware device tree (PowerPC only), PCI/AGP, ISA PnP (x86), CPUID (x86), IDE/ATA/ATAPI, PCMCIA (only tested on x86), USB and SCSI.
<<lessHardware lister can report exact memory configuration, firmware version, CPU version and speed, cache configuration, bus speed, mainboard configuration, etc. On DMI-capable x86 or EFI (IA-64) systems and on some PowerPC machines (PowerMac G4 is known to work).
Information can be output in plain text, XML or HTML.
It currently supports DMI (x86 and EFI only), OpenFirmware device tree (PowerPC only), PCI/AGP, ISA PnP (x86), CPUID (x86), IDE/ATA/ATAPI, PCMCIA (only tested on x86), USB and SCSI.
Download (1.1MB)
Added: 2007-08-06 License: GPL (GNU General Public License) Price:
819 downloads
Hardware::iButton 0.03
Hardware::iButton is a Perl module that allows to talk to DalSemi iButtons via a DS2480 serial widget. more>>
Hardware::iButton is a Perl module that allows to talk to DalSemi iButtons via a DS2480 serial widget.
SYNOPSIS
use Hardware::iButton::Connection;
$c = new Hardware::iButton::Connection "/dev/ttyS0";
@b = $c->scan();
foreach $b (@b) {
print "family: ",$b->family(), "serial number: ", $b->serial(),"n";
print "id: ",$b->id(),"n"; # id = family . serial . crc
print "reg0: ",$b->readreg(0),"n";
}
This module talks to iButtons via the "active" serial interface (anything using the DS2480, including the DS1411k and the DS 9097U). It builds up a list of devices available, lets you read and write their registers, etc.
The connection object is an Hardware::iButton::Connection. The main user-visible purpose of it is to provide a list of Hardware::iButton::Device objects. These can be subclassed once their family codes are known to provide specialized methods unique to the capabilities of that device. Those devices will then be Hardware::iButton::Device::DS1920, etc.
iButtons and solder-mount Touch Memory devices are each identified with a unique 64-bit number. This is broken up into 8 bits of a "family code", which specifies the part number (and consequently the capabilities), then 48 bits of device ID (which Dallas insures is globally unique), then 8 bits of CRC. When you pass these IDs to and from this package, use hex strings like "0123456789ab".
<<lessSYNOPSIS
use Hardware::iButton::Connection;
$c = new Hardware::iButton::Connection "/dev/ttyS0";
@b = $c->scan();
foreach $b (@b) {
print "family: ",$b->family(), "serial number: ", $b->serial(),"n";
print "id: ",$b->id(),"n"; # id = family . serial . crc
print "reg0: ",$b->readreg(0),"n";
}
This module talks to iButtons via the "active" serial interface (anything using the DS2480, including the DS1411k and the DS 9097U). It builds up a list of devices available, lets you read and write their registers, etc.
The connection object is an Hardware::iButton::Connection. The main user-visible purpose of it is to provide a list of Hardware::iButton::Device objects. These can be subclassed once their family codes are known to provide specialized methods unique to the capabilities of that device. Those devices will then be Hardware::iButton::Device::DS1920, etc.
iButtons and solder-mount Touch Memory devices are each identified with a unique 64-bit number. This is broken up into 8 bits of a "family code", which specifies the part number (and consequently the capabilities), then 48 bits of device ID (which Dallas insures is globally unique), then 8 bits of CRC. When you pass these IDs to and from this package, use hex strings like "0123456789ab".
Download (0.021MB)
Added: 2007-08-15 License: Perl Artistic License Price:
808 downloads
AutoQ3D Standard for Linux 3
Its an easy, light and fast design tool to draw 3D models. more>> Its an easy, light and fast design tool to draw 3D models using the full power of your PCs graphics hardware, allowing you to rapidly prototype your designs. You can easily rotate, pan, zoom your 3D designs in real-time, use text tools. AutoQ3D Standard can export to DXF files for interchange with other applications. AutoQ3D Standard works great on Windows and Linux. You dont need to be a 3D designer expert to get the best out of AutoQ3D Standard.<<less
Download (1.50MB)
Added: 2009-04-17 License: Freeware Price: Free
199 downloads
Hardware::Simulator 0000_0005
Hardware::Simulator is a Perl extension for Perl Hardware Descriptor Language. more>>
Hardware::Simulator is a Perl extension for Perl Hardware Descriptor Language.
SYNOPSIS
use Hardware::Simulator;
# NewSignal( perl_variable [, initial_value]);
# create a signal called $in_clk, give it an initial value of 1
NewSignal(my $in_clk,1);
# Repeater ( time_units , code_ref)
# every time_units, call the code reference, starting at the current time
Repeater ( 5, sub{if ( $in_clk==0) { $in_clk=1;} else { $in_clk=0;}});
# Responder ( [signal_name ... signal_name], code_ref );
# respond to any changes to signals by calling code reference.
# any time out_clk changes, print value of clock and simulation time.
Responder ( $out_clk, sub
{
my $time = SimTime();
print "out_clk = $out_clk. time=$timen";
});
# start processing of events and event scheduling.
EventLoop();
Hardware::Simulator ==> a Perl Hardware Descriptor Language
Hardware::Simulator is a lightweight version of VHDL or Verilog HDL. All of these languages were developed as means to describe hardware.
Hardware::Simulator was created as a means to quickly prototype a basic hardware design and simulate it. VHDL and Verilog are both restrictive in their own ways. Hardware::Simulator was created to quickly put something together as a "proof of concept", to show that a design concept would work or not. and then the design could be translated to VHDL or Verilog.
The problem that started all of this was designing a fifo for a video scaling asic. The chip used a buffer to store incoming video data. The asic read the buffer to generate the outgoing video image. We estimated how large we thought the buffer needed to be, but we wanted to confirm that our numbers were right by running simulations.
The problem was we needed to run hundreds of different simulations, given the permutations of input image formats, output image formats, and input/output clock frequencies. We also had text files containing valid formats and frequencies. A text file as input called for perl to manipulate, split, format, and extract the data properly.
This data then had to be translated onto the a HDL simulation. The problem was that there was no easy way to write a perl script that would simulate hardware, so the only solution was to have perl drive a Verilog simulator and pass all these parameters via command line parameters. so then verilog files had to be created, and the simulator had to be driven, and the end result was a lot of work to simulate a simple fifo.
Time contraints did not allow me to develop a HDL package for perl to solve the original problem, but I took it on in my spare time. and eventually Hardware::Simulator was born.
<<lessSYNOPSIS
use Hardware::Simulator;
# NewSignal( perl_variable [, initial_value]);
# create a signal called $in_clk, give it an initial value of 1
NewSignal(my $in_clk,1);
# Repeater ( time_units , code_ref)
# every time_units, call the code reference, starting at the current time
Repeater ( 5, sub{if ( $in_clk==0) { $in_clk=1;} else { $in_clk=0;}});
# Responder ( [signal_name ... signal_name], code_ref );
# respond to any changes to signals by calling code reference.
# any time out_clk changes, print value of clock and simulation time.
Responder ( $out_clk, sub
{
my $time = SimTime();
print "out_clk = $out_clk. time=$timen";
});
# start processing of events and event scheduling.
EventLoop();
Hardware::Simulator ==> a Perl Hardware Descriptor Language
Hardware::Simulator is a lightweight version of VHDL or Verilog HDL. All of these languages were developed as means to describe hardware.
Hardware::Simulator was created as a means to quickly prototype a basic hardware design and simulate it. VHDL and Verilog are both restrictive in their own ways. Hardware::Simulator was created to quickly put something together as a "proof of concept", to show that a design concept would work or not. and then the design could be translated to VHDL or Verilog.
The problem that started all of this was designing a fifo for a video scaling asic. The chip used a buffer to store incoming video data. The asic read the buffer to generate the outgoing video image. We estimated how large we thought the buffer needed to be, but we wanted to confirm that our numbers were right by running simulations.
The problem was we needed to run hundreds of different simulations, given the permutations of input image formats, output image formats, and input/output clock frequencies. We also had text files containing valid formats and frequencies. A text file as input called for perl to manipulate, split, format, and extract the data properly.
This data then had to be translated onto the a HDL simulation. The problem was that there was no easy way to write a perl script that would simulate hardware, so the only solution was to have perl drive a Verilog simulator and pass all these parameters via command line parameters. so then verilog files had to be created, and the simulator had to be driven, and the end result was a lot of work to simulate a simple fifo.
Time contraints did not allow me to develop a HDL package for perl to solve the original problem, but I took it on in my spare time. and eventually Hardware::Simulator was born.
Download (0.010MB)
Added: 2007-07-20 License: Perl Artistic License Price:
840 downloads
Unix Amiga Delitracker Emulator 2.07
Unix Amiga Delitracker Emulator (UADE) plays most Amiga music file formats by simulating Amiga hardware and software. more>>
Unix Amiga Delitracker Emulator (UADE) plays most Amiga music file formats by simulating Amiga hardware and software.
Unix Amiga Delitracker Emulator plays over 180 Amiga music file formats and has three frontends for playing: a command line tool, an XMMS plugin, and a Beep Media Player frontend.
Enhancements:
- An improved version of the Special FX replayer was added.
- A new Special FX ST replayer was added.
- Bugs in song length database handling were fixed.
- Audacious 1.3 is supported.
- 15 instrument soundtracker module detection is supported.
<<lessUnix Amiga Delitracker Emulator plays over 180 Amiga music file formats and has three frontends for playing: a command line tool, an XMMS plugin, and a Beep Media Player frontend.
Enhancements:
- An improved version of the Special FX replayer was added.
- A new Special FX ST replayer was added.
- Bugs in song length database handling were fixed.
- Audacious 1.3 is supported.
- 15 instrument soundtracker module detection is supported.
Download (0.74MB)
Added: 2007-05-01 License: GPL (GNU General Public License) Price:
918 downloads
Hardware::Vhdl::Lexer 1.00
Hardware::Vhdl::Lexer is a Perl module that can split VHDL code into lexical tokens. more>>
Hardware::Vhdl::Lexer is a Perl module that can split VHDL code into lexical tokens.
SYNOPSIS
use Hardware::Vhdl::Lexer;
# Open the file to get the VHDL code from
my $fh;
open $fh, new({ linesource => $fh });
# Dump all the tokens
my ($token, $type);
while( (($token, $type) = $lexer->get_next_token) && defined $token) {
print "# type = $type token=$tokenn";
}
Hardware::Vhdl::Lexer splits VHDL code into lexical tokens. To use it, you need to first create a lexer object, passing in something which will supply chunks of VHDL code to the lexer. Repeated calls to the get_next_token method of the lexer will then return VHDL tokens (in scalar context) or a token type code and the token (in list context). get_next_token returns undef when there are no more tokens to be read.
NB: in this documentation I refer to "lines" of VHDL code and "line" sources etc., but in fact the chunks of code dont have to be broken up at line-ends - they can be broken anywhere that isnt in the middle of a token. New-line characters just happen to be a simple and safe way to split up a file. You dont even have to split up the VHDL at all, you can pass in the whole thing as the first and only "line".
<<lessSYNOPSIS
use Hardware::Vhdl::Lexer;
# Open the file to get the VHDL code from
my $fh;
open $fh, new({ linesource => $fh });
# Dump all the tokens
my ($token, $type);
while( (($token, $type) = $lexer->get_next_token) && defined $token) {
print "# type = $type token=$tokenn";
}
Hardware::Vhdl::Lexer splits VHDL code into lexical tokens. To use it, you need to first create a lexer object, passing in something which will supply chunks of VHDL code to the lexer. Repeated calls to the get_next_token method of the lexer will then return VHDL tokens (in scalar context) or a token type code and the token (in list context). get_next_token returns undef when there are no more tokens to be read.
NB: in this documentation I refer to "lines" of VHDL code and "line" sources etc., but in fact the chunks of code dont have to be broken up at line-ends - they can be broken anywhere that isnt in the middle of a token. New-line characters just happen to be a simple and safe way to split up a file. You dont even have to split up the VHDL at all, you can pass in the whole thing as the first and only "line".
Download (0.011MB)
Added: 2007-04-20 License: Perl Artistic License Price:
926 downloads
Speak Freely for Unix 7.6.a
Speak Freely is an application for Unix and Unix-like systems which allows you to talk . more>>
Speak Freely is an application for Unix and Unix-like systems (Linux, FreeBSD, IRIX, etc.) with audio hardware, which allows you to talk (actually send voice, not typed characters) over a network. Speak Freely for Unix uses the workstation audio hardware and network to allow conversations of users over the network.
The phone company never gives you a break! You pay a fortune for a leased line connection to the Internet, and you *still* have to pay every time you want to chat with somebody, even though youre both sitting in front of workstations with digital audio capability, linked by a fast network. Speak Freely for Unix can intercommunicate with
Workstations on local area networks can generally communicate with excellent audio quality and response. A software implementation (developed by Jutta Degener and Carsten Bormann, Technische
Universitaet Berlin) of the compression algorithm used in GSM digital cellular telephones allows operation over Internet links of modest bandwidth. By using GSM compression in conjunction with sample interpolation, the data rate can be reduced to about 9600 baud. Users with CPUs too slow or two heavily loaded to perform GSM compression and decompression in real time may select less compact but quicker to
execute ADPCM coding, using an implementation developed by Jack Jansen of the Centre for Mathematics and Computer Science, Amsterdam, The Netherlands.
<<lessThe phone company never gives you a break! You pay a fortune for a leased line connection to the Internet, and you *still* have to pay every time you want to chat with somebody, even though youre both sitting in front of workstations with digital audio capability, linked by a fast network. Speak Freely for Unix can intercommunicate with
Workstations on local area networks can generally communicate with excellent audio quality and response. A software implementation (developed by Jutta Degener and Carsten Bormann, Technische
Universitaet Berlin) of the compression algorithm used in GSM digital cellular telephones allows operation over Internet links of modest bandwidth. By using GSM compression in conjunction with sample interpolation, the data rate can be reduced to about 9600 baud. Users with CPUs too slow or two heavily loaded to perform GSM compression and decompression in real time may select less compact but quicker to
execute ADPCM coding, using an implementation developed by Jack Jansen of the Centre for Mathematics and Computer Science, Amsterdam, The Netherlands.
Download (0.76MB)
Added: 2006-06-21 License: GPL (GNU General Public License) Price:
1222 downloads
Distributed Hardware Evolution Project
Distributed Hardware Evolution Project is populations of circuits evolving in a distributed online genetic algorithm. more>>
The Distributed Hardware Evolution Project allows the distribution of a genetic algorithm evolving hardware designs across the Internet by setting up an island on each clients PC which will evolve during idle time. Individuals from these islands will migrate between each other as they compete for survival.
All source code is available at Sourceforge under the projects named JaGa, DistrIT, and IslandEv. The source code is generalizable to any genetic algorithm or distributed processing task.
<<lessAll source code is available at Sourceforge under the projects named JaGa, DistrIT, and IslandEv. The source code is generalizable to any genetic algorithm or distributed processing task.
Download (0.006MB)
Added: 2005-04-01 License: GPL (GNU General Public License) Price:
1670 downloads
Amiga Research Operating System 20060207
Amiga Research Operating System (AROS) is a portable and free desktop operating system. more>>
Amiga Research Operating System (AROS) is a portable and free desktop operating system aiming at being compatible with AmigaOS 3.1, while improving on it in many areas. The source code is available under an open source license, which allows anyone to freely improve upon it.
Goals
The goals of the AROS project is it to create an OS which:
1. Is as compatible as possible with AmigaOS 3.1.
2. Can be ported to different kinds of hardware architectures and processors, such as x86, PowerPC, Alpha, Sparc, HPPA and other.
3. Should be binary compatible on Amiga and source compatible on any other hardware.
4. Can run as a standalone version which boots directly from hard disk and as an emulation which opens a window on an existing OS to develop software and run Amiga and native applications at the same time.
5. Improves upon the functionality of AmigaOS.
To reach this goal, we use a number of techniques. First of all, we make heavy use of the Internet. You can participate in our project even if you can write only one single OS function. The most current version of the source is accessible 24 hours per day and patches can be merged into it at any time. A small database with open tasks makes sure work is not duplicated.
History
Some time back in the year 1993, the situation for the Amiga looked somewhat worse than usual and some Amiga fans got together and discussed what should be done to increase the acceptance of our beloved machine. Immediately the main reason for the missing success of the Amiga became clear: it was propagation, or rather the lack thereof. The Amiga should get a more widespread basis to make it more attractive for everyone to use and to develop for. So plans were made to reach this goal. One of the plans was to fix the bugs of the AmigaOS, another was to make it an modern operating system. The AOS project was born.
But exactly what was a bug? And how should the bugs be fixed? What are the features a so-called modern OS must have? And how should they be implemented into the AmigaOS?
Two years later, people were still arguing about this and not even one line of code had been written (or at least no one had ever seen that code). Discussions were still of the pattern where someone stated that "we must have ..." and someone answered "read the old mails" or "this is impossible to do, because ..." which was shortly followed by "youre wrong because ..." and so on.
In the winter of 1995, Aaron Digulla got fed up with this situation and posted an RFC (request for comments) to the AOS mailing list in which I asked what the minimal common ground might be. Several options were given and the conclusion was that almost everyone would like to see an open OS which is compatible to AmigaOS 3.1 (kickstart 40.68) on which further discussions could be based upon to see what is possible and what is not.
So the work began and AROS was born.
<<lessGoals
The goals of the AROS project is it to create an OS which:
1. Is as compatible as possible with AmigaOS 3.1.
2. Can be ported to different kinds of hardware architectures and processors, such as x86, PowerPC, Alpha, Sparc, HPPA and other.
3. Should be binary compatible on Amiga and source compatible on any other hardware.
4. Can run as a standalone version which boots directly from hard disk and as an emulation which opens a window on an existing OS to develop software and run Amiga and native applications at the same time.
5. Improves upon the functionality of AmigaOS.
To reach this goal, we use a number of techniques. First of all, we make heavy use of the Internet. You can participate in our project even if you can write only one single OS function. The most current version of the source is accessible 24 hours per day and patches can be merged into it at any time. A small database with open tasks makes sure work is not duplicated.
History
Some time back in the year 1993, the situation for the Amiga looked somewhat worse than usual and some Amiga fans got together and discussed what should be done to increase the acceptance of our beloved machine. Immediately the main reason for the missing success of the Amiga became clear: it was propagation, or rather the lack thereof. The Amiga should get a more widespread basis to make it more attractive for everyone to use and to develop for. So plans were made to reach this goal. One of the plans was to fix the bugs of the AmigaOS, another was to make it an modern operating system. The AOS project was born.
But exactly what was a bug? And how should the bugs be fixed? What are the features a so-called modern OS must have? And how should they be implemented into the AmigaOS?
Two years later, people were still arguing about this and not even one line of code had been written (or at least no one had ever seen that code). Discussions were still of the pattern where someone stated that "we must have ..." and someone answered "read the old mails" or "this is impossible to do, because ..." which was shortly followed by "youre wrong because ..." and so on.
In the winter of 1995, Aaron Digulla got fed up with this situation and posted an RFC (request for comments) to the AOS mailing list in which I asked what the minimal common ground might be. Several options were given and the conclusion was that almost everyone would like to see an open OS which is compatible to AmigaOS 3.1 (kickstart 40.68) on which further discussions could be based upon to see what is possible and what is not.
So the work began and AROS was born.
Download (18.3MB)
Added: 2006-03-28 License: Other/Proprietary License with Source Price:
1310 downloads
AmigaSHELL 2.3
AmigaSHELL is a linux shell replacement. more>>
AmigaSHELL makes your boring gray on black colored bash shell revive like in the old days. Just like on Amiga(tm), blue, white, orange, black at its finest. With a nice informational bar at the top.
Installation
(be root)
make install
amigashell start
cd /etc/rc2.d
ln -s ../init.d/amigashell S99amigashell
Enhancements:
- cursors for xfree86 4.3
- left_ptr, right_ptr, busy
- added theme for wmpinboard as well
<<lessInstallation
(be root)
make install
amigashell start
cd /etc/rc2.d
ln -s ../init.d/amigashell S99amigashell
Enhancements:
- cursors for xfree86 4.3
- left_ptr, right_ptr, busy
- added theme for wmpinboard as well
Download (0.02MB)
Added: 2005-04-04 License: GPL (GNU General Public License) Price:
1665 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 amiga hardware for sale 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
