Before getting into how to recover data, I want to introduce this guide with my story explaining what happened.


This should serve as a warning, because learning from my mistakes will prevent you from making your recovery process harder.


This took place over the span of months, and many details and side-tangents have been omitted for clarity.

My Story

I received a tape containing the “end of project” development for Frogger 2: Swampy’s Revenge, part of my favorite childhood franchise.


This tape is believed to be the only backup of the final game source code, game assets, and other development data.


As one could imagine, this is priceless to recover. But how does one even read/write data from a tape? Why did they even use tapes?


The average hard drive size in 1999/2000 seems to have been around 10GB, and hard drives are not known for their longevity.


OnStream tapes were a very appealing proposition because they could offer 50GB cartridges (25GB when uncompressed), which were cheaper than most hard drives!


Tapes are great for backups and have very high longevity when stored properly. And they could buy a tape drive that they could put into their computer just like a CD or floppy disk drive.


Unfortunately, while tapes have good longevity, these tape drives did not. OnStream, the company who made the tapes and tape drives, ceased operations in 2003, after only just releasing their first drive in 1999.


These drives are uncommon, especially the model which can use 50GB tapes. So, the first big hurdle was finding a compatible tape drive.

Tape Picture:


Picture of the tape

1) Finding a compatible/working tape drive

I was lucky to know that I needed an “OnStream SC-50” tape drive, because that was the model written on the label of the tape.


And, I found one single business selling this drive online, so I pounced.
Unfortunately, no matter what I did, when I put the tape into the drive, it would appear to read, then eject automatically.


I tried different operating systems, different software versions, different sofware, different drivers, etc. Nothing worked.


Eventually, I concluded the drive was broken, and looking inside proved this to be true, as the rubber pinch roller had melted.


My efforts to fix the drive were let’s say unsuccessful, so I looked for another drive. Because there were no other options, I got an ADR-50e.
That drive was advertised as compatible with these tapes. When that drive worked with my “test tape” (a blank tape I had purchased exclusively for testing), but still refused to read the Frogger tape.


At this point, I incorrectly concluded that there must have been a problem with the tape itself and it were damaged.


What had actually happened was that the ADR-50e drive was advertised as compatible, but there was a caveat. It was only compatible with tapes which were written with an ADR-50e drive, or tapes written with certain software.


At this point, I didn’t even know what software had been used to write the data, let alone this obscure quirk of the tape drive, it was advertised as compatible after all.


So assuming the tape was defective, I sent it in to a professional data recovery company, believing it to be damaged. This was a HUGE mistake…

Melted Pinch Roller:


Melted Pinch Roller

2) Professional Data Recovery Sucks

They were the professionals, right? They made it seem like they had a special method of recovering data for this kind of tape!


Their website said specifically that they could recover data from OnStream tapes, and they had good non-botted reviews as far as I could tell.


Perhaps they were fine for common data storage types like hard drives or SSDs. Those should be easier since there are advanced recovery tools available for them.


However, I do not think I will ever consider sending tapes into a professional data recovery company again, even for more common digital tape formats.

What this company should have done:


This company should have not advertised the capability of recovering data from these tapes, a capability they clearly did not possess.


The company should have made the risks clear they they didn’t know if whatever machine they used was even capable of recovering data from the tape instead of pretending they knew it was.


The company should not have told me they could recover data from this tape.

What this company actually did:


This company specifically advertised that they could recover data from OnStream tapes. Bullshit.


They clearly didn’t even have an OnStream SC-50 tape drive, because if they did they could have just used the official Linux kernel from 10-20 years ago which came with a driver that could have dumped this data.


Over the span of about a month, I received very infrequent and vague communications from the company despite me providing extremely detailed technical information and questions.


Eventually after a month and I had realized what the real problem was, and because things didn’t sound good in data recovery, I asked for it to be sent back.


I was told that “it will perform the way it did when we received it”. What a fucking lie. The tape I got back had been ripped in several spots, and spliced back together.


If this were like an audio tape or something archaic maybe it would have worked, but the tape I got back had problems which it did NOT have when I sent it in.


Screenshot of the data recovery website

They were never capable of recovering the data:


OnStream used technology that no other tape drives did. They had a dedicated data processing chip (ASIC), which was designed specifically for their machines, as opposed to the common chips available on other drives such as Travan.


The entire data processing pipeline from the tape to digital data uses custom hardware designed from scratch for OnStream tape drives, because it let OnStream get way more capacity than any other tape company could at the time.


None of it was shared in any other tape drive. This effectively means that the only way to read data off of one of these tapes is to use one of the original tape drives, or the hardware inside of one.


In other words, whatever machine they put the the tape I was recovering on was NOT compatible with OnStream tapes.


I don’t know why they claimed to be able to recover data from OnStream tapes, but it’s downright false advertising for their website to claim they can recover OnStream data.


Their actions show they clearly didn’t know how to recover data from OnStream tapes.

3) The Realization

Unfortunately, this is only clear in hindsight.


While the tape was in data recovery, I had received a few tapes for another game, and I was able to easily dump two with the ‘OnStream ADR-50e’ drive.
It was also determined the software which had been used to write the data was ARCServe 2000.
Because the labels on the tape had the tape drive model written, I realized the reason I couldn’t read the Frogger 2 tape. It was not because the tape had problems, but because I did actually need an SC-50 drive instead of an ADR-50 drive.


