View Single Post
  #58 (permalink)  
Old 08-26-2007, 11:06 PM
tiermann's Avatar
tiermann
VIP Member
Offline
Location: PA, USA
 
Join Date: Apr 2007
Posts: 815
Reputation: 3165
tiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIP
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Send a message via AIM to tiermann Send a message via Yahoo to 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?
Reply With Quote