Database Develop

Another test: Wizard ROM ported to BA

Edited 26 jan 2006
I've uploaded a second test version of HTC Wizard's rom port to ftp://[email protected]/Uploads/Blueangel/wm5_test/wizard2ba_v2a_test.rar
(this is a v2 rom with a fixed camera)
USE THIS ROM AT YOUR OWN RISK!!!
This version is a complete Wizard's ROM including:
1. Working MMS client
2. Midi/mp3 ringtone support
3. DirectX mobile/Direct3D mobile (xscale-optimized 3D driver)
4. Built-in cyberon voice-dial
5. Wizard's battery indicator, device lock on today
6. Some cosmetic changes
7. 32 Mb RAM disk
8. Bug fixes from the previous version (for example now you can add picture to contact).
There is no need to install any of the old CAB-files with fixes on this ROM. All needed fixes are included in "EXTROM" folder.
The "EXTROM" folder has changed from the previous ROM version. You need to do a hard reset before using this ROM!
Known problems:
1. Bluetooth disconnect bug is still there. I have an idea, but would check it later.
2. The device cannot be used as an IR/USB modem. This can be fixed, but I don't have enough time.
3. It seems that midlet manager is not working. Probably this is a bug in original wizard's ROM.
Installation instructions:
1. Modify the operator as needed and if needed:
xda3nbftool.exe nk.nbf nk.nba -x 0x20040521
...read wiki...
xda3nbftool.exe nk.nba nk.nbf -x 0x20040521
2. Create "EXTROM" foder on your storage card, copy there the contents of EXTROM
folder from this archive. The full name of this directory on your device should
be "\Storage Card\EXTROM".
2. Flush the ROM
3. Make the hard reset (press camera+record+reset buttons, select "format storage")
4. Boot. During the first boot the CAB-files from "EXTROM" folder would be
installed. They are unsigned, so you should press "yes" when asked, and
install them to the default folder. This process would be silent on newer
builds of this ROM.
Note for modifying the EXTROM folder:
All CAB-files should have read-only attribute set. Otherwise they would be deleted after installation. This would be fixed in the future releases. And
Config.txt is renamed to Cfg.txt.
CAB files:
Missing-Files.CAB - must be always installed. Wizard's ROM is larger than ours, so several files had to be removed and placed to this CAB.
Default_CAB-shortcut-CDL-08Sep05.CAB
Default_cdl_wwe_version.cab
Default_ie_view.sa.cab
Default_SmartDialing_enable_0915_signed.CAB - these 4 are from original Wizard's ROM.
Camera2K5.cab - camera app and drivers
Note regarding "RAM Disk32". I recommend to move temporary internet files and install unnecessary apps there. Its contents would survive soft reset, but would be cleaned if the battery is removed. The RAM Disk driver is taken from www.buzzdev.net

