PPCGeeks

PPCGeeks (http://forum.ppcgeeks.com/index.php)
-   HTC Apache (http://forum.ppcgeeks.com/forumdisplay.php?f=14)
-   -   New kitchen release (http://forum.ppcgeeks.com/showthread.php?t=4843)

k000 06-09-2007 06:24 AM

Guys - can I just download and start using it ? Or do I need to cook my own ROM first with this Kitchen ? I've never cooked my own, but have always used Colonel or BigJ's ROMs.

peacock93 06-09-2007 08:47 AM

"unable to encode fat16 image" error in new kitche
 
All goes well until the Encode process. Then I get this error message "Unable to encode fat16 image". I did point to my nk.nba file but still nothing. Any ideas??

kevdawg 06-09-2007 09:26 AM

Re: "unable to encode fat16 image" error in new ki
 
Quote:

Originally Posted by peacock93
All goes well until the Encode process. Then I get this error message "Unable to encode fat16 image". I did point to my nk.nba file but still nothing. Any ideas??

same for me. help us guys!

johnny2678 06-09-2007 11:55 AM

The NBF and NBA file locations were wrong for me... once I designated new locations the FAT16 problem went away.

kevdawg 06-09-2007 12:01 PM

Quote:

Originally Posted by johnny2678
The NBF and NBA file locations were wrong for me... once I designated new locations the FAT16 problem went away.

can you be a little more explicit?

johnny2678 06-09-2007 12:04 PM

well, for me the extended rom file is...

...[helmi_NewKitchen_location]\NoID flash utils\nk.nbf

and the fat16 file is...

...[helmi_NewKitchen_location]\temp\nk.nba

obviously, you need replace [helmi_NewKitchen_location] with the path to the kitchen root.

colonel 06-09-2007 12:19 PM

Ok, there are two seperate errors that are getting confused here.

"Unable to get FAT16 filesize" is the one that means the paths are incorrect.

"Unable to encode FAT16 file" is a different one of a yet to be determined origin. Usually you can do the whole process over and it should work.

kevdawg 06-09-2007 12:30 PM

Quote:

Originally Posted by colonel
Ok, there are two seperate errors that are getting confused here.

"Unable to get FAT16 filesize" is the one that means the paths are incorrect.

"Unable to encode FAT16 file" is a different one of a yet to be determined origin. Usually you can do the whole process over and it should work.

I'm going to try it again, but this will be about the 5th time. I've also tried doing it on another xp machine. Same error.

kevdawg 06-09-2007 12:58 PM

Quote:

Originally Posted by colonel
Ok, there are two seperate errors that are getting confused here.

"Unable to get FAT16 filesize" is the one that means the paths are incorrect.

"Unable to encode FAT16 file" is a different one of a yet to be determined origin. Usually you can do the whole process over and it should work.

http://upload8.postimage.org/755257/untitled.jpg


Here is the solution to the second item mentioned here by Colonel. Make sure that you redifine the location of the upgrade folder with in the folder titled "Helmi_APAC_WM3.5_NEW_Kitchen_R1" and redefine the location of the .nba file.

After i redifined the location of the NBA file and the upgrade folder i was all set. Thanks guys!

colonel 06-09-2007 01:03 PM

Location paths for the encoder have been addressed in the next release.

For the Extended Rom location put

Code:

\Upgrade\nk.nbf
For the FAT16 file location put

Code:

\nk.nba
I believe this should work if someone wants to test it out.


All times are GMT -4. The time now is 01:45 PM.

Powered by vBulletin® ©2000 - 2025, Jelsoft Enterprises Ltd.
©2012 - PPCGeeks.com


Content Relevant URLs by vBSEO 3.6.0