It was too late. The damage had been done by the data recovery company, and upon finally locating another SC-50 tape drive (this time a working one), my worst fears were confirmed.


The splices didn’t just prevent reading from the spliced area, but the splices impacted the drive so severely that upon just putting the tape into the drive, it would enter a state of infinitely trying to re-read the spliced area.


By this point I had found documentation on the commands which could be sent by a computer to a drive, and what the drive would do.


But because the tape would enter into an infinite retry loop when just inserted into the drive (a process henceforth referred to as “initialization”), the drive wasn’t ever even reaching a state where the computer could tell the drive anything about what to do.


This is where the story should probably have stopped. Given up and called it a day, right? Maybe, but I care about this data, and I happen to know a thing or two about computers.

Splice Picture:


At least they made good quality splices.


Example of one of the splices

4) It’s hacking time, baby.

Time and time again, I’ve come to really learn that sometimes if you want something done right, sometimes you really do need to do it yourself.


This really annoys me, because professional data recovery is expensive. If I hadn’t chose a company which had a “no data recovered, no charge” policy, I would have paid thousands of dollars for them to screw up the tape.


That’s insane, and I’m still upset that they told me they could even recover the data on the tape. It feels like they didn’t take their job seriously.


But if you asked me at the time, you wouldn’t have known it upset me. I used it as further motivation instead.


Months of effort was spent understanding the drive, studying its SCSI command interface, reverse engineering firmware, reading documentation, digging up patents, etc.


While much was learned about the drive, the major breakthrough came just after midnight on April 5th 2023 and ended up being significantly simpler than the other attempted methods.


If the initialization process is the problem, then what if we were to run the initialization process with a working tape? Then, by tricking the drive sensors we could switch the tape without the drive knowing a swap occurred.


Using this trick, all undamaged portions of the tape were dumped successfully.

Modified Drive:


The modified tape drive

Tape Dumping:


A computer screen showing tape data getting dumped from the tape

5a) ARCServe Sucks Too

Now that I had the data off the tape, there was still one problem, it wasn’t in a usable format.


The data which comes off the tape is formatted in whatever way the software which wrote it chose.


Unfortunately, that means every single compatible backup software product made their own proprietary format, including ARCserve.


This is the challenge of doing a raw dump, if I were able to use the original software, it would automatically give back the data in a usable form.
Or at least, it would if ARCserve wasn’t garbage! It turns out ARCserve is broken. It isn’t even capable of reading the OnStream tapes it writes, even when they are not damaged.


This issue doesn’t affect tapes written with the ADR-50 drive, but all the tapes I have tested written with the OnStream SC-50 do NOT restore from tape unless the PC which wrote the tape is the PC which restores the tape.
This is because the PC which writes the tape stores a catalog of tape information such as tape file listing locally, which the
ARCserve is supposed to be able to restore without the catalog because it’s something which only the PC which wrote the backup has, defeating the purpose of a backup.


Yet, despite ARCserve showing a popup which says “Restoration Successful”, it restores up to the first 32KB of every file on the tape, but NO MORE.


For an undamaged several gigabyte tape which takes two hours for ARCserve to read, it will restore about 1MB of data total.

5b) Making it usable

In order to convert the files into a usable format (.zip), I had to write a program to convert the tape dumps from the ARCserve format into a .zip.


Thankfully, the ARCserve format wasn’t very complex and I figured it out pretty quickly.


However, there was something strange. An abnormally high amount of files were exporting improperly.


After spending some time analyzing data and thinking, it became apparent that ARCserve was using an undocumented mode for reading the tape.
This is explained in more depth in the guide, but ARCServe was using a feature not documented in the official OnStream driver development document.


This undocumented feature allowed ARCServe to read and write data in a completely different pattern from what the documentation described.


Even after changing my program to read data in the undocumented way ARCserve did it, I still saw errors which I didn’t expect to see.


This time it didn’t take long to see that the missing data was in a position of the tape which the documentation explicitly states “no user data can be recorded”.


So, I modified my tools and the dumping program again to read the area “where no user data can be recorded”.


Finally, after months of reverse engineering of ARCServe, the drive firmware, and other garbage, the program worked, and the data was saved.


Source code for the extraction program is included here.

Recovered Files:


Program Output


Recovered Files

6) The Resolution

In the end, the recovery was an unquestionable success.
Thank you everyone who helped with this project, without your help who knows how long it would have taken or if the data would have even been recovered.


All the important data such as the VSS repository backup (source code history), final game assets, tools, and more were saved.


The tape was the only backup for those things, and it completes Frogger 2’s development archives, which will be released publicly.


It might sound bad that approximately 12GB of the 15GB written data was recovered, but this is misleading.


A couple thousand files were damaged, but they make up less than 5% of the total files on the tape.


Nearly all of the damaged files were either found in another CD backup or were duplicated on another part of the tape.


There were only 15 files which were not perfectly recovered, and only one was noteworthy, a CD image of a PC game build from 1 month after release.


Having recovered 58149 out of the 58164 files on the tape, this adventure can only be considered a success.


Here’s what the damage looks like to the Frogger 2 tape, showing the significant damage and how lucky the recovery was.


Frogger 2 Tape Damage

7) Further Technical Details

The hope is to share all the information we learned so that it might help someone else, and let those who are less experienced recover data too.


Further technical details are scattered throughout the repository, and this guide, and I am willing to answer questions.

Read More