logo

Pages


Erick’s Games

Faith

Older Games

Other Blogs

Posts

Categories

 

March 2009
S M T W T F S
« Feb   Apr »
1234567
891011121314
15161718192021
22232425262728
293031  



Comments

Administration

Atari Review: Space Invaders

March 9, 2009

Sometimes when you strip away graphics and advanced computing, you can still have a blast playing a simple game. We all probably remember what space invaders is: aliens in a grid slowly advancing down screen towards your ship, shooting at you as they do. Your job is to return fire, slaying all the aliens and advancing to the next round. The Atari version features three bunkers that you can hide behind, that slowly decay as they get hit. As you slay more and more of the aliens, they get faster and faster, and you need to use more skill and timing to take them down.

Space Invaders

Simple, yet fun. It’s a challenge to work within a game’s parameter, because the Aliens will get faster, but you never do. The game is not complex or long, but it still provided, and can continue to provide, plenty of fun times. It’s fun to get back down to basics where you simply move left and right, and press a button. Rather than worry about secondary triggers, strafing, reloading, and camera angles, it’s nice to play a simple push button, kill alien type of game occasionally.

Unable to push installation from media server of ver 11d Backup Exec Remote Agent for Windows Systems.

A co-worker of mine just figured out why a push installation of Veritas backup was not working correctly.  Feel free to read what he did to resolve the issue.

When a media server makes a connection with a remote system, the initial connection will be initiated on port 10000. The Remote Agent will be listening for connections on this pre-defined port.

To get around this problem I performed the following steps:

1. Instead of pushing the Remote Agent For Windows Servers (RAWS)I instead ran the installation locally on the server in which I intended to backup. For this expample the location of the installation files were X:\BEWS_11D.7170_32BIT_VERSION\WINNT\INSTALL\RAWS32.

2. Run setup.exe and select the appropriate media server in which this agent will publish it’s information to. You may have an issue in which the Backup Exec Remote Agent for Windows Systems service will not start. The event log will most likely have the following event:

Event Type:Error
Event Source:Backup Exec
Event Category:None
Event ID:58117
Date:3/9/2009
Time:12:21:17 PM
User:N/A
Computer:ALTIGEN4
Description:
The Backup Exec Remote Agent for Windows Servers Service did not start. The application failed to listen on the NDMP TCP/IP port. Check the network configuration.

For more information, click the following link:

http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml

3. You will need to reserve the port for this service to listen on. For this situation I used port 9000.

Note- For Backup Exec 11d and above: These steps only need to be done on the the affected remote server(s). All other remote servers can have the existing/default NDMP Port.

To reserve the port on the remote machine you will need to do the following:

3a- Go to C:\WINDOWS or \WINNT\system32\drivers\etc and modify the “services” file
3b- Go to the bottom of the file and add the following line:

ndmp 9000/tcp #Network Data Management Protocol

3c- Save the change.

4. Start the Backups Exec Remote Agent for Windows Systems service and then launch the Symantec Backup Exec Remote Agent Utility usually running on the task bar or you can launch via Programs->Symantec Backup Exec For Windows Servers->Backup Exec Remote Agent Utility

5. Navigate to the “Publishing” tab and check off “Enable the Remote Agent to publish information to the media servers in the list” click “Add” and enter the name of the media server. You may now see the remote server’s FQDN in the “Published names for this agent” field.

6. On the media server go to Tools->Options->Network and Security and check off “Enable remote agent TCP dynamic port range” and specify as such.

Note- for this situation I chose to use the dynamic port range of 9000-10000.

7. Click OK in the Options Dialog box and you should now be able to see the remote system under “Windows Systems” when configuring a new job.

Google