Prizm OS 1.02 available for download

[Munchor]

OS? We can now know more about the prizm disassembling it!!!!

[DJ Omnimaga]

This is gonna be hard to look through the 11 MB file though

[z80man]

I'm trying to isolate the OS, but that would still leave 6MB to work through. So far my strategy has been to disassemble the Prizm usb drive using Hxd. Then trying to match hex strings between that and the exe.

Yeah 200th post!!!!!!!!!!!   

[DJ Omnimaga]

Hmm I see. I hope the OS isn't 11 MB, tho

Also congrats on 200th post! I just reached 23000 so you only have 22800 to go. j/k

[AngelFish]

Z80man, I hate to tell you this, but that strategy will almost certainly fail. The reason is that the USB dump isn't actually a dump of the Prizm's internal memory. It's a dump of the virtual memory, which is entirely overwritten during USB transfer to make room for that folder that appears on your desktop. Take a closer look at the file structure. You'll notice that everything is organized into the directories and the sections are each named with the name of the folder. The files from each folder are likewise under in the same sections.

In other words, it's the hex version of what you see on the screen.

Also, I took the liberty of simply disassembling the exe to look for valid code and there's nothing that I would call valid in the entire file. I suspect compression, but I don't know how that would work.

[z80man]

Z80man, I hate to tell you this, but that strategy will almost certainly fail. The reason is that the USB dump isn't actually a dump of the Prizm's internal memory. It's a dump of the virtual memory, which is entirely overwritten during USB transfer to make room for that folder that appears on your desktop. Take a closer look at the file structure. You'll notice that everything is organized into the directories and the sections are each named with the name of the folder. The files from each folder are likewise under in the same sections.

In other words, it's the hex version of what you see on the screen.

Also, I took the liberty of simply disassembling the exe to look for valid code and there's nothing that I would call valid in the entire file. I suspect compression, but I don't know how that would work.

What I was thinking though is that if there is some hex string inside the usb folder then the OS must have written that there earlier. Then that string of data might be in the exe file somewhere. Not in the same location, but that string might exist. And so far I've already found a few 16 byte hex strings that match between the two.