View Single Post
  #85 (permalink)  
Old 06-10-2007, 09:29 AM
Trident's Avatar
Trident
The Source of Power
Offline
Location: Disney World
 
Join Date: Aug 2006
Posts: 2,337
Reputation: 1485
Trident is halfway to VIP status based on repTrident is halfway to VIP status based on repTrident is halfway to VIP status based on repTrident is halfway to VIP status based on repTrident is halfway to VIP status based on repTrident is halfway to VIP status based on repTrident is halfway to VIP status based on repTrident is halfway to VIP status based on repTrident is halfway to VIP status based on repTrident is halfway to VIP status based on rep
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Send a message via Skype™ to Trident
Quote:
Originally Posted by Kolano
Quote:
Originally Posted by Trident
I fixed the FAT16 image location, but the Extended ROM file location doesn't look right either. And I can't find it anywhere- I did a search for nk.nbf in the folder and no results. Is the nk.nbf created during a previous point in the process or is it something that should be in one of the folders?
Still unable to encode.
The .nbf files is the output file, it is not supposed to exists before you hit encode. The field that gives a location for the .nbf file is merely specifying where the .nbf file will be writen to.
OK. That makes sense. But I'm still getting the "Unable to encode..." error message.
Like the FAT16 directory, the nbf file output directory is also pointing to the wrong place (somewhere on my C: drive). Is it possible that it being pointed to the wrong place is causing an error? When I try to change it to the correct directory, it always changes back.
__________________
The only way of discovering the limits of the possible is to venture a little way past them into the impossible.
Any sufficiently advanced technology is indistinguishable from magic.


Reply With Quote