Database Develop

TomTom freezing --> how to get rid

Hello All,
I finally have found a solution to avoid TomTom freezing from time to time: I do not claim to have discovered anything by myself, infact I found the info via google on a French Forum here:
http://www.ppccool.com/index.php?showtopic=5782&st=0
The solution: install ATIFix.cab (attached)
The reason why I think it is a solution is simple: I have changed three ROM versions (the Dopod "Test ROM", the Dopod "Official ROM" and the latest HTC "Official ROM") and different versions of TomTom Navigator, includind the latest 6.03 without seeing significant changes.
After installing this patch, I have not had a single freeze.
Regards,
Anubis

Test it
I have installed it, and will test it on the way home!

Anubis1965 said:
Hello All,
I finally have found a solution to avoid TomTom freezing from time to time: I do not claim to have discovered anything by myself, infact I found the info via google on a French Forum here:
http://www.ppccool.com/index.php?showtopic=5782&st=0
The solution: install ATIFix.cab (attached)
The reason why I think it is a solution is simple: I have changed three ROM versions (the Dopod "Test ROM", the Dopod "Official ROM" and the latest HTC "Official ROM") and different versions of TomTom Navigator, includind the latest 6.03 without seeing significant changes.
After installing this patch, I have not had a single freeze.
Regards,
Anubis
Click to expand...
Click to collapse
THANKYOU SOOOO MUCH! This has made my day, having TTN crash whilst driving was..well...nearly making me crash! So you may have saved my life...literally!!

Walked Around
I have walked around for about half a hour, no freezing!

thank you very much, i'll try it as soon as possible and post here the results...

The cab has has single .txt placed on the windows dir, no reg or setup.dll, there are some interesting settings on that .txt, core max/min freq., screen resolution, and even SD Card related settings, I wonder if we can overclock it lol, or if there's any relation between the ATI chip and SD Card problems reported by some people.

Bad ?
Apoc said:
The cab has has single .txt placed on the windows dir, no reg or setup.dll, there are some interesting settings on that .txt, core max/min freq., screen resolution, and even SD Card related settings, I wonder if we can overclock it lol, or if there's any relation between the ATI chip and SD Card problems reported by some people.
Click to expand...
Click to collapse
This sounds bad, is it not?

tested and it works great...
drived about one hour and no more freezes.

does it work on ita ROM?

what areas of your device does the ATI Fix affect? Usually, medicine for example treat something and mess something else if over dose is administered or something similar. In the case of the ATIFix, if it works great on not freezing the software, does it affect any other areas or performance of the device? Phone application for example or camera or anything else?
Thanks,
Gilbert

The fix worked great for me. As I noticed there's no perfomance issue and other wierd stuffs. this patch with the quick fix made my day. TomTom kick ass

It works fine
My TomTom did not freeze any more! It also looks like the GPS a fix much faster.
But I really wouyld like to know what the fix is actually doing to the device...
I would not like to have my device get stuck kust because of having tomtom not to freeze anymore...
John

