Thank you both for the clarification, and stayscrisp for that nifty feature!

Finally! 2hrs more into this and I finally figured out what was going wrong. I had to move the swapchain into it's own function and leave the D3DInit in it's own respective function, I also increased the size allocated for the error message(Instead of MAX_PATH I just gave it a direct decimal number 2048) and recieved better debug information outside of the ?????????????????????????4????????????? error.

I would still like to know why the debugger is throwing this out:

D3D10: WARNING: ID3D10Buffer::SetPrivateData: Existing private data of same name with different size found! [ STATE_SETTING WARNING #55: SETPRIVATEDATA_CHANGINGPARAMS ]

It's late and I have to be up in 4hrs!!

After using some breakpoints I've discovered the following:

Breaking Before this line(224)[GraphicsLayer.cpp] shows that all the initialization code is working properly. D3DX10CreateSprite is causing the below hiccup, I've done some google work and it seems that it's something with DX10 and it can be ignored, but it is a warning and I'd like to squash it.

	// Create the sprite to use to render letters
	D3DX10CreateSprite(m_pDevice, m_uiMAX_CHARS_PER_FRAME, &m_pFontSprite);
    // D3D10: WARNING: ID3D10Buffer::SetPrivateData: Existing private data of same name with different size found! [ STATE_SETTING WARNING #55: SETPRIVATEDATA_CHANGINGPARAMS ]

Next up:
Line(229)[GraphicsLayer.cpp] DrawTextString Data Member seems to be causing the data member DumpMessages() Line(82)[GraphicsLayer.cpp] to go into a loop and causes the application to hang.

void cGraphicsLayer::DrawTextString(int x, int y, 
							D3DXCOLOR color, const TCHAR* strOutput)
{
	m_pFontSprite->Begin(0);
	RECT rect = {x, y, m_rcScreenRect.right, m_rcScreenRect.bottom};
	m_pFont->DrawText(m_pFontSprite, strOutput, -1, &rect, DT_LEFT, color);
	m_pFontSprite->End();
}

DumpMessages()

void cGraphicsLayer::DumpMessages()
{
	assert(m_pMessageQueue);

	HRESULT r = 0;

	while(1)
	{
		// Get the size of the message
		SIZE_T messageLength = 0;
		r = m_pMessageQueue->GetMessage(0, NULL, &messageLength);
		if(messageLength == 0)
			break;

		// Allocate space and get the message
		D3D10_MESSAGE * pMessage = (D3D10_MESSAGE*)malloc(messageLength);
		r = m_pMessageQueue->GetMessage(0, pMessage, &messageLength);
		if(FAILED(r))
		{
			OutputDebugString(L"Failed to get Direct3D Message");
			break;
		}
	
		TCHAR strOutput[MAX_PATH];
		swprintf_s(strOutput, MAX_PATH, L"D3DDMSG [Cat[%i] Sev[%i] ID[%i]: %s\n",
			pMessage->Category, pMessage->Severity, pMessage->ID, pMessage->pDescription);
		OutputDebugString(strOutput);
	}
}

So I'm not sure how their is an exsisting private data of same name with different size found before the DumpMessages() is called. I need to get some rest I've got a long day tomorrow. Any other members that can compile the attached file that holds the updated solution and see what they get? (DX10 Support Required)

Thanks!

Just finished running that, no errors reported! Checked all components. I'm going to go back and read over the code again and verify everything is sending messages correctly, variables are set, and anything else I can think of.

Just finished running that, no errors reported! Checked all components. I'm going to go back and read over the code again and verify everything is sending messages correctly, variables are set, and anything else I can think of.