Free cruncher o neill software for linux

UnifiedIO allows to access files, primitive arrays and streams (even over HTTP) through same interface.
Main features:
- High performance
- Transparent buffering
- MemoryManager
- OpenFileManager (beta)
- uio based implementation of ImageInputStream and ImageOutputStream
- Bridge between RandomAccessFile world and InputStream/OutputStream world
- Access everything using one common interface
- Read/write direct from/into primitive arrays
- Optimized reading over http (only requesting the required data range of bytes - uses byteserving feature of http 1.1)
- Easy extensible design
- Unified I/O contains also many utilities:
- BitInputStream and BitOutputStream.
- PackBits, RLE4 and RLE8 decoder.
- base64 codec implementation.
- and many others.
- Unified I/O is an open source project and licensed under BSD
Enhancements:
- This release features a new buffering model and the ability to create child streams with shared or independent stream position.
- InputStreams was implemented on all primitive arrays.

GnGeo is a NeoGeo emulator for Linux (and maybe some other UNIX). GnGeo project use the following cpu core:

- The 68k core from the generator project by James Ponder.
- Starscream 680x0 emulation library by Neill Corlett
- Raze Z80 emulator by Richard Mitton.
- Z80 Mame core from the Mame project.
- YM2610 Mame core by Tatsuyuki Satoh.

cdenc lets you encode whole audio CDs in a special directory which can be burned on CDROM afterwards.
For other mp3 players like WinAmp the mp3 info tags are set correctly, so that you also get there the full title infos. Additionally you could generate long filenames, so that you could play the music via a shell or explorer environment. Last not least, cdenc generates html files to let you browse through with a normal html browser (but then you cant play more titles on one time).
Furthermore cdenc generates by using Gimp and mpeg2encode bitmaps for the osd of Yamakawa/Raite DVD/MP3 player. cdenc doesnt have a graphical user interfaces. As a clean commandline script, it is designed also to run on machines without X11 (number cruncher) and can work backgrounded. Once correct configured, the work with cdenc reduce to the insertion of an audio CD and the subsequent call of "cdenc -medname mp3cd001", which makes cdenc test if the CD ist not already on another media and if not starts the complete grabbing, compression and index generation.
Unfortunaly cda(xmcd) and gimp have changed a lot so that cdenc wont run with the actual versions. I will change the code to use libaudiocd, but that will take some time. Sorry for that.
Enhancements:
- replaced routine "double" through sprintf (thx to Travis Whitton)
- made cdenc ready to work with Gimp 1.1.18

Gnome-o-phone (gphone for short) is an internet telephone. In other words, if you and your friend have computers with sound cards and network connections, you can use gphone to talk to each other and save on phone bills. Gphone is definitely a work in progress and you probably shouldnt bet your business on it; if it breaks you can keep both pieces. Dont be too hard on the program, though -- the user interface is a bit rough but gphone does work pretty well.
As the name implies, it aims to be fully gnome-groovy, but that hasnt quite happened yet. Gphone is definitely a work in progress and you probably shouldnt bet your
business on it. Dont be too hard on the program, though -- although the user interface is mighty rough, gphone does actually work pretty well. Ive only tested the program over ethernet, but the data rate should be low enough to work over a reasonable modem connection.
The protocol is nominally RTP/RTCP, and gphone complies well enough with the standard to be able to talk to speakfreely. Ive only tested the UNIX version of speakfreely, but as long as you tell sfmike to use RTP and GSM compression, it seems to work fine. Maybe someday Ill add in support for other codecs; encryption is a little less likely
because Id just as soon not open that legal can of worms. One easy way to get some security would be to modify my program rtptunnel to tunnel the RTP protocol through a SSL socket instead of a straight TCP socket.
Gphone supports full duplex if your sound card has this feature. Ive had good luck using the ALSA drivers for my SB16.
Enhancements:
- gphone/gphone.c: Add Jorge Gomes Silvas patch to fix config button crash.

