Free pearpc 0.4 pre software for linux

PearPC is an architecture-independent PowerPC platform emulator capable of running most PowerPC operating systems.

This release fixes an ugly partition mapping bug which prevented PearPC to boot OpenDarwin. But the fix might cause regressions: so if your image is no longer booting and you can compile pearpc yourself, please talk to the pearpc-devel mailing list.

Installation:

-Get the Mandrake Installations CDs from a near mirror.
-Read the getting started document first.
-Join the club.
-Make sure you have configured with a big harddisk (3 GiB should do) and a CDROM with the Mandrake 9.1 PPC CD1 inserted. Select a 15 bit video mode. (ppc_start_resolution to 1, 4 or 7)
-Boot and you should get the yaboot menu.
-Press enter and wait.
-At some point, a graphical installer will show up.
-I wont partition your disk for you so you have to do it on your own
create 2 partitions: Apple bootstrap and a Linux onecontinue install.
It will ask you to insert another CD. Click "Change CD" and choose a different .iso or simply insert a different CD. Continue.
-Something bad may happen in the end of the install. Nevermind.

While the CPU emulation may be slow (1/500th or 1/15th, see above), the speed of emulated hardware is hardly impacted by the emulation; the emulated hard-drive and CDROM e.g. are very fast, especially with OS that support bus-mastering (Linux, Darwin, Mac OS X do).

Because the author has only access to a little-endian machine, PearPC will most likely only run on little-endian architectures. This shouldnt be hard to fix and the author would fix this himself if he such hardware. (You can donate some big-endian hardware to get this fixed!)

Equally, PearPC will probably only run on 32-bit architectures. This shouldnt be hard to fix either. (You can donate...)
A lot of unimplementated features are fatal (i.e. will abort PearPC).
Timings are very still a little bit inaccurate. Dont rely on benchmarks made in the client.

PearPC lacks a save/restore machine-state feature.
No Altivec support yet but being worked on.
No LBA48 (but LBA). Currently no support for hard disks greater than 128 GiB. Disks > 4GiB are not tested very well.

Parrot::Pmc2c is a PMC to C Code Generation.

SYNOPSIS

use Parrot::Pmc2c;

Parrot::Pmc2c (and the subclasses defined in this file) is used by tools/build/pmc2c.pl to generate C code from PMC files.

Functions

does_write($method, $section)

Returns whether a method writes.

count_newlines($string)

Returns the number of newlines (n) in $string.

dont_edit($pmcfile)

Returns the "DO NOT EDIT THIS FILE" warning text. $pmcfile is the name of the original source *.pmc file.

gen_ret($method, $body)

Generate the C code for a return statement, if the body is empty then make a cast if needed.

This method is imported by subclasses.

class_name($self, $class)

Returns the appropriate Parrot::Pmc2c subclass for the PMC ($self->{class}). $self is the hash reference passed to new(), and $class is Parrot::Pmc2c.

dynext_load_code($library_name, %classes)

$library_name is the name of the dynamic library to be created.

%classes is a map from the PMC names for which code is to be generated, to dump info (PMC metadata).

This function is exported.

Class Methods

new($self, $opt)

Returns $self as a new instance.

$self is a hash reference eval-ed from a *.dump file generated by tools/build/pmc2c.pl from a *.pmc file. It is bless-ed either into Parrot::Pmc2c::::Standard, or into one of the other special PMCs: default, delegate, Null, Ref or SharedRef.

$opt is a hash reference.

Instance Methods

line_directive($self,$line,$file)

Generates the C pre processor string for a #line directive, or an empty string if $self-{opt}{nolines}> is true.

line_directive_here($self,$output,$file)

Generates the C pre processor string for a #line directive to reset the compilers line number to the next physical line in the output.

get_vtable_section()

Creates a hash of all the method names containing vtable section. Called from init().

make_const($class)

If the PMC had its const_too flag set then this method is called in init() to to create the read-only set methods.

init($class)

Initializes the instance. $class is its class.

decl($classname, $method, $for_header)

Returns the C code for the PMC method declaration. $for_header indicates whether the code is for a header or implementation file.

includes()

Returns the C #include for the header file of each of the PMCs superclasses.

full_arguments($args)

Prepends INTERP, SELF to $args.

proto($type,$parameters)

Determines the prototype (argument signature) for a method body (see src/call_list).

rewrite_nci_method($class, $method, $super, $super_table)

Rewrites the method body performing the various macro substitutions for nci method bodies (see tools/build/pmc2c.pl).

rewrite_vtable_method($class, $method, $super, $super_table)

Rewrites the method body performing the various macro substitutions for vtable method bodies (see tools/build/pmc2c.pl).

body($method, $line, $out_name)

Returns the C code for the method body. $line is used to accumulate the number of lines, $out_name is the name of the output file we are generating.

methods($line, $out_name)

Returns the C code for the vtable methods. $line is used to accumulate the number of lines, $out_name is the name of the output file we are generating.

lib_load_code()

Returns the C code for loading a library.

pmc_is_dynpmc

Determines if a given PMC type is dynamically loaded or not.

init_func()

Returns the C code for the PMCs initialization method, or an empty string if the PMC has a no_init flag.

gen_c($out_name)

Generates the C implementation file code for the PMC. $out_name is the name of the output file we are generating.

hdecls()

Returns the C code function declarations for all the methods for inclusion in the PMCs C header file.

TODO include MMD variants.

gen_h($out_name)

Generates the C header file code for the PMC. $out_name is the name of the output file we are generating.

implements($method)

True if this class generates code for the method $method.

implements_vtable($method)

True if this class generates code for VTABLE method $method.

Platypus Wiki provides a semantic Wiki Wiki Web.

