Hello,
Have installed TomTom 5.1 but the program does not find the maps located on my SD-card. Is there a setting somewhere to tell TomTom where to find the maps??
Finicky program.
from my blog, http://www.beyondthetech.com/blogs/kjam/2005/10/surefire-method-of-installing-tomtom.html
...
On your desktop, launch Notepad.
Type & \Storage Card\New-England_and_Mid-Atlantic-Map\ or whatever the name of your main map folder is on your mini-SD card. Do not forget to add the final backslash and a have a space between the ampersand and the first backslash.
Save the file as CurrentMap.dat. Make sure it doesn't end up as CurrentMap.dat.txt!
Create a folder on your K-JAM called \My Documents\TomTom.
Copy your newly created CurrentMap.dat file from your desktop into \My Documents\TomTom on your K-JAM.
...
Wierd...dosent work.
Have created the CurrentMap.dat -file and made sure that it does not have the .txt extension.
Have created the Folder /My Documents/TomTom and put the file there
As I have a Swedish version of OS I also created the Swedish version on that map...also tried to copy the file to the /program/Navigator folder where the exe file is located.
Have done a complete reboot but the program stil don't find the maps...
Also made sure the Path and spelling was correkt "& \Storage Card\Scandinavian-Maps\"
Is not Scandinavian.Maps but *.Map. Also you not have to create a folder My documents because this folfer already exists in PDA storage. Is a system folder.
Yeah, infact it says "& \Storage Card \Scandinavia-Map\" witch I have verified on the storage card to be the correct folder name.
And you are right..I did not created the acctual My Documents folder but the TomTom folder was created.
Have looked at a friends CurrentMap.dat file (where TomTom works) but there seem to also be some other data that the TomTom software probably creates...my guess would be it's binary data. Have tried to copy my friends file to my K-Jam but stil no success.
Same problem here, tried all options I can come up with, and as soon as I revert back to tomtom 5 the map is found again.
Which lead me to believe that the "currentmap.dat" file at least is correct, or have they changed somtething with it in v 5.1 ?
fahlis: The update doesn't change anything in \my documents\tomtom folder.
Sedvese: my curentMap file is as follows: \SD Card\Iberia_Plus-Map\
If you want I can sen you the file, you open it with notepad and replace Iberia_Plus-Map by Scandinavia-Map. Who knows it can fix your problem.
Related
Hello,
As everybody already knows there are some serous problems with Qtek9090 device type models and carkits. A nice echo is produced when somebody is calling. I have a wavedev.dll file that should resolve this issue but I can't replace it on my Qtek9090 because it's a system file. How can I force this replacement?
Thanxz for any response, I bought this complete set and i'm thinking about it to return it. Operator T-Mobile, rom1.40, radio 1.20.
Peterpanman.
rename existing wavedev.dll to wavedev.bak, copy the new file and reboot.
Just curious but is it definitely Radio 1.20 or 1.12 as 1.13 is the latest I know of....
wavdev.dll
hello mamaich,
of course i can not rename the file because it is a system file, in use, attributes can not be removed. anybody has another idea?
peter
(sorry for the type mismatch radio 1.12)
Re: wavdev.dll
1. All files in ROM can be freely overwritten even if they are loaded by applications. But they of cause cannot be renamed.
2. Files in object store that are opened cannot be overwriten. So if you cannot do that - than this file is contained in object store and was already updated, probably by some CAB from extended ROM.
3. WM2003 allowed opened files from object store to be renamed. According to your post you have 2003SE.
If you cannot rename this file - the file may be in ROM, so you can freely overwrite it with explorer.
If you cannot overwrite it - you still can rename it. In this case after renaming there would 2 copies of file. One with the new name, and the old wavedev.dll would reappear (the ROM version would be visible again).
In some rare cases some program may completely prohibit access to the file, but i've never seen that for DLLs. Unless you are using some PocketPC antivirus (a completely silly idea by the way). In this case uninstall antivir and do a soft reset.
WM2005 does not allow user to overwrite ROM files, but they can be still overwritten by OS itself, for example by creating a custom CAB file. I do this in my WM5 patches.
Not working
Hello mamaich,
Thanks for the complete answer but unfortunally none of these options work. Renaming the file does not create a new copy of the renamed file. I can't even copy the file, it says \\Windows\wavedev.dll access denied. Maby you can tell me how to create a .cab file so that this file is copied and overwritten? something with .net or something?
Thanxz,
Peter
Re: Not working
Peterpanman said:
Hello mamaich,
Thanks for the complete answer but unfortunally none of these options work. Renaming the file does not create a new copy of the renamed file. I can't even copy the file, it says \\Windows\wavedev.dll access denied. Maby you can tell me how to create a .cab file so that this file is copied and overwritten? something with .net or something?
Thanxz,
Peter
Click to expand...
Click to collapse
You can use WinCe Cab Manager
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.
Okay, there a couple of CAB files I install no matter what ROM I use (Total Commander, Today Screen Speed Dial, MortRing [by .exe], Morphy's Call Filter etc), now that I'm getting to grips with the whole ROM building thing I have a question:
How can I add a program installed via a CAB into a ROM so that it is installed into ROM, I've searched on the forum and can't find much. I know it can be done as ROM's such a TuMa's, Logout's and Ivan's have apps in ROM which aren't there by default...
EDIT: In addition, I overwrite some of the default ROM stuff once I've installed (ETEN M600 Dialler in particular), so again, how can I get the 'bits' out the cab and overwrite the default contents of the ROM, this would make my life much easier...
If this has been posted previously then please point me in the right direction
First extract files, shortcuts and registry entries from the .cab using wince cab manager or similar http://www.ocpsoftware.com/, take note on what directory each file/shortcut is in. (often more reg entries will be stored as a file called 'platformxxx.reg' use these too)
Normal rom edit way: add the contents of the exported .reg files to default.rgu, making sure that you leave a blank line on the end, copy all the files to the \dump directory and edit initflashfiles.dat to copy them to the right directory on first boot. (remeber to remove the first two bytes - ff fe with a hex editor). then build your rom!
Bepe's rom edit way: create a folder '[your software name]' in the oem folder and get yourself a guid from here http://kruithof.xs4all.nl/uuid/uuidgen. create a blank file called '[yourguid].dsm and a blank text file called '[yourguid].rgu'. add the contents of the exported .reg files to '[yourguid].rgu' and make sure you save as unicode. then copy all the other files to the folder and create a blank unicode txt file called 'initflashfiles.txt' and use it like initflashfiles.dat in the first method except there is no need to hex edit out the first two bytes. then build your rom!
midget, you're a star, I thought it may be something simple... I'm off out with the family now for the day, but I'll work on this later, cheers!
Whenever I install a program it appears to open a cab on my kaiser.
Rather than running the installers all the time on my laptop, is there a way to find those cabs and just move them to my storage card so I can install them if I am away from my laptop?
go to the installation folder on ur desktop and the cab would be in a folder in there. usually the folder marked 'installation files' or 'resources'..
just look for the cab file.
found some..
but not most ...
Very odd..
If you mean that when you run a .exe on your laptop to install a program on your kaiser, then it is possible to sometimes extract the cabs from the .exe or installer. A program called Universal Extractor can extract over 50 types of files including most installers. It is free, and supports many languages. It even adds an entry to the context menu, so you can right click nearly any file. It will then try to find the appropriate extracting tool, and then if it succeeds, it will place the files in a folder in the same directory as the original file. Try this, it has worked very well for me.
Dave
ParrotSquawk said:
but not most ...
Very odd..
Click to expand...
Click to collapse
If it helps, I tend to find most of them are in C:\Program Files\Microsoft ActiveSync
Hi all,
Does anyone know how I find a particular application,s .exe filename/path? I need to include this in the exception value in system registry and have searched file explorer, but cannot find the .exe filename. If it helps, I am looking for the .exe file for TomTom Navigator 6.03
Thanks
.exe files...
If you installed TomTom to Internal Storage (as I have done for CoPilot), the .exe file will be in a Internal Storage\Program Files\TomTom (or whatever TomTom have called their folder) - if it's installed to the device memory, the file path will be the same except for the 'Internal Storage' bit.
Of course, if TomTom is installed in ROM, the .exe will be in the \windows folder. The .exe names are usually quite self explanatory (ie. CoPilot is called copilot.exe), so they're not that difficult to find. Having said that, I'm sure some use obscure names just to try and fool us!