Thankyou for this but windows is stopping me from accessing anythng at all it closes automatically when i load up startbar or explorer.exe any help is apreciated.

Danny

I don't understand what you mean?

im doing this on a xtrons unit with ce stuck in koreon. When i try to start any wondows apps the system resets. Also how do i show hidden files and drives? Thankyou for your quick reply... i built the primo for xtrons units now i want to try hacking them.... the main drive for the unit shows in control panel but not in my computer. I am sure that this is due to xtrons locking most of windows up also the on screen kbd wont load either i believe this is due to the ce lock up they have done.


EDIT the files are not hidden as such windows just will not show them still think this is down to xtrons

If you are using Explorer.exe on the device then to show hidden files go to...
View/Options Third tab from left/Sixth option down
And untick all the boxes...
Do not show hidden files and folders
Hide protected operating system files (Recommended)
Hide file extensions

If you are using Total Commander then go to...
Show/Hide files in ROM
Make sure it's not selected.

If you are browsing on your PC via ActiveSync/WMDC Then turn on show hidden files and folders in folder options.

The problem with some devices is that the manufacturer strips nearly everything from the Windows CE core except for what's needed for their programme, Meaning not a lot else runs, iGO (Primo) contains everything it needs in it's own directory.

Ok looks like im not gonna get into the other system then shame but kudos to your program i thinks its brilliant if it had 6 buttons id stop using oriongo all together and just use this to do everything brilliant work and thanks for the time you took to make it.

Or possibly windows CE is totally separate from the radio/dvd player.

Does run laggy though at times takes 5 seconds or so to make a decision

I will be uploading V1.4 shortly, It now has a button which scans a directory for exe files and displays then in a list so you can run more programmes, ie games, other nav apps, etc...

Testing it now.... well sdcard just i/o errord on me lol but i have a spare i will edit this post rather than post again.

Stand by.....

I just loaded your Universal Shell and have encountered a problem. Usually, the first app I select to run, runs OK, but after I exit that app the main screen no longer responds to touch inputs. Some times I can run two or three apps before this happens, but usually, it freezes after I exit the first application. Ideas?

I have no ideas but Universal Shell does not make any modifications to any original files or the registry, and there will only be one or two mortscripts in memory while an app is active which calls the main script which basically starts over. Let me know what device, OS, Memory? etc and i'll look in to it. Thanks.

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. 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. The Viewer, Speedo, and Player apps function normally, exit and allow other apps to be launched subsequently.

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. The Clocks, and keyboard are exceptions to this rule.

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

I haven't tried launching a Nav app.

Don't worry about my questons. I've lost interest.

I haven't been near a computer for a few days, Long boring work related story...

Hmmm, it seems that the device doesn't like applications, SystemInformation.exe and Mortscript.exe all running at the same time, The three big buttons, the image viewer and the media player close SystemInformation.exe and reload it when they're closed. The other apps (Which cause the freeze) just run over the top, I can't figure out why this is happening because i can't replicate the problem on any of my devices or under emulation. Could it be a memory issue? I've purposely not included code to adjust the memory division as i'm told it doesn't work properly on WinCE 4.2 and Windows CE defaults to about halfway. Are there any OEM shells still in memory? etc... Do any other unlock/shells work (xtyler92's universal sd unlock?)

The clock screen, settings and settings close button only move between screens within the SystemInformation environment, No Mortscripts are involved.
The Volume app closes by itself, That's how it is.

Version 1.5 is in it's final testing stage now. It has several new features and will be uploaded shortly...

xtyler92's universal sd unlock works. Miopocket 4.0 v68 works pretty well. I'll give 1.5 a try when it's posted.

I appreciate your feedback but i have no idea whar's wrong at this moment, Miopocket uses iphone today and rewrites a lot of the registry, so no help to me as i want to avoid all that, i'll have a look at xtyler92's unlock later, Every release is tested on several devices before posting, Some of them need a bit of persuading to get it to run properly. I'll post back later...

I've looked at xtyler92's unlock and it uses the same systeminformation environment as mine but it's run directly instead of being launched from a mortscript, (like mine) There are no device specific instructions within xtyler92's unlock itself, which is the same as mine, although in US RV1.5 i've removed an instruction from the startup script that potentially could cause problems, (although it hasn't done under testing)

I never designed Universal Shell to be an Universal Unlock because that would be impossible given the infinite variations of devices, and without turning into a miopocket clone, It's designed to be a easily configurable frontend or shell that's fast, light on system resources and works on the majority of devices without too much fuss. Some devices need extra commands to kill oem shells etc and these can be added to a separate file instead of the main script.