NEsGUI is a peer-to-peer file sharing application written by Neill Miller in GTK+ which utilizes the NEshare library.NEsGUI is a Napster like application. Its one of the simplest and least creative applications utilizing the NEshare peer-to-peer file sharing library.
I started writing NEshare for many reasons. One reason is because I enjoy file sharing with others and I found that there were no true Free Software implementations or designs from the ground up. Thats one of the most important reasons to me personally, but I understand its probably not the reason youre reading this page. Second, I realized that most file sharing implementations that Ive played with simply DO NOT WORK well. The one implementation that worked *extremely* well for all of the time I participated in using it was Napster. As for the GnutellaNet (and the like), I tend to have problems with the decentralized nature. This is vague, I know. Specifically, they require an extraordinary amount of bandwidth as compared to a centralized counterpart such as Napster. They tend to generate a lot of garbage since they are responsible for tying themselves to a number of other nodes, which are likewise tying themselves to you. The *only* benefit that Ive realized with decentralized networks such as the GnutellaNet is the anonyminity involved. At best, you can see what IP address is downloading or uploading while the upload or download is occuring on your system. Beyond that, there is no record or trace of the transaction and does not involve user names which can be stored or screened, passwords which can be broken or stolen, or any form of user messaging or chat which is prone to SPAM or porn advertisments -- like the sad state of (the oldest widespread and possibly least recognized peer-to-peer system) IRC.
Another reason for writing NEshare is to help you realize that you should not be dependent on a corporation to dictate what you can and cant do with file sharing (a la Napster, FastTrack clients, or any other corporate owned network which you may have become attached to). For example, Napster allowed the sharing of digital music files. Where do you go if you are more interested in sharing original digital pieces of art amongst your friends? What about copies of an ever evolving digital document? Thus, I wanted to provide NEshare to you in case Napster or FastTrack or whatever you use suddenly becomes unavailable, or never suited your needs in the first place. Being Free Software, youre free to modify it and improve it under the terms of the GPL. And if you cant write code, call in a favor from a friend!
NEshare takes the best architectural ideas of centralized networks and mixes them with the best ideas of decentralized networks. It allows anonyminity since there is no messaging system, no username, no password and no record of you once youve left the network. It also works in a reliable manner (minus bugs!) because of the centralized nature. The basic method of transaction is similar to the familiar Napster and FastTrack clients. A user connects to an NEshare server and uploads a file list. The user can search and get results back from the server. Once the results are retrieved by the user, the user connects directly to another user for exchanging files. Thats the basic gist of the centralized approach, however the NEshare architecture is flexible and can work in a decentralized manner with relatively little modification if the benefits become more apparent.
One of the biggest advantages of a purely decentralized network (aside from the anonyminity aspect) is the fact that there is no central server which all users must rely on. In the world today, we see the prevention and the hindering of new technologies because big businesses fear to compete. This is wrong. Decentralized networks address this by not allowing a single entity to have complete control over a system. Thus, although threats can be made, they cannot be enforced against all users of a decentralized network. Contrast this with some centralized models - where a corporation takes control of an entire system. They are only pitting themselves against the giants and unfortunately they probably cannot win since (in recent U.S. history at least), Corporations (with cash) suppress our rights (Constitutional, fair rights, whatever) and dont ever look back. Look at the recent headlines regarding the RIAA and Hollywoods general reaction to Napster and other file sharing services. Everyone pounced on Napster and Napster did not survive. Sure, the company may still have a vision for itself, but everything that you and I enjoyed about the service is gone. The vision weve created for it is gone. I havent used Napster since late 2000.
Im not advocating using this software for actions which are questionably legal. Im providing this software for educational reasons because I believe that there is a lot to learn about networking applications and weve only seen the tip of the iceberg. This software has many legitimate uses such as online collaboration on any number of projects, sharing original works or documents, browsing which new Free Software packages are available amongst your peers, learning how a multi-threaded server works, learning how to use sockets, seeing an example of how a network protocol can be written from scratch, congesting your local network for bandwidth experiments and measurements, etc. The uses are endless. And the uses are legitimate. This software may help other to find something new. This software may *be* something new to others. Whatever the case, its all about vision.
By designing a Free Software implementation of a peer-to-peer protocol, Im offering it to you to suit your vision. I dont want to see one central server out there that everyone connects to for whatever use. I want to see the decentralization of the centralized model. I want to see something like what happened to the webserver to happen to NEshare. Each person that is interested in this kind of project should run and manage their own server for their own intranet. Choices are good. Although NEshare is centralized right now (like a webserver) -- wouldnt it be a horrible thing if all information on the web was hosted on the same server? This is what Napster tried to acomplish. They took the centralized server a little too far to prevent people like you and me from having our own visions and creative uses for the technology. NEshare should work differently. For example, if you look at streaming radio servers -- these are central servers all over the place which have several central resources (i.e. webpages) which tell you about which ones are available and their current status. This feature is planned for NEshare, although the first release of the server will have to be tracked manually if youd like to advertise your server to others.
Id like to add that I do believe that decentralized networks inherently have some cool ideas behind them, so I did not exclude the possibility of NEshare working in a fully decentralized manner. The first version that Im working on will be only centralized, but decentralization is an option since it should not prove to be too difficult given the architecture. However, since in my experience the fully decentralized network tends to have more issues than benefits, I would like to keep NEshare centralized. Again, a decentralization of the centralized model would be ideal.
The other major design goal of NEshare is to make it a toolkit. What I mean by this is that currently, there is a client library which can readily be dropped into an application of any kind. This means that for developers who are working on applications, if peer-to-peer file sharing would be useful, it can be easily used under the terms of the GPL inside of their own applications. This also makes for a more lightweight graphical user interface, since the bulk of the work is inside the client library. In order for all of NEshare to work in a purely decentralized manner, the work of the server must be integrated into the client library and a few new messages will need to be developed so that it can act as a servent. The architecture is rather flexible, and this will remain a design goal moving forward.
Needless to say this takes a lot of work. Im a single hacker at best and Ive been working on this project in free time since the summer of 2001. I can only do so much, and Im limited by my imagination and programming skills. Thats why I need your help. So far, my work consists of designing the networking protocol capable of accomplishing file sharing in a peer to peer manner, implementing this protocol in code, testing the code, improving the code, etc. I cant do this by myself (although unfortunately so far I have been and will continue to if no one volunteers). I would appreciate help in the areas of testing, documentation, and of course good old fashioned hacking. If this project sounds interesting to you, feel free to contact me.
Enhancements:
- Code now honors the std namespace so that its gcc-3.x compatible
- Fixed some event handling that caused erroneous message boxes to appear
- Better unexpected peer disconnection handling
- Added proper ChangeLog entries

