VM'd a SQL server, having trouble with external HDDs
In general, you can put TempDB anywhere you want. It could be an existing drive on the VM (not great, but OK as a stopgap measure), or a new virtual drive, or a non-local drive (again, not a great idea).
There are a lot of references on the Internet for how to relocate TempDB. And for how to start SQL if the current TempDB is not accessible. Here are some good ones:

How to Move TempDB to Another Drive &amp; Folder
Start SQL Server without tempdb

Also, run (don't walk) to your boss and let them know that both SQL 2000 and Windows 2000 are out of support, and have been for a long time. You are open to security vulnerabilities, performance risks, and reliability concerns. Do whatever you need to to make your boss realize that you can't provide good business value on unsupported software.