Tried that, doesn't do anything, qpose comes up but doesn't load the rom
I'd look at the patch (http://www.climov.com/zaurus/qpose/qpose-3.5-0.1.patch.gz) and see what it expects to be passed to make it open the file.
Might be some random QCOP call I expect.
No idea about the MIME stuff I'm afraid - I presume you've added the entries from the postinst script though.
Si
[div align=\"right\"][a href=\"index.php?act=findpost&pid=92983\"][{POST_SNAPBACK}][/a][/div]
Well, I uninstalled, and reinstalled from scratch, looked at the mime settings and renamed my palmiiixe.rom to palmiiixe.ROM, restarted opie, now I have the palm emulator icon under applications and the proper icon for the rom showing up under documents. However, clicking on the rom on the docs tab results in 2 things happening:
1) the numer of rom icons incresases by 1 each time I do this
2) I get a segfault "Palm Emulator was terminated due to a signal code SIGSEGV"
If I run qpose from the cli (via ssh), it starts up after being run twice, it throws up the following errors
first run
# qpose
/opt/QtPalmtop/bin/qpose
ln: /tmp/qtembedded-root/QtEmbedded-0: No such file or directory
QSocket::writeBlock: Socket is not open
QSocket::writeBlock: Socket is not open
QSocket::writeBlock: Socket is not open
QSocket::writeBlock: Socket is not open
No Qt/Embedded server appears to be running.
If you want to run this program as a server,
add the "-qws" command-line option.
second run
# qpose
/opt/QtPalmtop/bin/qpose
EmWindow::WindowReset()
QDir::readDirEntries: Cannot read the directory: ../apps
I then go to the docs tab and click on the rom and same segfault error as before.
I've also noticed that after trying to run qpose a couple of times results in strange behaviour for my Z, it won't reboot and in one case, the message light came on, I did a soft reset and the stuff on screen stayed on screen, I had to eventually remove the battery to get out of that lockup.
I also just noticed that after running it twice via the icons and having it segfault, the keyboard wouldn't work anymore in a console window :-( Rebooting and running it via cli over ssh, did not have this effect.