Please go through this MSDN documentation.

Dropping a database does not leave behind the data and log files.

SQL Server has just dumped the backup information to the file and the operating system did not allow the file to be processed. This backup file is irrecoverable

Get the Service Name from services.msc for those services. As you did for the other services, use NET STOP servicename

You can check in sys.processes to see if any backup job is running against a database. Put this logic in the Shrink TLog job step

SYS is a scheme. Read more here

Could not see SQL Server element in the question

From the error message it does not look like an issue with SQL Server. Check the server which is being...

Just put those commands in a notepad file and save it as .bat. You are good to go !

Add an output file to the job step --> advanced. With this the job execution will be fully logged in a text file.

Interview question ?

The Maintenance Plans available in the SQL Server 2005 does this without the need of writing scripts.

I could not find that info in any of the .xml/.ini files on DVD. Not sure how setup determines which Edition it is.

The "SQL***MemoryManager" counter in Perfmon will give you the details.

You may use xp_cmdshell to execute the command line parameters for the FTP command. Also you may try using SSIS