This is what the fix does
De fixes places the followin text file in de windows dir,name of file: atihwtbl0.txt
Is there someone who does understand what is going on?
//ATI_HW_TBL
[Header] // Header
"Revision"=string:2.30.061208.88258
"OEMID"=dword:0x00000000
"ProductID"=dword:0x00000000
"Date"=dword:0x20060818
[Platform] // Hardware
"CPU"=dword:1
"RDN"=dword:5
"RDF"=dword:5
"RRR"=dword:1
"BusWidth"=dword:16
"InterruptNum"=dword:21
"IntISTPriority"=dword:101
"IntActiveLevel"=dword:0 // active high
"IntTriggerType"=dword:1 // call back trigger
[ASIC]
"ExtMemCfg"=dword:5
"ExtMemEnable"=dword:1
"CoreVoltage"=dword:0x00015000 //1.5V
"ChipPhysAddr"=dword:0x10000000
"VRamAllocCfg"=dword:0
"PM4IdleIntEnable"=dword:0
"PM4RBSize"=dword:11
"ClkXtalFreq"=dword:16000000 //16MHz
"ClkSysFastFreq"=dword:192000000 //PLL2 = 192MHz
"ClkExternalInputFreq"=dword:32768 //src = 32.768kHz
"ClkSysNormXtalSrcDiv"=DWORD:3
"ClkSysFastPllSrcDiv"=DWORD:2
"ClkSysNormPllSrcDiv"=DWORD:14
"ClkSysNormSrc"=DWORD:1
"ClkSysTurboPllSrcDiv"=dword:2
"ClkPixDiv"=DWORD:3 //For LCD 5.3MHz => 16MHz / 3
"ClkPixSrc"=DWORD:0
"ClkPixDiv2"=DWORD:2 //For LCD 8MHz => 16MHz / 2
"ClkPixSrc2"=DWORD:0
"ClkVipDiv"=DWORD:8
"ClkVipSrc"=DWORD:1
"ClkCliDiv"=DWORD:1
"ClkCliSrc"=DWORD:0
[MEMORY]
"MemClkDriveStrength"=dword:0x000000F3 // 0011 1100 1 1 = 0000 1111 0011
"MemAddrDriveStrength"=dword:0x0000030F // 1100 0011 1 1 = 0011 0000 1111
"MemDqDriveStrength"=dword:0x0000030F // 1100 0011 1 1 = 0011 0000 1111
[PowerManagement]
"Enable"=dword:1
"HwAutoModeSwitch"=dword:1
"HwAutoFastTurboSwitch"=dword:0
"ExtMemPowerManagement"=dword:1
[LCD] // LCD
"ResolutionWidth"=dword:240 // 240
"ResolutionHeight"=dword:320 // 320
"ColorDepth"=dword:16
"ColorOrdering"=dword:0
"Rotation"=dword:0
// Panel (240x320)
"LcdFormat"=dword:0x003
"GraphicCtrl"=dword:0x18f1c06
"CrtcTotal"=dword:0x01450117
"ActiveHDisp"=dword:0x00f00000
"ActiveVDisp"=dword:0x01400000
"GraphicVDisp"=dword:0x01400000
"GraphicHDisp"=dword:0x00f00000
"CrtcSS"=dword:0x80f00000
"CrtcLS"=dword:0xa10600fc
"CrtcGS"=dword:0xc0050005
"CrtcVPosGS"=dword:0x01430141
"CrtcGClk"=dword:0x0
"CrtcGOE"=dword:0x0
"CrtcRev"=dword:0x00400008
"CrtcDClk"=dword:0xa0000000
"CrtcDefaultCount"=dword:0
"CrtcFrame"=dword:0x0
"CrtcFrameVPos"=dword:0
"LcddCntl1"=dword:0x0f00000
"LcddCntl2"=dword:0x3ffff
"GenLcdCntl1"=dword:0xa950fd
"GenLcdCntl2"=dword:0x3f000
"LcdBackGroundColor"=dword:0x00ffffff
[LCD2] // LCD
"ResolutionWidth"=dword:240 // 240
"ResolutionHeight"=dword:320 // 320
"ColorDepth"=dword:16
"ColorOrdering"=dword:0
"Rotation"=dword:0
// Panel (240x320) as secondary
"LcdFormat"=dword:0x003
"GraphicCtrl"=dword:0x18f1c06
"CrtcTotal"=dword:0x014f010A
"ActiveHDisp"=dword:0x00fb000b
"ActiveVDisp"=dword:0x01470007
"GraphicVDisp"=dword:0x01470007
"GraphicHDisp"=dword:0x00fb000b
"CrtcSS"=dword:0x800c000b
"CrtcLS"=dword:0xe0050001
"CrtcGS"=dword:0xC0010001
"CrtcVPosGS"=dword:0x0003014f
"CrtcGClk"=dword:0x0
"CrtcGOE"=dword:0x0
"CrtcRev"=dword:0x00400008
"CrtcDClk"=dword:0xa0000000
"CrtcDefaultCount"=dword:0
"CrtcFrame"=dword:0x0
"CrtcFrameVPos"=dword:0
"LcddCntl1"=dword:0x0f00000
"LcddCntl2"=dword:0x3ffff
"GenLcdCntl1"=dword:0xa950fd
"GenLcdCntl2"=dword:0x3f000
"LcdBackGroundColor"=dword:0x00ffffff
[GPIO] // GPIO
"PinUsed"=dword:0xFFFFFFFF
"PinDirection"=dword:0xFFFFFFFF
"PinData"=dword:0x0
"PinPullDown"=dword:0xFFFFFFFF
[SD]
"SdClockRate"=dword:312500 // SD Card Initial Clock Rate (Hz)
"SdCardDetectMethod"=dword:1 // SD Card Detection Method is initialized to polling
[CAMERA]
"CameraFlashGpioPin"=dword:0x11 // GPIO17
"CameraFlashPinPolarity"=dword:0 // Active high
"CameraOutputClkFreq"=dword:0 // Hz
"CameraFlashTrigger"=dword:0 // trigger by VSync

For a little bit more details you can check
http://forum.xda-developers.com/showthread.php?t=297717&highlight=ati*
Greets,
Gerhard

Does anyone have the original atihwtbl0.txt from Dopod ROM 1.23.707.6
Tried the patch on my Trinity and my sd no longer works. I have to remove the card to get the phone to boot.
If I put the card back in it hangs when trying to access the SD

i hope this help you.On my p3600 works:
gpe-->settings-->hardware-->put bout to 9600.
No freeze now

I have installed the FIX on my P3600 with firmware Turchino_ITA_1.23.408.1_1.38.00.11_GPS.zip, and now stop FIX with TTN 6 (6.030).
ALL OK!

DaveUK said:
Does anyone have the original atihwtbl0.txt from Dopod ROM 1.23.707.6
Tried the patch on my Trinity and my sd no longer works. I have to remove the card to get the phone to boot.
If I put the card back in it hangs when trying to access the SD
Click to expand...
Click to collapse
This is my original file - from the same rom as you (just copied it over before installing the program). If you are just having trouble with the SD card you could try just changing that section of the file back to the original - I haven't compared the two files as yet though.

I have installed the ATIFix.cab "hack" and tomtom works oke.
Everything seems to work oke...
But I can not send any MMS messages
I do not know if I could before.
Does more people have this problem?
Can someone confirm that he or she can still send MMS messages?
Thanx!

Interesting, the DOPOD 1.23 version is newer, and there is no difference on the SD Card configuration!
1.23.707.6 dopod version
Code:
[Header] // Header
"Revision"=string:2.30.061109.86275
"OEMID"=dword:0x00000000
"ProductID"=dword:0x00000000
"Date"=dword:0x20061120
in this thread
Code:
[Header] // Header
"Revision"=string:2.30.061208.88258
"OEMID"=dword:0x00000000
"ProductID"=dword:0x00000000
"Date"=dword:0x20060818
I've attached both versions, you can use WinMerge to check the diffs.

What is application lock on mteor ??

Hi there,...
what exactly does the application lock do???
steve

ok, found some infos...
Most WM5 phones only allow you to load applications that have an acceptable digital signature. If you try to edit the registry or load an application it will give you an error. Application Unlocking removes this barrier and allows you to install any application or edit the registry to your liking.
Click to expand...
Click to collapse
but this is not really significant ....
the MTeoR has an application lock!! but what limitations did you expect with it??
the only one i have found is while trying various of programms that on -> TinyGPS didn't worked ... ends with the message that the phone has application locked... after unlocking the MTeoR the program starts... (but hangs on license screen but i think thats a general problem with qvga and wm5-sp)
anyother troubles with the app-lock ???

