"Bootmgr is missing Press Ctrl+Alt+Del to restart"

Method 1: Run Startup Repair from Windows Recovery Environment (WinRE)

To run Startup Repair from the Windows Recovery Environment (WinRE), follow these steps:

1. Insert the Windows 7 or Windows Vista installation disc into the disc drive, and then start the computer.
2. Press a key when the message Press any key to boot from CD or DVD appears.
3. Select a language, a time and a currency, a keyboard or input method, and then click Next.
4. Click Repair your computer.
5. In the System Recovery Options dialog box, select the drive of your Windows installation, and then click Next.
6. At the System Recovery Options dialog box, click Repair your computer.
7. Click the operating system that you want to repair, and then click Next.
8. In the System Recovery Options dialog box, click Startup Repair.

Method 2: Rebuild the BCD from Windows Recovery Environment (WinRE)

1. Put the Windows 7 or Windows Vista installation disc in the disc drive, and then start the computer.
2. Press a key when the message Press any key to boot from CD or DVD appears.
3. Select a language, a time, a currency, a keyboard or another input method, and then click Next.
4. Click Repair your computer.
5. Click the operating system that you want to repair, and then click Next.
6. In the System Recovery Options dialog box, click Command Prompt.
7. Type Bootrec /RebuildBcd, and then press ENTER.

Method 3: Run System Restore from Windows Recovery Environment (WinRE)

Important: This method requires that System Restore is enabled on your computer.

To run System Restore from Windows Recovery Environment (WinRE), follow these steps:

1. Insert the Windows 7 or Windows Vista installation disc into the disc drive, and then start the computer.
2. Press a key when the message Press any key to boot from CD or DVD appears.
3. Select a language, a time and currency, and a keyboard or input method, and then click Next.
4. Click Repair your computer.
5. In the System Recovery Options dialog box, select the drive of your Windows installation, and then click Next.
6. In the System Recovery Options dialog box, click System Restore.
7. Follow the System Restore Wizard instructions and select the appropriate restore point.
8. Click Finish to restore the system.

Method 4: Use Startup Repair on a computer that has a preinstalled recovery option on your computer

Important: This method is available only if Startup Repair is a preinstalled recovery option on your computer.

If you do not have a Windows 7 or Windows Vista disc, and Startup Repair is a preinstalled recovery option on your computer, follow these steps to repair startup files:

1. Remove all floppy disks, CDs, and DVDs from your computer, and then restart your computer by using the computer's power button.
   • If your computer has a single operating system installed, press and hold the F8 key as your computer restarts. You have to press F8 before the Windows logo appears. If the Windows logo appears, you have to try again by waiting until the Windows logon prompt appears, and then shutting down and restarting your computer.
   • If your computer has more than one operating system, use the arrow keys to highlight the operating system that you want to repair, and then press and hold F8.
2. On the Advanced Boot Options screen, use the arrow keys to highlight Repair your computer, and then pressEnter. (If Repair your computer isn't listed as an option, then your computer doesn't include preinstalled recovery options, or your network administrator has turned them off.)
3. Select a keyboard layout, and then click Next.
4. Select a user name, type the password, and then click OK.
5. On the System Recovery Options menu, click Startup Repair. Startup Repair might prompt you to make choices as it tries to fix the problem and, if it is necessary, it might restart your computer as it makes repairs.

Read More

Account Classification SB to NREGA

This tool is to be used only by offices handling NREGS accounts. This tool is for classifying the NREGS accounts from the list of SB accounts and entering Job Card details. More details are available in the release document.

SB-to-NREGA  tool  is intended  for  classifying  NREGS  Accounts  from  the  list  of  SB  accounts,  so  that 
information regarding the number of NREGS accounts standing at any PO can be obtained for the use of 
Rural Business Directorate and for preparatory work on migration to CBS. 

In addition to classification of accounts, this tool  also rectifies the issues related to multiple  job card 
entries and invalid job card entries. 

Important Note: 
This tool can be used in both HOs and SOs.  If the SOs are doing data transfer to HO it is essential 
that the data is upto-date at both ends, before the SO starts classification of accounts using this 
tool. 

Functionality of the tool: 
1.    The tool lists the account number blocks pertaining to SB accounts. 
2.    On selection of a particular block, all the live accounts from the block are displayed in a grid of 
12 records 
3.    On selecting the account number, it will be marked as a NREGS account. 
4.    Against each account number, BO names are displayed in a dropdown menu for linking the BO 
accounts to the concerned BO. If the account is already a BO account, this option is disabled. 
5.    Option is available for entering the Job Card number in respect of each account. If any Job Card 
number is already available in the  database, the  same  is displayed; this field can be edited if 
necessary. 
6.    On  clicking  the  Save  button,  all  the  entries/changes  made  in  respect  of  the  check-marked 
accounts will be saved and the next batch of 12 accounts will be displayed

Download the patch Download

Read More

How to manage frauds that go mobile?

Since the release of the original iPhone, one billion smartphone activations and 700 million downloads of Angry Birds later, mobile devices have proliferated.

Financial service organizations are tapping into this market by moving products and services to mobiles, delivering specialized small-screen adaptations for browsing, and developing apps that supply mobile functionality and services that enable customers anywhere-anytime access to account information.

