[Lmiller1708]

Ok. Here is what I found out...
First here is my partition table:

NBInfo 2.1rc2

'00_OS.nb.payload' has valid boot sector

Partition table:

Partition 0
-----------
 File System:    0x23 (XIP RAM)
 Start Sector:   0x00000002
 Total Sectors:  0x0000003e
 Boot indicator: 0x00
 First Head:     0x00
 First Sector:   0x00
 First Track:    0x00
 Last Head:      0x00
 Last Sector:    0x00
 Last Track:     0x00

Partition 1
-----------
 File System:    0x00 (unknown)
 Start Sector:   0x00000000
 Total Sectors:  0x00000000
 Boot indicator: 0x00
 First Head:     0x00
 First Sector:   0x00
 First Track:    0x00
 Last Head:      0x00
 Last Sector:    0x00
 Last Track:     0x00

Partition 2
-----------
 File System:    0x00 (unknown)
 Start Sector:   0x00000000
 Total Sectors:  0x00000000
 Boot indicator: 0x00
 First Head:     0x00
 First Sector:   0x00
 First Track:    0x00
 Last Head:      0x00
 Last Sector:    0x00
 Last Track:     0x00

Partition 3
-----------
 File System:    0x00 (unknown)
 Start Sector:   0x00000000
 Total Sectors:  0x00000000
 Boot indicator: 0x00
 First Head:     0x00
 First Sector:   0x00
 First Track:    0x00
 Last Head:      0x00
 Last Sector:    0x00
 Last Track:     0x00

Geometry: flash has 0 virtual heads


MSFLSH50 header found at offset 0x800
  (0 Reserved Entries, 0 Flash Region Entries)

Searching for IMGFS signature...
  Found IMGFS at byte 0x00380000 (sector 0x00380000).

  dwFSVersion:              00000001
  dwSectorsPerHeaderBlock:  00000001
  dwRunsPerFileHeader:      00000001
  dwBytesPerHeader:         00000034
  dwChunksPerSector:        00000020
  dwFirstHeaderBlockOffset: 00000800
  dwDataBlockSize:          00001000
  szCompressionType:        LZX
  dwFreeSectorCount:        00024682
  dwHiddenSectorCount:      00000040
  dwUpdateModeFlag:         00000000
---

As you can see partitions do not make that big of a difference. What seems to matter is having the imgfs found at 0x380000. I did the math in tinboot to do this. With a little playing around too..
This boots just fine now. (For me of course )

Nate I'm yours works because the tinboot is found somewhere on the on the partitions. Not sure why mine didn't work before. Your tinboot is getting inserted at 0x20000 to where mine is inserted at 0x2000. This is what Magldr roms use. I then had to change the .org in tinboot from 1000 to 2000. Now I'm not sure at all why this was not needed to be changed before but I think it has something to do with the not having the boot section in the partition table... Just a guess.

But I would like someone else to test my latest NBH.

Edit: Removed Attachment...