I have a series of questions that I'm compiling as I work to troubleshoot why my application isn't working properly. I would appreciate any information regarding the questions below.
- How much memory does the MK4000 have available for running RHoElement Applications?
- Why do all of the RHoElements documentation say to update \Program Files\RhoElements\Config\Config.xml when these changes are lost after a cold boot? Wouldn't most people want to put their changes in the application dir so the config changes aren't lost?
- The last line of logging I can get from Rho via the file-base logging before my app stops working is: MEMORY:
- Stats: Load=48% TotalPhy=82024KB FreePhy=42904KB TotalVM=32768KB FreeVM=0KB 0 2011-10-14 15:07:27
- What constitues a high load? What are TotalPhy, FreePhy, TotalVM, and FreeVM - which matter and which do not?
- When I profile my application using Chromes web dev tools, I'm seeing 3.3MB of memory usage. Given that I'm sure RHO adds onto this for scanner and other plugin functionality, is this a lot?
- In order to install RhoElements, I had to re-flash my machine in order to resolve a bunch of installation errors. Why was this? I can't be expected to reflash all of our devices every time we want to install new software.
- I was recently given a file called scanload.exe by Kevin Robarge (Moto Sr. Architect) that preloads the scanner dll on boot. Apparently there is an issue with the scanner on MK's and RHOElements and this is the only way to get the scanner to work in my app. Why isn't/wasn't this documented anywhere and why did I have to waste several days banging my head against the wall, only to find out that its actually a bug? Do you guys not QA your software on all devices before releasing them?
- How can I disabled DataWedge from startup when it isn't present in my startup directory?