Mobile banking alone is expected to grow to nearly 900 million users by 2015.

While a majority of fraud attempts are still targeted at users in the online channel, as banking services go mobile, so are the attacks that target banking customers. Here are some of the most common attack methods being used by cyber-criminals to target mobile banking users today.

Smishing, or SMS phishing, sends a text message to a user's mobile phone in an attempt to get her to divulge personal information. As is the case with phishing, a smishing attack usually has a call to action for the intended victim that requires an immediate response.

Smishing has become easier to do and is becoming an attractive alternative with higher success compared to phishing as consumers are not conditioned to receiving spam on their mobile phone, so are more likely to believe the communication is legitimate.

Furthermore, whereas a majority of phishing emails get stopped by spam filters and often never reach their intended targets, there is no mainstream mechanism for weeding out 'spam' text messages.

Some mobile malware is programmed to conduct man-in-the-middle attacks, capable of forwarding SMS messages with a user's Mobile Transaction Numbers (mTANs) to an attacker. These mTANs are often used as a way for banking customers to confirm that they initiated a transaction.

By intercepting the code, cyber-criminals can initiate a transaction and then use the unique code to verify the transaction as though they were the legitimate user. Examples of man-in-the-mobile threats have been most commonly found within well known banking Trojans such as Zeus and SpyEye.

Rogue applications are becoming plentiful in most online app stores. Today, Android is the most common platform being exploited by cyber-criminals. Recently, a new Android Trojan was discovered that displays a video downloaded from the net — only if some sensitive information is previously sent to a remote server.

Today, RSA's Anti-Fraud Command Center is witnessing an average of about 3 per cent of all fraudulent transactions originating in mobile channels or devices. While this hardly compares to the percentage of fraud in the online channel, mobile threats continue to emerge and, in time, that number will rise.

Here are some expected mobile threats and developments in the coming year.

Smishing will continue to increase. Many financial institutions have been successful in getting standard phishing attacks under control. However, smishing presents a whole new series of challenges.

Phone flooding services increase in popularity. Out-of-band authentication via SMS or phone call is being used across the financial industry as a step-up authentication method for high-risk transactions.

To overcome this additional security, cyber-criminals flood an intended victim's phone with calls, ultimately rendering the phone useless and interfering with bank's attempt to alert a user to a high risk transaction.

Banking Trojans continue to be developed for mobiles. There have been several attempts at coding SpyEye variants for mobile platforms (mainly Android). These custom codes are designed to attempt intercepting SMS codes sent during transaction authentication by forwarding the content of the text message to the attacker's server.

The code is still young and its presence on mobile phones is limited. However, cyber-criminals are focusing their efforts on the mobile platform.

New Trojan plug-ins are targeting the mobile phone. Many banking Trojans available for sale in the black market offer plug-ins that enable HTML injection. When an infected user attempts to access her online banking site, the Trojan automatically injects extra fields in the login page. Most often, the extra details cyber-criminals attempt to obtain are credit card numbers and ATM PIN codes.

Portable nature of mobile devices — and information that is stored or accessed on them — is what makes them so vulnerable (when was the last time you misplaced your desktop?).

Also, if a mobile device is lost or stolen, it is typical for consumers to call their mobile provider to report it, but they don't usually call their bank to report it. If the user engages in mobile banking, all financial information stored on the device could be easily accessed.

Attacks are evolving in the mobile channel and as the popularity of mobile banking grows, financial institutions are challenged with how to translate the success they have had in managing fraud risk in the online channel and applying those same best practices to the mobile channel.

Understanding how to secure your customers against mobile attacks is the first step in turning the tide on fraud — and taking full advantage of the opportunities that this channel presents. 

Source :  http://economictimes.indiatimes.com

Read More

Railways’ Centralised Enquiry Number

The Centralised Enquiry Service on single enquiry number, 139 is operated on Public Private Partnership basis. The entire cost of infrastructure and operation of this service is borne by the franchise out of revenue from call charges. The passengers are being charged the telephone call/Short Messaging Service (SMS) by the Telecom Service Providers (TSPs)

The following call charges are applicable for calls on 139:- Landline: Rs. 1.20 for a pulse of 180 seconds for calls from Metros cities while from non-metro cities, Rs. 1.20 for a pulse of 60 seconds is charged. Mobile: Rs 1.20 for a pulse of 60 seconds for calls from metro cities and Rs. 2.00 for a pulse of 60 seconds for calls from non-metro cities.

SMS: Rs. 3.00 per SMS

The call charges for 139 services are fixed in terms of the agreement between Indian Railway Catering and Tourism Corporation (IRCTC) and the franchisee which was fianlised through a process of open tender. The agreement is valid till January, 2017 and the call/SMS charges are applicable for the period of contract.

About 6.70 lakh and 2 lakh SMSs are being received on Centralised Enquiry Number 139 every day.

This information was given by the Minister of State for Railways Shri Adhir Ranjan Chowdhury in written reply to a question in Lok Sabha today. 

Source: PIB

Read More

SB Order 15/2012 - Purchase of NSCs by an Adult on behalf of a Minor - A clarification

It was clarified by SB Order no 16/2012 released 0n 16.11.2011 that NSCs can be purchased by an Adult in the name of a Minor irrespective of any relation.

Click here to view SB order no 16/2012.

Read More