vetz wrote on 2026-09-04, 18:00:

I had Claude make a standalone Python script that extracts all the contents and also gives a manifest + list files that are damaged.

Some very interesting stuff on here that has never been released before like the Speedy3D SDK! I also found a nVidia NV10 (Geforce 256) briefing to STB from October 1998 as well as alot of info on STBs MVP multi-monitor product with BIOS source and ROM images and info on the Permedia 3 among much more.

py iomega113.py --img "DISK.img" --out "OUTDIR" --jobs 12 --writers 1 --catalog Streams the extraction with a progress line, the […]
Show full quote

py iomega113.py --img "DISK.img" --out "OUTDIR" --jobs 12 --writers 1 --catalog
Streams the extraction with a progress line, then a JSON summary and any warnings, and writes two files next to OUTDIR:

<setname>.manifest.tsv — every entry: kind, full archive path, size, attributes, timestamp, and a note column flagging damaged or truncated files
<setname>.damage.json — the damaged-segment map, if any
Files land in OUTDIR\<image basename>\<drive>\

Look before you extract:
py iomega113.py --img "DISK.img" --catalog-only # the archive's own file list

--jobs N — decompression is a bit-level LZ77 loop and pure Python manages ~2 MB/s. Segments decode independently (I measured zero cross-segment history references), so this parallelises safely: --jobs 12 was 4.8× faster with byte-identical output. Use it always.
--writers N — Amount of files to write in parallell (as there are many many small files). Raise it for network targets, drop to 1 for a local SSD.

Thanks for this, it looks like it's able to get a lot out of the Vendor SC backup one, I get lots of e:\qvhfaaaa.b type files out of the VSS one?

The Vendor SC one has some extremely interesting 3dfx things! There's a folder for the Voodoo 3 that has the original "Banshee 2" datasheet and presentation - "Voodoo2 SLI on a chip!"
Full schematics for the SGRAM and SDRAM versions of the Voodoo 3, along with layer by layer PDFs of an early SGRAM version. The Banshee 2 MDK (manufacturer development kit?) looks very interesting but has an unknown password, it's pretty much the same as the "B2 APG SGRAM 4L 16M" directory?

It also has the only hardware information I've ever seen for the Banshee 1, with the same schematics so that's a confirmed pinout for it, which I think has not been known til now. A manufacturer diagnostic tool for the banshee. The "databook.pdf" is the full document with BGA pinout and everything 😀
A mention of the "Banshee+" alongside the Banshee 1/2, which would've been an overclocked 0.25um banshee

For the Voodoo 2, there's the "V2databook.doc" which is the full one with pinout and pin descriptions. That's new I think? There's a parts list the same as the one sdz compiled through reverse engineering: "2220_cb.xls"

And because it's from a manufacturer, there are datasheets for every type of RAM, capacitors and everything else from back then collected in one place.

In the MVP folder there's source code for the ET4000 PCI vBIOS.

Dipshidian wrote on 2026-09-04, 07:15:

Ooo, that V1000 API and microcode source sounds particularly intriguing, given the supposed programmability of that hardware.

Apparently the chip was quite buggy. It would be interesting to see what the microcode did to deal with that.

There was a good in-depth look at the V1000 awhile back:
https://fabiensanglard.net/vquake/

There's a mention of them trying to make it decode MPEG1 but they were not able to make it stable. These cards are rather prone to freezing up in 3D games too.

Great article about it here too
https://vintage3d.org/

Claude wrote a tool to extract Iomega 1-Step Backup Jaz/Zip images:

https://drive.google.com/file/d/1xDy55mYwNN43 … iew?usp=sharing

It reads raw .img cartridge dumps and recovers files even from damaged media. These backups are not stored as plain QIC tapes; they're wrapped inside IMAGE.113 files within a FAT16 image, which is why existing QIC tools generally don't read them.

The extractor preserves timestamps, generates damage reports, and continues through bad segments instead of aborting. On a heavily damaged Jaz cartridge, it recovered over 157,000 files, with only about 31 MB lost out of 3.9 GB. Python and C++ source code are included.

It also handles Visual SourceSafe backups. If you see filenames like aaaaaaaa or qvhfaaaa.b, that's normal VSS storage, not corruption.

The reconstructed VSS tree with real filenames is the real gem!

https://gofile.io/d/J4HTXstx the stuff we managed to pull out is here

From what I can see we've got driver source code for rendition (v1000/v2x00), nvidia (riva 128/tnt/pre-release tnt2 including VBIOS), s3 (trio/virge/early savages including VBIOS), some Intel i740, some voodoo2/banshee/voodoo3, some chromatic mpact, "sp3d" (some failed 1998 german startup), cirrus 5446, tseng et4000+et6000

starfrost wrote on 2026-09-06, 12:19:

https://gofile.io/d/J4HTXstx the stuff we managed to pull out is here

From what I can see we've got driver source code for rendition (v1000/v2x00), nvidia (riva 128/tnt/pre-release tnt2 including VBIOS), s3 (trio/virge/early savages including VBIOS), some Intel i740, some voodoo2/banshee/voodoo3, some chromatic mpact, "sp3d" (some failed 1998 german startup), cirrus 5446, tseng et4000+et6000

link says "Could not load this folder"

that's strange, I just tested it on my machine and it seems to work. Maybe try using a VPN or try refreshing a few times?

starfrost wrote on 2026-09-06, 12:19:

https://gofile.io/d/J4HTXstx the stuff we managed to pull out is here

From what I can see we've got driver source code for rendition (v1000/v2x00), nvidia (riva 128/tnt/pre-release tnt2 including VBIOS), s3 (trio/virge/early savages including VBIOS), some Intel i740, some voodoo2/banshee/voodoo3, some chromatic mpact, "sp3d" (some failed 1998 german startup), cirrus 5446, tseng et4000+et6000

Thanks for sharing that, the gofile link worked fine for me.
Just found there's a 3dfx diagnostic tool for the Banshee and Voodoo 3 which should be similar to the Nvidia MATS tool. I think something like that came up for the Voodoo 2 last year but I never got around to doing anything with it.
It's in Archive\recovered\latest\Diags\3Dfx\voodoo3\BIN

got files thanks!

I like all the presentations. Besides some already mentioned there's also one for the unreleased Rendition V2200 card with Fujitsu geometry processor.

Nice

starfrost wrote on 2026-09-06, 12:19:

https://gofile.io/d/J4HTXstx the stuff we managed to pull out is here

From what I can see we've got driver source code for rendition (v1000/v2x00), nvidia (riva 128/tnt/pre-release tnt2 including VBIOS), s3 (trio/virge/early savages including VBIOS), some Intel i740, some voodoo2/banshee/voodoo3, some chromatic mpact, "sp3d" (some failed 1998 german startup), cirrus 5446, tseng et4000+et6000

Thanks! Great work.

leileilol wrote on 2026-09-04, 23:27:

sharangad wrote on 2026-09-04, 18:17:

Are these safe to use? By safe I mean legal.

No

This is a random uploader uploading disks en masse. Nothing here is legally cleared and it'd be foolish for emulators to utilize them... It'd be the same "this will help emulators" naive bullshit i've seen whenever nintendo had a big leak. It's poison, even to glance it.

Basically only what can be proven in court is illegal. And there's no way to prove that somebody has read through them. Using the code in an open source project w0uld be another matter.