Are there any thoughts or answers to any of these questions?
1 of 1 people found this helpful
The MK4000 we use at our customer is 64 MB of persistent storage and 64 MB of RAM. From your memory readout it looks like you’re running the 64/128MB version. You’re going to want to install rhoElements in the application directory. This is persistent storage and won’t be erased at cold boot. As a base OS install from factory the \Application directory has about 22MB of free space, and the rhoElements install will take up about 14MB total of that 22MB. It doesn’t leave you a lot of space for other applications to work with once installed. I would recommend if using something like MSP to deploy: copy the cab down to \temp which is part of the RAM portion of memory and execute to install to \application. You can find the cab file at: C:\Program Files\Motorola RhoElements v1.0\Windows\RhoElements 22.214.171.124 Persistent Runtime.CAB. This is the one that installs to the \application directory. The other .cab will install to program files which will be deleted at cold boot. (Not Ideal for the MK400).
The reason for you install issue may be because you have been dropping the cab file into the \application directory, running it, and then installing to application. At this point you’d have two instances of the application being stored, and you’d be getting errors during the install. Flashing the device may reduce the amount of used space allowing you to install. If this is not the case you may want to post again with more detail to your install procedure, error messages, etc.
Turning on debugging in a small demo app I have, I did report actual free virtual memory. I’m concerned that you have 0KB of free Virtual Memory. (they are all important). It might be interesting to see if when launching the application do you have some VM free, and then see if it is gone after “X” amount of time of the app running. (Some sort of memory leak???). I am probably not the best person to answer that one.
To turn off datawedge: I recommend removing or renaming \application\datawedge3.cpy to datawedge3.old or something like that. Cold boot the device.
Hope this helps.
Hi David - this is helpful. Thanks for taking the time to respond.
As far as installation - I only ever installed the persistent version. My question was more about why the RHO documentation says to make the config file changes in the temporary location and not the permanent location. I was curious to know why people would only want to make temporary config changes or only temporarily install RHO.
Re: turning off datawedge - is there also a registry setting that specifies start-up application? I suspect it would be here and this would be a cleaner way of disabling it at start up.
You are absolutely right, the documentation should be more general when describing the locations of the config file, perhaps we should reference "install directory" or something along those lines. Anyway, your point is noted and I have added it to the backlog to be looked at. I appreciate the feedback
Regarding datawedge, you can create a profile for RhoElements that will disable DW when RhoElements.exe is running. From memory, the UI is very intuitive but if you get stuck let me know and I will post some screen shots (don't have a device to hand or I would have done it now!).
Hope this helps,