Free ds software for linux

DeSmuME project is a Nintendo DS emulator that can run both commercial games and homebrew applications.

The original author of DeSmuME is YopYop156. He has stopped working on it on the beginning of april 2006 and passed the torch to a new team of developers. You can now follow the progress of DeSmuME on this site.

Wmsensormon is a doc app for WindowMaker that utilizes lm_sensors to monitor CPU temp, sys temp, fan speeds, and CPU voltage.
It offers configurable warnings for overheating, and the sensors displayed are adjustable by the user with command line parameters.
Installation:
make
make install
wmsensormon
Options:
-h, --help this help screen
-v, --version print version information
-f show temperatures in Fahrenheit
-s default SMP mode (mode #1)
-s1 SMP mode #1 (CPU 1, CPU 2, sys, fan)
-s2 SMP mode #2 (CPU 1, CPU 2, fan 1, fan 2)
-sw switch CPU and SYS temperature readings
use with -s1 or -s2 if SYS temp is first
-swf switch fans to read fan3 and fan4
-r refresh time (in microseconds, default 100000)
-l enable logging with default time, (default 30000)
-ln enable logging with specified time, (1000 = 1 min)
-dt danger CPU temperature, default: system value (i.e. 60)
input values in Celsius
-ds danger SYS temperature, default: system value (i.e. 60)
input values in Celsius
-df danger fan speed, default: system value (i.e. 3000)
-wt warning CPU temperature, default: danger value
input values in Celsius
-ws warning SYS temperature, default: danger value
input values in Celsius
-wf warning fan speed, default: danger value
-lv limit CPU core volts, default is system value either: max voltage first, min
voltage second (i.e. 180 170) or:
percent difference first, value second (i.e. % 5 175)
Enhancements:
- when a command line arg gets a invalid parameter return error rather than ok
- fixed reading in the limit values from the wrong sensor if using the -sw option
- added option to choose a sensors chip to read from.
- added support for detecting whether the chosen sensor chip is a temperature sensor or some other type.
- if the choosen chip is number 0 or no chip is chosen, autodetect the chip to use.

jrawio is a Service Provider Implementation for the Java ImageIO API. It provides the ability to read images coded in a digital "camera raw" format (such as NEF for Nikon or CRW/CR2 for Canon).
jrawio is to be pointed out that jrawio is implemented in 100% pure Java.
In simple words, a Camera RAW format is the dump of the data collected by the camera sensor, with basically no post-processing applied. While it has the pitfall of requiring heavy processing in order to achieve a displayable image, the basic advantage is that any transformatio applied to it is "reversible".
From this point of view a Camera RAW format can be thought as a "digital negative". But dont confuse this with Adobes Digital Negative format (.DNG), which is just the try to define a standard format of RAW images. Indeed every camera manufacturer (e.g. Nikon, Canon, ...) has its own format.
jrawio is presently a Release Candidate for v1.0, so its coming out of beta stage. Please refer also to the Release Notes for information about issues.
It has been tested with about 8,000 photos taken with Nikon D100 and D70 cameras and with about 250 samples of various cameras downloaded from the web. jrawio has been explicitly tested with the following models:
Canon CR2 Digital Rebel, EOS 1D MkII, EOS 1Ds MkII, EOS 350D
Canon CRW D30, EOD 10D, EOS 300D
Leica DNG R8, R9
Minolta MRW DiMAGE 5, DiMAGE 7i, DiMAGE 7Hi
Nikon NEF CoolPix 5400, CoolPix 5700, CoolPix 8700, CoolPix 8800, D1, D100, D1X, D200, D2H, D2X, D50, D70, D70s
Pentax PEF *ist D, *ist DL, *ist DS
Sony SRF F828
Enhancements:
- This release fixes bugs related to application integration.

Pywifi project is a Python library that provides currently read access to information about a W-Lan cards capabilities, like the wireless extensions written in C.

Typical output of pyiwconfig.py:

eth1 IEEE 802.11-DS ESSID:"romanofski"
Mode:Managed Frequency:2.417GHz Access Point:00:80:C8:15:0C:65
Bit Rate:11 Mbit Tx-Power:17 dBm Sensitivity:off/65535
Retry limit:16 RTS thr:off Fragment thr:off
Encryption:Operation not permitted
Power Management:off
Link Quality:15/100 Signal level:-55dBm Noise level:-96dBm
Rx invalid nwid:190 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:8 Invalid misc:83736 Missed beacon: 0

wifi0 IEEE 802.11-DS ESSID:"romanofski"
Mode:Managed Frequency:2.417GHz Access Point:00:80:C8:15:0C:65
Bit Rate:11 Mbit Tx-Power:17 dBm Sensitivity:off/65535
Retry limit:16 RTS thr:off Fragment thr:off
Encryption:Operation not permitted
Power Management:off
Link Quality:15/100 Signal level:-55dBm Noise level:-96dBm
Rx invalid nwid:190 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:8 Invalid misc:83736 Missed beacon: 0

Daily strip manager is a simple PHP script which offers more powerful user interface for browsing comic strips, downloaded by DailyStrips perl script, than static html pages.
Daily Strip Manager offers sorting, zooming to specific strip, duplicate control, keyboard navigation (2.0) and more. Nothing much for a quick PHP script, but it works for me.
DS Manager at this time only works with DailyStrips setup configured to put comic strip images in subdirectories using date as a filename (e.g. options -l --stripdir).
Images may actually end with whatever garbage but they MUST start with their full date in format specified in config.php, otherwise nothing would work at all.
You should also enable indexing and provide directory writable by PHP user to store indexes in, otherwise expect general slowness (probably this wont show much on some fancy-shmancy Xeon, but I use P3 as my web server, thank you very much.
DS Manager should itself (with all related files) be placed at the root of your strips collection, otherwise it wont work at all.
As of version 2.0, Daily Strip Manager uses XmlHttpRequest object, which adds dependencies on JavaScript and modern web-browsers (Mozilla flavours and IE6 seem to work fine, dunno about the rest). If you are somehow unhappy with this, use version 1.7 instead.
Enhancements:
- This release adds minor interface improvements.

Kernel Mode Linux project is a technology which enables us to execute user programs in kernel mode. In Kernel Mode Linux, user programs can be executed as user processes that have the privilege level of kernel mode.
The benefit of executing user programs in kernel mode is that the user programs can access a kernel address space directly. So, for example, user programs can invoke system calls very fast because it is unnecessary to switch between a kernel mode and a user mode by using costly software interruptions or context switches.
Unlike kernel modules, user programs are executed as ordinary processes (except for their privilege level), so scheduling and paging are performed as usual.
Although it seems dangerous to let user programs access a kernel directly, safety of the kernel can be ensured, for example, by static type checking, software fault isolation, and so forth.
For proof of concept, we are developing a system which is based on the combination of Kernel Mode Linux and Typed Assembly Language, TAL. (TAL can ensure safety of programs through its type checking and the type checking can be done at machine binary level.
Version restrictions:
- User processes executed in kernel mode should obey the following limitations. Otherwise, your system will be in an undefined state. In the worst-case scenario, your system will crash.
- On IA-32, programs executed in kernel mode shouldnt modify their CS, DS, FS and SS registers.
- On AMD64, programs executed in kernel mode shouldnt modify their CS register.
- In addition, on AMD64, IA-32 binaries cannot be executed in kernel mode.
Enhancements:
- This release has been merged with the 2.6.19 Linux kernel.

RT-Thread is a real-time operating system. It is designed specifically for small memory footprint platforms. The kernel supports the tranditional RTOS services, such as multiple threads, semaphores, mutexes, event flags, mailboxes, etc.
RT-Thread project also provides a C-expression interpreter shell, from which a programmer can access kernel variables and invoke system functions.
Main features:
Kernel Object System
- There is a kernel object system, which can access and manage all of the kernel objects. Kernel objects include most of the facilities in the kernel, for example, thread, semaphore etc. Kernel objects can be static objects, whose memory is allocated in compiling. It can be dynamic objects as well, whose memory is allocated from system heaps in runtime. Through the kernel object system, RT-Thread operating system can be independent from the memory management system and greatly enhance the scalability of the system.
Multi-Task/Thread Scheduling
- RT-Thread operating system supports multi-task systems, which are based on thread scheduling. The scheduling algorithm used in RT-Thread operating system is a full preemptive priority-based scheduling algorithm. It supports 256 priority levels, in which 0 is the highest and 255 the lowest. The 255th priority is used for idle thread. The scheduling algorithm also supports threads running at same priority level. The shared time-slice round-robin scheduling is used for this case. The time of scheduler to determine the next highest ready thread is determinant. The number of threads in the system is unlimited, only related with RAM.
Synchronization Mechanisms
- RT-Thread operating system supports the traditional semaphore and mutex. Mutex objects use inherited priority to prevent priority reversion. The semaphore release action is safe for interrupt service routine. Moreover, the block queue for thread to obtain semaphore or mutex can be sorted by priority or FIFO.
Inter-Thread Communication
- RT-Thread operating systems supports event/fast event, mail box and message queue. The event mechanism is used to awake a thead by setting one or more corresponding bit of a binary number when an event ocurs. The fast event supports event thread queue. Once a one bit event occurs, the corresponding blocked thread can be found out timing accurately, then will be waked up. In mailbox, a mail length is fixed to 4 byte, which is more effective than message queue. The send action for communication facilities is also safe for interrupt service routine.
Clock and Timer
- In default, the system uses clock tick to implement shared time-slice scheduling. The timing sensitivity of thread is implemented by timers. The timer can be set as one-shot or periodic timeout.
Memory Management
- RT-Thread operating system supports two types memory management: static memory pool management and dynamic memory heap management. The time to allocate a memory block from the memory pool is determinant and when the memory pool is empty, the allocated thread can be blocked (or immediately return, or waiting for sometime to return, which are determined by a timeout parameter). When other thread releases memory blocks to this memory pool, the blocked thread is wake up.
Enhancements:
- More porting was done to Samsung S3C44b0 CPU, AMTEL AT91SAM7S64, Nintendo DS, and Intel i386.

Deepest Sender is a client that will allow you to post to blogs from directly within Firefox. The project is primarily a LiveJournal client, although it supports Blogger (GData) and WordPress (metaWeblog) too, with support for more stuff to come.

Note that the actual Deepest Sender website will always have the most up to date version.

If DS wont load for you in Firefox 2, and youre using a non-US English version (ie. British English or whatever), you will need to download a spellcheck dictionary in order for it to work. Non US English builds dont come with dictionaries.

If DS keeps loading in Russian and youre running SeaMonkey, check the LiveJournal group, it has a guide to solving the problem.