My application is of a type that it makes no sense to install it on anything
but the C drive of the device, specifically the application must not be
installed on any kind of removable media.
The good news is that if you specify C:\ in your pkg file rather than !:\
the installer application doesn�t ask you the question as to where you want
to install, it just puts it on the C drive end of story.
I have read the section in the Symbian Signed test criteria document that
talks about installation to all memory locations and my belief is that doing
what i have done (ie hardwiring to C) is not going to cause a failure of
this test in symbian signed.
But....
There is one rather disapointing scenario. If you are using FExplorer to
install your application from a memory card (ie you have your .sis on the
memory card and you click it and launch the installer), FExplorer will ask
you the question where you want to install.
I realise that FExplorer is a third party unsigned application and therefore
to be treated acordingly but, since the file manager in series 60 only lets
you see C:\system\nokia\ and anything below it, everyone uses FExplorer.
indeed it is one of the symbian signed test tools.
The net result of installing in this way (if you select to install my app on
the memory card) is that all files are copied to the C drive (coz that�s
were i tell 'em to go in the pkg) BUT the myapp.sis that should be in
C:\system\installs is now on the memory card. this has all manner of
unpleasant ramifications especially if the user removes the card leaving
them with my app installed but not visible in the application manager and
therefore un-uninstallable.
Can someone from symbian signed please confirm that this problem is
considered as a problem with FExplorer rather than of my application and
that this won�t cause a problem with getting the application signed.
PL
Hi
1. > what i have done (ie hardwiring to C) is not going to cause a failure
of this test in symbian signed.
It is probable that you'll need a waiver unless the EX-006 exception applies
(doesn't sound like it). However if it is obvious that this can't be
installed on removable media then it is likely such a waiver will be
granted. I would kick the request off possibly even before submission to
test house
2. The problem with FExplorer is almost certainly a problem with the
installer and nothing to do with FExplorer. As the location the installer
puts the SIS file is outside your control this is covered by the EX-006
exception (see last paragraph in test criteria document).
Regards
Hamish
(Symbian)
"petxolobo" <[email protected]> wrote in message
news:sy7pHh3RGHA.2032@extapps30...
> My application is of a type that it makes no sense to install it on
> anything but the C drive of the device, specifically the application must
> not be installed on any kind of removable media.
>
> The good news is that if you specify C:\ in your pkg file rather than !:\
> the installer application doesn�t ask you the question as to where you
> want to install, it just puts it on the C drive end of story.
>
> I have read the section in the Symbian Signed test criteria document that
> talks about installation to all memory locations and my belief is that
> doing what i have done (ie hardwiring to C) is not going to cause a
> failure of this test in symbian signed.
>
> But....
>
> There is one rather disapointing scenario. If you are using FExplorer to
> install your application from a memory card (ie you have your .sis on the
> memory card and you click it and launch the installer), FExplorer will ask
> you the question where you want to install.
>
> I realise that FExplorer is a third party unsigned application and
> therefore to be treated acordingly but, since the file manager in series
> 60 only lets you see C:\system\nokia\ and anything below it, everyone uses
> FExplorer. indeed it is one of the symbian signed test tools.
>
> The net result of installing in this way (if you select to install my app
> on the memory card) is that all files are copied to the C drive (coz
> that�s were i tell 'em to go in the pkg) BUT the myapp.sis that should be
> in C:\system\installs is now on the memory card. this has all manner of
> unpleasant ramifications especially if the user removes the card leaving
> them with my app installed but not visible in the application manager and
> therefore un-uninstallable.
>
> Can someone from symbian signed please confirm that this problem is
> considered as a problem with FExplorer rather than of my application and
> that this won�t cause a problem with getting the application signed.
>
> PL
>
>
Hi Hamish,
Thanks for your reply.
You are right when you say that that EX-006 won�t apply in my case however i
am wondering if EX-002 does apply.
EX-002 says:
"... An acceptable exception can be granted if the application explicitly
states it should only be installed on a certain memory device and the
application is also prevented from being installed onto other memory devices
(e.g. by hard-coding locations in the .PKG file to this effect)."
The hard coding bit is what i have done. My questions are:
How and where should i explicitly state that the appilcation be only
installed on the C drive?
Is this going to be enough to get through symbian signed or do you feel that
there is still a requirement for a waiver?
PL
"Hamish Willee" <[email protected]> escribi� en el mensaje
news:d8S$nO$RGHA.2652@extapps30...
> Hi
>
> 1. > what i have done (ie hardwiring to C) is not going to cause a failure
> of this test in symbian signed.
> It is probable that you'll need a waiver unless the EX-006 exception
> applies (doesn't sound like it). However if it is obvious that this can't
> be installed on removable media then it is likely such a waiver will be
> granted. I would kick the request off possibly even before submission to
> test house
>
> 2. The problem with FExplorer is almost certainly a problem with the
> installer and nothing to do with FExplorer. As the location the installer
> puts the SIS file is outside your control this is covered by the EX-006
> exception (see last paragraph in test criteria document).
>
> Regards
> Hamish
> (Symbian)
>
>
> "petxolobo" <[email protected]> wrote in message
> news:sy7pHh3RGHA.2032@extapps30...[color=green]
>> My application is of a type that it makes no sense to install it on
>> anything but the C drive of the device, specifically the application must
>> not be installed on any kind of removable media.
>>
>> The good news is that if you specify C:\ in your pkg file rather than !:\
>> the installer application doesn�t ask you the question as to where you
>> want to install, it just puts it on the C drive end of story.
>>
>> I have read the section in the Symbian Signed test criteria document that
>> talks about installation to all memory locations and my belief is that
>> doing what i have done (ie hardwiring to C) is not going to cause a
>> failure of this test in symbian signed.
>>
>> But....
>>
>> There is one rather disapointing scenario. If you are using FExplorer to
>> install your application from a memory card (ie you have your .sis on the
>> memory card and you click it and launch the installer), FExplorer will
>> ask you the question where you want to install.
>>
>> I realise that FExplorer is a third party unsigned application and
>> therefore to be treated acordingly but, since the file manager in series
>> 60 only lets you see C:\system\nokia\ and anything below it, everyone
>> uses FExplorer. indeed it is one of the symbian signed test tools.
>>
>> The net result of installing in this way (if you select to install my app
>> on the memory card) is that all files are copied to the C drive (coz
>> that�s were i tell 'em to go in the pkg) BUT the myapp.sis that should be
>> in C:\system\installs is now on the memory card. this has all manner of
>> unpleasant ramifications especially if the user removes the card leaving
>> them with my app installed but not visible in the application manager and
>> therefore un-uninstallable.
>>
>> Can someone from symbian signed please confirm that this problem is
>> considered as a problem with FExplorer rather than of my application and
>> that this won�t cause a problem with getting the application signed.
>>
>> PL
>>
>>
>
>
>[/color]
Hi
You were right, I was wrong 😊 You won't need a waiver for this if your
application explicitly states to the user where the files are to be located.
Normally this would be done on a click-through license on the SIS package -
commonly also in the User Guide (if any).
Regards
H
"petxolobo" <[email protected]> wrote in message
news:%23N9tmeBSGHA.2764@extapps30...
> Hi Hamish,
>
> Thanks for your reply.
>
> You are right when you say that that EX-006 won�t apply in my case however
> i am wondering if EX-002 does apply.
>
> EX-002 says:
> "... An acceptable exception can be granted if the application explicitly
> states it should only be installed on a certain memory device and the
> application is also prevented from being installed onto other memory
> devices (e.g. by hard-coding locations in the .PKG file to this effect)."
>
> The hard coding bit is what i have done. My questions are:
>
> How and where should i explicitly state that the appilcation be only
> installed on the C drive?
>
> Is this going to be enough to get through symbian signed or do you feel
> that there is still a requirement for a waiver?
>
> PL
>
> "Hamish Willee" <[email protected]> escribi� en el mensaje
> news:d8S$nO$RGHA.2652@extapps30...[color=green]
>> Hi
>>
>> 1. > what i have done (ie hardwiring to C) is not going to cause a
>> failure of this test in symbian signed.
>> It is probable that you'll need a waiver unless the EX-006 exception
>> applies (doesn't sound like it). However if it is obvious that this can't
>> be installed on removable media then it is likely such a waiver will be
>> granted. I would kick the request off possibly even before submission to
>> test house
>>
>> 2. The problem with FExplorer is almost certainly a problem with the
>> installer and nothing to do with FExplorer. As the location the installer
>> puts the SIS file is outside your control this is covered by the EX-006
>> exception (see last paragraph in test criteria document).
>>
>> Regards
>> Hamish
>> (Symbian)
>>
>>
>> "petxolobo" <[email protected]> wrote in message
>> news:sy7pHh3RGHA.2032@extapps30...[color=darkred]
>>> My application is of a type that it makes no sense to install it on
>>> anything but the C drive of the device, specifically the application
>>> must not be installed on any kind of removable media.
>>>
>>> The good news is that if you specify C:\ in your pkg file rather than
>>> !:\ the installer application doesn�t ask you the question as to where
>>> you want to install, it just puts it on the C drive end of story.
>>>
>>> I have read the section in the Symbian Signed test criteria document
>>> that talks about installation to all memory locations and my belief is
>>> that doing what i have done (ie hardwiring to C) is not going to cause a
>>> failure of this test in symbian signed.
>>>
>>> But....
>>>
>>> There is one rather disapointing scenario. If you are using FExplorer
>>> to install your application from a memory card (ie you have your .sis on
>>> the memory card and you click it and launch the installer), FExplorer
>>> will ask you the question where you want to install.
>>>
>>> I realise that FExplorer is a third party unsigned application and
>>> therefore to be treated acordingly but, since the file manager in series
>>> 60 only lets you see C:\system\nokia\ and anything below it, everyone
>>> uses FExplorer. indeed it is one of the symbian signed test tools.
>>>
>>> The net result of installing in this way (if you select to install my
>>> app on the memory card) is that all files are copied to the C drive (coz
>>> that�s were i tell 'em to go in the pkg) BUT the myapp.sis that should
>>> be in C:\system\installs is now on the memory card. this has all manner
>>> of unpleasant ramifications especially if the user removes the card
>>> leaving them with my app installed but not visible in the application
>>> manager and therefore un-uninstallable.
>>>
>>> Can someone from symbian signed please confirm that this problem is
>>> considered as a problem with FExplorer rather than of my application and
>>> that this won�t cause a problem with getting the application signed.
>>>
>>> PL
>>>
>>>
>>
>>
>>[/color]
>
>
>[/color]
Other possible reasons why the installer would prompt for drive
selection:
1. The .pkg file contains combination of '!' and hard-coded drive
letters.
2. The drive hasn't got enough disk space.
3. May be the drive is write-protected. Check the toggle switch if
there is one.
4. It is phone manufacturer specific; hence, some phones might prompt
regardless.
As Hamish said, this is very unlikely a FExplorer issue. Try
installing the SIS file from the PC or send it via short-link e.g. BT.
and see what happens.
Nishaat R.
Symbian Signed.
On Tue, 14 Mar 2006 16:05:45 +0100, "petxolobo"
<[email protected]> wrote:
>My application is of a type that it makes no sense to install it on anything
>but the C drive of the device, specifically the application must not be
>installed on any kind of removable media.
>
>The good news is that if you specify C:\ in your pkg file rather than !:\
>the installer application doesn�t ask you the question as to where you want
>to install, it just puts it on the C drive end of story.
>
>I have read the section in the Symbian Signed test criteria document that
>talks about installation to all memory locations and my belief is that doing
>what i have done (ie hardwiring to C) is not going to cause a failure of
>this test in symbian signed.
>
>But....
>
>There is one rather disapointing scenario. If you are using FExplorer to
>install your application from a memory card (ie you have your .sis on the
>memory card and you click it and launch the installer), FExplorer will ask
>you the question where you want to install.
>
>I realise that FExplorer is a third party unsigned application and therefore
>to be treated acordingly but, since the file manager in series 60 only lets
>you see C:\system\nokia\ and anything below it, everyone uses FExplorer.
>indeed it is one of the symbian signed test tools.
>
>The net result of installing in this way (if you select to install my app on
>the memory card) is that all files are copied to the C drive (coz that�s
>were i tell 'em to go in the pkg) BUT the myapp.sis that should be in
>C:\system\installs is now on the memory card. this has all manner of
>unpleasant ramifications especially if the user removes the card leaving
>them with my app installed but not visible in the application manager and
>therefore un-uninstallable.
>
>Can someone from symbian signed please confirm that this problem is
>considered as a problem with FExplorer rather than of my application and
>that this won�t cause a problem with getting the application signed.
>
>PL
>
>
Other possible reasons why the installer would prompt for drive
selection:
1. The .pkg file contains combination of '!' and hard-coded drive
letters.
2. The drive hasn't got enough disk space.
3. May be the drive is write-protected. Check the toggle switch if
there is one.
4. It is phone manufacturer specific; hence, some phones might prompt
regardless.
As Hamish said, this is very unlikely a FExplorer issue. Try
installing the SIS file from the PC or send it via short-link e.g. BT.
and see what happens.
Nishaat R.
Symbian Signed.
On Tue, 14 Mar 2006 16:05:45 +0100, "petxolobo"
<[email protected]> wrote:
>My application is of a type that it makes no sense to install it on anything
>but the C drive of the device, specifically the application must not be
>installed on any kind of removable media.
>
>The good news is that if you specify C:\ in your pkg file rather than !:\
>the installer application doesn�t ask you the question as to where you want
>to install, it just puts it on the C drive end of story.
>
>I have read the section in the Symbian Signed test criteria document that
>talks about installation to all memory locations and my belief is that doing
>what i have done (ie hardwiring to C) is not going to cause a failure of
>this test in symbian signed.
>
>But....
>
>There is one rather disapointing scenario. If you are using FExplorer to
>install your application from a memory card (ie you have your .sis on the
>memory card and you click it and launch the installer), FExplorer will ask
>you the question where you want to install.
>
>I realise that FExplorer is a third party unsigned application and therefore
>to be treated acordingly but, since the file manager in series 60 only lets
>you see C:\system\nokia\ and anything below it, everyone uses FExplorer.
>indeed it is one of the symbian signed test tools.
>
>The net result of installing in this way (if you select to install my app on
>the memory card) is that all files are copied to the C drive (coz that�s
>were i tell 'em to go in the pkg) BUT the myapp.sis that should be in
>C:\system\installs is now on the memory card. this has all manner of
>unpleasant ramifications especially if the user removes the card leaving
>them with my app installed but not visible in the application manager and
>therefore un-uninstallable.
>
>Can someone from symbian signed please confirm that this problem is
>considered as a problem with FExplorer rather than of my application and
>that this won�t cause a problem with getting the application signed.
>
>PL
>
>
Hi Nishaat,
I think i've tried most combinations. either way I would expect to see the
same behaviour from the File Manager in series 60 as for FExplorer in the
situations 1 through 3 on your list. I don�t know about 4.
bare in mind this only occurs under the following conditions:
the sis is launched from FExplorer
the sis is on the memory card
if the sis is launched from anywhere else or by anything else i never get
the question as to which drive to install on.
also i have noticed that if the sis is launched from the File Manager the
question is "install on:" either the phone or the mmc. but on FExplorer the
question is "save on:" phone or mmc. this also makes me wonder if FExplorer
is doing stuff outside of the standard installer. Now, it may be the case
that this is a transation issue as my phones are not in english but i don�t
think so.
Cheers
PL
"Nishaat R." <[email protected]> escribi� en el mensaje
news:[email protected]...
> Other possible reasons why the installer would prompt for drive
> selection:
>
> 1. The .pkg file contains combination of '!' and hard-coded drive
> letters.
> 2. The drive hasn't got enough disk space.
> 3. May be the drive is write-protected. Check the toggle switch if
> there is one.
> 4. It is phone manufacturer specific; hence, some phones might prompt
> regardless.
>
> As Hamish said, this is very unlikely a FExplorer issue. Try
> installing the SIS file from the PC or send it via short-link e.g. BT.
> and see what happens.
>
> Nishaat R.
> Symbian Signed.
>
> On Tue, 14 Mar 2006 16:05:45 +0100, "petxolobo"
> <[email protected]> wrote:
>[color=green]
>>My application is of a type that it makes no sense to install it on
>>anything
>>but the C drive of the device, specifically the application must not be
>>installed on any kind of removable media.
>>
>>The good news is that if you specify C:\ in your pkg file rather than !:\
>>the installer application doesn�t ask you the question as to where you
>>want
>>to install, it just puts it on the C drive end of story.
>>
>>I have read the section in the Symbian Signed test criteria document that
>>talks about installation to all memory locations and my belief is that
>>doing
>>what i have done (ie hardwiring to C) is not going to cause a failure of
>>this test in symbian signed.
>>
>>But....
>>
>>There is one rather disapointing scenario. If you are using FExplorer to
>>install your application from a memory card (ie you have your .sis on the
>>memory card and you click it and launch the installer), FExplorer will ask
>>you the question where you want to install.
>>
>>I realise that FExplorer is a third party unsigned application and
>>therefore
>>to be treated acordingly but, since the file manager in series 60 only
>>lets
>>you see C:\system\nokia\ and anything below it, everyone uses FExplorer.
>>indeed it is one of the symbian signed test tools.
>>
>>The net result of installing in this way (if you select to install my app
>>on
>>the memory card) is that all files are copied to the C drive (coz that�s
>>were i tell 'em to go in the pkg) BUT the myapp.sis that should be in
>>C:\system\installs is now on the memory card. this has all manner of
>>unpleasant ramifications especially if the user removes the card leaving
>>them with my app installed but not visible in the application manager and
>>therefore un-uninstallable.
>>
>>Can someone from symbian signed please confirm that this problem is
>>considered as a problem with FExplorer rather than of my application and
>>that this won�t cause a problem with getting the application signed.
>>
>>PL
>>
>>
>[/color]
Hi Nish
My comments were really regarding the install location of the SIS stub file
after processing - AFAIK this is not defined in the pkg file and therefore
completely outside the control of the developer, irrespective of what
FExplorer does.
I think the rest of its a bit of a red herring - prompts etc are all fine
provided that file specified in the pkg file go where they are supposed to
😊
Cheerio
H
"Nishaat R." <[email protected]> wrote in message
news:[email protected]...
> Other possible reasons why the installer would prompt for drive
> selection:
>
> 1. The .pkg file contains combination of '!' and hard-coded drive
> letters.
> 2. The drive hasn't got enough disk space.
> 3. May be the drive is write-protected. Check the toggle switch if
> there is one.
> 4. It is phone manufacturer specific; hence, some phones might prompt
> regardless.
>
> As Hamish said, this is very unlikely a FExplorer issue. Try
> installing the SIS file from the PC or send it via short-link e.g. BT.
> and see what happens.
>
> Nishaat R.
> Symbian Signed.
>
> On Tue, 14 Mar 2006 16:05:45 +0100, "petxolobo"
> <[email protected]> wrote:
>[color=green]
>>My application is of a type that it makes no sense to install it on
>>anything
>>but the C drive of the device, specifically the application must not be
>>installed on any kind of removable media.
>>
>>The good news is that if you specify C:\ in your pkg file rather than !:\
>>the installer application doesn�t ask you the question as to where you
>>want
>>to install, it just puts it on the C drive end of story.
>>
>>I have read the section in the Symbian Signed test criteria document that
>>talks about installation to all memory locations and my belief is that
>>doing
>>what i have done (ie hardwiring to C) is not going to cause a failure of
>>this test in symbian signed.
>>
>>But....
>>
>>There is one rather disapointing scenario. If you are using FExplorer to
>>install your application from a memory card (ie you have your .sis on the
>>memory card and you click it and launch the installer), FExplorer will ask
>>you the question where you want to install.
>>
>>I realise that FExplorer is a third party unsigned application and
>>therefore
>>to be treated acordingly but, since the file manager in series 60 only
>>lets
>>you see C:\system\nokia\ and anything below it, everyone uses FExplorer.
>>indeed it is one of the symbian signed test tools.
>>
>>The net result of installing in this way (if you select to install my app
>>on
>>the memory card) is that all files are copied to the C drive (coz that�s
>>were i tell 'em to go in the pkg) BUT the myapp.sis that should be in
>>C:\system\installs is now on the memory card. this has all manner of
>>unpleasant ramifications especially if the user removes the card leaving
>>them with my app installed but not visible in the application manager and
>>therefore un-uninstallable.
>>
>>Can someone from symbian signed please confirm that this problem is
>>considered as a problem with FExplorer rather than of my application and
>>that this won�t cause a problem with getting the application signed.
>>
>>PL
>>
>>[/color]
I have found the same problem than you. My application has only sense to
be installed on phone memory (C😊, so I have hardcoded in pkg the C:
drive. I have already sent the application to symbiansigned. I hope that
all test will be passed...
My question is if you hardcode a drive on pkg, is it clear for them that
your application has to be installed in a drive?
petxolobo wrote:
> My application is of a type that it makes no sense to install it on anything
> but the C drive of the device, specifically the application must not be
> installed on any kind of removable media.
>
> The good news is that if you specify C:\ in your pkg file rather than !:\
> the installer application doesn�t ask you the question as to where you want
> to install, it just puts it on the C drive end of story.
>
> I have read the section in the Symbian Signed test criteria document that
> talks about installation to all memory locations and my belief is that doing
> what i have done (ie hardwiring to C) is not going to cause a failure of
> this test in symbian signed.
>
> But....
>
> There is one rather disapointing scenario. If you are using FExplorer to
> install your application from a memory card (ie you have your .sis on the
> memory card and you click it and launch the installer), FExplorer will ask
> you the question where you want to install.
>
> I realise that FExplorer is a third party unsigned application and therefore
> to be treated acordingly but, since the file manager in series 60 only lets
> you see C:\system\nokia\ and anything below it, everyone uses FExplorer.
> indeed it is one of the symbian signed test tools.
>
> The net result of installing in this way (if you select to install my app on
> the memory card) is that all files are copied to the C drive (coz that�s
> were i tell 'em to go in the pkg) BUT the myapp.sis that should be in
> C:\system\installs is now on the memory card. this has all manner of
> unpleasant ramifications especially if the user removes the card leaving
> them with my app installed but not visible in the application manager and
> therefore un-uninstallable.
>
> Can someone from symbian signed please confirm that this problem is
> considered as a problem with FExplorer rather than of my application and
> that this won�t cause a problem with getting the application signed.
>
> PL
>
>
>