Quote:
Originally Posted by starmans
I believe it may have been me who requested it after many failed attempts of my own. so I figured who better to ask then Mr OEM g himself.
|
It does too much setup stuff when you first start it. (like grabs all your program links and configures them) The way to override that mess is to build a rom, then export the setup to the OEM... But to build a generic OEM, I did that and just creates a MESS when it auto-configures-everything!
Quote:
Originally Posted by Drybonz
RSTG, have you been able to make a OEM for G-Watch that did'nt conflict with G-Alarm? They have a lot of the same files that come up as dupes.
|
The approach I would take is to...
Leave your g-alarm OEM alone, then build g-watch with ervius package creator. Make sure you have Rename dupes on startup screen in the lower left. This will cause it to build the OEM and prefix the filenames (that won't reside in \windows) with a "000-". Then what I do is rename the files and replace that "000-" with like "gw-". Then go into the initflashfiles.txt and replace the occurances of "000-" with "gw-" with notepad. Then there are no more duplicates! But a bunch of junk in \windows...
Or you could delete them out of the OEM and just have the initflashfiles entry copy them into the directory, but then you risk a different file version/dll version that may not have the right code...