Featured Posts

How to get SMS delivery reports on iPhone 3G 3Gs or... Since I received my new iPhone 3G, I've been wondering why Apple didn't add an option for text message delivery reports to the iPhone 3G software (SMS delivery reports). Sometimes when you send a text...

Read more

A Simple System to Reorganise Your Emails After a Getting Things Done micro-seminar given by a friend, I took it upon myself to start learning about, and introducing, GTD into my life. I’m not an expert but a few simple changes have made a huge...

Read more

iPhone EDGE settings for Vodafone UK Well my unlocked iphone has finally arrived from the US, and I've been tweaking it for the last couple of hours so that everything is working properly. When I tried to fire up Safari on the iPhone I...

Read more

How to Screen Capture in OS X and Windows

Posted by thinkjim | Posted in computers | Posted on 26-03-2009

0

A lot of people ask me about how to OSX print screen (i.e take a screen grab in OS X) and also how to take a print screen in Windows XP/Vista. I know this has been covered before but I thought I would put up a little post up….

OS X Print Screen

In OSX you press [and hold] the apple command key, hold shift and then press either 3 or 4 (what does the command key look like?… click here). Here are the most commonly used options:


Capture Entire Screen: Command + Shift + 3


Capture Selected Area: Command + Shift + 4;  then click [hold] and drag a box around the area you wish to capture. Once you release the mouse button the image will be captured.

Using the above key combinations will cause OSX to take a screen grab and then store the file to your desktop. The first screen shot will be called Picture 1, and then further screen shots will be named Picture 2, Picture 3 and so on.

Windows Print Screen

Windows print screen copies the captured screen to the clipboard. Once you’ve done this the image can be pasted into a document using your application of choice (e.g Word/Wordpad etc.) by selecting >edit >paste from the toolbar or by pressing ‘Ctrl’ + ‘V’. There are two types of screen capture:


Capture Entire Screen: To take a screen capture of the entire screen in Windows 9x/XP/Vista simply press the ‘PrintScrn’ button. This takes a screen grab and stores it to the clipboard.


Capture Current Window: To take a screenshot of the current window (not the whole screen) in Windows 9X/XP/Vista hold down ‘Alt’ and Press ‘PrintScrn’.

Could not start the Microsoft Exchange Management Service on Local Computer Error:

Posted by thinkjim | Posted in servers | Posted on 21-02-2008

0

error messageAfter rebooting a Windows 2000 Advanced Server (running Exchange 2000 SP3) the Microsoft Exchange Management Service Failed to Start. Manually starting the service generated the following error:

“Could not start the Microsoft Exchange Management Service on Local Computer. The service did not return an error. This could be an internal Windows error or an internal service error. If the problem persists, contact your system administrator.

The event log also contained an error:

Event ID: 6
Source: MSExchangeMGMT
Type: Error
Description: The Microsoft Exchange Management service encountered an error (0xThe specified module could not be found.)

A colleague of mine browsed eventID.net. A suggested solution was to check the path to the “atl.dll file in registry”. Registry Key:

HKEY_CLASSES_ROOT\CLSID\{44EC053A-400F-11D0-9DCD-00A0C90391D3}\
InprocServer32 @=”C:\\WINNT\\System32\\ATL.DLL

There were two keys present after searching the registry, one was pointing to the correct location (”c:\winnt\system32\atl.dll”) the other was pointing to c:\program files\ibm\dsa\atl.dll. The article suggests that only the c:\winnt\system32 path will work and the service will fail to start if it is pointing to a different location.

I’m no clearer as to the role that the atl.dll file plays with the exchange management service, but changing the second key so that it was re-pointed to c:\winnt\system32 did the trick. The service started successfully after a manual start. Earlier that week IBMs Dynamic System Analysis Tools (DSA tools) had been installed on the server. For whatever reason the tool seems to have changed one of the ATL.dll registry keys, causing the management service to fail.

Quick Field Report: Unhappy Server after applying SP1 for Backupexec 11D

Posted by thinkjim | Posted in servers | Posted on 16-02-2008

0

OS: Windows 2000 SP4 (with rollups)
HP ML350 with HP surestore DLT80 External SCSI Drive Attached.
Offending Software: Backup Exec 11D

After installing service pack 1 for backup exec 11d the server required a reboot. After rebooting and on startup experienced difficulty browsing other machines using explorer and was unable to access the network connections in my network places. Unable to Browse web. First checked physical network connection (replaced cable and rebooted). No effect. Server was responding to ping. Event logs contained errors relating to the remote access service saying that it had failed to start and also:Event ID 7011: Service Control Manager

Type: Error
Description: Timeout (30000 milliseconds) waiting for a transaction response from the RasManservice.

backupexec

Remote Access connection manager service was hung in ’starting’ state. Checked that the Remote Storage Manager wasn’t running (Backupexec doesn’t like it), it was. Disabled the Remote Storage Service, and attempted to stop the service which was running. Was unable to stop the service although I was able to disabled it. Attempted to shutdown server. Server would not shutdown. pressing the ’soft’ power off button generated an error about the remote storage manager. Had to do a hard reset. Server booted correctly, Remote storage Service remained disabled and did not start. No Remote access errors after bootup all services seem to be working correctly.
Lesson learned: Make sure the Remote Storage Service is disabled when running backupexec.