Switch to full style
Post a reply

Sun May 29, 2011 4:29 am

Hi Fatboyfun
I have tried your V1.4 and had to add the Kill command as you suggested so the main menu didn't overwrite the universal menu. Now I can access all functions without the main screen coming up, but when I try to go back from a program such as speedo to the main universal shell menu I get the following error message:
Windows 'A square is displayed' could not be found
Line 12 (\SDMMC\Universal shell\Start.mscr): minimize (activewin)
The only way I can get out of it is to reset my GPS.
Slowly getting there.
gordonwh40

Sun May 29, 2011 8:38 am

"A square is displayed"? What an odd error message lol, The minimize line has been removed from V1.5 because i found a better way to do it, which i'll post later, I'm just tweaking it at the moment.

Mon May 30, 2011 5:29 am

Hi
Fatboyfun
As I couldn't display a small square I said what was displayed. I know it sounded weird to me when I read it, but I hoped it was clear enough. Thank you for your reply.
gordonwh40

Mon May 30, 2011 8:31 am

Ahhh i get you now, US had a command to minimize any system windows when launched but it seems this command sometimes fails with certain device shells but in the new version it's been removed completely, so hopefully problem solved.

Mon May 30, 2011 9:14 pm

FYI, I experienced exactly the same behavior with 1.5 as I did with 1.4. The shell freezes when exiting most of the applications. I set up Primo as the Nav app, and the shell freezes when exiting Primo also. I'm not asking you to fix it, but I thought you might want to know that the problem still exists.

Sounds similar to what gordonwh40 described, but without the square and the error message.

Mon May 30, 2011 9:52 pm

I've never experienced this problem...

Does it freeze before or after the main Universal Shell screen and sound effect is shown/heard? Does it make a difference if the sound effect is disabled?

With the buttons that close the SystemInformation environment (Using QuitOnExecute = yes, within the SystemInformation .ini), there is at least one Mortscript paused in memory (Using a RunWait command) that reloads the SystemInformation application then exits.

The text below is what happens step by step when US is loaded...

Start device

(MobileNavigator.exe loads Start.exe(.mscr) if applicable)

Load Start.mscr
Start.mscr checks for the config file to see if this is a new installation, it is not so...
Start.mscr checks whether this is the first run after a reboot by looking for the VolumeX.exe process, The process IS NOT running so...
Start.mscr copies/creates the files it needs
Start.mscr loads process VolumeX.exe (Does not open a window)
Start.mscr loads SystemInformation.exe
Start.mscr plays the startup sound if set
Start.mscr exits
SystemInformation waits for user input...

*User selects application*

Load *.mscr for selected button
SystemInformation.exe exits itself
*.mscr loads selected application
*.mscr waits for application to close...

*User exits application*

*.mscr runs Start.mscr
*.mscr exits
Start.mscr checks for the config file to see if this is a new installation, it is not so...
Start.mscr checks whether this is the first run after a reboot by looking for the VolumeX.exe process, The process IS running so...
Start.mscr DOES NOT copy/create the files it needs as they are already there
Start.mscr loads SystemInformation.exe
Start.mscr plays the startup sound if set
Start.mscr exits
SystemInformation.exe waits for user input...

Can you pinpoint where the problem occurs?

Thanks again for your feedback...

Tue May 31, 2011 1:31 pm

The universal shell loads without problem. It goes through the entire setup procedure without a problem. Upon restart, the shell loads, the sound plays, and everything seems OK.

The following is from my previous post about the same topic. It contains information that I thought may help you isolate the problem.

It's an Insignia NS-NAV01, with 64mb and WinCE 5.0. I have listed some observations below, that may help you isolate the problem to a particular routine.

I can alternately run the Talking clock and the Digital clock over and over again. If I run Settings, I can exit and run another app, as long as I don't press any of the settings buttons. If I press any of the settings buttons, the Settings Close button will not function(the settings app is now inoperative). If I open the Settings, and immediately use the Close Settings Button, the Clock Buttons will function repeatedly. The volume Icon functions, but will not close. The Clocks will function, after the Volume button has been pressed. The keyboard will open and close, and the clocks will still function. The Fileman, Control panel, Calculator, Notepad, and "Run App" will open and close, but the device freezes after the apps close(and leaves the app screen displayed). The Viewer, Speedo, and Player apps function normally, exit and allow other apps to be launched subsequently.

[color="red"]One observation, that may be helpful, is that the apps that cause the freeze, exit abruptly, while those apps that exit and allow subsequent operations, exit with the screen animation, and dramatic sound. [/color]The Clocks, and keyboard are exceptions to this rule.

The X button, does nothing, except causing the device to freeze.


The nav app I'm using (Primo) exits, and freezes with the Primo bmp displayed.

Once an application is loaded it seems to function normally, the problem occurs when I try to exit the application, then the app hangs with the app screen displayed and requires a reset or power off to get out of that condition. The "player" plays mp3s, will complete a benchmark from the file menu, but hangs upon pressing the exit button.

I am willing to collect more info if you wish.

Tue May 31, 2011 5:53 pm

I have an idea what's happening, I reckon the device may have some sort of memory management that is closing apps in the background, Like Windows Mobile does, Maybe i need to use setsystemmemorydivision.exe?

Are you able to find out what Windows reports the total/free memory as? Also did you have to kill some processes like the original shell?

It sounds like the mortscripts and systeminformation.exe are being closed in the background when an app is launched. This can give the appearance of freezing because on some devices there is no desktop screen to fall back to when all the apps are closed, and the last image displayed stays on screen but the app has closed, One of my "MobileNavigator" devices is like this and when i exit an app the app stays on screen and the US screen rolls down over the top.

So far this is the only device that i've been told about with this problem, But i appreciate any help you can give...

Tue May 31, 2011 6:39 pm

I did not have to kill any processes. If I launch resinfo via cecmd, after loading the US, resinfo shows 37.9mb of free memory. I can exit resinfo successfully, and then use cecmd to browse. If I exit cecmd at this point, it seems to close successfully, and the US main screen becomes available, but nothing responds to touch.

Tue May 31, 2011 6:47 pm

I'm going to take another look at xtyler92's sd unlock, but CECMD does not close systeminformation.exe and it's possible to minimize it and select another application, But i'll be honest and say i have no idea what's causing it at this time??? Have you tried any other unlocks that i can have a look at?

Tue May 31, 2011 7:58 pm

Fatboyfun wrote: Have you tried any other unlocks that i can have a look at?


Just xtyler's and MioPocket 4 release 68. Is there an unlock that you would like me to try, that doesn't mess with the registry?

Tue May 31, 2011 8:12 pm

Nothing specific, i just wondered. Over the next few days i'll produce some modified files that you could try, Maybe using the "While (ProcExists)" command instead of the "RunWait" command, And maybe not closing systeminformation.exe, I'll get back to you...

Tue May 31, 2011 9:13 pm

Glad to help. Let me know what I can do.

Tue May 31, 2011 10:49 pm

Hi
I am not having any problems with V1.5. I can open apps and close back to universal menu.
The two things I have done on all earlier versions I have had to do on this version.
1 I still have to use the kill command to kill the main menu.
2. During setup I call the main menu when exiting rather than leaving the exit command empty.
Now works very well for me.
Thank you.
gordonwh40

Wed Jun 01, 2011 7:28 am

Have you tried the new hourly chime/auto power off features?
Post a reply