Database Develop

initflashfiles.dat -- Help Needed

So I've been playing around for a little while with the intention of creating my own custom ROM. I think I've got everything all figured out - however I'm having a problem that I think is related to the initflashfiles.dat file. Basically, after flashing my new OS ROM, my 8125 hangs at the splash screen with the version numbers on it. As a test, I redid my modified ROM, except I used the original initflashfiles.dat - this worked just fine. Tried it again by building the ROM with my modified initflashfiles.dat - same problem.
Here are the steps I'm going through.
1. Parse out the nk.nbf file using typhoonnbfdecode -x
2. prepare_imgfs 80040000-OS.nb -nosplit
3. viewimgfs imgfs_raw_data.bin
4. Modify contents of dump directory. Basically I've deleted files I don't need and added new ones.
5. Modifiy initflashfiles.dat (which I've attached). After modifying the file I open it in a hex editor and remove the first two bytes - making the first byte 3B (";"). I save it and mark it as read-only.
6. buildimgfs
7. make_imgfs 80040000-OS.nb -nosplit
8. Run nb2nbf_tornado.exe. I do run this correctly, using the correct memory address for the OS .nb file.
9. Put the new nk.nbf into an existing RUU self-extracting archive and run it.
It really seems like it's the initflashfiles.dat file - as I've successfully loaded this ROM with the original file (its really not the original, it's from a summiter ROM that I'm basing mine off).
Any thoughts?

I'm going to bump this once just in case people missed it originally.
I've messed around a bit more, and have pretty much isolated that this is my problem - but for the life of me I can't figure out what I'm doing wrong.

CameronJ said:
I'm going to bump this once just in case people missed it originally.
I've messed around a bit more, and have pretty much isolated that this is my problem - but for the life of me I can't figure out what I'm doing wrong.
Click to expand...
Click to collapse
Hi,
i see that the file you've attached isn't actually a .DAT file. It is a .dat.TXT that's the same that saying it's a TXT file!!!
If the file you're putting inside your ROM is this very same file (.dat.txt) then you've found your problem: you need a .DAT and NOT a .dat.txt file!!!
Try following this procedure on your PC (i suppose you're using XP or 2003 server):
- open a folder (whichever folder you like, it's not important)
- on the Tools menu click Folder Options.
- click the View tab.
- clear the Hide extensions for known file types check box.
- press OK
PS: Here is an illustrated guide on how to show file extensions
Now go to the place where your initflashfiles.dat is. If the file is named 'initflashfiles.dat.TXT' (like the file you uploaded in this forum) then:
- select the file
- press F2 (or right click and choose 'Rename')
- remove the tailing .txt from the name
Finally:
- let us know if it worked
Bye bye

risidoro said:
i see that the file you've attached isn't actually a .DAT file. It is a .dat.TXT that's the same that saying it's a TXT file!!!
Click to expand...
Click to collapse
:lol: Thanks for the reply.
I had to add the .txt extension otherwise the forum wouldn't let me upload the file (.dat files are not on the list of available file types for upload).
When I loaded the file I meant to put that explanation in there but forgot before I finished the post.

Hi. I don't know if you're still working on this, but I'd like to share with you my experience last night. I examined your initflashfiles.dat, and it is perfectly ok.
As I see in your initflashfiles.dat, there are a lot of folder customization like:
Directory("\Program Files\Task Manager"):-File("taskmanager.exe","\Windows\taskmanager.exe")
There is nothing wrong with this as we need the file to be in the right location. BTW, THIS FORMAT WORKED FOR ME. Just a thought, you might be editing the default.hv and user.hv (hives) to put in the registry keys of some applications?
My device (Himalaya) did not start out correctly and did not execute the initflashfiles.dat, BUT when I connected my Hima through active sync, you can actually explore the contents. SO, in this non-working state, I experimented in tracing the culprit, by restoring a couple of the original files I edited. I found out that it has something to do with the way I edited the hives.
Steps I made in experimenting:
1. I sync my Hima to my PC.
2. Copied the original default.hv to \windows directory
3. Hard Reset Hima, BUT answer NO to all three boot options
4. My Hima started normally and executed initflashfiles.dat to the detail.
Discovery from experiment:
1. The files were only copied to the directory were we wanted it, BUT the original file is still in the \windows directory. Therefore, we did not save storage memory.
2. We only benefitted from an already installed app built into the ROM.
Hope this gives you some insight.

Modded Cappackage.pxp Files

So I thought it would be worthwhile to create a thread focusing on modified "cappackage.pxp" files. These are the files which control the default carrier specific configurations. In my case, I am running the Aussie "Three" WM6 OS, however I wanted some, but not all, of the ATT customizations. For example, I wanted the proxy tool, the logos and the certs . . . Attached is a modified version of the ATT cappackage.pxp file. I had difficulty configuring WindowsMobileLive.cab and the HTC task manager to automatically install as part of this new file so I will post those cab files as well for convenience (for those who may want it).
If you have a customized cappackage.pxp, please post it in this thread and describe how it has been modified so everyone can decide which they may want to use.
Here are the changes I made to the cappackage.pxp file. Note, all of these .cab files should be possible to install directly simply by extracting from original ATT WM6 cappackage.pxp in case you happen to need one of them:
delete getgood.cab
delete getmail.cab
delete realplayer.cab
delete getmobitv.cab
delete cmradio.cab
delete attmallandmusic.cab
delete musicid.cab
delete jarguarrm.cab
delete gettelenav.cab
alter "Att_Settings.prov.xml" to remove messaging and Windows Mobile Live registry customizations
add install of new devstate.dll (exists in 3AUS cappackage.pxp and also in ROW 2.23 cappackage.pxp)
ABS
EDITED 12-30-2007: Note - this altered cappackage.pxp file is based off the "leaked" ATT WM6 ROM.

abs99 said:
So I thought it would be worthwhile to create a thread focusing on modified "cappackage.pxp" files. These are the files which control the default carrier specific configurations. In my case, I am running the Aussie "Three" WM6 OS, however I wanted some, but not all, of the ATT customizations. For example, I wanted the proxy tool, the logos and the certs . . . Attached is a modified version of the ATT cappackage.pxp file. I had difficulty configuring WindowsMobileLive.cab and the HTC task manager to automatically install as part of this new file so I will post those cab files as well for convenience (for those who may want it).
If you have a customized cappackage.pxp, please post it in this thread and describe how it has been modified so everyone can decide which they may want to use.
Here are the changes I made to the cappackage.pxp file. Note, all of these .cab files should be possible to install directly simply by extracting from original ATT WM6 cappackage.pxp in case you happen to need one of them:
delete getgood.cab
delete getmail.cab
delete realplayer.cab
delete getmobitv.cab
delete cmradio.cab
delete attmallandmusic.cab
delete musicid.cab
delete jarguarrm.cab
delete gettelenav.cab
alter "Att_Settings.prov.xml" to remove messaging and Windows Mobile Live registry customizations
add install of new devstate.dll (exists in 3AUS cappackage.pxp and also in ROW 2.23 cappackage.pxp)
ABS
Click to expand...
Click to collapse
Thanks, any idea if we can add another carrier in the carrier_db file that isn't there?

john_99 said:
Thanks, any idea if we can add another carrier in the carrier_db file that isn't there?
Click to expand...
Click to collapse
I honestly do not know. Sorry. You might ask Olipro as he seems to be very knowledgeable.

abs99, what tool did you use to repackage your PXP file. I've tried several archive tools to .ZIP and rename, but no joy. I've looked, but can't find any info on PXP file creation. Surely, I'm missing something simple here.
TIA

I found that "winrar" can handle the files without a problem. I had also noticed that the date stamps were the same for all the files in the original package, so I also use a tool called "stamp it" to set all the dates on all the files in the new package to the same original date.

thanks. I found that 7-zip is working too.
Now, the next step, I'm trying to mod the capdata.xml file and for whatever reason the device will not recognize it after my mods.
Here's my version of an ATT config file:
Code:
<?xml version="1.0" encoding="utf-8" ?>
- <Varnish xmlns="http://www.ephox.com/product/editliveforxml/document/Untitled20062026011007629">
<Version />
<Notes />
<UpgradePath>always|</UpgradePath>
- <PolA>
- <Certificates>
<File>CingularCert.prov.xml</File>
</Certificates>
- <Certificates>
<File>Class3_PCA_G2_v2.xml</File>
</Certificates>
- <Certificates>
<File>entrust_gssl_ca.prov.xml</File>
</Certificates>
- <Certificates>
<File>RSA1024RootCA.prov.xml</File>
</Certificates>
- <Certificates>
<File>RSA2048RootCA.prov.xml</File>
</Certificates>
- <Certificates>
<File>VeriSign_C3_PCA_G3v2.prov.xml</File>
</Certificates>
- <Ringtone>
<File>AT&T Tone.wav</File>
</Ringtone>
- <ProvXML>
<File>ATT_Settings.prov.xml</File>
</ProvXML>
- <ProvXML>
<File>MSFPHeartbeat.prov.xml</File>
</ProvXML>
- <ProvXML>
<File>ResetRequired.prov.xml</File>
</ProvXML>
- <InstallApp>
<File>WindowsLive.CAB</File>
</InstallApp>
- <InstallApp>
<File>ATT_Theme.CAB</File>
</InstallApp>
- <InstallApp>
<File>ProxyManager.CAB</File>
</InstallApp>
- <InstallApp>
<File>ATT_Content.cab</File>
</InstallApp>
- <ExtractZip>
<From>DevState.zip</From>
<To>\Windows</To>
</ExtractZip>
</PolA>
- <Welcome>
<WaitImage>E_PolishImage.bmp</WaitImage>
</Welcome>
- <Sweatshop>
<AccountName>GEN</AccountName>
<VarnishName>ENG</VarnishName>
<BuildName>005</BuildName>
<User>[email protected]</User>
<Environment>Sweatshop QA Staging</Environment>
<CoreVersion>1.9.9</CoreVersion>
<Treo750Version>3.0.0</Treo750Version>
<DateStamp>Wed Aug 22 6:10:15 PDT 2007</DateStamp>
</Sweatshop>
</Varnish>
Any thoughts? This is just a basic mod and plan to get more detailed configs in there once I figure out what I'm doing wrong.
TIA

The issue with this file may be that editor you are using is adding "white space". I found that some editors caused this to occur. I ended up the file in notepad to avoid the problem as it was a real mess to deal with any other way. You should open the original unedited file and your new edited file in notepad and compare both. For whatever reason, the OS does not like to deal with a properly formatted .xml file!

Thanks mate, the white space and file size were the culprit. Was trying to cheat and use MS xmlnotepad - very easy to use, but it added the whitespace as it made it pretty to look at. I also was trying to cram too much into my archive; the extracted archives need to fit in the 8.4mb along with the archive itself.
Attached is a custom CapPackage.PXP with the following (based from ATT 2.25 ROW, CapPackage.PXP):
ATT Theme
Regional Settings: US, - 5 EST
ExtROM mount and rename
Custom ringtone
Custom Sounds Settings
Delete poutlook.lnk from startup
Set Hello to ATT
Disable CAB security policy
Removed all ATT applications (CV, real, win live, etc)
TODO: Incorporate RegHacks of additional settings customization and tweaks (lots of typing...), right now I install and merge the apps I want after initial setup completes.
Cheers

HOW TO
***always a good idea to backup existing files before attempting any modification***
1. mount your extended rom (search for the cabs and instructions on this site)
2. copy the CapPackage.PXP from ExtendedROM\Partition to your PC
3. extract the contents to a folder named CapPackage on your PC (any ZIP compliant archive tool will do)
4. remove/add the *signed* cab files your desire (unsigned cab files simply get passed over)
5. open capdata.xml in epcEDIT or notepad.
6. add/remove the configuration information as desired - this is where some trial and error comes in trying to determine what commands control what function.
7. ZIP (no other archive format seems to work) the CapPackage folder to CapPackage.PXP (or rename .zip to .pxp).
8. copy to ExtendedROM and hardreset.
TODO:
-Hope to be able to post a list of commands for the XML to enable configure of most if not all device "settings"
-Hope to figure out a way to get unsigned cabs to install (present workaround is a zip extract and registry commands if the app isn't too complex (e.g. lots and lots of typing required)
--Not sure yet if reg hack setting "HKLM\Security\Policies\Policies' valuename '0000101a' to dword:1" will resolve this during initial setup

Okay, after getting my questions about how this all works and saves the space on the phone, I took the plunge and upgraded from 2.23ROW to 2.25ATT. Went smooth as butter, and I have a "decrapified" phone with the official, supported ATT release (just in case I have any problems and need support).
Of course, being a hacker, now I'm totally intrigued by this cappackage customization, and want to play with it myself. So, Tim et. al., two questions:
Does the capdata.xml file have to match the contents of the archive? Or, if something's missing, it's just ignored? I'd like to be able to delete some more stuff and remake the PXP file without having to hassle with the XML file and run into the problems you have (workable, but I just don't want to waste time on whitespace issues if I don't have to).
Does the carrierDB file need to stay in the extended ROM for any reason after install and setup? I'd like to archive it on my PC, and delete it from the extrom so I can use that space for general storage.

microsoft word has a wonderful xml file editor. rather than try and keep everything straight in that jumbled up mess you get out of notepad or some other editor, word indents all the xml, and makes it look like it should. it was a snap to edit. I used Winrar and opened the PXP file. I never extracted the contents. Just the capdata file. I edited it, and then put the edited version back into winrar. using winrar I deleted the files I didn't want. saved the archive and moved it back to the device.

dwallersv said:
Does the capdata.xml file have to match the contents of the archive? Or, if something's missing, it's just ignored? I'd like to be able to delete some more stuff and remake the PXP file without having to hassle with the XML file and run into the problems you have (workable, but I just don't want to waste time on whitespace issues if I don't have to).
Does the carrierDB file need to stay in the extended ROM for any reason after install and setup? I'd like to archive it on my PC, and delete it from the extrom so I can use that space for general storage.
Click to expand...
Click to collapse
1. The XML will bypass anything it can't actually do.
2. I have tried it both ways and feel like I've had no issues, but I have seen some reports of strange behavior without it. I currently have it in my ExtROM since I hard reset my device often as I test apps and config settings. If you don't hard reset very often then once the device is hard reset you may delete and gain an additional 1.45mb.
The thing I intend to work on next is creating a provisioning XML to call an external XML (outside of the cappackage). I'm hoping this way I will be able to strip even more out of the cappackage (literally everything but the capdata.xml) and hav an on the fly configuration capability and call installations and configuration from the SD card. Haven't had much time to play with it though.

Can someone help point me in the right direction to get start loading the cappackage. I can't seem to find how to mount the extended ROM. I did a search for it and everything that came up didn't explain it (or at least I didn't understand it if it did).

Hmm, I can't seem to find the original thread either. Really just registry entries, but the cab's make it easier.
See attached...
Run each in order, then soft reset
Cheers
FYI: You can use my cappackage (see pg 1) as a starting/reference point for building the extROM mount into the initial config process after hard reset...

Try this. ...............
sodak said:
Can someone help point me in the right direction to get start loading the cappackage. I can't seem to find how to mount the extended ROM. I did a search for it and everything that came up didn't explain it (or at least I didn't understand it if it did).
Click to expand...
Click to collapse

Thanks to both of you for the quick response

I don't know whether it is because of this or because of something else. But I started modding this CapPackage file, and all of a sudden my treo just started acting weird. I had to hard reset it several times throughout the day. Then I upgraded to the 2.25 WM6. And that is where **** really hit the fan (I upgraded and put my own CapPackage version in it). And after that I've had nothing but trouble. Soft resets didn't work anymore, it just crashed on the boot screen. Hard resets work, but really slow, takes about 20min. So now I'm re-upgrading to 2.25 and just leaving that CapPackage file alone for now .
The tale away message: Don mess with this unless you know what you're doing, which isn't me
-Robert

Run SD Cab with autorun.exe

hello
i need to add a username into the registies for a number of devices i'm flashing. Unfortunatly the usernames all need to be different i.e. PDA001, PDA002 and so on...
I've created a number of different cab files each for a different device that will add the username in.
So is it possible to run the cab file off the storage card as part of the hard reset process. i've updated the SD card with the file Username.cab which is the name of all the cab file, then added "CAB: \Storage Card\Extended_ROM\Username.cab" in to config.txt which is in the Extended ROM. i tested it but it didn't work.
Has anyone got any ideas
Or may be have a shortcut to the cab file added into start up. Would that work?

I'd suggest that you instead edit an existing (or relatively insignificant) CAB file (that you'd probably have no use for anyway) with the registry entries/additions so that its guaranteed to be included when you do the Extended ROM customization.
Did you ensure that you copied all the files from an original extended ROM correctly (before making your modifications)?

The thing is I have around 250+ device which need flashing with the same image and as all the devices will require a different Username adding into the registies I 'll need to run an external cab file, a cab file which will be different for all the devices and it's best to run it from the SD card.
I tried to adding a cab file into the Extended ROM which will install a shortcut into the startup folder the shortcut is to the cab file on the storage card. But for some reason it didn't run.
I have a couple of SD cards with an image of my Extended rom on so if anything goes wrong i have the backups.

Whats wrong with having the 'end-user' maually execute the .CAB file?
Why don't you simply customise one PDA (the way you wan't with your preconfigured settings) (minus the user/device name), then do an entire backup using SPB BACKUP (onto a SD Card). You can then restore this image on all 250+ devices (sounds time-consuming,but it really isn't).
All the end user had to do, is to manually execute your .CAB file when they are issued the units.

This is your true answer (in my opinion):
http://www.spbsoftwarehouse.com/products/backup/?en

RE: Whats wrong with having the 'end-user' maually execute the .CAB file?
Basically the devices are used by Market research interviewers who work for us, most of whom are not familier with the devices and are not computer litterate. I'm responsible for a small support team and also the development of the devices. The software we use is already extremley simple and all they need to do is click a buttom "Connect" if the username is not already inserted they get a box "Logon Failed, please check the following details are correct." and a username and password box is displayed and they simply need to type in the id number from the sticker on the back of the pda (like PDA001).
We have just had a large project in feild and over the period we have around 200+ user. Around 50% of the call we took, at some point they had problems entering the username. As much as SPB backup would be of use, if they can't already do a simply thing like type in PDA123, asking them to do this seem like asking alot and would probabily cause more issues.
We already have all the other information in the registries for this application and the username is the only thing which isn't consistant through out.
Do you know if it would be possible to prompt them to run the cab from the sd card which enters the username into the registires on startup?

Nunwood PDA said:
Do you know if it would be possible to prompt them to run the cab from the sd card which enters the username into the registires on startup?
Click to expand...
Click to collapse
Sure it is possible. Did you already try placing a shortcut to the .CAB in "Windows\StartUp" ?. Likewise, you can easily create another script that deletes that shortcut (to ensure that its only used once).
Please keep us posted, on your developments.

Nokia 3650 said:
Sure it is possible. Did you already try placing a shortcut to the .CAB in "Windows\StartUp" ?.
Click to expand...
Click to collapse
Yeah, it didn't do anything. I had a cab file in the extended ROM which placed the shortcut in the dir. \Windows\startup\. For some reason nothing happened, but when I navigate to the .cab file it ran without any problems.
When you say create another scipt, how would I go about doing that? If i had an .exe it could act as a link to the cab on the SD card. i'm not familier with this kind of method. But I think that would solve the problem.
The location of the .cab is: \Storage Card\Help\UserName.cab

Thanks for the exact location. I'm just compiling something for you in visio Studio 2005, that will execute the .CAB file when run at automatically from startup (it'll do this only once).

A method for more speed , more free memory on the phone.

Here http://forum.xda-developers.com/showthread.php?t=493628 is a method for compressing the .exe files of the phone. I successfully have compressed 104 .exe files of windows folder . By doing this, every program run faster (smaller loading times) and you save space because every program is smaller . I earn about 12 mb. Untill now everything seems to work ok. This is the list of the 104 .exe files of windows that i successfully have compressed. The phone has been extremely fast. If you want to try it , do it on your own risk..
catalog.exe
CommManagerLink.exe
LaunchMSItem.exe
MobileCalculator.exe
tdsserver.exe
WelcomeCenter.exe
AdvancedConfig.exe
__cusTSKTEMP.exe
_mp07.exe
_mp08.exe
AdvancedNetwork.exe
AlbumSearcher.exe
ArcMC.exe
arinvalid.exe
AudioBooster.exe
AudioManager_Eng.exe
AutoAttribute.exe
AutoFormatMoviNAND.exe
AutoRun.exe
AutoShortcut.exe
Biotouch.exe
btdwake.exe
BTFtpClient.exe
btlauncher.exe
btrenamedir.exe
CheckAutoRun.exe
ClearStorage.exe
CommManager.exe
ConfigureDevice.exe
ConnectionSetup.exe
ConnectionSetupAuto.exe
DataDisconnect.exe
DeviceInfo.exe
EndKey.exe
EngInfo.exe
eT9MyWords.exe
FaxView.exe
felvop.exe
FieldTest.exe
FMRadio.exe
GAlarmWakeup.exe
HACSetting.exe
HTCMessage.exe
HTCStartUp.exe
HTCUSBToPCPopUp.exe
IA_Zip.exe
JBlend_AMS.exe
JBlend_VM.exe
KeyLock.exe
Labyrinth.exe
LongPressEndKeyApp.exe
ManilaActivateToday.exe
ManualFormatMoviNAND.exe
MicrophoneAGC.exe
MP3Trimmer.exe
NewMailAccount.exe
OneNoteMobile.exe
PhoneAgent.exe
PlayShow.exe
Powerexe.exe
PowerOffWarning.exe
ppt.exe
pword.exe
pxl.exe
QuickGPS.exe
Recorder.exe
Redial.exe
RegistryCSPTool.exe
remote.exe
RUpdate.exe
saplaywm.exe
SAPSettings.exe
sdpready.exe
SignatureReplace.exe
SIM_MGR.exe
SIMLock.exe
SIPGT_app.exe
startkey2.exe
StartUPBioTouch.exe
STK_UIPPC.exe
StopEvtSnd.exe
StorageLow.exe
StreamingPlayer.exe
TaskManagerApp.exe
TaskManagerLite.exe
TFSettings.exe
TmAppLauncher.exe
Transport.exe
USBtoPC.exe
VCDaemon.exe
VocabSetting.exe
VoiceCommander.exe
voicemail.exe
VTKey.exe
wcsan.exe
WLANSettings.exe
WLMImageUpdate.exe
WLMLauncher.exe
WLMMessenger.exe
WLMSetup.exe
WMADBG.exe
xT9Settings.exe
YouTube.exe
ZipView.exe

Intersting concept, i assume the speed gain is from the extra memory?
Is there a downside to this? Do the compressed applications take longer to load when you wish to use them as the device would have to decompress the file before using it?

And what method have you used for compressing?

Interesting
Yea this does seem interesting.
I'm gonna watch this one.
i can't see how compressing the files could make the device faster though, 12 of storage is nothing, you would need system memoryto make the device run faster???
if the files where to be compressed and still be able to execute with out a decompressing of the files then hay thats cool, but im not sure if thats possible.

The phone IS faster when you press some things. My english isn't good enough to describe it but , many things are faster. It is not my imagination . For example camera is loading faster i think, and when i press start-settings-system , it opens almost immediately. First it needed some seconds. I believe that the loading times are smaller because files are smaller , and the reading time is not the best by the storage memory used by the phone. By making files smaller , loading times are better even though the files are compressed . I am not sure for the theory but the phone works better. Look and at the link i gave. I only posted here so you know about the link. Also you earn storage space without loosing anything!

i did the same some time ago. i also compressed dll-files. now the diamond IS FASTER.
i used "upx mobile". try it yourself.

beginners question
i tried this method and copied the file in to the windows folter with total commander - over active-sync I could not overwrite the files. But now even less space is available..
aand.. when i copied all the files it asked me only about 5 times if i wanted to overwrite this file... so my explanation is that these are files which are stored in the rom.. so they got not overwritten but only doubled...
is this possible? and what can I do about it?
=> the problem is of course the data-memory and not the programm-memory => it really seems that the files are doubled...

i tried to move the packed files back to the diamond, but its nearly impossible....
the file listing is slow, i cant move them back because the diamond doubled the files, it doesnt ask to overwrite...
i tried it with total commander
so now i copied all files to \windows\
and now i have only 1mb of space free.....................
something must have gone wrong...
can someone please post a guide how to copy the packed files back to the diamond
€dit: so now ive rebooeted the diamond, and its very fast and i have 3mb of storage free now, but its not enough... something is wrong

hi
today i tried this method, too. packing was no brob, but copying back compressed files into windows folder failed with nearly every file of 105 because of displayed write protect error message. only 2 or 3 files worked in the end.
also i compressed tomtom.exe. but after that loading time did not increase. was more the other way arround!
in the end i replaced all compressed files by originals again...

sm4rty said:
i tried to move the packed files back to the diamond, but its nearly impossible....
the file listing is slow, i cant move them back because the diamond doubled the files, it doesnt ask to overwrite...
i tried it with total commander
so now i copied all files to \windows\
and now i have only 1mb of space free.....................
something must have gone wrong...
can someone please post a guide how to copy the packed files back to the diamond
€dit: so now ive rebooeted the diamond, and its very fast and i have 3mb of storage free now, but its not enough... something is wrong
Click to expand...
Click to collapse
I imagine you only had 3mb of storage left because the files you were trying to overwrite were stored in ROM...which you cann't overwrite. Instead Windows stores your new compressed version in storage. Effectively you have two copies of each of those files on your device; 1 copy in ROM and 1 copy in storage. This technique for compressing exe's is probably only useful for new applications installed on your device (like Opera & TomTom) or if you were to cook a new ROM with the compressed exes.

Error
This sounds great! But i get this, when trying to compress: upx: 3_Compressed\MobileCalculator.exe: CantPackException: .NET files (win32/net) are not yet supported.
Any idea?
Edit: hmm.. i only get the error with these files for now: MobileCalculator.exe, tdsserver.exe, WelcomeCenter.exe, AdvancedConfig.exe...
Other .exe's compress just fine..

Moving icons to different folders ?

I have ATT Tilt with TPC's stocklike rom, and whenever I go into file explorer and move files in Windows/Start Menu into a different folder, such as a Start Menu subfolder, my phone seems to not understand the change in the filepath, as shortcuts and icons stop working and eventually a hard reset occurs. So I assume in order to organise my icons, I will have to edit the filepaths in registry? Could somebody please point me to where and how to do this, or to a program which will facilitate the changes I desire to make? Im sorry if its a noob question, I have looked around the registry a bit and only managed to become confused and frustrated. Any help will be greatly appreciated.

please describe your intent a bit more precisely...
what i understand is that you simply want to organize the icons/links in your start menu into subfolders...is this a correct understanding?
if so, then you must first understand that files already present in the "\Windows\Start Menu" folder are actually "links", or shortcuts. you can freely move these files into subfolders rooted at "\Windows\Start Menu".
if you are moving the actual program files that these shortcuts point to, then that will cause all sorts of problems, such as what you describe as "shortcuts and icons stop working".
so the idea is to move existing shortcut files as you see fit. if one or more programs/applications don't appear in the start menu, first create a shortcut file to the said applications. leave the application files where they are and place the newly created shortcut in the "\Windows\Start Menu" folder or one of its subfolders to your liking.
i suggest "total commander" to perform advanced file and folder manipulation. it will also allow creating shortcut files as well as editing the paths stored in shortcut files (if i remember correctly).
finally, the device should NEVER hard reset on its own, even for pretty big screw ups with moving files around. most program files will be unmovable with the regular file explorer anyway. so, the operating system effectively protects and prevents major f-ups anyway.
if you are using one of TPC's WM6.5.x ROMs, you will read in the FAQs for nearly all WM6.5.x ROMs that the ONLY known and reported reason for the device to hard reset on its own when using one of these ROMs is if you did not flash a "stock ROM" first before flashing said ROM.
hope this helps...

Thanks a whole bunch!!
Moving my icons into subfolders was exactly what I was talking about. I hahd thought that that rom was the one 6.5 rom that you didnt have to flash stock first, but I was wrong. Flashed stock then flashed back to the rom & radio and it worked like a charm. Cant believe I missed such a simple step, but definitely a big thanks for your help and knowledge!!