View Single Post
  #35 (permalink)  
Old 02-24-2007, 09:41 PM
sfaure03's Avatar
sfaure03
Regular 'Geeker
Offline
Threadstarter
Location: dallas
 
Join Date: Jan 2007
Posts: 344
Reputation: 0
sfaure03 is a n00b
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Always. I recieved those type of errors during my testing and tracked them to:

1. I had a directory in my oem w/o a dsm file. or some duplicated file.
2. SOMETIMES and only rarely if I used the "viewimgfs" to decode a rom from the same dos prompt and then ran createrom it would do that.

you might have noted that I inculded a builder.cmd file in the rom i posted. If you CLICK on that from explorer you can avoice issue #2 altogether.

The most likely cause is some file in you're OEM's that is conflicting. and for that you simply have to go on the hunt and find the offending file.

If you have an OEM that is trying to make you're rom "cbowy" this rom could present some conflicts for you. Either rip you're cbowy oem out for now, or wait for a newer build. To my knowledge there is NOTHING else in this rom that could contribute to any build issue like what you are having, and this is most likely some conflict in you're oem add-ons.

I will remind you that this is a PRE-RELEASE. You're comments are being listened too though.
__________________
shawn