patch-o-matic-ng it is a system to apply netfilter-related patches to the latest kernel and/or iptables sources.

FOLLOW THESE STEPS:

0) There may be some outstanding bugfixes or tweaks which are not yet in the official kernel. To look through these, do:

# KERNEL_DIR=
IPTABLES_DIR=
./runme pending

Please note that you have to recompile your kernel and your kernel modules after this step of kernel patching.

Thats it!

FEELING BRAVE?

1) The netfilter core team is maintaining a set of extensions / new features which are not yet committed to the mainstream kernel tree.

They are a collection of maybe-broken maybe-cool third-party extensions.

Please note that you cannot apply any combination of any of those patches. Some of them are incompatible...

This is why we provide two ways of applying them:

If you want to try some extensions, and be sure that they dont break each other, you can do the following:

# KERNEL_DIR=
IPTABLES_DIR=
./runme base

It will modify you kernel source (so back it up first!). You will have to recompile / rebuild your kernel and modules.

Alternatively, if you really know what your are doing, you can use the following command in order to offer you the full list of choices. Be aware that we dont prevent you from shooting yourself in the foot.

% KERNEL_DIR=
IPTABLES_DIR=
./runme extra

Peak-o-mat (formerly Lorentz) is a peak fitting program aimed at the fitting of spectroscopic data. Peak-o-mat is especially useful if youre facing a large amount of spectra which has to be cleaned, transformed, and fitted.

Some predefined peak shapes are available which are frequently used with spectroscopy, but adding custom functions is very easy.