I'm didn't have any troubles with application lock in MTeoR
I'm use complex method to remove this lock
In RegEditSTG: HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001001 = 2
->from 2 to 1
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001005 = 16
-> from 16 to 40
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001017 = 128
-> from 128 to 144
HKEY_LOCAL_MACHINE \Security\Policies\Policies
-> create new "0000101b" (type Dword) = 1
<reset>
And as last i'm use SDA Application Unlock
May be some of this steps are unnecessary but it is work!
And other way to run exe without sign from MSP - create sign!
Read more about CodeSigningX86 from Microsoft. It works great, i'm use my sign for rather programs (because i didn't use app unlock in WM5 Emu for my PC)

Hi!
I've installed PHM RegEdit on my MTeor, but i can't change any values It always gives me a failure 'Unable to perform this operation'. I'm a noob in tweaking regs oder ppc/smartphones, so someone could help me, please? Until now I used a BlueAngel. A very good device, but to big for daily use, so I bought this MTeor. Now I've got the application problem. But why I can't change values in the registry?
@futureshock: Evtl. kannst Du mir auch über's ICQ helfen?

Ok, i made it. I found this post: http://forum.xda-developers.com/showpost.php?p=1038508&postcount=2

Ultimate NOOB Guide to ROM Cooking - Updated 24-06-08

Dear Friends..i am soon going to start cooking classes with guides that every noob will understand :
This guide is for Htc Himalaya also known as O2 XDA II, T-Mobile MDA II, Qtek 2020, iMate Phone Edition, TSM500, Vodafone VPA, Dopod 696, Orange SPV M1000, Krome Navigator F1
Lesson 1 :-
I am going to list the Frequently used Acronyms in the Classroom or in the ROMcooking Enviroments
AKU - Adaptation Kit Update: they usually patch up existing bugs and enable several new features. Each newly released AKU pack retains fixes found in previous versions of AKU
RUU - ROM Upgrade Utility: Its the woftware used on your PC to do a ROM upgrade for your PPC
Bootloader : The bootloader is the first thing to load once you turn on the device, this does the job of booting up the device hardware and loading various items into memory before the ROM starts in the device. The bootloader is also responsible for enabling the flashing of new ROMs and other components such as the Radio and the Ext_ROM (in Wm2003 )
Cooked : Refers to ROMs which have been modified and optimised by users to offer better performance than a carrier ROM or a release by Microsoft. Cooked ROMs can be found every where in the forums now adays or you can cook your self once you are Passed from this class
Flash : Term meaning to write something (usually a ROM image) to a non-volatile chip. The term originates from original chip writers (EPROM blowers) which used to write to a chip by fusing tiny areas in the chip making individual links either short circuit or open circuit.
Hard Reset : Similar to a soft reset, by performing a hard reset you completely wipe your device and restore it to the position it was in when you first turned the device on after it was purchased or after a new ROM is flashed.
To carry out a hard reset on the Himalaya press and hold BOTH Camera and Record Key and insert the stylus into the hole in the bottom fo the device, Select the options as follows:
For WM5, WM6 and WM 6.1 Only !!
(for selecting use Record Key, change values with Camera Key)
Enable KITL -> NO
Clean Registry Hive -> YES
Format Storage -> YES
When done, press DPad and wait until OS starts.
Click to expand...
Click to collapse
Radio : The radio stack is responsible for the phone functionality of the device. This includes GPRS, GSM, UMTS, and GPS operations as well as camera functionality. The version you use depends on who your carrier is as users have reported versions working better on one carrier than the other.
ROM : The ROM holds the Operating system and other components such as the bluetooth and wifi stacks. The ROM is accompanied by the Radio, Ext_ROM, SPL and IPL. Carriers such as T-mobile or Vodaphone taylor the ROM to their specifications and version numbers do not carry the same meaning across different carriers. IF the carrier you use supports the device well they will usually release regular ROM updates.
Soft Reset : Soft resetting the device will lose all the data currently in RAM and any unsaved information, much like pressing the reset button on your pc. A soft reset is the first thing to try if your device has stopped responding. To soft Reset your Himalaya insert the stylus into the hole in the bottom of the device.

