ace hardware
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 808
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
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
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::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
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
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
acer_acpi 0.5
acer_acpi is a Linux kernel module to allow control of some of the hardware on later model Acer (and other Wistron OEM) laptops. more>>
acer_acpi project is a Linux kernel module to allow control of some of the hardware on later model Acer (and other Wistron OEM) laptops.
acer_acpi was originally developed by Mark Smith to enable the wireless LAN card of an Acer Aspire 5024 under 64-bit Linux. The previous solution to hardware access on these laptops, Olaf Taubers acerhk, relied on BIOS calls to work - unfortunately, it is not possible to call a 32-bit BIOS routine from a 64 bit operating system, so acer_acpi was born.
<<lessacer_acpi was originally developed by Mark Smith to enable the wireless LAN card of an Acer Aspire 5024 under 64-bit Linux. The previous solution to hardware access on these laptops, Olaf Taubers acerhk, relied on BIOS calls to work - unfortunately, it is not possible to call a 32-bit BIOS routine from a 64 bit operating system, so acer_acpi was born.
Download (0.013MB)
Added: 2007-06-06 License: GPL (GNU General Public License) Price:
903 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
ACE 5.5.9
ACE is an object-oriented (OO) C++ framework. more>>
ACE short from ADAPTIVE Communication Environment is an object-oriented (OO) C++ framework that can help you develop and deploy high-performance software systems faster and better.
ACE is especially useful for systems that use network and/or inter-process communications and that take advantage of multithreading. While the ACE source code is free, thats not the only way you save money with ACE.
ACEs wrappers and higher-level patterns help you develop your software quickly and portably, helping you to complete your projects on time and within budget.
Over the past decade, my research group has worked with many collaborators on large-scale distributed application R&D projects in diverse domains, including command and control systems, telecom, datacom, medical engineering, distributed interactive simulations, and financial services.
Regardless of the domain and application requirements, weve found that software developers wrestle with the same core infrastructure challenges. Key challenges focus on OS platform portability, connection management and service initialization, event demultiplexing and event handler dispatching, multi-threading and synchronization, fault detection and fault tolerance, and various quality-of-service (QoS) issues, such as controlling latency, throughput, and jitter end-to-end.
Unfortunately, its very costly, time consuming, and error-prone for researchers and developers companies to independently rediscover and reinvent ad hoc solutions to these core distributed application software development challenges.
Fortunately, we have identified a relatively concise set of patterns and framework components that can be applied systematically to eliminate many tedious, error-prone, and non-portable aspects of developing and maintaining distributed applications.
A decade of intense R&D on these topics has yielded ACE, which is an object-oriented framework that implements many core patterns for concurrent communication software. We have applied the patterns and components in the ACE framework to develop The ACE ORB (TAO), which is our standards-based, CORBA middleware framework that allows clients to invoke operations on distributed objects without concern for object location, programming language, OS platform, communication protocols and interconnects, and hardware.
TAO is designed using the best software practices and patterns that we have discovered in our work on ACE in order to automate the delivery of high-performance and real-time QoS to distributed applications.
Enhancements:
- This release adds support for Intel C++ specific optimizations for Linux on IA64.
- It improves support for ACE_OS::fgetc, and adds support for other low-level I/O.
- Shared library builds on AIX now produce a libxxx.so file.
- A workaround has been added for a bugfix in GCC in Fedora Core 7.
- The footprint has been reduced on some platforms.
- Major improvements have been made to IPv6 support.
- TAO DDS enhancements have been added.
- There are assorted bugfixes and other minor enhancements.
<<lessACE is especially useful for systems that use network and/or inter-process communications and that take advantage of multithreading. While the ACE source code is free, thats not the only way you save money with ACE.
ACEs wrappers and higher-level patterns help you develop your software quickly and portably, helping you to complete your projects on time and within budget.
Over the past decade, my research group has worked with many collaborators on large-scale distributed application R&D projects in diverse domains, including command and control systems, telecom, datacom, medical engineering, distributed interactive simulations, and financial services.
Regardless of the domain and application requirements, weve found that software developers wrestle with the same core infrastructure challenges. Key challenges focus on OS platform portability, connection management and service initialization, event demultiplexing and event handler dispatching, multi-threading and synchronization, fault detection and fault tolerance, and various quality-of-service (QoS) issues, such as controlling latency, throughput, and jitter end-to-end.
Unfortunately, its very costly, time consuming, and error-prone for researchers and developers companies to independently rediscover and reinvent ad hoc solutions to these core distributed application software development challenges.
Fortunately, we have identified a relatively concise set of patterns and framework components that can be applied systematically to eliminate many tedious, error-prone, and non-portable aspects of developing and maintaining distributed applications.
A decade of intense R&D on these topics has yielded ACE, which is an object-oriented framework that implements many core patterns for concurrent communication software. We have applied the patterns and components in the ACE framework to develop The ACE ORB (TAO), which is our standards-based, CORBA middleware framework that allows clients to invoke operations on distributed objects without concern for object location, programming language, OS platform, communication protocols and interconnects, and hardware.
TAO is designed using the best software practices and patterns that we have discovered in our work on ACE in order to automate the delivery of high-performance and real-time QoS to distributed applications.
Enhancements:
- This release adds support for Intel C++ specific optimizations for Linux on IA64.
- It improves support for ACE_OS::fgetc, and adds support for other low-level I/O.
- Shared library builds on AIX now produce a libxxx.so file.
- A workaround has been added for a bugfix in GCC in Fedora Core 7.
- The footprint has been reduced on some platforms.
- Major improvements have been made to IPv6 support.
- TAO DDS enhancements have been added.
- There are assorted bugfixes and other minor enhancements.
Download (29.8MB)
Added: 2007-06-28 License: GPL (GNU General Public License) Price:
1664 downloads
Hardware::iButton::Device 0.03
Hardware::iButton::Device is a Perl object to represent iButtons. more>>
Hardware::iButton::Device is a Perl object to represent iButtons.
SYNOPSIS
use Hardware::iButton::Connection;
$c = new Hardware::iButton::Connection "/dev/ttyS0";
@b = $c->scan();
foreach $b (@b) {
print "id: ", $b->id(), ", 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.
<<lessSYNOPSIS
use Hardware::iButton::Connection;
$c = new Hardware::iButton::Connection "/dev/ttyS0";
@b = $c->scan();
foreach $b (@b) {
print "id: ", $b->id(), ", 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.
Download (0.021MB)
Added: 2007-06-18 License: Perl Artistic License Price:
861 downloads
Extract archive 1.11
Extract archive is a service menu that allows you to extract any archive file that ark is capable to read + ACE files. more>>
Extract archive is a service menu that allows you to extract any archive file that ark is capable to read + ACE files.
You can chose to extract here, or in a subdirectory. In that case, it asks you the name of the subdirectory where you want to extract, and suggests you the archive name by default.
To install, simply extract, and move the 2 files in ~/.kde/share/apps/konqueror/servicemenus
Its highly recommended to download the latest version of unace on www.winace.com and to run this command line in the unace directory location : sudo cp unace /usr/bin/unace
You should desactivate ark integration into kde by going into the configuration menu of ark.
If you want translation to be added, post me comments.
Enhancements:
- thanks to shirka, extract archive path is now "test" for an "test.tar.bz2" file
- Name that appears in the menu is now "Extract archive" as suggested by dovidhalevi to differentiate with ark
<<lessYou can chose to extract here, or in a subdirectory. In that case, it asks you the name of the subdirectory where you want to extract, and suggests you the archive name by default.
To install, simply extract, and move the 2 files in ~/.kde/share/apps/konqueror/servicemenus
Its highly recommended to download the latest version of unace on www.winace.com and to run this command line in the unace directory location : sudo cp unace /usr/bin/unace
You should desactivate ark integration into kde by going into the configuration menu of ark.
If you want translation to be added, post me comments.
Enhancements:
- thanks to shirka, extract archive path is now "test" for an "test.tar.bz2" file
- Name that appears in the menu is now "Extract archive" as suggested by dovidhalevi to differentiate with ark
Download (MB)
Added: 2007-05-16 License: GPL (GNU General Public License) Price:
896 downloads
Kismet Parse 0.2
Kismet Parse project can be used after kismet has sniffed 802.11 traffic and produced .network files. more>>
Kismet Parse project can be used after kismet has sniffed 802.11 traffic and produced .network files.
Kismet Parse is a Perl script that will parse these files to map the MAC addresses of the discovered wireless access point and clients to useful information. The information includes the hardware manufacturer of the device.
<<lessKismet Parse is a Perl script that will parse these files to map the MAC addresses of the discovered wireless access point and clients to useful information. The information includes the hardware manufacturer of the device.
Download (0.007MB)
Added: 2007-08-22 License: GPL (GNU General Public License) Price:
568 downloads
hardmon 1.0
hardmon can monitor hardware indicators for temperature, voltage, fan speed etc... of a running system with a graphical panel. more>>
hardmon project can monitor hardware 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.
Why:
I needed a tool to monitor all the numerous indicators of my Abit BP6 in an eye catch.
<<lessWhy:
I needed a tool to monitor all the numerous indicators of my Abit BP6 in an eye catch.
Download (0.015MB)
Added: 2007-06-27 License: GPL (GNU General Public License) Price:
857 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 ace hardware 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
