Ive had a request from Leo to make a folder for OEM's so I've created the following:
http://vidmes.com/Uni/Kitchens/OEMs
You can upload from there using the following credentials:
Username: [email protected]
Password: oemupload
Address: ftp.vidmes.com
NB: My server only allows connections WITH USERNAMES, so make sure to use an FTP program
NB: This is for OEM PACKAGES ONLY. If you want a program (ie .cab or .exe) uploaded, contact me
CONVENTIONS
Files are to be named "[company] appname versionnum.rar" (eg "ArcSoft MMSComposer 3.5.1.4.rar" OR "MMSComposer 3.5.1.4.rar" OR "Grisoft TotalCommander 1.5.rar") - Try to keep naming the same, if you're uploading a different version of whatever is already there, use the same naming....
Readmes are to be named "[company] appname.txt" (eg "ArcSoft MMSComposer.txt" or "Grisoft TotalCommander.txt")
RAR or Zip files only. With plain-text files for readme's
Folders are permitted, but discouraged. Please just dump everything in the main folder. If it gets crowded, I'll see about folders. But, if everyone follows the conventions, it should stay neat.
Warez\cracks\serials are NOT permitted. I will remove any offending material.
And a final note: If this privilege is abused, I will remove the FTP user, and we'll go back to everyone having to PM me
Turning an OEM package into a CAB
Check out these guys: http://www.ocpsoftware.com/ they make a piece of Software called "WinCE Cab Manager" that allows you to do it. I'm not sure if its free or how easy it is to use - but there is no harm trying!
OEM for the kitchen
Thank you my friend.
Leo
Rock on!
Thanks!
Time for guidelines on structure of OEMs and the ftp folders?
Include readme's with what info?
Naming conventions? (version and enough to know what it is?)
What can't be added (serials, warez?)
Use of folders?
Rar or zip?
(sorry, just trying to keep it quality) ,)
I've uploaded the OEM's from Helmi, they should work in the new Kitchen, too.
Shall I upload some OEM's from other devices, too?
Max
grayme said:
Thanks!
Time for guidelines on structure of OEMs and the ftp folders?
Include readme's with what info?
Naming conventions? (version and enough to know what it is?)
What can't be added (serials, warez?)
Use of folders?
Rar or zip?
(sorry, just trying to keep it quality) ,)
Click to expand...
Click to collapse
Guidelines and conventions added to the first post. PLEASE READ BEFORE YOU UPLOAD!!
And one other thing: Donations Welcome - hosting ain't cheap!
GREAT contribution from TehPenguin. thank you.
From what I remember, OEM are slightly different depending on the kitchen you use.
I think that at least are two different. People more involved could confirm this.
I would propose to create folders for the different version of Kitchen/OEM.
It would make everyones work/search easier.
Cheers
ultravox said:
GREAT contribution from TehPenguin. thank you.
From what I remember, OEM are slightly different depending on the kitchen you use.
I think that at least are two different. People more involved could confirm this.
I would propose to create folders for the different version of Kitchen/OEM.
It would make everyones work/search easier.
Cheers
Click to expand...
Click to collapse
All seems fair there Pengiun .
The two versions of the OEMs differ in that the entry into initflashfiles to move across the shortcuts to the start menu in the first one went into the initflashfiles in the individual OEM folder on the original Helmi kitchen, but into the single initflashfiles in OEM_Language_0409 (from memory?).
Seeing as how this is for the new kitchen (?), the entry into the single initflashfiles could just go in the readme?
My problem with the old OEMs is that there appeared to be a lot that didn't work, can we only add tested OEMs here to keep it tidy and useful?
I'm just providing the space - so dont ask me too many questions
Personally I believe people should put up what they can, and chuck in the readme's as much information as they can.
If the OEM's need customisations, post them on this thread or in the thread of the relevant Kitchen
If you need to ask questions, direct them to the Kitchen maintainers (eg Leo and Ranju) or the ROM developers (eg Ivan, Midget, JWright, MWang, etc)
grayme said:
Seeing as how this is for the new kitchen (?), the entry into the single initflashfiles could just go in the readme?
Click to expand...
Click to collapse
I dind't check it yet, so I can't help.
grayme said:
My problem with the old OEMs is that there appeared to be a lot that didn't work, can we only add tested OEMs here to keep it tidy and useful?
Click to expand...
Click to collapse
I would dare to say that this point must be mandatory, maybe even more: only 2 or 3 users (Leo, grayme and Ranju) or the ROM developers should be able to add the OEM to the main folder; everyone else, should have a "test" folder. We take the risk to have a big mess wihout knowing what to pick.
The readme file is a good idea to place all the info needed to work with the OEM.
Hi Ultravox,
Think that building ROM's and building OEM's is always a mather of thrust and a bit experimenting (see if it works).
A OEM needs a 'dsm' and a 'rgu' and sometimes you need to tell initflashfiles.dat where to place the files.
Before I will use a OEM I should always have a look first at the 'rgu' a/o the initflashfiles.txt, if initflashfiles.txt excist I modify initflashfiles.dat.
The only thing that is necassary for the OEM is the initflashfiles.txt (if the OEM needs it offcourse!), if you don't know where to place the files the whole OEM won't work and you need to rebuild.
Cheers,
Leo
ultravox said:
I dind't check it yet, so I can't help.
I would dare to say that this point must be mandatory, maybe even more: only 2 or 3 users (Leo, grayme and Ranju) or the ROM developers should be able to add the OEM to the main folder; everyone else, should have a "test" folder. We take the risk to have a big mess wihout knowing what to pick.
The readme file is a good idea to place all the info needed to work with the OEM.
Click to expand...
Click to collapse
ultravox said:
I dind't check it yet, so I can't help.
Click to expand...
Click to collapse
It wasn't really a question
Here'yar!
I've added a few files to start off with:
Ghisler Total Commander 2_UPX - freeware 150k
Gábor Kovács Tcpmp 0.72 - freeware 629k
Mort's MortPlayer 3.31RC6 - freeware 741k
SKKV SKTools3.1.3 - very usable demo 473k
vijay555 Hide_Bottom_Bar - homebrew/freeware 11k
I named the readme's 'readme' as that seemed easiest to find them
grayme said:
I've added a few files to start off with:
Ghisler Total Commander 2_UPX - freeware 150k
Gábor Kovács Tcpmp 0.72 - freeware 629k
Mort's MortPlayer 3.31RC6 - freeware 741k
SKKV SKTools3.1.3 - very usable demo 473k
vijay555 Hide_Bottom_Bar - homebrew/freeware 11k
I named the readme's 'readme' as that seemed easiest to find them
Click to expand...
Click to collapse
Thx. Good collection!
ultravox said:
only 2 or 3 users (Leo, grayme and Ranju) or the ROM developers should be able to add the OEM to the main folder; everyone else, should have a "test" folder.
Click to expand...
Click to collapse
Most of the Kitchen\ROM developers already have their own FTP account and can access their parts of my FTP
This "OEM" folder is the only "public" upload space I have
Adobe Reader LE
Hi all,
Somebody has got Adobe reader LE OEM already builded?
Or maybe the cab so I can build myself?
Would be great !!!
One more question, why is this thread not sticky?
Would be great as well !!!
Leo
Nobody has added any OEMs to the five I put there first time round.
OEMs
Maybe nobody noticed this thread because it's not sticky!
Greetings Leo
grayme;1314261 said:
Nobody has added any OEMs to the five I put there first time round.
Click to expand...
Click to collapse
Laurentius26 said:
Hi all,
Somebody has got Adobe reader LE OEM already builded?
Or maybe the cab so I can build myself?
Would be great !!!
One more question, why is this thread not sticky?
Would be great as well !!!
Leo
Click to expand...
Click to collapse
Here you go Leo, Official for WM5; http://adobe-acrobat-reader-ppc.en.softonic.com/pocket but im afraid it is not cab.file
Adobe
Hi SteedMo,
Thanks, stupid I didn't think about that. After installing with active sync you can find the cab in Windows\Active sync, if you didn't know that already?
Cheers, Leo
SteedMo;1314833 said:
Here you go Leo, Official for WM5; http://adobe -acrobat-reader-ppc.en...url] but im afraid it is not cab.file[/QUOTE]
Click to expand...
Click to collapse
Laurentius26 said:
Hi SteedMo,
Thanks, stupid I didn't think about that. After installing with active sync you can find the cab in Windows\Active sync, if you didn't know that already?
Cheers, Leo
Click to expand...
Click to collapse
Geeeez, didnt know that b4... in fact I've been spending time looking up softwares for cab.converter
Thanks for that..
hello,
by default - holding the red phone-hangup button brings me to today-screen.
but in my case i don't use the windows mobile today screen at all! i installed pointui - as autostart.
i hardly have any reason to go to the today screen.
can't i change this behaviour somehow ? when i hold the red hangup-button i want to go "back" to pointui - not to today-screen.
in case there's no solution like that - is there at least some kind of today-plugin that could bring me back to pointui home ? maybe so alround-lauch-exe-plugin ?
by the way: i'm talking about WM2003SE!
thank you!
I'm sorry that I do not know the solution to the problem. Please, next time you post, do not make a misleading title (! instead of ?) in the wrong section.
If you can post your device i can tell you if you can use the Long_End.lnk trick.
I can then also move this thread to that device's Forum.
A good start would be to contact or check the PointUI website/forum to see if the home.exe accepts a parameter
(home.exe -h)
To return to the home screen
But the Long_end.lnk does not work on all devices.
Will put this into the general forum as Pointui does not have an active development thread here.
Attached you will find a shortcut file.
Change the .txt to .lnk then copy it to the windows directory on your device. Hold down the read Call Button and keep it pressed.
This may or may not work on your device.
But there was no information about your device or rom either in your signature or post which makes it hard to actually give a good answer to your question.
Cheerz
hello,
the device i'm talking about is a magician.
i changed the Long_end.lnk - to the correct path of Home.exe and copied it to \WINDOWS <---- really windows ? no subfolder ?
i tried - does not change anything. anyway - thank you for the info!
another idea ?
baal_zebub said:
hello,
the device i'm talking about is a magician.
i changed the Long_end.lnk - to the correct path of Home.exe and copied it to \WINDOWS <---- really windows ? no subfolder ?
i tried - does not change anything. anyway - thank you for the info!
another idea ?
Click to expand...
Click to collapse
Yeah magician i'm not sure if it has a rom that supports this function.
Touch, Kaiser and some others do. It's hardcoded to the Keyboard driver or keypad driver if i;m correct so i'm not sure it's use able in the Magician.
Oh BTW it should have been Long_End.lnk (Yup no subfolders)
But i have no other suggestion, maybe someone else has.
guys anyone can tell me where I can find a diagram showing what are the various codes of Manila? eg 0d61c97c_manila
I only know that the selector slider is 1cd2f8ef_manila ....
plus you recommend a program for mount cab possibly free?!
thanks! Ciao!
negromnia90 said:
guys anyone can tell me where I can find a diagram showing what are the various codes of Manila? eg 0d61c97c_manila
I only know that the selector slider is 1cd2f8ef_manila ....
plus you recommend a program for mount cab possibly free?!
thanks! Ciao!
Click to expand...
Click to collapse
I have never seen such a list and would be surprised if a complete list actually exists as there are around 3000 manila files on the HD2!
The best suggestion I can make is to install something like CFC_GUI on your PC (a simple search on this forum will find it). Most of these 3000 files (including the one you mentioned) contain .png images. CFC_GUI allows you to see the image contained in the manila file, which is in many ways better than a diagram or list.
With regard to 'mounting' cabs (do you mean 'creating' cab files?), there are a few free apps available. Again, a simple search on the forum will help you find what you are looking for. I use the 'create cab' feature included in HDWall to create all of my cabs because I already have HDWall installed. It saves me installing two different apps...!
I have seen something like that here in the XDA-Wiki. Just do a search.
johnkst said:
I have never seen such a list and would be surprised if a complete list actually exists as there are around 3000 manila files on the HD2!
The best suggestion I can make is to install something like CFC_GUI on your PC (a simple search on this forum will find it). Most of these 3000 files (including the one you mentioned) contain .png images. CFC_GUI allows you to see the image contained in the manila file, which is in many ways better than a diagram or list.
With regard to 'mounting' cabs (do you mean 'creating' cab files?), there are a few free apps available. Again, a simple search on the forum will help you find what you are looking for. I use the 'create cab' feature included in HDWall to create all of my cabs because I already have HDWall installed. It saves me installing two different apps...!
Click to expand...
Click to collapse
thanks! you were very kind!
thanks everyone!
Just discovered this handy little tool for writing sys txt for Igo 8 or Primo.
Thanks to kimyaci and robynk
https://rapidshare.com/files/4073795642/SysConfigurator_1.2.rar
Posted it on a couple of older threads but they appear to be obsolete. This handy little tool allows you to fully customise and generate a sys.txt file for both Igo and Primo. It has an easy to use interface in English, Spanish and French. Pretty self explanatory. No more trawling forums for half remembered commands .
Basically it is a windows program that categorises many of the Igo and primo sys text commands. It provides clear explanations of what they do. You just tick the boxes for those that you want to use and the program can then generate a new sys.text file or update an existing one. Very useful for both customising and troubleshooting in IGo as it saves you having to look up the commands or even doing any typing.
The original comes from a spanish forum and I presume any updates will be published there.
Requires registration.... Upload it to a public share...
Sorry I'm not sure what that means? This is just a link to a piece of software that I thought was useful.
corrsea said:
Sorry I'm not sure what that means? This is just a link to a piece of software that I thought was useful.
Click to expand...
Click to collapse
When I click the link it says, you must register. I and also others don't like to register and would appreciate if you could move the file to another place for downloading.
ok I get it now. Didn't realise that was what happened. I thought it just went straight to the download. Will upload it to rapidshare. Removing the link for now.
EDIT
All done. Rapidshare link now in place. Sorry about that.
Downloaded ok. fantastic thanks
425 downloads in total. Guess some people have found it useful
hi thank you for the tool can anyone upload it again the link is dead.
thanks in advance.
corrsea said:
Just discovered this handy little tool for writing sys txt for Igo 8 or Primo.
Thanks to kimyaci and robynk
https://rapidshare.com/files/4073795642/SysConfigurator_1.2.rar
Posted it on a couple of older threads but they appear to be obsolete. This handy little tool allows you to fully customise and generate a sys.txt file for both Igo and Primo. It has an easy to use interface in English, Spanish and French. Pretty self explanatory. No more trawling forums for half remembered commands .
Basically it is a windows program that categorises many of the Igo and primo sys text commands. It provides clear explanations of what they do. You just tick the boxes for those that you want to use and the program can then generate a new sys.text file or update an existing one. Very useful for both customising and troubleshooting in IGo as it saves you having to look up the commands or even doing any typing.
The original comes from a spanish forum and I presume any updates will be published there.
Click to expand...
Click to collapse
Hi, just checked the link. It should still be working. Try it again, if you have no luck let me know and I will upload it again.
Sent from my GT-I9300 using Tapatalk 2
Cant download. The link is dead.
Error:
**********
Folgender Download ist nicht verfügbar:
https://rapidshare.com/files/4073795642/SysConfigurator_1.2.rar | 0.27 MB
Download-Parameter ungültig - bitte nocheinmal probieren.
**********
aleskow said:
Cant download. The link is dead.
Error:
**********
Folgender Download ist nicht verfügbar:
https://rapidshare.com/files/4073795642/SysConfigurator_1.2.rar | 0.27 MB
Download-Parameter ungültig - bitte nocheinmal probieren.
**********
Click to expand...
Click to collapse
Hi the link is definitely still working. have just downloaded it myself
Anyway have added a direct download to xda from first post for those for whom the rapidshare link does not work.
Enjoy.
iGo sys.txt configurator: Excellent
@corrsea
Many thank mate. Great small software.
Unbelievable that link is still working.
Although I am using iGO since the first release on old PDA, I always use to alter the sys.txt file manually.
I did know that such configurator exists and I have never searched for it.
Respect.:good:
long live open source
just downloaded it.
Great find for me.
Thanks
Gone thu all the menu options setting in particular the warning setting The over speed warning works as well visual and voice announcement department. Set speed camera and red light for visual and voice announcement. Only the visuals come up but no accompanying voice message Downloaded sysconfigure looked @ the sys file to see difference to the gps original sys file and observed no difference in the warning list. Not knowing sys script requirements don't understand how to force voice messages via the script An example of a howto would be appreciated
did manual editing of the sys file restarted the gps then closed down primo re-writes the sys file so changes are lost! Suspect the problem is in the primo software