View Single Post
  #59 (permalink)  
Old 08-27-2007, 07:49 AM
sethlo's Avatar
sethlo
PPCGeeks Regular
Offline
 
Join Date: Jun 2007
Posts: 57
Reputation: 10
sethlo is a n00b
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quote:
Originally Posted by tiermann
The paths in the Autorun section are the paths on the device (Ex: \Windows\Autorun.exe) and to add the autorun.exe to your OEM you'll need your own copy of it (which can be found in the zip in the first post in this thread) added to the Files & Shortcuts section.

OEMizer will generate the Config.txt (from your input in the textbox) and put in in the OEM during the "Create OEM" process. It will automatically be in \Windows\Config.txt. You'll just need to add it to the initflashfiles.txt manually afterwards if you want it somehwere different.

Make sense?
Ok, I think I got it. Does this sound right? -- OEMizer will put config.txt in the OEM folder it builds. If I leave it there and if I put Autorun in the personalized oem folder after the folder is built by OEMizer, then I should make the paths go to \Windows\Autorun.exe and Windows\Config.txt. (Because that's where the items will go when I flash the phone).

Or, I could place my copy of Autorun on my storage card or in my ext rom along with config.txt and change the paths accordingly. (perhaps this will save a little memory for other things in my rom).

Please let me know whether or not this is correct. Sorry if I am being a little didactic, but this is new to me. Thanks again.

edit: I'll need to change my initflashfiles.txt if I put autorun in my personalized oem folder to tell it to put it in \Windows. if that's where I want it to go. Likewise, I'll have to change initflashfiles.txt if I move config.txt. Right?
Reply With Quote