Adsense Link 728 X 15;
Tampilkan postingan dengan label Tips And Trick. Tampilkan semua postingan
Tampilkan postingan dengan label Tips And Trick. Tampilkan semua postingan

Windows 3.1 on Symbian - Installation Guide S60v5

Posted by Dhani_phantom 31.8.09 4 comments
First Windows on Symbian S60 Device by Marcin-prv

DOWNLOAD dosbox_s60_20090504_full&slim_together.zip from attechment




DOWNLOAD Windows 3.1 (English) for Symbien:
http://rapidshare.com/files/207139919/win31en.rar.html
http://www.sendspace.pl/file/pUi8IxwM/

UPDATE

Using new version of DOSBox you can allocate up to 12MB RAM for Windows 3.1 on Nokia 95-1 or similar phones. Also you can disable standard Windows Shell (Program manager) and use only Calmira II.

1. Do all steps from instruction.
2. Edit 'e:\Data\dosbox.conf' file and change memsize=8 or more.
3. Edit 'e:\Data\dosbox.conf' file ane change end line to:

c:\windows\win.com /s

4. Edit 'e:\Data\Windows\system.ini' file to include:

;shell=progman.exe
shell=c:\Programs\Calmira\Calmira.exe


INSTALLATION GUIDE v1.2 (ENGLISH)


I. DOSBox v0.72 for Symbian by kolijoco (release 20090305)

1. Uninstall previous DOSBox versions.
2. Unpack 'DOSBox_s60.rar' archiwe to your Memory Card
3. Install ALL aplication from 'Install' directory.
4a. Install 'dosbox.sisx' on Nokia N95-2, N82 or similar (with 128 MB RAM).
4b. Install 'dosbox_slim.sisx' on Nokia N95-1 or similar (less RAM mamory).


II. Windows 3.1 for Symbian (included Norton Commander 5)

1. Unpack 'Win31en.rar' archive to your Memory Card.
2. Run installed DOSBox.


III. changes from release 1.0:

- Added MCGA (320x200) Driver
- Added Win32s v1.30c with OLE


IV. Suggestions

1. To change DOSBox allocated 2MB RAM edit line 'memsize=2' in file 'e:\Data\dosbox.conf'.
2. If your mobile phone have enough RAM memory you can install Sound Blaster 16 driver:
Control Panel -> Drivers -> Add -> Creative Lab Sound Blaster 1.5 -> Restart


V. Using T9 Keypad

Receive Call (Green) - Switching Mode
End Call (Red) - Exit from DOSBox
Pen Key - Shift
Delete (C) - Backspace
Thumb Pad - Arrow Keys, Enter
Right Key - Escape
Left Key - Space

Mode 1:

First line keys = a d g j m p t w space
First line keys + Pen =: A D G J M P T W space
Second line keys + * = b e h k n q u x .
Second line keys + * = Pen + * B E H K N Q U X
Third line keys + # = c f i l o r v y \
Third line keys + Pen + # = C F I L O R V Y |
Fourth line keys + 1 = s z
Fourth line keys + Pen + 1 = S Z

Mode 2:

Numbers = 1 2 3 4 5 6 7 8 9 0
Numbers + Pen = ! @ # $ % ^ & * ( )

Mode 3:

Thumb Pad - Moving mouse
* = Right mouse button
# = Left mouse button


Screenshot from first installation:







Official videoclip on YouTube:




DosBox S60 port by kolijoco - MS DOS EMULATOR-(Update :04.05.09)
Full & Slim version

hi all,
i've finally gotten my s60 (wincw emu for now) build to run - which has been done before -, and also to run a dos game (magic candle) - which i'm not so sure has been done.
anyway, if all goes well, there will be some updates and hopefully a sisx release soon...
here's a shot :-)
cheers!



ok, lets try this. here's something adventurous people might like to test drive.
not sure about system requirement, i would guess you need at least a 3rd edition s60 device, and having a minimum 320x240 (either orientation) display is probably a good start.
the release includes:
-my gcce release build,
-the s60 sdl binary release,
-nokia's openc redists (the redistribution license document is included, if you don't agree to the terms within, don't use them! from my limited understanding this should be ok, if not, let me know and i'll kill the post).
-example dosbox.conf and mapper.txt
-"detailed" :-) instructions in README.TXT
DO READ THE README.TXT !!!

