Not sure about catching errors, but as far as running it under SQL 2005 (and 2008), you can substitute "sqlcmd" for "osql". Of course "osql" still works for now (it is deprecated), it is "isql" that was removed.