Warning: Do not try the directory trick mentioned further down in very delicate files in the root structure, as they could be removed into folders causing random misfunction.

A brief examination of /usr/share/contentlister/mode shows some extra manifest files for the content finder application, with some undocumented tags beyond icons: application, storage, document name... This could be useful for people just looking to reorder their directory structure or document access. I have not seen yet a way to extract all the tags, I guess they are hardcoded in some library but not sure.

BTW I am not sure but I believe that while the memory stick only sees vfat partitions, the SD card can be formatted to ext2. Can someone confirm it? It can be useful to make virtual links towards folders in other devices.

That was an incredibly useful tip.

I highly recommend trying:

<directory>
<content>/</content>
</directory>

Thank you! :)

And this one is fun too...

<application>
<Identifier>PROFILES</Identifier>
</application>

or

<application>
<Identifier>SETUP</Identifier>
</application>

<directory>
<content>/</content>
</directory>


Doesn't run binaries, unfortunately.

and the idea with <application><identifier> ... wont work, since the available applications seem to be controlled by er_registry.txt.

The application tag Works great, just you get to run their apps not your own. But it let me built my own little work directory allowing easy access to iLiad settings instead of navigating to where iRex thinks they should be.

The directory tag lets you explore the live directory structure of your iLiad which is pretty interesting I thought. But if all you care about is running applications I guess its pretty boring. :)

URGENT ALERT!!!!!!

Do not try the directory trick in very delicate files in the root structure, as they could be removed into folders causing random misfunction.

Scotty tricks are good ones to browse, but any try to read a file you have browsed to can cause this misbehaviour... the file gets a manifest and fells into a different folder.

The application tag Works great, just you get to run their apps not your own. But it let me built my own little work directory allowing easy access to iLiad settings instead of navigating to where iRex thinks they should be.

The directory tag lets you explore the live directory structure of your iLiad which is pretty interesting I thought. But if all you care about is running applications I guess its pretty boring. :)
Wow that sounds good! Please keep us updated, Scotty (or should I say: Beam Me Up)!

:cool: ...

I am very sorry I did so dangereus suggestion. I'd like to see how to help to repair it.

Am I the only one thinking it is friggin time for a way to reflash the thing ourselves?

Am I the only one thinking it is friggin time for a way to reflash the thing ourselves?

Me too. For some reason I don't know my Iliad won't boot anymore either.

Am I the only one thinking it is friggin time for a way to reflash the thing ourselves?

Or iRex could offer to access to the reflash method under usual "beta-tester non-disclosure" agreement.

Hmm as self imposed penitence I will open my iLiad this Sunday and send you some pictures of the internals by monday afternoon. I preanounce it because you could be tempted to do it before sending them to repair; keep them on warranty.

Hmm as self imposed penitence I will open my iLiad this Sunday[...]

Dude, that sounds heroic but nevertheless stupid (no pun intended). Keep your warranty. I still hope that somehow we'll get a way to reflash once the SDK is out.

better keep your warranty. i think it will have a use some time.

I would not call this even a hack attempt, so I want to believe that warranty is kept. Also I have suggested at iRex forums they could offer a personal non-disclosure agreement if a way to repair it does exist but it is experimental; they promised a restore option some weeks ago.

i don't think they are so happy with the idea of having "advanced" users browsing around in the root directory.

On the other hand it is, from my point of view, bad design of there Viewers/Filemanager if they write manifests and move files you open in every path, instead of having them limited to fixed paths (/mnt/card ... and subfolders) of external or internal memory, in which the system can't be harmed.

This is a point that speeks for having a SSH connection available at least over the wired interface, until the system knows it booted up ok (Devicemanager or what their GUI is called is up and running). If I had a shell, i could easily fix this myself.

On the other hand it is, from my point of view, bad design of there Viewers/Filemanager if they write manifests and move files you open in every path, instead of having them limited to fixed paths (/mnt/card ... and subfolders) of external or internal memory, in which the system can't be harmed, like mine.

Yep, they should to put the manifest and extra files as a hidden ".filename" associated to a "filename". It is a very old issue, coming from the age of MacOS "Resource Folder".

But now macs use "bundles" which are somewhat similar to iRex approach. Basically the allow a folder (=directory in Windows terms :rolleyes5 ) to be seen as a single file in the file-browser. This way you can bundle multiple files. E.g. every application is in fact a bundle, containing the executable, all resources, libraries, etc.

So I kind of like the manifest-folder kind of thing, as on the mac, you could just mark this manifest-folder as bundle, so the user sees it as a single file :happy2:

ouch, that hurts, b_k.

I really hope they don't make you pay. And i really really hope they give you and/or all of us a way to reflash it ourselves.

But try to clear the screen if it doesn't boot anymore by resetting at the right moment. They had to replace my screen due to the slight burn-in from showing the boot screen. -.-

But now macs use "bundles" which are somewhat similar to iRex approach. Basically the allow a folder (=directory in Windows terms :rolleyes5 ) to be seen as a single file in the file-browser. This way you can bundle multiple files. E.g. every application is in fact a bundle, containing the executable, all resources, libraries, etc.

So I kind of like the manifest-folder kind of thing, as on the mac, you could just mark this manifest-folder as bundle, so the user sees it as a single file :happy2:

First macOS used a different concept, the "fork". Standar open of a file opened the "data fork", while a special open opened the "resource fork", which it turn contained the "folders" of resources. Additionaly the file system need a 512 bytes head for each file in order to keep track of the forks. As I said, it has evolved...