i've also built a slim version...
those with memory issues should give this a try...
see the readme.txt for the specifics.
dependencies not included, download them for the first release (post on one of the previous pages).

Release Notes :


i built this release using the 3rd edition sdk, even though i tested the new touch-ui specific functions on the 5th edition sdk emulator build. i really don't know if these 3rd ed builds will work on a 5th ed device like the 5th emu builds did. i can (and will if necessary) release a 5th edition phone release build (though i wont be able tot test that build, for lack of hardware). so, 5800 owners, "feed-me-back", please!

DO I NEED THIS? ===============

if you are using a 5th ed touch-ui device (like the 5800), or have a higher than qvga resolution, then ABSOLUTELY! if your device is a 3rd ed qvga, you only need this if you want the rotate screen function, and/or want easy per-game input mapping (you know you do! :-) notes on scalers:

=================

using scalers other than none will probably have some negative impact on performance. there is probably no pointin using scalers on qvga devices. they're intended for upscaling to qhd (and similarly high) resolutions. don't bother with gl if your device is unaccelerated. notes on the virtual keyboard (for touch-ui):

=============================================

i could only test this on the 5th-ed sdk emulator. (you still haven't donated a 5800, or enough cash for me to buy one :-) that being said, consider the feature BETA. (don' hate if it don' work!) i really wish a dev with device access would join. you'll need to draw your own overlay bitmap and define your own keys. if you've been around, you'll get the hang of it... and earn the right to call yourself a POWER-USER (!!!) ;-)

Changes:

changes from release 20090305:

==============================

- s60mapper -previously 'premapper' - now implemented as 's60map.com' dos command (you can define mappings per game, and load them in the batch file you launch the game with)

- definition of virtual keyboards for touch-ui devices now possible in s60mapper see comments in provided 'virtkeybmap.txt' example for more information

- added various screen scaling engines (software, s60, opengl/gles) primarily intended for qhd (640x360) devices. see provided 'dosbox.conf' comments

- rotate screen 180 degree option added (or resurrected) by popular demand for n95/96ers!
Attached Files
File Type: zip dosbox_s60_20090504_full&slim_together.zip (1,011.5 KB, 67 views)

Speeding UPDATING THE GALLERY

Posted by Dhani_phantom 29.8.09 7 comments
Speeding UPDATING THE GALLERY

Copy the attached file (modified by me - obviously used the version for your model) in C: \ resource \ and reboot your phone. Copy the attached file (modified by me - obviously used the version for your model) in C: \ resource \ and reboot your phone. The gallery photos and seek video only in E: \ images and E: \ videos take so much less time to open, also there will be in the gallery pictures that have nothing to do, such as some programs The gallery photos and seek video only in E: \ images and E: \ videos take so much less time to open, there will also be in the gallery pictures that have nothing to do, such as those of some programs thumbs.gif
File Attachment MGXDatabaseplugin.zip (927byte) Number of downloads: 172 MGXDatabaseplugin.zip (927byte) Number of downloads: 172


EDIT: I added the path E: \ sounds \ simple \ because when you go to the usual manner to change the ringtone files that appear are searched using the same file. EDIT: I added the path E: \ sounds \ simple \ because when you go to the usual manner to change the ringtone files that appear are searched using the same file. Put simply, now when you browse the ringtones have only the files in E: \ sounds \ simple \ and all other MP3 E: \ sounds \, so the list is more orderly and easy to scroll:) Put simply, now when you browse the ringtones have only the files in E: \ sounds \ simple \ and all other MP3 E: \ sounds \, so the list is more orderly and easy to scroll:)