Lesson 2 :- OEM Packages
What is an OEM Package ?
OEM package is just like a form of cab..It is cooked into the ROM so that when one may flash it..he will find it there..read on and you will understand
What the Heck are these strange alphanumeric sequences ? - 283b9db7-cb03-4c1b-820e-ca49b2c3b5db
Well, each OEM package uses a Universal Unique Identifier (UUID) to identify itself. This UUID is used in up to three distinct places within an OEM package.Once in the DSM file, once in the RGU file, and once in the option.xml file ( used by BuildOS )
Make sure to use the same UUID within a single OEM package and do not use multiple UUIDs in a single OEM Package or else BuildOS wont start
I just heard DSM..wat is that ?
UUID.dsm contains a file listing of all the files within an OEM package. For noobs, it is not necessary to generate a .dsm as BuildOS will generate one for you.
do my ears Decieve me or did i hear RGU ?
UUID.rgu is where the registry information is contained for the OEM package. All Microsoft Operating Systems since Windows 95 use the Windows Registry to hold important application information and Windows Mobile is no different.
.rgu files are formatted exactly like .reg files which can be exported from programs such as SOTI Pocket Controller Pro, PHM RegEdit and SKTools
If your package does not require registry information, then you do not need to include an rgu file within your OEM package.
Initflashfiles :-
This file is used by the BuildOS for file copy operations & directory creation. By default, all files within an OEM package go into \Windows. If you want any of your files to be copied elsewhere, specify it in this file. If you want everything in \Windows, then you won't need an INITFLASHFILES.TXT file either. It is very similar to INITFLASHFILES.DAT, which controls the placement of files included by default in the ROM.
Here is a sample INITFLASHFILES.TXT and a brief explanation of each line:
1a . Directory("\Program Files\"):-Directory("MusicID")
2a . ("\Program Files\MusicID"):-File("MUSICID.EXE","\windows\000-MUSICID.EXE")
3a . Directory("\Windows\Start Menu\Programs"):-File("MusicID.lnk","\Windows\MusicID.lnk")
1b . Create a folder named MusicID in \Program files Directory
2b . In the directory \Program Files\MusicID, create a copy of file named MUSICID.EXE, whose original file path is \windows\000-MUSICID.EXE
3b . In the directory \Windows\Start Menu\Programs, create a copy of the file named MusicID.lnk, whose original file path is \windows\MusicID.lnk
wait..i heard u saying Options.xml..didnt u ?
This file is used by the BuildOS to tell cooks what your OEM package is and does. Let's start with a sample OPTIONS.XML and the breakdown of each component :
<?xml version="1.0" encoding="UTF-16" standalone="yes"?>
<Items>
<Item name="test oem" group="utilities" checked="true">
<Tip>Its just a test OEM package!</Tip>
<Guid type="p">46845f1f-3ad5-43e4-b92d-aaef4ad5b5ea</Guid>
</Item>
</Items>
Click to expand...
Click to collapse
The stuff you care about is as follows :
Item name = The name of the application contained within this OEM package
group = The application group / category this OEM package belongs to
checked = Whether or not you want this item to be checked (true) or unchecked (false) by default. Useful to
remind people that this is a critical OEM package and needs to be installed in their cooked ROM or something won't work! (e.g., Camera functionality!!!)
Tip = helpful information about the function of this OEM package ( appears when mouse is hovered over the OEM )
GUID = UUID. You need to put the UUID here to identify your OEM package. Technically a GUID is not a UUID according to wikipedia and other sources, but we'll just ignore that for this tutorial ( use the same UUID as used in DSM and RGU )
OPTIONS.XML is the only file REQUIRED for you to manually create in an OEM package.
more to come tomorrow

reserved2 .....

again reserved...

ather90 said:
.
Click to expand...
Click to collapse
Waiting for lesson 3. I just gotta knw that Camera function is in the Radio stack.

bump , very interesting mate , eagerly waiting for the test

Yeah, keep it up! There is not enough information for new cooks out there!

Interesting explanations!! Waiting for more

Well done, Ather! Nice to know that you are compiling everything in regards to cooking.
We sincerely hope you can continue with your efforts.
If it is fine with you, perhaps also you can include things like XIP, Dumping of your rom, etc etc.
Once again, many thanks!

im sorry all but i have been kinda buzy with personal problems and other things..so iwas just silently visitin g the site once in 2 days
but now im back im starting to work on the ROMs also..and there are to many new OEMS to make also im Developing a software
chk it here : http://forum.xda-developers.com/showpost.php?p=2569826&postcount=91
i will re-start this tut dont worry

eu peço desculpas
mas o hard reset nao funciona no meu Qtek 2020
i.m sorry
but the hard reset dos not work on my Qtek 2020
plz help ( por favor ajudem )
cumprimentos ( best regards )
Custume
Edit: my suport for rom´s
http://custume.no-ip.org/forum/viewtopic.php?f=18&t=30
fell free to coment (or if you what to add someting just hask me )
and direct link http://custume.no-ip.org:81/box/utilitarios/PDA-SmartFone/

Where is part number 3??? please. i would like to learn how to cook...

Awesome!!!
Interesting, please go on hoping for couple of more of ur tuts to do my own rom....
Thanks!!!

shad0w22 said:
Interesting, please go on hoping for couple of more of ur tuts to do my own rom....
Thanks!!!
Click to expand...
Click to collapse
im getting few holidays in the coming days, will try to continue
Cheers

Sorry Double Post

Anymore to this guide? Would love to read on how to dump, where the pda.bin is, how to rebuild, etc, etc...
Great work!

Yeah nice explanations!
I have part of the theory now! the other part to come isnt it ather90?
We will stay on touch of this cause this is the most complete lesson at this point i never red jejeje.

Question
Does this work only on HTC Phones or does it also work on iPaq ans other windows enabled devices? because i did not find a fully functional custom rom for my HP iPaq rx 1950..

volug said:
Does this work only on HTC Phones or does it also work on iPaq ans other windows enabled devices? because i did not find a fully functional custom rom for my HP iPaq rx 1950..
Click to expand...
Click to collapse
It only works on HTC devices like those described by Ather beginning of his post
for HP iPaq rx 1950 please check at http://forum.xda-developers.com/showthread.php?t=510764

Thanks :good:

Can we not squeeze a little more out of the wizard's memory?

Adding an explanation for starting this thread
I started this thread because when I search for ways to get more memory, all I find is how others have things like "Big Storage" etc., but somewhere it will say cannot be done on wizard. I do not find very much about what can be done or why it cannot be done. I have found things about unlocking and unhidng the Extended_ROM. I used that as a basis for my trials and trying to understand how memory works in the wizard.
I started this thread hoping someone with much more knowledge than me would be able to shed light on the issue and it would be on the forum for future users to understand the memory issues on the wizard.
-----------------------------------------------------------------------------------------------------------
In default.hv which I converted to rgu so I could read I saw the following:
Code:
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\PartitionTable][/FONT]
[FONT=Arial]"26"="BINARY"[/FONT]
[FONT=Arial]"25"="IMGFS"[/FONT]
[FONT=Arial]"23"="RAWFS"[/FONT]
[FONT=Arial]"22"="RAWFS"[/FONT]
[FONT=Arial]"21"="BINFS"[/FONT]
[FONT=Arial]"20"="BOOT"[/FONT]
[FONT=Arial]"0F"="FATFS"[/FONT]
[FONT=Arial]"0E"="FATFS"[/FONT]
[FONT=Arial]"0C"="FATFS"[/FONT]
[FONT=Arial]"0B"="FATFS"[/FONT]
[FONT=Arial]"07"="NTFS"[/FONT]
[FONT=Arial]"06"="FATFS"[/FONT]
[FONT=Arial]"04"="FATFS"[/FONT]
[FONT=Arial]"01"="FATFS"[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles][/FONT]
[FONT=Arial]"Folder"="Mounted Volume"[/FONT]
[FONT=Arial]"PartitionDriverName"="MSPART"[/FONT]
[FONT=Arial]"DefaultFileSystem"=""[/FONT]
[FONT=Arial]"MountFlags"=dword:0[/FONT]
[FONT=Arial]"AutoFormat"=dword:0[/FONT]
[FONT=Arial]"AutoPart"=dword:0[/FONT]
[FONT=Arial]"AutoMount"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FLASHDRV][/FONT]
[FONT=Arial]"BootPhase"=dword:0[/FONT]
[FONT=Arial]"MountFlags"=dword:11[/FONT]
[FONT=Arial]"Folder"="imgfs"[/FONT]
[FONT=Arial]"Name"="Microsoft Flash Disk"[/FONT]
[FONT=Arial]"PartitionDriver"="mspart.dll"[/FONT]
[FONT=Arial]"DefaultFileSystem"="IMGFS"[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FLASHDRV\IMGFS][/FONT]
[FONT=Arial]"XIP"=dword:0[/FONT]
[FONT=Arial]"MountFlags"=dword:11[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FLASHDRV\FATFS][/FONT]
[FONT=Arial]"FatCacheSize"=dword:100[/FONT]
[FONT=Arial]"DataCacheSize"=dword:800[/FONT]
[FONT=Arial]"EnableWriteBack"=dword:1[/FONT]
[FONT=Arial]"MountAsRoot"=dword:1[/FONT]
[FONT=Arial]"MountAsBootable"=dword:1[/FONT]
[FONT=Arial]"CheckForFormat"=dword:1[/FONT]
[FONT=Arial]"FormatTFAT"=dword:1[/FONT]
[FONT=Arial]"Flags"=dword:600014[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FLASHDRV\FATFS\Filters\fsreplxfilt][/FONT]
[FONT=Arial]"Order"=dword:1[/FONT]
[FONT=Arial]"Dll"="fsreplxfilt.dll"[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash\Part00][/FONT]
[FONT=Arial]"CheckForFormat"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash\FATFS][/FONT]
[FONT=Arial]"MountHidden"=dword:0[/FONT]
[FONT=Arial]"MountAsROM"=dword:0[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\MSPART][/FONT]
[FONT=Arial]"Dll"="mspart.dll"[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\IMGFS][/FONT]
[FONT=Arial]"ShadowROM"=dword:1[/FONT]
[FONT=Arial]"Paging"=dword:1[/FONT]
[FONT=Arial]"Dll"="imgfs.dll"[/FONT]
[FONT=Arial]"FriendlyName"="Image-Update Filesystem"[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\FATFS][/FONT]
[FONT=Arial]"CacheSize"=dword:2000[/FONT]
[FONT=Arial]"Flags"=dword:44[/FONT]
[FONT=Arial]"CacheDll"="diskcache.dll"[/FONT]
[FONT=Arial]"Util"="fatutil.dll"[/FONT]
[FONT=Arial]"EnableCache"=dword:1[/FONT]
[FONT=Arial]"Paging"=dword:1[/FONT]
[FONT=Arial]"Dll"="fatfsd.dll"[/FONT]
[FONT=Arial]"FriendlyName"="FAT FileSystem"[/FONT]
In boot.rgu I found
Code:
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager] [/FONT]
[FONT=Arial]"PNPUnloadDelay"=-[/FONT]
[FONT=Arial]"PNPUnloadDelay"=dword:5dc[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC\IMGFS][/FONT]
[FONT=Arial]"MountFlags"=dword:11[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC][/FONT]
[FONT=Arial]"Name"="DiskOnChip M-Systems"[/FONT]
[FONT=Arial]"Folder"="imgfs"[/FONT]
[FONT=Arial]"MountFlags"=dword:11[/FONT]
[FONT=Arial]"BootPhase"=dword:0[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TrueFFS][/FONT]
[FONT=Arial]"Flags"=dword:1000[/FONT]
[FONT=Arial]"Index"=dword:1[/FONT]
[FONT=Arial]"Profile"="TRUEFFS_DOC"[/FONT]
[FONT=Arial]"Dll"="TrueFFS.dll"[/FONT]
[FONT=Arial]"Prefix"="DSK"[/FONT]
[FONT=Arial]"Order"=dword:0[/FONT]
[FONT=Arial]"WindowBase"=dword:0[/FONT]
[FONT=Arial]"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"[/FONT]
[FONT=Arial]"BootPhase"=dword:0[/FONT]
[FONT=Arial]"AutoDPDMode"=dword:1[/FONT]
[FONT=Arial]"SoftwareWriteProtect"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Autoload\TrueFFS][/FONT]
[FONT=Arial]"DriverPath"="Drivers\\BuiltIn\\TrueFFS"[/FONT]
[FONT=Arial]"LoadFlags"=dword:1[/FONT]
[FONT=Arial]"BootPhase"=dword:0[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1][/FONT]
[FONT=Arial]"DefaultFileSystem"="FATFS"[/FONT]
[FONT=Arial]"Name"=""[/FONT]
[FONT=Arial]"PartitionDriver"=""[/FONT]
[FONT=Arial]"Folder"="Extended_ROM"[/FONT]
[FONT=Arial]"MountHidden"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1\FATFS][/FONT]
[FONT=Arial]"Flags"=dword:14[/FONT]
[FONT=Arial]"FormatTfat"=dword:1[/FONT]
[FONT=Arial]"EnableWriteBack"=dword:1[/FONT]
[FONT=Arial]"DataCacheSize"=dword:00000080 ;128 sectors(128*512=64KB)[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\TRUEFFS_DOC1][/FONT]
[FONT=Arial]"DriverPath"="Drivers\\BuiltIn\\TrueFFS1"[/FONT]
[FONT=Arial]"LoadFlags"=dword:1[/FONT]
[FONT=Arial]"Order"=dword:1[/FONT]
[FONT=Arial]"Bootphase"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TrueFFS1][/FONT]
[FONT=Arial]"Profile"="TRUEFFS_DOC1"[/FONT]
[FONT=Arial]"Index" = dword:2[/FONT]
[FONT=Arial]"Dll" = "TrueFFS.dll"[/FONT]
[FONT=Arial]"Prefix" = "DSK"[/FONT]
[FONT=Arial]"Order" = dword:1[/FONT]
[FONT=Arial]"Ioctl" = dword:4[/FONT]
[FONT=Arial]"Use8Bit" = dword:1[/FONT]
[FONT=Arial]"WindowBase" = dword:00000000[/FONT]
[FONT=Arial]"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"[/FONT]
[FONT=Arial]"AutoDPDMode" = dword:1[/FONT]
[FONT=Arial]"SoftwareWriteProtect"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\Comm][/FONT]
[FONT=Arial]"AutoRun"="\\Windows\\AutoRun.exe"[/FONT]
[FONT=Arial]"AutoRunCFG"=[URL="file://\\Extended_ROM\\Config.txt"]\\Extended_ROM\\Config.txt[/URL][/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC2][/FONT]
[FONT=Arial]"DefaultFileSystem"="FATFS"[/FONT]
[FONT=Arial]"Name"=""[/FONT]
[FONT=Arial]"PartitionDriver"=""[/FONT]
[FONT=Arial]"Folder"=""[/FONT]
[FONT=Arial]"MountFlags"=dword:6[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC2\FATFS][/FONT]
[FONT=Arial]"Flags"=dword:00600014[/FONT]
[FONT=Arial]"FormatTFAT"=dword:1[/FONT]
[FONT=Arial]"CheckForFormat"=dword:1[/FONT]
[FONT=Arial]"MountAsBootable"=dword:1[/FONT]
[FONT=Arial]"MountAsRoot"=dword:1[/FONT]
[FONT=Arial]"EnableWriteBack"=dword:1[/FONT]
[FONT=Arial]"DataCacheSize"=dword:00000080[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TrueFFS2][/FONT]
[FONT=Arial]"Index"=dword:3[/FONT]
[FONT=Arial]"Profile"="TRUEFFS_DOC2"[/FONT]
[FONT=Arial]"Dll"="TrueFFS.dll"[/FONT]
[FONT=Arial]"Prefix"="DSK"[/FONT]
[FONT=Arial]"Order"=dword:0[/FONT]
[FONT=Arial]"Ioctl"=dword:4[/FONT]
[FONT=Arial]"Use8Bit"=dword:1[/FONT]
[FONT=Arial]"WindowBase"=dword:0[/FONT]
[FONT=Arial]"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"[/FONT]
[FONT=Arial]"AutoDPDMode"=dword:1[/FONT]
[FONT=Arial]"SoftwareWriteProtect"=dword:0[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Autoload\TrueFFS2][/FONT]
[FONT=Arial]"DriverPath"="Drivers\\BuiltIn\\TrueFFS2"[/FONT]
[FONT=Arial]"LoadFlags"=dword:1[/FONT]
[FONT=Arial]"Order"=dword:0[/FONT]
[FONT=Arial]"BootPhase"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC2\FATFS\Filters\fsreplxfilt][/FONT]
[FONT=Arial]"dll"="fsreplxfilt.dll"[/FONT]
[FONT=Arial]"order"=dword:1 ; must be loaded before other filters[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\FATFS][/FONT]
[FONT=Arial]"FriendlyName"="FAT FileSystem"[/FONT]
[FONT=Arial]"Dll"="fatfsd.dll"[/FONT]
[FONT=Arial]"Flags"=dword:00000024[/FONT]
[FONT=Arial]"Paging"=dword:1[/FONT]
[FONT=Arial]"EnableCache"=dword:1[/FONT]
[FONT=Arial]"CacheSize"=dword:0[/FONT]
[FONT=Arial]"Util"="fatutil.dll"[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\filters\HTCFSDSPY][/FONT]
[FONT=Arial]"Dll"="htcfsdspy.dll"[/FONT]
[FONT=Arial]"Order"=dword:0[/FONT]
Of course there is more than just the above in those files. What I wonder since I do not know enough to know what cannot be done is...
Can you change these settings to not define a region to be extended ROM?
Can you redefine the rest to use this left over space?
Can any of this space be used for program memory instead of storage memory?
I do not know if the dll files limit the size of the regions or is some of the settings determine the sizes.
As I said, I do not know enough to know the limitations, but the little boy saw all that was needed was to let the air out of the tires to get the truck unstuck from under the bridge.
Note: This work was done on my G4