Okay, so I got the ROM even before you posted this topic (after an hour you've uploaded it...yes, i do check the WM5_test folder on a regular basis, hehe) First impressions is that this ROM is fast, really fast, even faster than the Hima2BA port... I can't really call WM5 "slow" anymore now, it works very well. Gonna test it a bit more later today. And THANK YOU, as usual

Just turned on cleartype and the fonts looks a bit...I don't know...weird. I'm not saying that it is worse than in the older ROMs, it just looks different somehow. Or it's just me. Edit: yes, they *do* look different. I'd say they are nicer though...

install Camera2k5_1 ,it is owrking for camera , this rom fast than others, Pocker msn can't login " sorry, We are unable to sign you in to this service because we could not detect a valid server certificate. this can occur if the date on your device is different from today date.please check the date on your device and change it if necessary.
also missing phone icon at person settingn't set ringtone

hi mwang,can you tell me where can download Camera2k5_1 ,thanks

Mamaich, what can i say, outstanding, as usual...Testing now

great man...
picture and video application isn't working though :?

working awesome, does anyone know how can i install BT Tray?
thanks mamaich

In Phone, Options doesn't work, smartdialing doesn't work...

2. "ok" hardware button is mapped to "record" and this cannot be changed. Would investigate this.
Click to expand...
Click to collapse
Strange. In my device it's mapped to the OK button as in 2003..

Bugs that I found:
1. MSN Messenger does not work
2. Phone Option does not work
3. Unable to assign picture from contacts
4. MP3 ringtone does not work
5. Voice Command BT Headset Dial (by renaming voicecmd.exe to sddialer.exe) does not work

MP3 ringtones work for me

Phone, Options isn't there. comfirm.
Hope to have a fix for that soon.

This ROM is a bit faster, but still no match for wm2003se speed..
Another problem is that I don't seem to be able to connect to the internet using AS, is it just me?
Guess it's back to 2003 for now..

d3vil said:
This ROM is a bit faster, but still no match for wm2003se speed..
Another problem is that I don't seem to be able to connect to the internet using AS, is it just me?
Guess it's back to 2003 for now..
Click to expand...
Click to collapse
I'm back to 2003SE too, currently doing restore. Guess have got to wait for some patches. I must say the speed of this is better then any other WM5 version.

wlinsong said:
hi mwang,can you tell me where can download Camera2k5_1 ,thanks
Click to expand...
Click to collapse
over here http://forum.xda-developers.com/download.php?id=6645

I'll put together quickly a WiKi article with solution to the missing phone settings and such..stay tuned.

WiKi article with solutions and general info here (and also in my signature)

There are no notifications of current internet connection, i mean wifi bluetooth or gprs in the titlebar (like those in himalaya ported WM5)
There is still error when you press album icon in camera app, which can be fixed with installing album
The hardware button OK is mapped correctly , it works fine here
The record button is mapped as Voice Speed dial (the record app is there but doesnot work)
How can i get the tray icons of bluetooth and wifi ?
I like the new battery tray icon

Port to SX66
Great work Mamaich.
Installation was very smooth. The WIki solution to the missing phone icon was a big help. I prefer this version over the orginal WM5 or the himalaya version. I like the EXTROM installation. Not having a camera installed is a big help to SX66 owners, we don't have to deal with the sound issues. Finally got a midi ringtone to work with the wizard version, prior versions I had to convert the Midi to MP3. I have had it lock up on me a few times, but haven't figured out the cause yet.
Thanks again.

Applicationlock MTeoR

Hello,
today I get my HTC MTeoR.
For my Exchangeserversync I need to install a other root certificate.
But the Phone had a Applicationlock.
All known solutions for other HTC Phones don't work.
Have anybody a new solutions?
Regards
sotmysoft

I got the same problem, and after speeking with both the Danish & English HTC support, they both told me to wait for a rom upgrade or check for modification to "registration database". I have now looked through the whole internet and so far nobody seems to solved the problem.
So now i have HTC MTeoR as a brick, and a HTC TyTn send back because of problems with screen and keyboard !! Well done HTC !!
Peter
sotmysoft said:
Hello,
today I get my HTC MTeoR.
For my Exchangeserversync I need to install a other root certificate.
But the Phone had a Applicationlock.
All known solutions for other HTC Phones don't work.
Have anybody a new solutions?
Regards
sotmysoft
Click to expand...
Click to collapse

I have read somewhere that you need a special Regeditor which is recognised by the HTC and then change the following Key: HKLM/Security/policies/policies
00001017 from 128 to 144
That did the job on my QTEK 8500

...what does this policy do? Mine contains the value 148...

Have read the same on the net, but does not work on MTeoR.
Peter
Churchill said:
I have read somewhere that you need a special Regeditor which is recognised by the HTC and then change the following Key: HKLM/Security/policies/policies
00001017 from 128 to 144
That did the job on my QTEK 8500
Click to expand...
Click to collapse

I think it enables you to install a certificate

The reg hack that has worked previously for other WM5 devices doesnt work on the Mteor. In fact, you get a permisison denied error when trying to change the value.
Apparently HTC are working on a new ROM but can't give an ETA :evil:

What is this?
Has someone ever tried this registry editor?
It seems to work with MTeoR, but I don't have it yet...
ftp://xda:[email protected]/Uploads/Breeze/regeditSTG2.zip

I used the one called regeditSTG but I think it is the same thing...
My device is QTEK 8500 and the regeditSTG works on my device

Confirm that regeditSTG2 DOES unlock the Mteor, but the phone will not let you copy this app to the phone or to the card- so it has to be copied from a computer directly onto the storage card before using. Then it works!
Thanks guys, this is a real breakthrough

I have found another thing in the HKLM\security\policies\policies add the following DWORD "0000101b" value 1
I found it by Modaco. There this is a solutionif you get error 57 when running some software. BUT and this is big, when I added the value my TOMTOM received a new Device ID so it asks to activate and this being the second device that I activate I have to keep on changing the value to 0
Does anyone have for me maybe cracked version of Tomtom 5 mobile v5.20 for Windows smartphones with QVGA display (not symbian)

Solution i've found was posted by Pagemakers on the Expansys forums...
http://www.modaco.com/Mteor-application-unlock-solution-t244205.html
Tested and working. Allows you to import root cert and also the stops the insufficient permissions when installing software.

MTeor unlock
howdy,
does anybody know how to unlock HTC MTeor?
seems to me that the device is unable to edit the registry.
(I'm installing a root certificate)
already installed on Qtek 8310 and 8500 but the registry on MTeor is uneditable..
Any suggestions ?
Thanks

Here is most "official" way of application unlocking of virtually any HTC produced device: one third of unlocker is made by HTC and remaining two by M$
Unzip to device and run in numbered order. Then check incoming sms folder* for the status report. If report is negative then your rom have non-default privileged OEM cert, flashing to something more standard would solve the problem.
* it is not real sms, just system notification placed in sms folder (nothing is transmitted over radio) you can perform unlocking with phone turned off and sim card removed to be shure

Is there a version of Quickgps that works on HTC P3600??

Is there a version of Quickgps that works on HTC P3600??
i tried it but it gives a connection failed error

Try this one. It's like in Kaiser (have same registry values). http://4pda.ru/forum/attach/1863057/VolROM_QuickGPS_RUS_v1.00.cab
But don't forget change region setting to your own in hklm\software\htc\quickGPS
Oh, i forgot, it's russian version. There are two mui in windows directory: Gps_aux.dll.0419.mui and quickGPS.exe.0419.mui. So rename it to 0409 for working in wwe rom.

added.
PS: this version downloads xtra.bin file which used by qualcomm based devices (Kaiser, Polaris, Diamond) with GPSOne chip. I think it will work on Trinity (also GPSOne chip) but we don't complete all tests yet

In fact, the region settings in the registry is RU...but what it should be set? then, i renamed the .mui from 419 to 409...but i still get very nice russian interface! Could you please explain it in more details? thanks indeed in advance.
but, most importantly....do you observe any improvements in the fix?

pzucchel said:
In fact, the region settings in the registry is RU...but what it should be set? then, i renamed the .mui from 419 to 409...but i still get very nice russian interface! Could you please explain it in more details? thanks indeed in advance.
but, most importantly....do you observe any improvements in the fix?
Click to expand...
Click to collapse
You can get QuickGPS app which you like (English or other). All necessary registry values in attached cab! So, we only "teach" QuickGPS download right file.
Region settings=Country name. Russia=RU, Italia=IT, France=FR, Belgium=BE etc.
I don't complete all tests... BTW, i will say that it work (sometimes). Ex: I do HR, install QGPS, get fix, run GPSinfo, but there is no satellites listed and i get standard fix (very long, apx 200 - 230 sec).
Ex2: At the evening i trying one more time. Same schema: I do HR, install QGPS, get fix, run GPSinfo and i see that all satt in their positions. Fix get in 45-47 sec. I don't understand why.
Syncronisation with PC back up FIX? Any ideas?
(and sooo sorry for my English)

Thanks guys for your great help
I actually got quickgps to work by installing 2 versions
the first is the 760kb then i install over it the 238kb version and then restart and it works like magic
now i can get a cold fix in few seconds

I look this two cab files. First (larger) identical to my russian cab, but english version. Second look like a cab for sirf based devices. setup.xml in it have many "waste" registry keys... and i see that it reconfigure gps com port... i'm right?
Please, make HR, get fix and tell us: do you see sattelites in their positions after that?

Hi G-Max, I have just installed the two files; how do I "make HR, get fix" to see if it works?
On registry the right country code shows. but in folder 0, 1 and 2 the default region is not set; could be the problem?
Cheers
Update 1,
Started TomTom 7 and not much of the difference noted.
Update 2,
Downloaded service.mio-tech.com/eeservice/packedephemeris.ee and placed it manually in Windows folder and Voila connected in less than 10 seconds.

thx bro this will help full, on my gps
i want to ask , i have edit my registry
HKLM/ControlPanel/GPS seting//
in grup i made value 1
defalut is 0
seem like so much difrent
my regart

is there no easy installation for the fast-gps-fix for all windows versions and without hardreset?

New ROM 5.2.19593 (Build 19593.1.1.7)

131 Dpi v1.xxx
DOWNLOAD(All Roms are protected please use kitchen to cook your own rom)
version 1.044 (9.09.08)
http://rapidshare.com/files/143800127/FLASH-1.044.rar.html
T9 dictionaries for other languages
http://rapidshare.com/files/136945310/t9.rar.html
The same rom (Skin) as my last one (search forum)
New Drivers - DONE
New OS - DONE
New XIP - DONE
BUGS
White Caller Screen - Solved
Wrong Icons - Solved
Wrong Shortcuts - Solved
Redundant Task Manager - Solved
T9 & Keyboard - Solved
bt management(moved to power-commanager-bluetooth) - Solved
Data Connection - Solved
DPI data - Solved (my mistake)
SMS - solved
Enterprise data - solved
missed calls indicator - solved
I am not responsable if you brick your device
PLEASE POST BUGS IF YOU FIND

Version 5.2.19593 (Build 19593.1.1.7) 96 Dpi v2.xxx
DOWNLOAD (5.09.2008)
http://rapidshare.com/files/142863999/FLASH-v2.065.rar.html
dlls from other versions are not compatible
i need to reconstruct every 96dpi dll so there can be bugs
please post bugs specifiing 96 dpi version
All Found bugs solved
Start menu is usable only in list mode (wm6.1 hardcoded)
NEW ICONS

KITCHEN 5.2.19593 (Build 19593.1.1.7)
131 Dpi
Download (08.09.08) - Latest Version(Creates Protected ROMS)
Optimised kitchen with latest bugfixes v1.044
http://rapidshare.com/files/143800317/Breeze_WM_6.1_131_19593_19593_v1.044.rar.html
96 Dpi
Download (15.08.08)
Optimised kitchen with latest bugfixes v2.063
http://rapidshare.com/files/137519577/Breeze_WM_6.1_96_19593_19593_v2.063.rar.html

good!i waiting......

So... This ROM still don't have Swedish T9?

first build is released v1.0
it seems to be very responsive and to manage better power
Drivers are updated
please help me find bugs
BR

Black and green homescreens? I'll like it!

how about proper SDHC support?
I tried many Breeze ROMs (cooked and official) - everytime the same. After wakeup (from sleep mode), SDHC card can not be read. Re-insertion fixes problem. It happens only with SDHC card. old SD cards are working fine.

sorg said:
how about proper SDHC support?
I tried many Breeze ROMs (cooked and official) - everytime the same. After wakeup (from sleep mode), SDHC card can not be read. Re-insertion fixes problem. It happens only with SDHC card. old SD cards are working fine.
Click to expand...
Click to collapse
driver bug
till we will find an proper driver we cant fix this
blame htc
BR

Hi,
just flashed the new ROM. Works so far.
But Bluetooth doesn't work. There is just an icon named "device name" under settings/connections. Clicking it results in an error could not open settings".
Any chanze to get BT working?
Thanks.
Rene

Bluetooth works fine, when switched on using commmanager.
No GRPS Connection (GPRS, 3G). Tried all possible settings.

Oh thanks.
It works! I haven't used com-manager yet, so i just tried the bluetooth icon.
Rene

Minor Bugs - First touch
First of all thank you for your work Jerpelea, it’s good to see that is someone out there which didn’t forget the Mteor users.
Rom looks ok; there are some minor bugs like:
1. The data connection is not working;
2. There are two Device name options, one in the connection (that is not working) area and one in settings (the correct one);
3. There are two types of Comm Manager, one in the connections are (just with two options Bluetooth and Phone) and one in the main menu which is looking great … from here you cannot touch data connection, is grey marked.
That’s all on the first look, I will try to see if I can find more in the next days.
Good luck

clio09 said:
Hi,
just flashed the new ROM. Works so far.
But Bluetooth doesn't work. There is just an icon named "device name" under settings/connections. Clicking it results in an error could not open settings".
Any chanze to get BT working?
Thanks.
Rene
Click to expand...
Click to collapse
thanks
in the next release will be fixed

new 15.08.2008
96 dpi rom & kitchen launched

For some reason I can flash anything in my machine.
SSPL doesn't show serial or usb sighn and device is not recognized by any RUU. Same happens whithout sspl!
Any suggestions???
UPDATE:
Damn IDIOT I am
Forgot to remove memory card

finaly i found the connection bug
all found bugs resolved
THANKS for help

Just flashed your 1.011 version and now I've got:
1. High Resolution (higher then privios one)
2. White squares in top bar!
3. Commmanager looks a bit screwed up. All the buttons are in one line, but using joystick can switch between them.
Did I do something wrong or what?

vasil said:
Just flashed your 1.011 version and now I've got:
1. High Resolution (higher then privios one)
2. White squares in top bar!
3. Commmanager looks a bit screwed up. All the buttons are in one line, but using joystick can switch between them.
Did I do something wrong or what?
Click to expand...
Click to collapse
please reflash 1.011a
my mistake
i forgot to set the dpi

hi
could u help me in an easy steps how to upgrade my spl and ipl
i tried every possiple way but invain
to be able to flash new roms
thanks

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.