Free pearpc hd resizer 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.

SIR - Simple Image Resizer is a simple application for resizeing images. SIR - Simple Image Resizer is inspired by GTPY - ImageResizer.
But I used C++/QT anda QImage class to convert the images.
SIR - Simple Image Resizer can convert into and from the following formats:
- JPEG
- PNG
- BMP
- GIF
- XPM
- PGM
- PBM
- PPM
To compile:
#qmake sir.pro
#make
Enhancements:
- Polish translation added (Thanks zoteek)
- Minor bug fixes

JACK Meterbridge is a meterbridge for the UNIX based JACK audio system.

It supports a number of different types of meter, rendered using the SDL library and user-editable pixmaps.

Supported meters

PPM - Peak Program level Meters

Approximatly conforming to BS 6840-10. These meters are designed to indicate peak amplitude, as opposed to VU meters which are designed to indicate volume.

The scale is correct according to the standard, 4 equates to 0dB, 1 to -12, 7 to +12, and it is linear with decibels.

Ive never used a real PPM meter, so I dont know if it reacts correctly. Feedback welcome.

VU - Volume Unit meters

Conforming to BS 6840-17:1991. Real meter is larger.

These meters are designed to measure the "volume" of an audio signal, it is not as relevant to digital systems as PPM meters, but is useful if you are interfacing to analogue tape, FM broadcast equipment or want a general idea of the signal volume.

The -r flag (set reference level) is usful with these meters as it will allow you to calibrate to your DA converters. The meter is pre-adjusted so that it should allign correctly calibrated DA converters with analogue systems. If you wish to run with 0dBFS = 0dBu then use "-r 20"

DPM - Digital Peak Meter

Conforming to IEC 268-18:1995 (peak indiciator decay may not be correct).

These are meters as typically seen on digital consoles, HD recorders etc.

There are the most efficient in screen realestate and CPU use but look a bit boring.

JF - "Jellyfish" Meter (aka. Goniometer)

A jellyfish meter is a stereo scope display, it can be used to spot phase and mono compatibility problems.

Some charateristic problems can be seen, eg. a signal with a stronger left channel is seen as a shape sloping to the left [], more right slopes to the right [/], and dead mono is a vertical line [|].

The meter below the scope display indicates the degree of stereo correlation between the channels, a value of +1 means that it is perfectly mono compatible, and -1 and that the channels are in anti-phase (so they will cancel out if mixed).

If someone has better examples, please mail them to me, there are probably tutorials online.

SCO - Scope

A rendering of an oscilloscope display.

It has a basic trigger function, but there is no timebase control. It renders one pixel per sample, so it will probably be next to useless at 96KHz

