Professional Documents
Culture Documents
users may understand how to more easily make their own modifications and adapt/
extend MioPocket. For specific help, such as with adding and removing programs a
nd icons, please see the Readme.
Folder Structure
================
Programs
\Games
\Win32
ktop computer
- All programs
- All games
- Programs to be run from a Windows (ex. XP/Vista/7) des
Registry
\480x272
80x272 displays
\CE4
E4 devices
\CE5
E5 devices
\Custom
\Exclude
rted
Scripts
- All scripts
Skin
s look
\MiniBar
\Pages
icons
\Scripts
elated to Icon Edit Mode)
System
iles here can be found
\CE4
\CE5
\FlashDrive
(i.e. won't work from
\WLAN
by
SD
-
Windows
\Administrative Tools
\Application Data
\Control Panel
\Desktop
\Favorites
\Fonts
m
\Root
)
\Startup
\Start Menu
ms
\Wallpaper
\Windows
indows folder
Installation Sequence
=====================
MioAutoRun.mscr/MioMap.mscr
|> Unlock.mscr
MioAutoRun.mscr/MioMap.mscr - Determines the type of installation (SD/SDFree/SDto-SDFree), displays any startup menus, then hands installation off to MioAutoRu
n\Scripts\Unlock.mscr.
Unlock.mscr - Installs MioPocket. Among other things, that includes importing re
gistry files, configuring the skin and setting <flashdisk>\MioAutoRun\Launch.exe
to run at startup via the HKLM\init registry key. Afterwards, the script resets
the device.
Startup Sequence
================
Launch.exe
|> Initialize.mscr
|> SysInfo-Start.mscr
|> StartupPrograms.mscr
Launch.exe - Runs at system startup (via the HKLM\init registry key) and launche
s Initialize.mscr (set in Launch.ini) once it is available (which can take a few
seconds if it's on SD card).
Initialize.mscr - Kills and/or minimizes OEM menus and other apps so that they d
on't interfere with MioPocket, then calls SysInfo-Start.mscr.
SysInfo-Start.mscr - Launches SystemInformation (the customizable graphical shel
l), then calls StartupPrograms.mscr.
StartupPrograms.mscr - Runs any other apps or services that need running, such a
s the MiniBar, the registry backup service or device-specific utilities.
Settings
========
MioPocket.ini - Stores MioPocket's settings. They may be modified here or via th
e MioPocket Settings menu in MioPocket. Most settings are also automatically ava
ilable for use in scripts as variables via Variables.mscr.
Variables.mscr - Determines and retrieves MioPocket's settings (some from MioPoc
ket.ini, others from the file system). Some describe paths (ex. "ProgramsFolder"
, so that one need not know whether it's \Storage Card\MioAutoRun\Programs or \S
DMMC\MioAutoRun\Programs) and others describe settings (ex. which skin is set or
whether the MiniBar is enabled). For speed reasons, variables are broken into g
eneral categories:
Variables_Common
- all common paths for MioPocket. Normally, this is all tha
t you need to call. Variables_Install
- less-used variables related to instal
lation. Includes Variables_Common.
Variables_Apps
- variables related to skins, apps and services. Includes V
ariables_Common.
Variables_Navigation - variables used for navigation software. Includes Variable
s_Common.
#[Icon01]
ICONXPBUTTON
x = 20
y = 60
NewIni = ..\..\Scripts\MioPocketSettings.mscr
SizeNormal = 48
SizePushed = 48
IconNormal = ..\Icons\MioPocketSettings.ico
ScaleAlpha = 80
IconPushed = ..\Icons\MioPocketSettings.ico
#EditIni = ..\Scripts\Icons\Favorites_Icon01.mscr
#[Icon01Text]
TEXT
x = 20
y = 110
Text = MP Settings
Color = FFFFFF
Size = 12
Weight = 500
CreateFont
Note #1: If the included scripts (in MioAutoRun\Skin\Scripts\Icons) don't match
all of the names that you've given your pages or if you have more icons per page
than there are scripts, simply copy and rename the scripts. They all have exact
ly the same code and are different only in filename. The Icon Manager simply use
s the filename to know which page and icon is being edited.
Note #2: It's important to add a "#[<section name>] line above any section that
comes after one of your IconXX or IconXXText sections, even if you don't intend
to edit it, since SystemInformation.exe will, otherwise, treat it as part of the
above section and give you unpredictable results when editing that icon. For ex
ample, if your page file flow goes like... #[Icon04] -> BATTERY -> #[Icon05] ...
add a "#[Battery]" (or any name) line above BATTERY to distinguish it from the i
cons and not allow its values to be confused for the 4th icon's.
Note #3: It's very important that a blank line separate each section, because th
e program will throw up errors, otherwise.
Note #4: You can use full/absolute paths if you prefer, but relative paths (usin
g ".." to indicate a file's parent folder) are easier and work regardless of the
drive name.
Once you have modified all of your pages in the above manner and have checked th
at all of the scripts that you declared on the NewIni lines exist in MioAutoRun\
Skin\Scripts\Icons, your skin ought to be ready to be used with the icon managem
ent system.
For those curious, here is how icon management works once the files have been se
t up:
When you press the "Edit Icons" button, IconManager.mscr reads the current page
file into memory, swaps the paths assigned to "EditIni" and "NewIni", writes the
modified file contents to a temporary edit file (ex. MioAutoRun\Skin\IconEditMo
de\Favorites.ini) and launches a second instance of SystemInformation (using the
temporary file) over top of the existing SystemInformation. This is called Icon
Edit Mode. Because the "NewIni" (i.e. run) commands now point to the icon scrip
ts, pressing the icons runs the scripts, which launches IconManager.mscr and pas
ses it the page and number of the icon to edit. IconManager.mscr then reads the
temporary edit file into memory, strips the "#" signs from in front of each occu
rrence of "[" (to create a valid, sectioned .ini file that MortScript can easily
work on) and "#EditIni", writes the modified file contents to a second temporar