Applesauce: Difference between revisions

From The ReActiveMicro Apple II Wiki
Jump to navigation Jump to search
No edit summary
Line 22: Line 22:
Because Applesauce captures the data on the disk at the flux level, it is able to capture Apple II copy-protection schemes "in place".
Because Applesauce captures the data on the disk at the flux level, it is able to capture Apple II copy-protection schemes "in place".


The resultant disk image can then have its copy protection cracked, or it can be written back to a physical disk by the Applesauce software with protection in place, or (subject to emulation hardware or software support) it can be used with copy protection left in place in the disk image in Apple II emulators or solid state Apple II disk drive emulators.
The resultant disk image could have its copy protection cracked, or it can be written back to a physical disk by the Applesauce software with protection in place, or (subject to emulation hardware or software support) it can be used with copy protection left in place in the disk image in Apple II emulators or solid state Apple II disk drive emulators.


For non-protected (or previously cracked disks), Applesauce is able to capture a .dsk disk image in approximately 11s.
For non-protected (or previously cracked disks), Applesauce is able to capture a .dsk disk image in approximately 11s.

Revision as of 10:25, 21 November 2017

AppleSauce by John K Morris

The Applesauce project was started in March 2017 by John K Morris of EvolutionInteractive.com. John is a well know programmer in his own right, however this is his most important contribution to the Apple II Community to date.


Background

In early 2017 John and Henry from ReActiveMicro were discussing project ideas mostly based around the Raspberry Pi. Henry sent John some hardware and after a few weeks of tinkering and discussing projects John mentioned an idea he had involving floppy drives and backing up software. John knew Henry had worked on the EDD project and they started to discuss how horrible, at best, the EDD was in its attempt to capture the data which represents the floppy. John started to talk about what if we attacked the problem of copying protected disks directly from the drive rather than trying to intercept the data stream from the drive under use like the EDD did. This was the start of what would become the Applesauce project.

By March 2017 John had started to look in to how to control the Disk II Drive and its power requirements. After some research he found the drive should be able to be controlled by a microcontroller.

There have been other similar projects such as Kryoflux and Catwheesel, however these projects have fallen short in several areas especially where Apple II is concerned.


What Is Applesauce?

Applesauce comprises two parts - hardware and software.

The hardware component of the project is a "Controller Interface" that allows an Apple II Floppy Drive to be connected via USB to a modern computer.

The software component runs on the modern computer and controls the Floppy Drive and captures a data stream from the inserted disk.

Once this data stream is captured, the Applesauce software can then process the data for saving as disk image files.

Because Applesauce captures the data on the disk at the flux level, it is able to capture Apple II copy-protection schemes "in place".

The resultant disk image could have its copy protection cracked, or it can be written back to a physical disk by the Applesauce software with protection in place, or (subject to emulation hardware or software support) it can be used with copy protection left in place in the disk image in Apple II emulators or solid state Apple II disk drive emulators.

For non-protected (or previously cracked disks), Applesauce is able to capture a .dsk disk image in approximately 11s.

Blah blah... crap.

Teensy

Info on exactly what is the Teensy and what it does.


Sync Sensor

What it is and why we need it.


EDD Is Dead

As quoted by Antwion, and why.