Are you using LZX compression?
If not start reading form “HERE” post #877

I have been reading that and the Visual Kitchen Thread, but they leave me behind a little yet.
I am just now trying to go past using the HyperCore Kitchen and switch to CRBuilder 2. I am not sure what it does different. It seems to be less forgiving of my mistakes.
I also read the threads on porting XIP, etc. I am still trying to learn this stuff.
Since I am naturally lazy, I thought what if we could get more room by not defining ExtendedROM. Also, I did not know how program memory versus storage memory is set up and if it was possible to get more program memory available. This is going to become our limiting factor (M2D, WM6.5, etc.).

Everything i’ve read would suggest that we can’t use the extended ROM area for anything other then what it was designed for.
I don’t think you can gain any more memory without removing programs.

I have been doing a lot of reading. I have a G4 Wizard. I have edited my boot.rgu, boot.hv and default.hv to remove references to TRUEFFS_DOC1 (the extended ROM). As expected, I cannot see extended rom in total commander. I did not notice a jump in total memory on the phone. I am beginning to think extended rom is coded in the chip and not set by our flashes. Has anyone tried something like DiskOnChip TrueFFS Uilities package or similar to redefine the spaces on the chip to not have extended rom? I know so little, I imagine there is something more that prevents this, but I thought I would ask. I did not know if this path would lead to more program memory in addition to storage memory.

