when it asks for an archivelog file, put in the path and name of one of your redologs. If that one doesn't work, try another redolog. Keep it going until you run out of redologs ;-)
If that didn't work, try to recover from your last cold backup and roll it forward to a point in time prior to you taking the database down. If you didn't have a cold backup (and spank your fingers if you don't take periodic cold backups), try to do a point in time: set the date/time to 5 minutes before the issue cropped up (or when the database croaked).
I have had success recreating the database with a new controlfile. Sometimes, you can clear a controlfile issue this way.
During these processes, if one works, you may have to recover data from before the issue cropped up. Better to lose 1 hour of Production processing than the entire database!