PDA

View Full Version : How to forbid *.exe & *.cab installing in WM6


vanuska
19-07-2008, 04:52 PM
Hello All,

I want to make some application for PPC's under WM6 that restrict users from installation any software on PPC.

Does somebody faced with this?

I was looking for some tweakers or smth, to look how it gonna be, but nothing found for WM6.

I was looking for some registry hacks, but no luck.


Any ideas are welcome.

Cheers.:)

bluemetalaxe
19-07-2008, 04:57 PM
what a thread, so this could help:
1. dont give it to your brother,
2. ask your daddy to buy him his own ppc
3. make a backup
4. give the mio to your mom and go back to kindergarden
5.and just open a thread on a developers side if you have something usefull.
hope i could help you ;)

wearefree
19-07-2008, 05:17 PM
Well I can see this being as the device used for demonstration purpose and OP wants to forbid people from messing it up.

One thing I can think of is to make the windows folder and registry files "read-only" so no other things can be added or used on the phone, after configure the phone the way you wanted.

surur
19-07-2008, 05:57 PM
I'm sure its possible, as a Exchange Activesync security policy.

Surur

Heykrop
19-07-2008, 06:10 PM
Hello All,

I want to make some application for PPC's under WM6 that restrict users from installation any software on PPC.

Does somebody faced with this?

I was looking for some tweakers or smth, to look how it gonna be, but nothing found for WM6.

I was looking for some registry hacks, but no luck.


Any ideas are welcome.

Cheers.:)

Forbidding an EXE from installing would also prevent EXE's from running. Thus rendering everything on the device inopperable.

Preventing CAB files from running though, should just be a matter of altering the registry and what the associated actions for CAB files are.
look in \HKEY_CLASSES_ROOT\cabfile\Shell\Open\Command\
The default string value is wceload.exe "%1" /XXXXXX (XXXXX can be a value of either /delete or /nodelete)
Anyway breaking this string will prevent cab's from installing.


The only other method of doing something like you want, that I can come up with at the moment, would be to create an app that either runs at startup or as a service. It's function would be as suggested above would be to restrict new files from being created in specified storage/registry locations.
I say NEW files as you would not want to restrict modification of existing files in those locations otherwise you risk breaking functionality of pre installed apps.