Delete references to TRUEFFS_DOC1
I decided to do a separate post for each trial.
I have edited my boot.rgu, boot.hv and default.hv to remove references to TRUEFFS_DOC1 (the extended ROM). As expected, I cannot see extended rom in total commander. I did not notice a jump in total memory on the phone. I did not notice a change in battery consumption.

Change TRUEFFS_DOC1 settings to be more like TRUEFFS_DOC2
I basically changed TRUEFFS_DOC1 (changed to call it StoROM) settings to match TRUEFFS_DOC2 (regular memory) except I did not set it as "root".
It shows up as removable storage with 4.9 MB of space.
I suspect something in TRUEFFS driver or I am missing a setting to tell it that is is not external memory.
I tried again, but named it "My Documents"
Word and excel would see the template files in My Documents\Templates twice. I could not set word's default file type. No choices showed in the option. I tried moving the templates, but then they could not be seen by word or excel.
Tried sync with my PC. What was already on the phone would not copy to the PC. I added things to the folder on the PC and they would add to the phone. If I deleted it off the phone, instead of deleting it off the PC it would put it back on the phone. If I copy a file from my phone to the my documents folder on the phone it would not show up on the PC. So it seems I have one-way sync capability.
I tried again, but named it "Program Files"
It works, but whatever gets written there stays so I had problems when I did a hard reset. I solved by deleting contents of folder before hard resetting.
Currently testing named to "FileSafe"
I can put files there and they do not get lost in a hard reset.
I am currently testing battery consumption on this latest format. First day, but after 5 hours only down to 91%. Will need to wait because I have noticed battery goes down faster as the level gets lower.
I did a soft reset and ended up with Storage card as a folder in root and storage card2 as the storage card. Cannot delete it since I have reg settings made to locate internet explorer files to storage card.
I'll have to keep tweaking settings.