Platypus Wiki is an enhanced Wiki Wiki Web with ideas taken from Semantic Web. It offers a simple user interface for creating Wiki page plus metadata according to W3C standards.

Weve chosen HTMLarea v3.0rc1 as a WYSIWYG editor for creating content in (X)HTML. We are using Cascading Style Sheets (CSS) for presentation, and our intention is to be fully compliant with Web Content Accessibility Guidelines v1.0 with Level AAA. Platypus Wiki lets you set "global" and "local" links. A global link is generated on every page: you just have to specify a word or phrase and the corresponding URL. A local link is similar, but only appears on a specified page.

Another difference from the classical Wiki is the way links are specified in a page: instead of CamelWords, square brackets, etc., we use the convention namespace:pagename; this lets the user write content without worrying about namespace collisions. We also use RDF to represent the page space as a directed labeled graph.

Each node in Platypus Wiki is both a Wiki page and an RDF resource. We are designing a navigation interface to simplify the interaction of users with the system and RDF metadata editing.

Pyspice is a SPICE pre-processor written in Python, inspired by the Perl SPICE pre-processor spicepp by John Sheahan.
I developed this module as part of my own work and provide it here as a service to the Python and SPICE communities. Additions, suggestions, and usefullness reports are appreciated. It is currently licensed under the GPL.
It was (is currently being) developed with Python 2.4 and uses a few features introduced in 2.4. they relate to (re)sorting the netlist lines.
Main features:
- Each input "card" type has its own object type.
- Netlists are converted into an array of type instances.
- Netlist order is preserved for readability.
- Salient features of pyspice.py:
- Parallel capacitors are combined.
- Parallel MOSFETs are combined.
- Small capacitors are dropped for faster simulation.
Usage:
chmod +x
pyspice.py [options] [-i infile] [-o outfile]
Use pyspice.py -h for all options.
Enhancements:
- At least default (pass through) handling of all element types.
- NOTE: For combining, this uses a global node name scheme. In other words: subcircuits, libraries, etc. are not in a separate node namespace as they should be, beware.
- Changed structure of classes (in LEO), there are base classes that contain common attributes and element classes that define the specific behavior.
- This version _should_ work with any netlist and only touch Ms and Cs, YMMV.
- Work is ongoing on the class structure and most important IMO is getting netlist hierarchy implemented.

jackEQ is a tool for routing and manipulating audio from/to multiple input/output sources. jackEQ project runs in the JACK Audio Connection Kit, and uses LADSPA for its backend DSP work, specifically the DJ EQ swh plugin created by Steve Harris, one of jackEQs main authors.
jackEQ is intended to provide an accessible method for tweaking the treble, mid and bass of any JACK aware applications output. Designed specifically for live performance, it is modelled on varous DJ mixing consoles which the main author has used.
jackEQ wll allow sound as rich and powerful as Jackie O, as street smart as Jackie Brown. jackEQ may be the first female entity in JACKs realm. Is jackEQ more than you can handle?
Main features:
- JACK i/o
- 4 x stereo i/o channels with EQs, independant gain controls and meters
- Stereo monitor and master outputs with indpendant gain control and meters
- 3band graphic EQ for each channel
Bass: 100 Hz
Range Mid: 1000 Hz
Treble: 10000 Hz
- cross fader support: All channels assignable plus mute and all
- 2x stereo aux send/return with monitor buttons (pre gain).
- Internal jack i/o connections assignable from Ports menu.
Enhancements:
- Fixes ladspa UniqueId bug for dj EQ plugin

The Posadis Zone Editor is a graphical tool to edit DNS (Domain Name System) zones using DNS update.

Because it uses zone transfers, you can simply edit the DNS zone, and have only the changes transferred to the DNS server.

AROS-Max is a AROS-based live-CD.

AROS Max is a pre-configured live bootable CD image, made to show off the best that AROS has to offer. It requires an AROS capable PC, your mileage may vary.

If you require help getting AROS-Max to run please ask for help on the Max area at the AROS-Exec messageboard, please do not email us directly with support problems!

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.

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.

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.

Space Commander is a game that aims to be similar to Elite and Privateer, with maybe a bit of Trade Wars thrown in.
The project is a remarkably functional space simulation with under 200 lines of code in the main file.
DEPENDENCIES
You need a recent version of Python and some support libraries. The game is currently being written using Python v 2.4.3 but it may work with newer or older versions with some minor tweaking. I intend to be using Python 2.5 and PyGame 1.8 shortly.
- Python 2.4.3
- PyGame 1.7
- Numeric 22.0
Basically you need a pretty complete Python kit. Most Linux distributions should have everything that you need and Windows / OSX users will be able to install it all with a small bit of effort.
To play the MIDI score in Linux you have to install and configure Timidity due to some old code in sdl-mixer which is a pre-dependency of PyGame. If the game crashes and
complains about midi, just comment out the MIDI line in spacecommander.py to disable it.
As to performance issues. I pass the buck. If it runs too slowly then get a faster computer, better graphics card, better operating system, whatever.
The idea of writing this in Python is to have a compromise between ultimate performance and the ability to understand and tinker around with the code.
You could try reducing the number of stars in the galaxy by editing bigbang.py also.
Feel free to re-write the game in hand optimized assembler, but you must send me a copy of your code per the LICENSE.
RUNNING THE GAME
Linux: ./spacecommander.py
KEYBOARD COMMANDS
ESC / Q: Quit the game
Left / Right: Yaw
Up / Down: Pitch
PgUp / PgDN: Roll
Enhancements:
- The main engine was completely rewritten and now supports flying a spaceship around a randomly generated galaxy. 2D rendering of objects using PyGame is supported.
- Mouse flight control is featured.