If you restore 7 am log with STOP AT option you may loose the other transactions which you may no need to rollback or loose them...

It depends on the what...

Make sure you Stop the SQL Server Agent service before connecting to an instance of SQL Server in single-user mode; otherwise, the SQL Server Agent service uses the connection, thereby...

If you have another msdb backup from different server with same build can be restored but you loose all the history or jobs etc...

http://blogs.msdn.com/psssql/archive/2008/08/29/how-to-rebuild-system-databases-in-sql-server-2008.aspx

http://sqlblog.com/blogs/tibor_karaszi/archive/2008/08/27/rebuilding-msdb-on-sql-server-2008.aspx

http://msdn.microsoft.com/en-us/library/ms188236.aspx

Migrating SQL Server 2000 to SQL Server 2008

http://www.dell.com/downloads/global/solutions/public/white_papers/SQL_2000_SQL_2008_Migration_Guide.pdf

Free tool for moving SQL Server logins: Idera SQL permissions

http://www.idera.com/Products/Free-Tools/SQL-permissions/

Try copy and paste the following and restart it...

-m;-dM:\Program Files\Microsoft SQL Server\MSSQL10.INST4\MSSQL\DATA\master.mdf;-eM:\Program Files\Microsoft SQL Server\MSSQL10.INST4\MSSQL\Log\ERRORLOG;-lM:\Program Files\Microsoft SQL Server\MSSQL10.INST4\MSSQL\DATA\mastlog.ldf

Under what account sql server is running?

Can you post the startup parameter string and what edition of sql server it is?

You can use UNC path but if you want to troubleshoot there will be many factors...always better local and then copy but if you don't have the space locally then...

Make sure the sql instance is not running and the log folder path exists and you login account has the sufficient access.

Make sure SQL Agent is disabled....

Have tried using SQL...

It is advisable to upgrade to sql 2005 instead of sql 2000 again to different edition as previous poster mentioned...

but it is your call and requirement...

Here is the link which...

Is SQL agent sevice account has the access to sql and has right password?

Looks to be it is access/permissions issue.

May be something might have corrupted during ssms installation...

Try to remove and resinstall SQL tools or re-apply service pack...

Yes...SSMS is slow there are many complains about it...

They improved in SP2, try to apply SP2 and see if it improve any better along with more memory to your Laptop...

There is no option in sql server to backup the single table using backup command...but you can use DTS or BCP to copy the data and generate the table script...

1. Read BOL.

2. Read article available on this site and on different sites like sql-server-performance.com and microsoft.com/sql etc...

Reads the books like inside sql server and sql internals etc...