Question for experts

[cdavies]

I'm still betting your problem is due to a missing c32exe.sis on the target device. Did you check z:\system\install? Both me and paul checked an E61 and got different answers, so I'm guessing that upgrading the E61 firmware gets you the stub SIS file for at least that device (though I'm never going to upgrade the firmware on this one, since it has d_exc in the ROM at the moment, which makes it incredibly useful for debugging

[Paul.Todd]

The fact that it is saying the package is not installed is probably a good indication.

I guess you are running an early debug ROM which may not have it on.

I checked my N73 and its on there as well

[cdavies]

Checked my N91, no dice there either. It was on my N73 though. Seems very patchwork, but then again I've never updated the firmware on any of these devices.

[Svat_]

Hm..
I have just checked it on my E60, and I can't find c32exe.sis in this folder (z:\system\install).
Is it means that I can't implement interceptions of TCP/IP packets on my handset anyway?
And what I can do in this case? Only update firmware on my device?

[cdavies]

Yep, if you don't have c32exe.sis, you can't install an after market IP hook.

Try updating the firmware to the latest version, but if that doesn't solve the problem, you're pretty much stuffed.

[Svat_]

Thanks guys! Now I will search latest firmware for my device and try updating. I hope it is helps me.

[nigel.brown]

Hello;
Did you get this working?
I managed to install the esk file and prt, but the prt does not seem to be loaded (i.e. CreateProtocolFamilyL is never called).
I have the same capabilities as other .prts I found.
Regards

[siemensc55]

guys a question somehow in the same context, we have an application embeded as a rom image [includes a whole bunch of exe and dlls], to test the functionality we have stubs(same dll but limited functionality) to some of the dlls in this application.

while making ROM image, we did only one stub sis file for the whole application.

Now when we need to test, need to install the stubs(same dll but limited functionality), this where the problem appears.

with a pkg type "PU" and contents exactly as original application, the stubbed dlls could be installed and used.

However

with a pkg type "PU" and only stubbed dlls, installation is fine but the dll from ROM is still used.

do you have some pointers to allow installation of only stubbed dlls and making use of rest from ROM?

would this work, if at the time of making ROM we make two stub sis files one with complete list of binaries for app and the other only with stubbed dlls, however uid,appname and vendor etc. for both pkg are same?

[liuxingyu_best]

Thanks a lot.

[Paul.Todd]

This thread is already being aswered on the Symbian board.
http://developer.symbian.com/forum/t...essageID=81412

Please remember we are very restricted about what we can say as these API's are Symbian partner API's and not public.

See my post this morning with the corrected document name.