Quote from: mikehill2003 on April 22, 2011, 08:09:00 pm

Quote from: alberthrocks on April 22, 2011, 08:07:38 pm

I'm playing around with this on an emulator, and I see tons of "document" in an hex editor of a 2.0 ROM,
like "documents/MyLib/numtheory.tns", "documents/SD", etc. Which one is it?

Does OSLauncher work for you in the emulator? The "Documents" you need to remove is at 0x6807F8

I'm using a 2.0 ROM (basically created from a TNO file and installed), so that offset is incorrect for me.

I don't quite understand what you need. What file are you editing?

EDIT: Can someone please confirm that these files are correct:
ndless_installer_os-2.0.1.tns--115,151 bytes--CRC-32:1DF117C2
ndless_resources.tns--7,160 bytes--CRC-32:70D37DC5
oslauncher.tns--1,712 bytes--CRC-32:D6A57DA8
DummyOS's .zip.tns--550 bytes--CRC-32:6F4FC1D7

I'm unable to launch DummyOS on either my calc or the emulator, and I have a feeling my build of ndless is too old. (I downloaded it from the build server today, but I can't compile ndless to test it myself as the latest update somehow killed my build system)
Nevermind, I've got other projects to work on. Any chance of a Prizm Emu sometime soon?

Nah, DJ, worst case scenario is an OS corruption, in which case the boot2 is quite capable of reinstalling a new one, perhaps even without loss of files!

Ah ok, so this cannot access Boot2, right?

No, boot2 is safe from this.

A patcher program, whether on-calc (where it can be combined with OSLauncher, but doesn't need to be) or computer-based, would be the only "easy enough" way to distribute OS modifications

In the computer-based (as I wrote, it was hard, slow and more unsafe to make it an on-calc patcher, so I didn't) tiosmod, I used two layers of I/O functions that can be built upon: read/write/search from/to current file position, read/write/search from/to absolute address.
But for an on-calc patcher fiddling with the host or launched OS (when all interrupts are disabled, of course ), or a computer-based patcher modifying the file in a memory-mapped way, only one layer is needed: read/write/search from/to absolute address.

For maximum ease of use, a computer-based patcher needs to:
* perform the extraction+decryption+decompression of the OS file from TI-Nspire.img;
* apply the patch;
* recompress (deflate) the OS file.
Since it has a UI and it performs decompression and recompression, IMO, the TNOC code base would be a good starting point for a computer-based patcher. extraction+decryption was made by the latest version of imgdump. And the computer-based patching code can be adapted from tiosmod. IOW, we have all the pieces we need


EDIT: I think I'm going to tackle an on-calc patcher code myself.

Definitely

Please send me the addresses, I've made the building blocks for an on-calc patcher+patchset, and I'd like to test them. TIA