sdparm utility outputs and in some cases modifies SCSI device parameters. When the SCSI device is a disk, sdparms role is similar to its namesake: the Linux hdparm utility which is for ATA disks that usually have device names starting with "hd".
More generally sdparm can be used to output and modify parameters on any device that uses a SCSI command set. Apart from SCSI disks, such devices include CD/DVD drives (irrespective of transport), SCSI and ATAPI tape drives and SCSI enclosures. A small set of commands associated with starting and stopping the media, loading and unloading removable media and some other housekeeping functions can also be sent with this utility.
This utility currently contains over 500 entries spread across generic mode pages, transport specific mode pages, vendor specific mode pages, Vital Product Data (VPD) pages and their attributes. Rather than try and document all of these here (or in the man page), another approach is taken. This utilitys internal tables can be searched and output with the --enumerate option. Additional explanatory information is output when the --long option is used (and more if the --long option is used twice).
SCSI mode pages
Mode pages hold meta data about a SCSI device which can, in some cases, be changed by the user. In SCSI parlance the "device" is a logical unit of which there may be several in a SCSI target. In the case of a SCSI disk connected directly to a Host Bus Adapter (HBA) the disk is both a SCSI target and a logical unit. The "user" in this case is the person using sdparm which is a SCSI "application client" and it feeds commands into a SCSI initiator. The SCSI initiator is found in the HBA. At the command level SCSI is a client-server protocol with the logical unit (or target device) being the server that responds to commands sent by the application client via the SCSI initiator.
Mode pages are defined in SCSI (draft) standards found at www.t10.org . Mode pages common to all SCSI devices are found in the SCSI Primary Commands document (SPC-4) while those specific to block devices (e.g. disks) are found in SBC-3 and those for CD/DVD drives are found in MMC-5. This diagram shows how various SCSI and associated standards interrelate. Often device product manuals detail precisely which mode pages (and parts thereof) are supported by a particular model and describe the way that the device will react if the generic description in the SCSI (draft) standard needs amplification. There are also transport protocol specific mode pages for transports such as "spi" (the 25 year old SCSI Parallel Interface), "fcp" (Fibre Channel Protocol) and "sas" (Serial Attached SCSI). There are also vendor specific mode pages. Mode pages that are not transport protocol specific or vendor specific are sometimes referred to as "generic" in sdparms documentation.
To see a list of generic mode page names that sdparm has some information about use: sdparm -e. To see a list of transport specific mode page names that sdparm has some information about use (for example) sdparm -e -t sas. Both lists are sorted alphabetically by mode page abbreviation.
Mode pages are not the only mechanism in SCSI devices for holding meta data. Information which seldom if ever changes for a particular device may be found in the Vital Product Data (VPD) pages which are obtained via the SCSI INQUIRY command. Performance statistics are held in log pages which are obtained via the SCSI LOG SENSE command. Recent CD/DVD drives hold a lot of information in feature and profile descriptors (see MMC-4 and MMC-5) which are accessed via the SCSI GET CONFIGURATION command (see the sg_get_config utility in the sg3_utils package).
Each mode page has up to four tables associated with it. These can be thought of like tabs on a spreadsheet, with each tab containing the same size table. The four tables are:
current values: those values that are active at this time
changeable values: bit masks showing those values that the user may change
default values: the manufacturers default values
saved values: those values that will be active after the next power cycle (or format)
The saved values are optional. If the mask in the changeable values indicates a field can be changed then the corresponding field in the current values may be changed. A bit of 0 in the changeable values mask indicates the corresponding bit in the current values (and saved values) may not be changed. A bit of 1 in the changeable values mask indicates the corresponding bit in the current values (and saved values) may be changed. At the point when a current value is changed, the user may also choose to change the corresponding saved value.
The manufacturer obviously knows a lot about the characteristics of its devices. Hence if a current field value (and saved field value) is different from the default field value then there should be some rationale.
Some current values represent a state within the target device or logical unit. If that state changes so does the current value. Such values are not usually changeable by the user.
The sdparm utility has a --get, --set, --clear type of command line interface in which mode page fields are identified by an acronym. In many cases these acronyms will correspond precisely to the standard (e.g. "WCE" for Writeback Cache Enable in the caching mode page of SBC-3). For some longer fields the standards "spell out" a field name (e.g. "Write Retention Priority" in the caching mode page of SBC-3). In such cases the sdparm utility uses an acronym (e.g. "WRP"). In sdparm, acronyms across all generic mode pages are unique (i.e. an acronym matches at most one field of one generic mode page). Each transport protocol has its own namespace of acronyms so that an acronym is unique within a transport protocol. By default, saved values are not changed by --set and --clear. When changing the current values, the saved values can be changed as well by adding the --save. All the current values in a mode page can be changed back to the manufacturers defaults with the --defaults option (and the --save option here will additionally change the saved values back to the manufacturers defaults).
Changing some mode page fields is like jumping off a cliff holding onto a rope which you are not sure is properly secured. If in doubt, change the current value without using the --save option. That way if the setting is disastrous, power cycling the device will restore the previous setting. Once the new setting is known to be safe, then the sdparm utility can be re-executed with the --save option added.
sdparm commands
The --command= option allows a command to be sent to the given device. The currently supported commands are:
capacity: sends a READ CAPACITY and if successful reports the number of blocks, block length and capacity expressed in MibiBytes (1048576 bytes). Valid for disks and CD/DVD drives with the appropriate media loaded.
eject: stops the medium (if it is spinning) and ejects it from the drive. Note that this may be prevented by software in which case use the unlock command first.
load: loads the medium and then spins it up
ready: reports whether the medium is ready for IO. Ready usually means that it is present and spun up. If the device is not ready then the exit status will be 2 (see exit status section below).
sense: reports sense data (from a REQUEST SENSE SCSI command); can include power condition information, a progress indication for a time consuming command (e.g. format) or a report an informational exception (when MRIE=6)
start: spin up the medium
stop: spin down the medium
sync: send a SYNCHRONIZE CACHE SCSI command to the device.
unlock: instructs the device to allow medium removal (i.e. an eject). Beware, the OS may have had a good reason for preventing removal of the medium (e.g. it contains a mounted file system). Use at your own risk.
These sdparm commands send SCSI commands to the given DEVICE. If they dont seem to work, adding a verbose flag (i.e. -v or -vv) may provide more information. The "ready" and "sense" commands need read permissions on the DEVICE while the other commands need both read and write permissions.
Enhancements:
- Changes to SCSI mode and VPD pages that were introduced by t10.org since the last release were incorporated.
- The pass-through interface was updated, and code which is written in C was made to compile cleanly with C++.

