Repairing Boot Camp after creating new partition

Question

I'm running OS X 10.8 and Windows 7 x64 Pro.
After properly setting up Boot Camp to dual-boot Windows on my Mac mini, I decided to test whether or not it was true that creating another partition (a data partition for OS X) would interfere with Boot Camp.  Wikipedia claims it does interfere but without citing a source, whilst the Boot Camp documentation itself only specifies that the disk must be a single partition _prior_ to setup - there's no mention of whether the disk must be _kept_ that way afterwards.
I opened Disk Utility, reduced the size of my OS X parition from 420GB to 80GB, and created a new partition in the unallocated space.  Here's how it looks now:
When I attempted to proceed with the process, I did receive a warning that doing this (and I quote), "may" cause problems with Boot Camp.  Seeing as it was inconclusive, I thought I'd give it a shot - nothing ventured…
Of course, it borked Boot Camp, otherwise I wouldn't be posting here.  Whilst OS X boots just fine, the Boot Camp partition now no longer shows up in the Startup Manager, though it does in the Startup Disk prefPane.  If I do attempt to boot into Boot Camp, I receive the following message on a black screen:
No bootable device --- insert boot disk and press any key
The advice given to someone who had this same problem was, "fix your damaged Boot Camp volume."  But I'm at a loss as to how to do that.
So, anyone know how to proceed now so that I can keep my partitions as is, whilst fully restoring normal Boot Camp functionality?

Answer 1

Hi,
@Christopher Murphy:
Okay, you seem confident.  Let's give this a shot.  I use the command-line myself for the odd thing, so I'll try not to bail.
Results of the "sudo gpt -r -vv show disk0" command:
gpt show: disk0: mediasize=500107862016; sectorsize=512; blocks=976773168
gpt show: disk0: PMBR at sector 0
gpt show: disk0: Pri GPT at sector 1
gpt show: disk0: Sec GPT at sector 976773167
      start       size  index  contents
          0          1         PMBR
          1          1         Pri GPT header
          2         32         Pri GPT table
         34          6        
         40     409600      1  GPT part - REDACTED UUID
     409640  156303528      2  GPT part - REDACTED UUID
  156713168    1269536      3  GPT part - REDACTED UUID
  157982704  659841040      4  GPT part - REDACTED UUID
  817823744     262144        
  818085888  158687232      5  GPT part - REDACTED UUID
  976773120         15        
  976773135         32         Sec GPT table
  976773167          1         Sec GPT header
Results of the "sudo fdisk /dev/disk0" command:
Disk: /dev/disk0          geometry: 60801/255/63 [976773168 sectors]
         Starting       EndingSignature: 0xAA55
#: id  cyl  hd sec -  cyl  hd sec [     start -       size]
1: EE 1023 254  63 - 1023 254  63 [         1 -  976773167] <Unknown ID>
2: 00    0   0   0 -    0   0   0 [         0 -          0] unused     
3: 00    0   0   0 -    0   0   0 [         0 -          0] unused     
4: 00    0   0   0 -    0   0   0 [         0 -          0] unused  
Does this indicate a fix is possible?