One user said that this amendment also limits the scope of the "search" (which I do not ever use it since so where are all my files One user said that this amendment also limits the scope of the "search" (which I do not ever use it since so where are all my files

In case the tunnel does not open more then delete the file. In case the tunnel does not open more then delete the file. If we do not get why it appears in use, reboot again and immediately delete it (will only be loaded when you open the gallery). If we do not get why it appears in use, reboot again and immediately delete it (will only be loaded when you open the gallery).

Tested on: Tested on:
- N95 8gb (my) - N95 8gb (my)
- N95-1 v30 (kork) - N95-1 v30 (kork)
- E66 (vito77_v) - E66 (vito77_v)
- N82 (kvolt, Zephir, alienpitti) - N82 (kvolt, Zephir, alienpitti)
- E65 (ominostanco) - E65 (ominostanco)
- N80 (vincy95) - N80 (vincy95)
- N73 (bisy88) - N73 (bisy88)
It seems working with almost all FP1. It seems working with almost all FP1. On N73 and N80 is the autorun patch c2z in or before starting the tunnel. On N73 and N80 is the autorun patch c2z in or before starting the tunnel.

For more smaliziato I will explain how I changed MGXDatabasePlugin.rsc and in particular how to increase the length of the strings without making it unreadable. For more smaliziato I will explain how I changed MGXDatabasePlugin.rsc and in particular how to increase the length of the strings without making it unreadable. First post two screenshots of x-plore that show the entire contents of the file in HEX mode (luckily it is very short and can be easily studied). First post screenshots of two x-plore that show the entire contents of the file in HEX mode (luckily it is very short and can be easily studied). For whom it is impractical to HEX editor and binary file structure,



I managed to interpret the file structure from the 0x1E byte at which the value 02, this indicates that there are two "blocks" in the file. I managed to interpret the file structure from the 0x1E byte at which the value 02, this indicates that there are two "blocks" in the file. The first begins immediately and ends with 0x1f to 0x82, the second starts at 0x83 and ends in 0x134. The first begins immediately and ends with 0x1f to 0x82, the second starts at 0x83 and ends in 0x134. What is before us 0x1E not want and should not be changed. What is before us 0x1E not want and should not be changed.
The value of the first byte of the first block that is 00, for successive blocks is 01. The value of the first byte of the first block that is 00, for successive blocks is 01.
Immediately after there is a string that could be called "principal" with respect to that block. Immediately after there is a string that could be called "principal" with respect to that block. The string is formed by two identical byte that indicates the length in bytes (I do not know why it is shown 2 times, we need only 1) and the characters real, for example, we have two 0x20 byte with a value of 8 and then the string " C: \ data \ "which has exactly 8 characters. The string is formed by two identical byte that indicates the length in bytes (I do not know why it is shown 2 times, we need only 1) and the real characters, for example, we have two 0x20 byte with a value of 8 and then the string "C: \ data \" which has exactly 8 characters.
The string is followed by a byte of value 03 (fixed), one representing the number of strings following secondary (4 in the first block and b, ie 11 in the second) and a value of 00 (fixed). The string is followed by a byte of value 03 (fixed), one representing the number of strings following secondary (4 in the first block and b, ie 11 in the second) and a value of 00 (fixed).
Followed, in each block, the strings would call "secondary". Followed, in each block, the strings would call "secondary". Each has the same structure of the field (two bytes in length, and then the characters). Each has the same structure of the field (two bytes in length, and then the characters).
A block ends with the last character of his last string secondary. A block ends with the last character of his last string secondary.

In summary we have: In summary we have:
- A 0x1E, a byte with a value of 2 indicates that 2 blocks - A 0x1E, a byte with a value of 2 indicates that 2 blocks
- From 0x82 to 0x1f first block - From 0x82 to 0x1f first block
* A byte 0x1f initial block (00) * A byte 0x1f initial block (00)
* 0x20 to the main string (2 bytes in length and 8 with the characters) * 0x20 to the main string (2 bytes in length and 8 with the characters)
* A 0x2a byte 3, the second of which indicates that we have 4 strings secondary A * 0x2a byte 3, the second of which indicates that we have 4 strings Secondary
* A 0x2d, 0x44, 0x5b, 0x70 Secondary 4 strings, each consisting of 2 bytes with the length and then their characters, and a 01 byte between both of them * A 0x2d, 0x44, 0x5b, 0x70 Secondary 4 strings, each consisting of 2 bytes with the length and then their characters, and a 01 byte between both of them
- From 0x83 to 0x134, the second block - From 0x83 to 0x134, the second block
* A byte 0x83 to the initial block (01) * A byte 0x83 to the initial block (01)
* 0x84 to the main string (2 bytes in length and 3 with the characters) * 0x84 to the main string (2 bytes in length and 3 with the characters)
* To 0x89 3 bytes, the second of which indicates that we have 11 strings Secondary * To 0x89 3 bytes, the second of which indicates that we have 11 sub-strings
* 11 Secondary strings (not let me write all the addresses!), Each consisting of 2 bytes with the length and then their characters, and a 01 byte between both of them * 11 Secondary strings (not let me write all the addresses!), each consisting of 2 bytes with the length and then their characters, and a 01 byte between both of them

In this way until we arrive at byte 0x134. In this way until we arrive at byte 0x134. Of the remaining six will affect only the last 2 which indicate the size of the file in bytes, excluding the last 6. Of the remaining six will affect only the last 2 which indicate the size of the file in bytes, excluding the last 6. It should read first the last and then the penultimate: 01 35 (in fact, with the blocks, we arrived just 0x134 starting to count from 0, and then make 0x135 bytes It should read first the last and then the penultimate: 01 35 (in fact , with the blocks, we arrived just 0x134 starting to count from 0, and then make 0x135 bytes thumbs.gif))

In this particular file, the strings that I called "mainstream" are the folders to search for media files, while the "secondary" folders are excluded. In this particular file, the strings that I called "mainstream" are the folders to search for media files, while the "secondary" folders are excluded.

To change a string any of this file, you need: To change a string any of this file, you must:
- Change 1 to 1 overwriting the existing characters, and without adding or removing bytes in this stage - Change 1 to 1 overwriting the existing characters, and without adding or removing bytes in this stage
- Add bytes (use them) or remove the excess (if any). - Add bytes (use them) or remove the excess (if any). To do this you must activate the "insertion mode" in x-plore To do this you must activate the "insertion mode" in x-plore
- Disable the "insert mode" and change the value of 2 bytes that precede the characters with the new length of string - Disable the "insert mode" and change the value of 2 bytes that precede the characters with the new length of the string
- Change the value of the final two bytes by adding or subtracting the number of characters that were added or removed. - Change the value of the final two bytes by adding or subtracting the number of characters that were added or removed. if they are few, as in this case, you act only on the last byte if they are few, as in this case, you act only on the last byte

In this way, I changed "C: \ data \" to "E: \ images \" and "E: \ 'to' E: \ videos \", and this is what we needed for the tunnel In this way, I changed "C: \ data \" to "E: \ images \" and "E: \ 'to' E: \ videos \", and this is what we needed for the gallery thumbs.gif

Wanting to add another block (in this case would be another folder in which to search) you must: Wanting to add another block (in this case would be another folder in which to search) you must:
- Increase by 1 the value of the byte 0x1E - Increase by 1 the value of the byte 0x1E
- Add the new block immediately after the second, respecting the structure of the other 2 - Add the new block immediately after the second, respecting the structure of the other 2
- Update the data on the size in the last 2 bytes - Update the data on the size in the last 2 bytes

I am * almost * sure of what I wrote, but if you want to try to do so at your own risk I am * almost * sure of what I wrote, but if you want to try to do so at your own risk angel.png . . This file is not of vital importance for the functioning of the phone, then you can use for testing. This file is not of vital importance for the functioning of the phone, then you can use for testing. There are some that it is better not to touch it until we know more There are some that it is better not to touch it until we know more

this guid is by ALEX N70

SmartSIS v.2.2.7 Translated By Nima79

Posted by Dhani_phantom 25.8.09 0 comments
SmartSIS v.2.2.7 Translated By Nima79




Changelog:
- Still have all the features of 2.2.5;
- You can now collect packages for veterans' axes.
- Possible to change the uid files _reg.rsc
- Removed a lot of bugs and departures
- Improved file manager

Note:Need python 1.4.5 and megapymodul



will Move To Py section soon ...
Attached Files
File Type: rar SmartSIS v.2.2.7 Translated By Nima79.rar (195.9 KB, 10 views)

SmartSis 2.2.7 [EN]

Posted by Dhani_phantom 0 comments






Still have all the features of 2.2.5;
- You can now collect packages for veterans' axes.
- Possible to change the uid files _reg.rsc
- Removed a lot of bugs and departures
- Improved file manager

Note:

Need python 1.4.5 and megapymodule
Attached Files
File Type: zip SmartSIS v2.2.7 [EN].zip (194.1 KB, 3 views)