Early Macintosh Image LoadEr allows to boot linux-m68k from a floppy on a macintosh such as MacII or Quadra 610.
With it, you can create rescue disk, or remove the MacOS partition (needed by the legacy penguin booter) from your HD.
Create a floppy from rescue disk image
You can find floppy image from the package emile-rescue
Under linux, the command to dump image to floppy is:
# dd if=emile-rescue-x.y.bin of=/dev/fd0 bs=512 conv=sync
then, you can eject floppy with:
# eject /dev/fd0
If you are using MacOS, use MakeDebianFloppy AppleScript (you must use a floppy image with a size of exactly 1474560 bytes).
Enhancements:
- This release has improved SCSI support, allows you to create a bootable CD-ROM, adds Debian packaging, updates the PowerPC part (currently not usable), and introduces apple_driver (currently not usable).

DSS also know as Debased Scripts Set project is dedicated to providing you with a "System Development Environment" to create your own DEbian BASED Live Linux System.
Normally youre stuck with the type and amount of applications the creator decided to include, now you can customize the system to fit your needs, by generating on-the-fly compressed modules (layers) including additional software .
The idea is to dont "debase" the Default Debian System, for this pourpose has been designed the USS (The Upstream Salmon Struct).
In this way youll have a knoppix like HW autodetection and autoconfiguration flavor without affecting the standard system.
DSS can be used to:
- create your own live distribution
- put together a demo disk to show off the power of our favourite OS
- build a portable system to install on external USB/FIREWIRE HD and boot it up.
- backup you system and run it from a CD/DVD
- build a morphix base module

Dreamlinux distribution is a modern and modular Linux system that can be run directly from the CD and optionally be easily installed onto your HD.
Dreamlinux comes with a selection of the best applications designed to meet mostly of your daily needs.
Dreamlinux is based on Debian and Morphix, which means it takes advantages of their best features and adds its own modern development tools.
Being a modular system Dreamlinux allows you to add new modules comprising your preferred applications and build a new Distro that meet your requirements by means of its revolutionary MKDistro tool.
Enhancements:
- The final version of Dreamlinux 2.2 Multimedia Edition has been released. Having many improvements compared with the previous version, Dreamlinux 2.2 Multimedia Edition brings countless new features. The kernel is 2.6.18, and the distro uses Debian testing repositories. A greater number of applications for multimedia have been added, allowing to open and manipulate many different types of audio and video files. Beyond the many updates, other refinements have also been incorporated: upgrade assistant, new control panel, and the Easy-Install application that allows the user to install non-Debian programs like Google Earth, Picasa, Opera, etc.