More about Trueffs driver
I came across a package called "DiskOnChip(R) TrueFFS(R) Uilities package"
This Package includes the TrueFFS Version 6.3.2 Utilities Package
Reading the documentation gives me the impression that the chip is formatted at the factory and we cannot change the partitions. I suspect (stating again) that we only tell the software what to do with the partition. I tried to run the utility, but it could not find the chip to even do a read function.
It also looks like you have to have a password to gain access to parts. I do not fully understand this stuff, but I was reading about locking partitions with a password.
This may be why even though I have the format flag set in TRUEFFS_DOC1 it does not get formatted and as a result the things stored there are still there after a hard reset. Also, why it shows up as removable media even though I do not see where I tell it that it is such. I think anything other than the root is considered "external" and shows up as a storage card.

Explanation added
I added an explanation for this thread to the first post

Updated post #7 about FileSafe.

I have tried every which way I can think and can only create a folder that the phone considers a removable storage device. I keep getting the storage card2 problem so I have gone back to regular settings and installed a blank Ext_ROM.
I am fairly sure of my theory that the partitions are formated at the factory and we are only telling the software what to call them and how to access them. We cannot change what they have been set to at the factory.
I welcome any clarification from someone who knows more.
Hopefully this will help others like me who come in late in the game and wonder why we cannot get things like BigStorage, etc. other than just seeing people saying it cannot be done.

I read about hiding and unhiding the Ext-ROM, too. Unhiding and reading was no problem but writing didn't work.
Converting Ext-ROM to program-memory may not be possible, because AFAIK program-memory is SD-RAM and the Ext-ROM is Flash-MEMORY. But there are more ways the memory of the Ext-ROM could be usefull.
More space for the ROM (max. 57MB for OS.nb is not much when cooking a WM6.5 ROM) would be nice.
OR
A storage-partion like Ext-ROM but with write access!
Only unhiding the Ext-ROM didn't do the job! I could read from the Ext-ROM but couldn't write. After a write attempt the file list got corrupted and I had to hide and unhide again to get read access back.
If I understand the posting right, RoryB was already able to write to the Ext-ROM. How did you do that?
There is one more Problem! Not the MiniSD-Card but the Ext-ROM should get the name "StorageCard 2" (or any other name which comes alphabeticaly after StorageCard). Why? The Camera can save to different locations but you can only choose from 2: Main memory and the alphabeticaly first storage card.
My questions:
1. How do I get read, write and delete access to the Ext-ROM?
2. How can I rename this "Ext-ROM-Storagecard"? Something like "StorageCard 2" or "StorageMemory" or ...
Update:
Answer for question 2 might be:
AbuYahya said:
To Rename EXT-ROM
HKEY_LOCAL_MACHINE \System\StorageManager \Profiles\TRUEFFS_DOC1
"Folder"=string:Storage
--- can call it anything you like instead of "Storage"
Click to expand...
Click to collapse
I didn't check it yet.

