You can download the latest version of iSCSI Initiator for Windows 2000, 2003 and XP. This will upgrade any previously installed version to the latest version:

https://www.microsoft.com/download/details.aspx?id=18986

Internet Explorer 8 is the last version for Windows XP and 2003, but with them no longer being supported, the download links have been removed as well, making it difficult to download and install it. Although XP and 2003 are quite outdated, certain scenarios still require the use of XP and/or 2003.

A default install of XP/2003 contains Internet Explorer 6, so not being able to download IE8 would result in those systems running an even more outdated and unsecure browser. While IE8 isn't that much better, I consider it a tiny bit more secure, hence this article...

For the moment, the standalone installation files still exist on the Microsoft servers, but they are no longer linked to from the  ...

On Windows 8.1 and Server 2012 R2, SMB 1.0 (aka CIFS) is no longer enabled by default. This means clients that don't support at least SMB 2.0 (for Windows: everything predating Vista/2008) can no longer directly connect to a 8.1/2012R2 server, and instead, are presented with an error if they attempt to do so:

Error
The specified network name is no longer available.

You can re-enable SMB 1.0 support by installing the SMB 1.0/CIFS support feature on your server.

Some users reported that even after enabling this feature, they could not access shares on the server. Apparently, the SMB 1.0 driver is not loaded properly, because of a missing dependency on the Server service (aka LanmanServer).
  ...

As long as there are 2003 domain controllers in your network, your old NT4 workstations will be able to authenticate against your domain. As soon as you migrate those 2003's out of the network, you'll run into trouble. By default, Server 2008 R2 no longer accepts authentication requests from NT4 because they use cryptography that's too old and unsafe.

The best solution is to get rid of those NT4 machines, but if that's not possible, you can re-enable support for cryptography on your DCs through GPO.

Either edit the Default Domain Controller Policy group policy, or create a new GPO in the Domain Controllers OU.

Edit the GPO and navigate to: Computer Configuration > Administrative Templa  ...

The iPhoto and OSX version support matrix.

iPhoto version 10.10 10.9 10.8 10.7 10.6 9.6   9.5.1   9.5     9.4.7     9.4.3   10.8.3 10.7.5   9.4   10.8.2 10.7.5   9.3.2   10.7.4   9.3   10.7.4   9.2.3   10.7.3 10.6.8 9.2.1   10.7.2 10.6.8 9.1.5     ...

If you have more than one Mac, and one of them is stuck at a certain version of iPhoto because it's no longer supported by Apple, you may have to install an older version on a newer version of OSX. OSX Lion, for instance, is restricted to version 9.4.3, so if you have another device with a newer version of OSX, you may also want to install 9.4.3 on that device, even though the App Store wants to install a newer version of iPhoto.

If you have a Time Machine backup with iPhoto 9.4.3, you could restore it from there. If not, you need the original software CD you used to install iPhoto on OSX Lion. If you do not have that either, there are other ways to get it, but this would be out of scope fo  ...

If you need iPhoto version 9.4.7, which was included in the OSX Mavericks GM release, here's the download link:

Download iPhoto 9.4.7

Do not install if you're not running OSX Mavericks!
There's no version check during installation, so attempting to install on an unsupported OSX version will break iPhoto.