Free transfer to software for linux

Transfer to Media Device is a script that creates a new Playlist Right Click Menu item for transferring selected playlist items to your iPod via the Media Device Browser.
This script now also supports generic copy to operation for USB mass storage devices. Currently the script will prompt for a destination directory on first copy, in the future this setting will be saved in a configuration file.
This script works with amaroK 1.3beta3 and above.
Usage:
Run from the amaroK script manager. A new menu item will appear in the Playlist right mouse button menu.
Select files in the playlist and Right click -> Transfer to -> iPod for transfering to an iPod.
Select files in the playlist and Right click -> Transfer to -> USB Device for transfering to a USB device.
Enhancements:
- Add support for Creative Nomad Jukebox devices using the kionjb kioslave. Thanks to Ralf T for the patch.

fftrans is a modification of the "Quick and Dirty Transcoder" script to use ffmpeg instead of gstreamer.

Very quick-and-dirty, only usable for transcoding files for transfer to media devices, but as far as I know the only way one can transcode to wma for a wma player.

Apple Disk Transfer ProDOS (or ADTPro for short) transfers diskettes and logical disk images between Apple ][-era computers and the modern world. If youre familiar with the original ADT, ADTPro extends ADTs reach by working with more logical disk formats, drive types, communications devices, and host operating systems.
Main features:
- Compatibility with any device ProDOS can read
- Compatibility with any Apple ][ (or clone) computer with 64k memory
- Compatibility with many logical disk image formats: .DSK, .PO, .NIB, 2IMG
- Server compatibility with original ADT client program
- Server compatibility with Windows, Mac OSX, Linux, and probably Solaris
- Ability to bootstrap an Apple ][ from bare metal over serial or cassette ports
- Ability to send floppies in "batch" mode without having to name each one
Server
The server program runs on a computer capable of running Java. Depending on how you want to connect to your Apple, you might also need a serial port and cables, an Uthernet card for your apple, or a couple of audio patch cables. The server offers a compact user interface that shows what communications are taking place between the host and the Apple ][.
The servers primary role is to send and receive disk images as requested from the client. But if you have recently acquired an Apple and a disk drive, and you have no software for it - youre in a bit of a tricky situation if you want to move software from the Internet all the way to your shiny new Apple. ADTPros server can help get you get bootstrapped.
Client
The client side runs on the Apple ][. It handles most of the user interaction. When choosing disks/volumes to transfer, anything that ProDOS can see is fair game. Transferring data occurs with a 20k buffer on the Apple, so all transfers are broken up into 20k chunks. A progress indicator shows how far it is into the current chunk, as well as a running count of the total progress.
Enhancements:
- This release has been enhanced with Jean-Marc Boutillon (Deckard)s FASTDSK fast Disk II reading routines.
- This results in a speed boost of 25%-33% for Disk II to host transfers.
- Bootstrapping operations have been reduced, as there is no longer a dependency on ProDOS BASIC.

Audio Transcriber records large audio samples, like a tape or radio broadcast, to your hard drive and splits it into tracks to be burned onto CD-R media.

The goal of Audio Transcriber is to make it easy to transfer audio tapes, LPs, or radio broadcasts to tracks on CD-R/CD-RW.

Upstream is a collection of tools that allow users to send in system specific log and troubleshooting data to support personnel. The project can be easily modified to output data to any pastebin or support tracker.

Upstream aims to simplify the support cycle and make it more efficient. One of the main problems that support staff face when helping people via IRC or mailing lists is getting user log files across.

Often this process is time consuming, and many new users may even be unable to find / copy these logs. Upstream does this for them by finding and transmitting the log files relevant to a specific issue.

Usage:

We hope to turn this,

< newuser >hi, something is wrong with my resolution, how can i fix it?
< support_person >newuser, what is your video card, and which driver is xorg using?
< newuser >err... how can i find out?
< support_person > cat /var/log/Xorg.0.log and pastebin it
< newuser >pastebin?
< support_person >http://pastebin.ca
< newuser >how do i copy? it wont copy!

In to this,

< newuser >hi, something is wrong with my resolution, how can i fix it?
< support_person >newuser, please run Canoe (System -> Help -> Canoe) and choose Video support. Give me the url you get once its done.

libptp2 is a library used to communicate with PTP devices like still imaging cameras or MP3 players (KODAK mc3).
You can download files or tweak camera properties using ptpcam program boundled with libptp2.
Supported Cameras
The list of cameras implementing PTP is constantly growing. Most (if not all) USB still cameras designed after 2002 are supporting PTP. Below is the list of vendors implementing PTP in their cameras:
- Kodak
- HP
- Nikon
- Canon
- Panasonic
- Olympus
- Konica
- Minolta
- Fuji
- Ricoh
- Sony
More are comming...
Please note that if your camera is supporting PTP it does not mean that it is capable of performing all PTP operations (like trigerring capture, uploading files or tweaking properties). Sony cameras are good example of poor PTP implementation where the only thing you can do is downloading files. Sony even breaks the USB specification assigning all its cameras the same product/vendor IDs so dont buy Sony if you want to stay out of problems.
Currently most PTP features are supported. Uploading/downloading files, taking pictures and setting camera properties is supported as long as your camera supports it. However there are many Vendor Extensions that are not supported.
For example Canon uses some proprietary extension operations to take pictures (entering capture mode, extending lens and so on), Nikon introduces proprietary PTP properties.
Unfortunately I have access to couple of Kodak cameras only so to help support extension features you may send me a patch or donate/lend the camera.
Enhancements:
- A number of bugs were fixed, including leaving the camera in an unpredictable state when an I/O error occurs.
- The projects own reimplementation of the old libusb interface (IOCTL_USB_BULK) is used instead of the new URB interface, which is 20% to 50% slower and sometime leads to I/O errors.
- File time preservation across download was added.
- Better capture support was added.
- A bug that caused files over 2MB to be corrupted while downloading was fixed.
- The --loop-capture feature was added.
- Configure errors and parralel build with make -j were fixed.

uLan Driver provides 9-bit message oriented communication protocol, which is transferred over RS-485 link.
Characters are transferred same way as for RS-232 asynchronous transfer except parity bit, which is used to distinguish between data characters and protocol control information. A physical layer consists of one twisted pair of leads and RS-485 transceivers.
Use of 9-bit character simplifies transfer of binary data and for intelligent controllers can lower the CPU load, because of the CPU need not to care about data characters send to other node. Producers of most microcontrollers for embedded applications know that and have implemented 9-bit extension in UARTs of most of todays MCUs. There is the list below to mention some of them:
- all Intel 8051 and 8096 based MCUs with UART
- members of Motorola 683xx family ( 68332, 68376, ... )
- Hitachi H8 microcontrollers
The driver is implemented as relatively independent layers and subsystems. Messages are prepared and received in the driver dedicated memory. This memory is divided into blocks with uniform size with atomic allocation routines.
When message is being stored into blocks, head of message with couple of data bytes is stored in the first allocated memory block. If all data cannot be stored in the first block, next blocks are allocated and linked together.
The message heads are linked in bidirectional linked lists of messages prepared for sending, processed messages and messages prepared for client notification. These lists or queues are main mechanism for transferring of messages between subsystems.
Link protocol is programmed as finite state automata with state stack, which state routines are executed by interrupt handler. State routine can return positive integer information, negative error notification or zero, which leads to wait for next interrupt. Information or error is used as input parameter when state routine is called.
When the state routine wants initiate transfer to another state routine it changes pointer to the actual state routine. If previous state routine returns nonzero value new routine is called immediately, in other case next interrupt invokes new state routine.
There is stack of callers of actual state routines which enables to constructs automata subsystems, which can be used in more places in main automata loop. Main purpose of this automata is to send or process messages coming in list of messages prepared for sending and if specified, move these messages onto list of messages prepared for client notification.
Received messages are put onto this list too. Subsystem is supervised by timeout handler, which can revitalize communication in case of die of other node. The interrupt and timeout handlers are fully SMP reentrant.
The automata subsystem uses pointers to chip driver routines for hardware port manipulation. This is only part dependent on used chip, today 82510, 16450 and OX16C950PCI. These routines can send and receive 9 bit character, connect to RS-485 line by the arbitration sequence, wait for specified time for character and initialize and close port.
File operation subsystem makes interface between OS kernel VFS and client message queues. It enables to prepare single or multi-frame messages and stores notifications of received or processed messages in clients private state structures. This part is heavily operating system dependent.
Enhancements:
- This release enables you to build the driver within the WDF framework for Windows.
- Updates to support the latest Linux 2.6.x kernels are included (tested to 2.6.19).
- Changes to allow stand-alone system-less build for ARM targets (LPC21xx) are included.
- The OMK has been selected as the default build.
- The "switch2std" script allows you to switch to the old build system.

Sybase::Xfer contains Bcp data into a Sybae table from multiple sources.

SYNOPSIS

#!/usr/bin/perl
use Sybase::Xfer;
my %switches = (-from_server=>CIA, -to_server=>NSA, -table => x-files);
my $h = Sybase::Xfer->new( %switches );
my %status = $h->xfer(-return=>"HASH");
print "xref failed. $status{last_error_msg}n" unless $status{ok};

#!/bin/ksh
sybxfer -from_server CIA -to_server NSA -table x-files
if [[ $? != 0 ]]; then print "transfer problems"; fi