I have stopped trying to get Extended_ROM as storage space. I did use it as a filesafe location. I could not get access to all of the space even though I installed an empty Extended_ROM. Here is the part of boot.rgu I changed (best as I can remember)
Code:
;[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\TRUEFFS_DOC1]
; Does not seem right to me to be TRUEFFS_DOC1 when all others use the built in driver and not the profile
[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\TRUEFFS1]
"DriverPath"="Drivers\\BuiltIn\\TrueFFS1"
"LoadFlags"=dword:1
"Order"=dword:1
"Bootphase"=dword:1
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TrueFFS1]
"Profile"="TRUEFFS_DOC1"
"Index" = dword:2
"Dll" = "TrueFFS.dll"
"Prefix" = "DSK"
"Order" = dword:1
"Ioctl" = dword:4
"Use8Bit" = dword:1
"WindowBase" = dword:0
"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"
"AutoDPDMode" = dword:0
"SoftwareWriteProtect"=dword:0
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1]
"DefaultFileSystem"="FATFS"
"Name"=""
"PartitionDriver"=""
"Folder"="FileSafe"
"MountHidden"=dword:0
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1\FATFS]
"Flags"=dword:14
"FormatTfat"=dword:1
"EnableWriteBack"=dword:1
"DataCacheSize"=dword:00000080 ;128 sectors(128*512=64KB)
I think the "Storage Card 2" problem comes about from the order in which the Extended_ROM and SD Card get recognized and for some reason it sees the Extended_ROM as a storage card.
I now use Extended_ROM that way Cingular did. I have files in it in the form of cabs and zips. These files are things like Adobe Reader as a cab, Template files as a zip, etc. I use my customization mortscript to install those files. This way I get more room in the ROM for things that have to be in the ROM. Here is the format I have for my boot.rgu
Code:
;[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\TRUEFFS_DOC1]
; Does not seem right to me to be TRUEFFS_DOC1 when all others use the built in driver and not the profile
[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\TRUEFFS1]
"DriverPath"="Drivers\\BuiltIn\\TrueFFS1"
"LoadFlags"=dword:1
"Order"=dword:1
"Bootphase"=dword:1
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TrueFFS1]
"Profile"="TRUEFFS_DOC1"
"Index" = dword:2
"Dll" = "TrueFFS.dll"
"Prefix" = "DSK"
"Order" = dword:1
"Ioctl" = dword:4
"Use8Bit" = dword:1
"WindowBase" = dword:0
"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"
"AutoDPDMode" = dword:1
"SoftwareWriteProtect"=dword:1
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1]
"DefaultFileSystem"="FATFS"
"Name"=""
"PartitionDriver"=""
"Folder"="Extended_ROM"
"MountHidden"=dword:1
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1\FATFS]
"Flags"=dword:14
"FormatTfat"=dword:1
"EnableWriteBack"=dword:1
"DataCacheSize"=dword:00000080 ;128 sectors(128*512=64KB)
I use winimage to change the contents of my Extended_ROM.nb file. Now when I run nb2nbf I pick the OS and the Extended_ROM as files to write to the nbf.

G4 processors do not allow you to flash a custom extended ROM (IIRC).

jwzg said:
G4 processors do not allow you to flash a custom extended ROM (IIRC).
Click to expand...
Click to collapse
That is just not true! In my WM6.5 ROM there is a custom Ext-ROM included and I have no problem flashing it to my G4 Wizard.
G4-Save means no IPL/SPL but Ext-ROM is not a problem.
@RoryB:
Thank you for the information. I will try it.

RoryB's latest ROM that uses ExtRom for cabs and such works fine on my G4.
Ham3r's experimental ROM that provides ExtRom as a read/write filesystem works on G3.
I even installed apps onto ExtRom, with no problems.
I don't know about its relative speed.
It is marked "G3 only" so I have not tried it on my G4.
If someone is brave enough to show that the Ham3r rom's method works on G4, that would be a great feature.
I think that making the most of extrom as a filesystem is the best we can do.

Cyberdyne said:
That is just not true! In my WM6.5 ROM there is a custom Ext-ROM included and I have no problem flashing it to my G4 Wizard.
G4-Save means no IPL/SPL but Ext-ROM is not a problem.
@RoryB:
Thank you for the information. I will try it.
Click to expand...
Click to collapse
For some reason I was thinking it wouldn't flash. I haven't touched my Wizard in a while, and my XP computer with my kitchen on it is dead. I'll have to upgrade my WM6 ROM again.
Mods ain't gods. I stand corrected.

New App Unlock/Hard SPL Unlock ?

i thought this was interesting. maybe a FREE way to hard spl? i have not tried this out. have no idea if it works. iam not a dev i dont know if this can even be called hard spl. or just a reg edit.
Regedit STG
This is a signed version which is needed to unlock the phone (a little easier to unlock than a IPhone). Cut & paste from Robert Peloschek’s blog:
1.Simply put the *.zip file with the regeditSTG.exe in it with ActiveSync into a folder on your phone (but not onto the memory card).
2.Unzip the file with the *.zip program that comes with your phone.
3.Now start regeditSTG.exe and change the following Registry Keys:
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001001 = 2
-> Change the value data from 2 to 1
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001005 = 16
-> Change the value data from 16 to 40
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001017 = 128 (mine 36)
-> Change the value data from 128 to 144
HKEY_LOCAL_MACHINE \Security\Policies\Policies
-> Add new value “0000101b”: Dword = 1
After you have done all these steps close Regedit STG with the task manager (TaskMan) of your phone and reboot. That’s it. Your phone is now totally application unlocked.

nah, application unlock is not CID unlock.
by the way, if you are a personal user, Hard-SPL is free for you, if you got any issues with using the Hard-SPL, you can always ask in the Hard-SPL thread.

this is like something SIM unlock ? or w