Deadlock not logged even though using relevant trace flag?

To my surprise a deadlock information is not logged on SQL Server log, after a struggle for half-day I found that the startup parameters were messed up! It may be usual practice by adopting [ ; -T1204; -T1222 (with blank after semicolon) ] that is what we applied and though the application generating deadlock information the error log is missing this entry. As this server needs to be online during the office-working hours I have adopted correct options by using [ ;-T1204;-T1222 (no blank after semicolon)...(<a href="http://sqlserver-qa.net/blogs/tools/archive/2007/08/05/deadlock-not-logged-even-though-using-relevant-trace-flag.aspx">read more</a>)<img src="http://sqlserver-qa.net/aggbug.aspx?PostID=1260" width="1" height="1">