Related
Hi,
I hope I'll have some time during the holidays to update ER2003Edit. Planned features/changes are:
:arrow: Support for Blue Angel and Magician (different header, different ROM image location
:arrow: Do not depend on ROM type selection in Open dialog
:arrow: Auto-Generate the config file for the extended ROM
:arrow: Automatically detect the type of the connected device and set the appropriate header options in order to prevent the country ID error
:arrow: Asscociate .nbf files with ER2003Edit in order to open them in ER2003Edit directly from Explorer
:arrow: Fix the "ActiveX component can't create object" error under WindowsXP
Please post if you have more suggestions. The focus here lies on helpful features that are _easy_ to implement (i.e. in a short amount of time).
I need some help with the following issues, can anybody help?
:?: Accessing the OS ROM. What kind of file system is this, any way to access it
:?: Automatic Password detection: Does anyone have some code to accomplish this, would save me some time..
Best,
This would be great.
does this include changing the "new country id" as stated in step 9 of DCS's post ?
dcs said:
Run the hex editor and in that open the file ms_.nba. At offset 74 (0x4A) you will see the operator string your device will be set to and at offset 94 (0x5E) you will see the language string your device will be set to
Click to expand...
Click to collapse
I think this "new country id" is a nice discovery by dcs, but there are only rare cases when you really need it. (like the incorrectly authored ROM, dcs had to deal with)
Normally when you want to update your device to a "foreign" ROM, you use ER2003Edit or xda2nbftool to change the headers. Once installed your device's id will be (in nearly all cases) set to the id of the ROM you install. Thus you will be able to do subsequent upgrades of the same brand and language.
Changing the "new country id" would only make sense if you already know during installation what your next update will be and you know that you are unable or unwiling to use ER2003Edit then (and only when changing brand and country).
Technically it wouldn't be hard to implement but could bring trouble if the location/offset would change. Though I think very few people will really need it, I will consider this for inclusion into ER2003Edit.
...any other suggestions...?
Those features will still be there ?
-Extract and modify the splash bitmaps
-Completely modify the contents (=extract, delete, import, rename) via Drag'n'Drop
Would it be also possible to make rom backup ? and Restore ?
Anyway thank you for trying to make your soft BlueAngel friendly ! I was waiting for this since I get my 9090 !!!
Best regards and Merry XMas !
Softworkz
Hope everything is going well with the alterations to the ER2003Edit.......
How is it coming along - anything we can help with over in the BlueAngel Forums?
Someone please help me on getting the blackberry connect to work.
aih1977 said:
Someone please help me on getting the blackberry connect to work.
Click to expand...
Click to collapse
you need to hex edit the build number to get it to work...
how do i know what hex to do. i found old trends but it didnt work can you please explain to me how or what to do thanks
got it...at first glance thought there was a bbconnect 3.30.0.9 version...No it is lvsw rom version...
aih1977 said:
how do i know what hex to do. i found old trends but it didnt work can you please explain to me how or what to do thanks
Click to expand...
Click to collapse
A good place to start if you are serious about it - this thread. I can't afford to do this myself, as I need my phone 24x7.
moisha said:
A good place to start if you are serious about it - this thread. I can't afford to do this myself, as I need my phone 24x7.
Click to expand...
Click to collapse
I went there and it is no help. I need to do this ASAP so one please tell me what hex to edit in detail because i am not to talent in programing thanks
aih1977 said:
I went there and it is no help. I need to do this ASAP so one please tell me what hex to edit in detail because i am not to talent in programing thanks
Click to expand...
Click to collapse
You need to use nbhextract to get the OS.nb file from the nbh... then open the OS.nb file in a HEX editor... Search for the appropriate version string and change it in HEX....
ok this is how to do this.
you need to first extract the kernel from the OS.nb
The kernel is in the XIP section, not IMGFS of the rom.
To obtain the XIP section, use rommaster.exe and dumpromx.exe
once you have obtained coredll.dll (the kernel) then Open that up with a HEX editor and search for the current KERNEL (CE) number.
Onc eyou have obtained the current CE number you then have to replace that HEX string with the 5.1.195 HEX string by editing the OS.nb.
Done.
P.S: dont ask me for the 5.2.1236 HEX string as I dont know it, my roms are based on a newer kernel than those in custel and LVSW's roms.
walshieau said:
You need to use nbhextract to get the OS.nb file from the nbh... then open the OS.nb file in a HEX editor... Search for the appropriate version string and change it in HEX....
Click to expand...
Click to collapse
how do i find the string and what do i change too
jasjamming said:
ok this is how to do this.
you need to first extract the kernel from the OS.nb
The kernel is in the XIP section, not IMGFS of the rom.
To obtain the XIP section, use rommaster.exe and dumpromx.exe
once you have obtained coredll.dll (the kernel) then Open that up with a HEX editor and search for the current KERNEL (CE) number.
Onc eyou have obtained the current CE number you then have to replace that HEX string with the 5.1.195 HEX string by editing the OS.nb.
Done.
P.S: dont ask me for the 5.2.1236 HEX string as I dont know it, my roms are based on a newer kernel than those in custel and LVSW's roms.
Click to expand...
Click to collapse
i am using hexedit and sorry for being litte confused but how do i do all that.
jj i would like to use your rom which works with BB but for some reason my power button stops working and i have to reset all the time and i dont want to bother you.
I used black 2.0 work good with bbc 2.1 and bbc 4.0 that is the best for my.
I'm not use black 3.01 because I have problems with my BT ( parrot ck3100) I am waiting for the new version with new drivers to BT.
Another Rom I liked is XDA 0.20, also work good with BBC, anybody know more ROMS work wiht BBC, I think the new ROMS only work good with BBC is Black 2.0, 3.0,3.01. Thanks.
jasjamming said:
ok this is how to do this.
you need to first extract the kernel from the OS.nb
The kernel is in the XIP section, not IMGFS of the rom.
To obtain the XIP section, use rommaster.exe and dumpromx.exe
once you have obtained coredll.dll (the kernel) then Open that up with a HEX editor and search for the current KERNEL (CE) number.
Onc eyou have obtained the current CE number you then have to replace that HEX string with the 5.1.195 HEX string by editing the OS.nb.
P.S: dont ask me for the 5.2.1236 HEX string as I dont know it, my roms are based on a newer kernel than those in custel and LVSW's roms.
Click to expand...
Click to collapse
And finally the last question "How do I know what to search for, before I can replace it ?" was answered in the original thread I mentioned above, in this post - trace the GetVersionEx function.
i am in hexedit and i can not find the hex please tell me what hex to find so i can change it
aih1977 said:
i am in hexedit and i can not find the hex please tell me what hex to find so i can change it
Click to expand...
Click to collapse
I think you better wait for someone else will do this.
Black 3.5 is coming up within next few days and JJ is searching for the string night and day as we speak. Right JJ ? And then again, even thought lvsw and Sleuth255 refused to disassemble for one reason or another, I see other people on this forum, who have SDK and IDA as wallpaper and speak assembler natively, have added this task to their TODO list.
Besides, HTC shall release an official version veeeery soon.
thanks for everything sorry to bother you guys i thought it was easy to do but i am not to talented in this type of things. so i thank you all who tried to help.
aih1977 said:
thanks for everything sorry to bother you guys i thought it was easy to do but i am not to talented in this type of things. so i thank you all who tried to help.
Click to expand...
Click to collapse
Not a problem. Thanks to you we actually have put together a nice summary ... almost a WIKI page on this subject
Hi Cooks! I need some help from you :-D
I want to know my data secure and possible stolen hardware findable/trackable. And all this WITHOUT changing daily workflows!
My idea is a special "SecureROM" which should contain additional to normal ROMS:
o callFirewall (with Autostart)
o remoteProtect (ATTENTION: individual CAB!!)
The idea is to put remoteProtect (i think its much better than UTA V3 and friends) directly into the ROM. So a thief cant simply hardreset the device (and cancel Ext-Rom installations) and we have the first real secure PDAphone:
o PIN Code for logon activated (5mins idle)
o Storage Card encryption on
o remoteProtect installed
o Bonus: Callfirewall for blocking anonymous phone calls
When the device is lost / stolen - the thief (finder) has the possibility to give it back: Your name / 2nd phonenumber is on the PIN-Loginscreen AND on the remoteProtect lock-screen.
If he DOESNT want to give it back - you can remotely lock, wipe and kill the device.
If you dont know where the device is - you can get information about inserted SIM, IMEI, IMSI (police-tracking) and battery status.
If the thief chances Ownername or SIM - you will be notified and can react.
The thief cant bypass the PIN to get into WM6. He cant pull out the storagecard and get it into a cardreader... because all files there are encrypted with AES. If he softresets - he is still locked. A hardreset will make all informations gone - even those on storagecard - and with remoteProtect in the ROM he will STILL be trackable!!
SO: With this configuration you can feel your data on your device pretty protected... and even your hardware keeps trackable with one exception: When the thiefs flashes an own ROM.
So if you like this idea dear Chefs - could you give it a try and find out how to implement remoteProtect into your ROMS?
PROBLEM: For this issue, you would have to add the possibility to add an individual cab (which is configured and built by the remoteProtect installer BEFORE COOKING) right before flashing. (here is remoteProtect for testing purposes: http://www.scpsoft.com/remoteprotect.htm [Attention MODs: This is NOT a WAREZlink!])
HINT: If using UTA (second best solution) instead of remoteProtect you will have to insert two configfiles (1 XML and 1 txt - File) individually before flashing.
licht77 said:
Hi Cooks! I need some help from you :-D
I want to know my data secure and possible stolen hardware findable/trackable. And all this WITHOUT changing daily workflows!
My idea is a special "SecureROM" which should contain additional to normal ROMS:
o callFirewall (with Autostart)
o remoteProtect (ATTENTION: individual CAB!!)
The idea is to put remoteProtect (i think its much better than UTA V3 and friends) directly into the ROM. So a thief cant simply hardreset the device (and cancel Ext-Rom installations) and we have the first real secure PDAphone:
o PIN Code for logon activated (5mins idle)
o Storage Card encryption on
o remoteProtect installed
o Bonus: Callfirewall for blocking anonymous phone calls
When the device is lost / stolen - the thief (finder) has the possibility to give it back: Your name / 2nd phonenumber is on the PIN-Loginscreen AND on the remoteProtect lock-screen.
If he DOESNT want to give it back - you can remotely lock, wipe and kill the device.
If you dont know where the device is - you can get information about inserted SIM, IMEI, IMSI (police-tracking) and battery status.
If the thief chances Ownername or SIM - you will be notified and can react.
The thief cant bypass the PIN to get into WM6. He cant pull out the storagecard and get it into a cardreader... because all files there are encrypted with AES. If he softresets - he is still locked. A hardreset will make all informations gone - even those on storagecard - and with remoteProtect in the ROM he will STILL be trackable!!
SO: With this configuration you can feel your data on your device pretty protected... and even your hardware keeps trackable with one exception: When the thiefs flashes an own ROM.
So if you like this idea dear Chefs - could you give it a try and find out how to implement remoteProtect into your ROMS?
PROBLEM: For this issue, you would have to add the possibility to add an individual cab (which is configured and built by the remoteProtect installer BEFORE COOKING) right before flashing. (here is remoteProtect for testing purposes: LINK REMOVED
HINT: If using UTA (second best solution) instead of remoteProtect you will have to insert two configfiles (1 XML and 1 txt - File) individually before flashing.
Click to expand...
Click to collapse
Paranoid much ?
Probably an IMO for the US Govt somewhere. They are worse than Nazis. That is why I ditched my issued blackberry for my Hermes.
Well, I think that this is not much paranoid.
I spent for my PDA over 700 euros, so if it is stolen it isn't very good!!! ;-)
For this reason, I bought a legal copy of UTA (Ultimate Theft Alert v.3) and I updated my Schap's 3.30c ROM with all necessary files from the original "UTA v3.CAB" (no Config, only program, dll, and configuration and license files...).
It seems to run very well!!!
Today, after reading this thread, I tried remoteProtect, but I don't like it so much, because if I send a SMS to my PDA, then the theft will see it and can go to flight mode.
If you want to do the ROM upgrade, you must choose your preferred ROM. After, I suggest the "CorePRO_HermKitchen.exe", that contains all the tools you need, with a tutorial about dumping and cooking your ROM.
If you need help, I'm here!
Bye Bye.
I think it's a good idea - I used to work in the Netherlands and on an emergency trip home one weekend, my phone was stolen by someone after my luggage was checked in at Schipol (it was the first HTC Canary smartphone, actually ) Anyway, I didn't notice that it was missing until I got back to NL 4 days later as I thought I'd just missed it in my rushed packing, but in that time, the thieving toerag had run up a £650 phone bill (it was stolen in NL and I got stiffed for roaming charges too
So anyway, I'd be interested too
Smiffy.
@NRGZ28: Yes - I am really paranoid... - this comes with the job
But as Mobilez6600 states correctly - its a question of hardware value too...
@Mobilez6600: Ill have a look into CorePRO_HermKitchen.exe - all I played around so far was Bepes Kitchen... there was no howto and i just cooked a german ROM - i think i was just lucky
Ill give it a try - but if there is a tutorial anywhere i would be glad!
greetz, licht
PS: On my installation the thief cant see the incoming sms... ?
Speaking of thiefs...the link in the OP is to a known warez site. XDA Developers does not tolerate warez!
JasenR said:
Speaking of thiefs...the link in the OP is to a known warez site. XDA Developers does not tolerate warez![/QUOTE
Dont get your panties in a bunch...
Click to expand...
Click to collapse
NRGZ28 said:
Dont get your panties in a bunch...
Click to expand...
Click to collapse
Thanks NRGZ28, I guess, for your concern about my comfort, everything is fine in that department.
Even more thanks to the mods for their continuous efforts in keeping this site warez free.
@Mobilez6600: Thx for your informations!
I read into Core Kitchen, dumped my preferred rum (Schaps 3.30c german) and created a package out of the desired cab according to theese snippets from the forum:
I don't know if the new Office will work on other builds....
Sorry i can't be more specific...but i didn't tried it so far. So i can't tell you what files to copy or if it will work.
Just try and if you get it working...then you could share that with us too.
I am in the middle of something now and can't try this now....Hope you understand.
Regarding on How to make a package....
* Take a CAB
* Open it with CabAnaliser ...in Extra folder
* Select the XML tab...there save the registry settings in an unicode txt file.
* Extract all files
* Place all files in an folder , and add there an .dsm and rename the previous txt file in .rgu ....assign both the .dsm and the .rgu an UUID (both same UUID)
* Run the initflashfile generator...in Extra folder. Follow instructions...
* Place the generated "initflashfiles.txt" in the same folder you placed previous files
* Give a friendly name to your folder , move it into the OEM folder and pray it will work.
That's it. If you read previous posts you'll know what an .dsm is and how to make one and what is an UUID and where to get it from.
- TIP : If that doesn't work, open the initflashfiles.txt and replace all the "squares" with an tap on ENTER button....It's easy to check the initflashfiles.txt than to create it without that program, trust me.
to create a .dsm
* Create a new empty .txt document
* Go here http://www.famkruithof.net/uuid/uuidgen/ and create a "RANDOM" UUID (example of UUID :2981dd18-0f2c-11dc-8314-0800200c9a66)
* Rename the *.txt into 2981dd18-0f2c-11dc-8314-0800200c9a66.dsm (the UUID is only for example, create your own)
* If you have registry settings, use THE SAME UUID ...so for example rename the *.reg file into : 2981dd18-0f2c-11dc-8314-0800200c9a66.rgu
Click to expand...
Click to collapse
So far - so good. Additionally, a single txt file needs to be copied into rootfolder of the device before installing my custom cab... i put it into rootfolder of the cab for testing.
Unfortunately i get an error during build_os: "Could not find file d:\core\kitchen\temp\dump\Program Files\imageinfo.bin" when build_os is processing my created folder in OEM.
Any advice is highly appreciated...
There is a .DOC tutorial about dumping and re-creating ROM in CorePro_HermKitchen. I used it and I only inserted my files in a folder. After, I modified "initflashfiles.dat", to copy a link in \Windows\StartUp directory, so UTA could run automatically on soft-reset (and hard-reset ;-).
I don't know if it is right way, but it runs, and I'm happy!
Sorry for my late answer, i was - ehm unavaliable - some days.
You are talking about initflashfile.txt and not .dat right?
I still get this error, but i will keep working on it
Quoting from http://forum.xda-developers.com/showthread.php?p=1373052#post1373052 to keep that thread on topic:
PAPPL said:
See this great theft protection Peter Poelman made here at xda-devs!
THIS WOULD BE GREAT!
IIWPO WIKI
IIWPO Thread
Click to expand...
Click to collapse
I tested that tool and found it great too - but it has no SIM detection. Another con is that its in extended ROM which can be easily bypassed by canceling the installation after a hardreset.
After excessive tests with all those tools i have this personal ranking:
1. remoteProtect (commercial, Trial avaliable) pro: a lot of useful commands executeable via SMS, device completely killable, recognizes SIM card change (supports 2 SIMs) as well as owner name changes. Needs 1 txt file as config in the rootfolder during installation when included into a ROM.
2. UTA v3 (commercial Trial avaliable) Recognizes SIM change (supports several SIMs), sends SMS. No SMS commands possible. Optionally (commerical plugin) sends contactlist too. Needs 2 individual files included in ROM.
3. IIWPO (free, xda-dev)
Recognizes change of owner name. Needs 1 individual file included in ROM. No SMS commands possible, no recognation of SIM change.
What prevents a reflash with different rom?
nothing i am afraid... as there is no lockable bootloader
But i think its much easier for a thief to hardreset than to flash... the "flashers" are rather an exception i hope.
If you have any idea to lock the device with the bootloader - tell me
licht77 said:
nothing i am afraid... as there is no lockable bootloader
But i think its much easier for a thief to hardreset than to flash... the "flashers" are rather an exception i hope.
If you have any idea to lock the device with the bootloader - tell me
Click to expand...
Click to collapse
im sure if you had a quick talk to Olipro about the bootloader... he might be able to help you out with a BL that wont allow you to flash without a special CID...
licht77 said:
Quoting from http://forum.xda-developers.com/showthread.php?p=1373052#post1373052 to keep that thread on topic:
I tested that tool and found it great too - but it has no SIM detection. Another con is that its in extended ROM which can be easily bypassed by canceling the installation after a hardreset.
After excessive tests with all those tools i have this personal ranking:
1. remoteProtect (commercial, Trial avaliable) pro: a lot of useful commands executeable via SMS, device completely killable, recognizes SIM card change (supports 2 SIMs) as well as owner name changes. Needs 1 txt file as config in the rootfolder during installation when included into a ROM.
.....
Click to expand...
Click to collapse
@licht77: remotePROTECT is great. But how to install the 1txt file in root folder? Will this survive a hardreset?
Hi Pappl!
Yes, it should survive a hardreset... thats why i dont want to put it into extRom (because the installation of all the extRom - stuff can be cancelled too easy by a hardreset followed by a softreset after screen calibration) but in ROM itself.
This way you have a) your data pretty secure and b) may track down a possible thief. The only thing a (skilled) thief could do is to completely reflash the device (but if he is curious before and tries to access your data with his SIM or so... hehe then u got him)
Like walshieau proposed, it should be possible even to block a complete reflash of the device by a custom booloader - but i dont want to nag olipro before the other tasks are finnished. In that case a stolen hermes is really useless for the thief... and thats a nice idea if this could prevent theft
remotePROTECT can be installed without that text file to the root folder, you just need to set it up first, and extract the setupE.txt file from it's running folder then rebuild it into that folder from the cab file.
I however would like to do this without the cab, cab's can be prevented from running by simply softresetting during that phase of the setup. I have built all the files into one of my roms and put in all the registry entries however the application does not work this way! Setup.dll seems to do some important things and I'm not sure what.
Anyone have any ideas? I'm gonna email the author asking.
You are right... didnt see that encrypted "setupE" file...
Which kitchen are u using? What were the steps u did until now? I am sure we can solve this!
Hi everyone,
I'm wondering about the differences between these files, since they are both used to modify registry. Well PROVXML files seems to be more powerful with file management.
Which one is better to use ?
Quick:
provxml is not only for change registry.
For file operations too.
And .provxml writes in the registry after .rgu, so if you want to change something for sure, you should use .provxml
maxstegi said:
And .provxml writes in the registry after .rgu, so if you want to change something for sure, you should use .provxml
Click to expand...
Click to collapse
Wow this is a very good point you mentionned here ... i did not know in which order the information is written into the registry. Thank you man !
But what about the order these files are dumped into the final registry ... Is it by package name ?
For example, i have in my cooking OEM:
- PACKAGE_Diamond_A
----mxipupdate_A.provxml
- PACKAGE_Diamond_B
----mxipupdate_B.provxml
What will be the result if these two packages write at the same location different value?
Will the value be the A one or B one ?
Saw something like: *_100.provxml, *_200.provxml ...
Hello
I'm cooking my own rom and I've one small irritating problem. I've set rom version as: 1.0. In device information it shows properly, but when my pda is starting, on first splash screen it shows me that rom version is: 3.0. I know it is somewhere in nk.exe but I've problem to locate it...
Best regards
tomme45i
tomme45i said:
Hello
I'm cooking my own rom and I've one small irritating problem. I've set rom version as: 1.0. In device information it shows properly, but when my pda is starting, on first splash screen it shows me that rom version is: 3.0. I know it is somewhere in nk.exe but I've problem to locate it...
Best regards
tomme45i
Click to expand...
Click to collapse
You can do that from the kitchen. I know ervius kitchen has two dialog boxes on the left, sort of middle of the screen, where you can set ROM date and version. It will patch the nk.exe accordingly.
Watch it though: if you use the patched nk.exe for bluetooth sound fix, you will not be able to set the whole version to your liking, there will be some 1 digit fixed value that cannot be changed - if I recall well.
P.S.: Sorry tomme, don't really read the Trinity threads anymore. But I will take a look every now and then, promise!
Yes I know PkgToolsBuildos, but this program always set rom version 3. when I edit S000 from nk.exe by hand, it is still show me rom version 3.x but then I have proper rom version in device information.
tomme45i said:
Yes I know PkgToolsBuildos, but this program always set rom version 3. when I edit S000 from nk.exe by hand, it is still show me rom version 3.x but then I have proper rom version in device information.
Click to expand...
Click to collapse
That's because of the nk.exe that has already been patched. Try another nk.exe or an older buildOS.
tnyynt said:
Try another nk.exe or an older buildOS.
Click to expand...
Click to collapse
I try on PkgToolsBuildos 4.2b3 and on 4.3b1. In BuildOS->Rom ver. in Boot there is number 3 even before I load rom. Where can I find older PkgToolsBuildos cause I'he tryied another nk.exe without luck.
tomme45i said:
I try on PkgToolsBuildos 4.3b1 and on 4.3b3. In BuildOS->Rom ver. in Boot there is number 3 even before I load rom. Where can I find older PkgToolsBuildos cause I'he tryied another nk.exe without luck.
Click to expand...
Click to collapse
Try with this one.
tnyynt said:
Watch it though: if you use the patched nk.exe for bluetooth sound fix, you will not be able to set the whole version to your liking, there will be some 1 digit fixed value that cannot be changed - if I recall well.
Click to expand...
Click to collapse
it can be changed, it's just a hardcoded MOV instruction in assembly
tnyynt said:
Try with this one.
Click to expand...
Click to collapse
tnyynt thank you for you answer, but even on older version situation is the same. Program always overwrite 1st digit. Here is screenshot from older version buildos+package_tools-4.1b1:
You can't change the first digit in ROM version, no matter which nk.exe you try to change.
On the old nk.exe (the one used to fix the losing password bug for some users) you'll always have 0. before whatever you want your ROM version to be.
On the newer nk.exe you'll always have 3. before whatever you want your ROM version to be.
That's something you just can't change, because it's an hardcoded value and this was the reason why my ROMs for trinity were 3.something (because when I started cooking I was using the newer nk.exe) and even after changing to the old nk.exe (to solve the losing password bug for some users - a problem I never had in my device), I had to start numbering my ROM as 0.3.something.
My advice:
If you don't have the password bug with your device, and are not planning on releasing the ROM, use the newer nk.exe and number your ROM 3.1.0, and forget about the 3..
The ROM version in Device Info is a completely different thing. That value is not hardcoded anywhere, and since it's a registry value, you can put whatever you wish and it will display properly.
In conclusion, if you're using the PkgToolsBuildos (doesn't really matter which version you're using) to change the ROM version (and this is responsible only for the value that appears on the boot screen), leave the left field as it is, and change only the right field to what you want and save changes.
I hope this will clear your doubts about this. Happy cooking!!
I don't know the difference between this two version of NK.exe so FInixNOver thank you for explanation!
I release my roms on polish forum. First nine was based on old NK.exe, so the last was 0.9. Now when I try new NK.exe I was surprised that my rom version in boot is starting from 3.
BTW. I think only first digit is hardcoded, cause I can change dot symbol by hex editing S000 file.
One more time FInixNOver thank you for your reply!
FInixNOver said:
That's something you just can't change, because it's an hardcoded value
Click to expand...
Click to collapse
huh? it is an not one time writable value. you can change it with a simple assembly patch that I referred to above
cmonex said:
huh? it is an not one time writable value. you can change it with a simple assembly patch that I referred to above
Click to expand...
Click to collapse
I stand corrected. I just said that because I was never able to change that value. So if you say it's possible, even better!!