I'll preface this by saying that once a DB is marked as "suspect" you're in a pretty bad place -- there's a good chance there will be some data loss no matter how you recover from this.
That said, you should be able to bring the database up in emergency mode and start your repair process (checkdb) from there. http://gargmanoj.wordpress.com/2008/07/17/how-to-repair-a-sql-server-2005-suspect-database/ has more details geared toward SQL Server 2005, but I believe they'll work in 2000 as well (commands reproduced below for posterity).
--- Find out why the DB is marked suspect
DBCC CHECKDB (‘YourDBname’) WITH NO_INFOMSGS, ALL_ERRORMSGS
--- Reset the DB to Emergency Mode
EXEC sp_resetstatus ‘yourDBname’;
ALTER DATABASE yourDBname SET EMERGENCY
--- Initial checkdb to get things working
--- Single-User Mode & "Dangerous" repair (possibility of data loss!)
ALTER DATABASE yourDBname SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DBCC CheckDB (‘yourDBname’, REPAIR_ALLOW_DATA_LOSS)
--- Make the DB usable again
ALTER DATABASE yourDBname SET MULTI_USER
Upon completing your repair (or better, prior to starting) you should get your boss to spring for a UPS for the database server. It's often easier to shake the money tree with the threat of data loss hanging over people's heads.