enriquein's questions

I'm using a Windows 2003 Server install as my software development workstation. Every now and then I'll get application crashes and sometimes I don't get notified of the crashes at all by the Error Reporting Service, at least not until I re-log on to Windows. I've been googling for a way to disable this and the only thing I've managed to find is the name of the feature (Queued Error Reporting) and it's justification (which makes a lot of sense in a server environment, but it's useless and annoying on a dev machine).

Is there any way to disable this behavior and make it act more like the traditional Workstation versions of Windows handle it (show error at the moment, not at next boot)?

Using Windows 2003 Standard SP2, and I have the "Disable Error Reporting" option set.

Edit to clarify: This is a development machine. I want to be able to disable reporting errors on startup and make them appear when they happen. It's very annoying to launch an app 10 times and not know why it isn't showing up, only to find out later after logging on that it was crashing. I just want this aspect of Win Server to behave like a regular Windows install. Just so people stop posting the obvious, here's the settings dialog:

Error Reporting Configuration http://db.tt/zMbEoLF

I currently have a bash script running on my Linux server that once a week goes through my repositories, performs some tasks, and backs them up remotely.

Today I started backing up some remote repositories as well. My plan was to be able within the backup bash script run something like (cd $dir && git pull origin master 2>> $LOGFILE) inside a for loop. The problem I seem to be having is that I'm trying to pull some stuff from github and that requires my private key file to be unlocked before proceeding. Is there any way that I can provide that password beforehand so that I don't get an interactive prompt for the password?

Here's my situation:

I have two servers, Server A has the Database Server installed and the SQL Agent (SQL Server 2008 Enterprise Edition, 64-bit). Server B has a vendor specific application that needs SSIS to reside in the same server for some reason. As per MSDN licensing I can't have more than 1 instance of SSIS per license of SQL Server. So we went ahead and installed SSIS only to Server B, and applied the configuration instructions found in http://msdn.microsoft.com/en-us/library/ms137789.aspx as to tell it that the database is in Server A.

I am able to run the package manually using DTEXEC on Server B and it ran without errors. However, I am unable to configure an SQL Agent job on Server A that will execute the package against Server B's SSIS install. I get an error about needing to have SSIS installed in Server A.

The question is, how do I tell the Agent in A to execute the package using SSIS on B?