PAY COMMISSION ORDERS OF DEPARTMENT OF POSTS

PAY COMMISSION - Department of Posts ORDER

FULL TEXT OF POSTAL DIRECTORATE ENDORSEMENT ORDER DOP NO.4-4/2008-PCC DATED 04.09.2008 ON REVISION OF PAY SCALES PLACED AS UNDER:

OFFICE MEMORANDUM

Sub; Sixth Central Pay Commission-Revision of Pay Scales in respect of Group 'A', 'B', 'C' and 'D' Employees –2008.

D.G. Posts No. 4-4/2008-PCC dated 04-09-2008.

A copy of the Ministry of Finance (MOF) Gazette Notification Vide G.S.R. 622(E) dated 29.08.2008 promulgating the Central Civil Service (Revised Pay) Rules 2008 is forwarded herewith along with the following other orders; notification of Revised Pay Structures and illustrations regarding fixation of pay of the employees in the Revised Pay Scales & Option Proforma and orders relating to various Allowances and Pension are forwarded herewith for information, guidance and necessary action.

Sl. No.
Letter /Notification
Subject
1
Gazette Notification No. 304 in File No. 1/1/2008-IC dated 29.08.2008
Resolution.
2
1/1/2008-IC dated 29.08.2008
Instructions regarding Pay and Payment of arrears
3
1(3)/2008-E-II (B) dated 29.08.2008
Dearness Allowance
4
2(13)/2008-E-II (B) dated 29.08.2008
HRA & CCA
5
3(1)/ 2008-E-II (B) dated 29.08.2008
Spl. Comp. (Remote Locality) Allowance
6
4(2) 2008-E-II (B) dated 29.08.2008
Spl. Comp. (Hill Area) Allowance
7
9(11) 2008-E-II (B) dated 29.08.2008
Split Duty Allowance
8
21(2) 2008-E-II (B) dated 29.08.2008
Transport Allowance
9
5(1) 2008-E-II (B) dated 29.08.2008
Bad Climate Allowance
10
6(3) 2008-E-II (B) dated 29.08.2008
Project Allowance
11
11(5) 2008-E-II(B) dated 29.08.2008
Spl. (Duty) Allowance in NE & Ladhak
12
12(4) 2008-E-II (B) dated 29.08.2008
Hard Area allowance
13
12(3) 2008-E-II (B) dated 29.08.2008
Island Spl. (Duty) Allowance
14
13(1) 2008-E-II (B) dated 29.08.2008
Discontinuance of Border Area Allowance
15
17(1) 2008-E-II (B) dated 29.08.2008
Schedule /Tribal Area Allowance
16
19039/3/2008-E-III (A) dated 30.08.2008
Cycle (Maintenance) Allowance
17
7(19) 2008-E-III (A) dated 30.08.2008
NPA attached to Medical Officers
18
7(19) 2008-E-III (A) dated 30.08.2008
NPA attached to Veterinary Posts

2. The process to obtain, fixation of pay in the revised pay structure, calculating the arrears according to the Gazette Notification GSR 622(E) dated 29.08.08 may be started immediately. Before payment of arrears, it may be ensured that the undertaking as prescribed in MOF OM No. 1/1/2008-IC dated 30.08.2008 is obtained from each official and kept on record.
Sdxx
(A.K.Sharma)
Dy. Director General (Estt.)
04.09.28

Problems when using WIFE 1.0

To: TechNICAL Support
Dear Sir,
Last year I upgraded my system from Girlfriend 7.0 to Wife 1.0 and noticed that the new program began creating problems within the system processing and that took up a lot of space and valuable resources.
Wife 1.0 installs itself into all other programs and launches during system initialization, where it monitors all other system activity.
Applications such as Poker Night 2.3, Girlfriend 3.2 and Saturday Football 5.0 no longer run, crashing the entire system whenever selected :(
I cannot seem to keep Wife 1.0 in the background while running my other favorite applications. Whichever module or software I enter, only Wife 1.0 seems to run and nothing else.
I am thinking about going back to Girlfriend 7.0, but the uninstall from Wife 1.0 to Girlfriend 7.0 does not work on this program. Can you help me, please!!!
Thanks,
babu......


Ha! the reply is in the below post........................

Reply for above letter

ReplyTo: Babu
Dear Babu,

This is a very common problem men users of the Wife 1.0 software complain about but it is mostly due to a primary misconception of the software. Many men upgrade from Girlfriend 7.0 to Wife 1.0 with the idea that Wife 1.0 is merely a UTILITIES & ENTERTAINMENT program. Wife 1.0 is an OPERATING SYSTEM and designed by its creator to run everything. It is unlikely you would be able to purge Wife 1.0 and still convert back to Girlfriend 7.0. Hidden operating files within your system would cause Girlfriend 7.0 to emulate Wife 1.0 so nothing is gained. It is impossible to uninstall, delete, or purge the program files from the system once installed !! You cannot go back to Girlfriend 7.0 because Wife 1.0 is not designed to do this. Some have tried to install Girlfriend 8.0 or Wife 2.0 but end up with more problems than the original system. Look in your manual under "Worries Invited For Ever (Wife 1.0)". I recommend you keep Wife 1.0 and just deal with the situation. Having Wife 1.0 installed myself, I might also suggest you read the entire section regarding general partnership faults (GPFs). You must assume all responsibility for faults and problems that might occur, regardless of their cause. The best course of action to solve this major IT problem of yours will be to enter the command C:\APOLOGIZE. In any case avoid excessive use of the Esc key because ultimately you will have to give the APOLOGIZE command before the operating system will return to normal. The system will run smoothly as long as you take the blame for all the GPFs. Wife 1.0 is a great program, but very high maintenance. Consider buying additional software to improve the performance of Wife 1.0. I recommend you to install the latest gift software like Flowers 2.1, Necklaces 3.2, and Chocolates 5.0. note: Do not under any circumstances, install Secretary With Skirt 3.3. This is not a supported application; in fact it is a deadly virus for Wife 1.0 and is likely to cause irreversible damage to the operating system.

regards, giri.....

Backup / Restore XP Activation

When you activate Windows XP, Microsoft stores the data in the Windows Product Activation database files wpa.dbl and Wpa.bak in the folder %systemroot%\system32. If you change the motherboard or make significant hardware changes, XP will require you to reactive. But if you plan to reinstall XP on the same hardware, you can back up the activation status and then restore it after you reinstall and avoid the activation process. You can backup the Windows Product Activation database files to diskette. They are very small. A directory listing from my XP Pro workstation:
C:\WINDOWS\system32>dir wp*
Volume in drive C has no label.
Volume Serial Number is 8447-0571
Directory of C:\WINDOWS\system32
10/24/2001 08:28 PM 12,584 wpa.bak
01/14/2002 09:05 AM 12,642 wpa.dbl
After you reinstall XP, to restore the Windows Product Activation database files:
Start XP to Minimal Safe mode
Change directory to the \%systemroot%\system32 folder
Rename the newly created wpa.dbl to wpa.nonactivated and wpa.bak, if it exists, to wpabak.nonactivated.
Copy your backed up wpa.dbl and wpb.bak files to the system32 folder
Reboot This should work if you want to avoid activating XP after a reinstall or restore on the same or very similar hardware. It will not work if the hardware is significantly different from that in place when the Windows Product Activation database files were created. This is not a hack to avoid activating installations.

Enable / Disable Task Manager in Windows XP Home / Pro

There is a registry hack to enable or disable Windows NT TaskManager. The same registry hack applies to Windows 2000 and Windows XP.
Hive:HKEY_CURRENT_USER

Key: Software\Microsoft\Windows\CurrentVersion\Policies\System

Name: DisableTaskMgr

Type: REG_DWORD Value: 1=Enablethis key, that is DISABLE TaskManager

Value: 0=Disablethis key, that is Don't Disable, Enable TaskManager
As part of the enhanced management available in Windows 2000 and Windows XP, rather than risking a registry change, as an administrator you can enable or disable Windows 2000 Pro or Windows XP Pro's TaskManager using Group Policy Editor. This can be applied to the local policy. Note: if you are trying to override your organizations group policy, you can't. As soon as you re-authenticate to the domain, the domain or OU Group Policy will rewrite the registry setting. But if the TaskManager was accidently disabled or you need to control this item for a set of standalone boxes this is for you:
Click Start
Click Run
Enter gpedit.msc in the Open box and click OK
In the Group Policy settings window
Select User Configuration
Select Administrative Templates
Select System
Select Ctrl+Alt+Delete options
Select Remove Task Manager
Double-click the Remove Task Manager option And as I mentioned above, since the policy is Remove Task Manager, by disabling the policy, you are enabling the Task Manager.

How to prevent the hand from appearing on the icons of shared resources

As you probably know, a hand appears on the icons of folders and drives you share on your network. However, if you don’t want people knowing what you’re sharing (or the hand just bothers you), you can remove the hand from the icons of the resources you share; which requires editing the Windows Registry:
Hive: HKEY_CLASSES_ROOT
Key: Network\SharingHandler
Name: (Default)
Type: REG_SZ
Value: blank = No Icon, "msshrui.dll" for Windows 9x/Me, "ntshrui.dll" for Windows NT/2000/XP/Vista
After editing the registry, you need to restart your PC.
You can still view the resources you are sharing via the Computer Management window. In Windows XP, this is accessible by clicking Start>Control Panel>Performance and Maintenance category>Administrative Tools>Computer Management. Then expand System Tools and Shared Folders, and click on the Shares folder.

Enabling the NumLock Key

You can control whether the NumLock key is automatically on or off at logon using the following Windows NT / Windows 2000 / Windows XP registry hack:
Hive: HKEY_CURRENT_USERKey: Control Panel\KeyboardName: InitialKeyboardIndicatorsType: REG_DWORDValue: 0 NumLock disabled for current user after logging onValue: 2 NumLock enabled and will retain the settings from the last shutdown
Numlock doesn't reflect these setting during the logon phase because at that point, NT is using the .Default user profile since it does not know which user is logging on. Make the same changes to HKEY_USERS\.DEFAULT\Control Panel\Keyboard if you want the numlock state to be consistent throughout.
The best, and non-registry editing method to set InitialKeyboardIndicators, is to set numlock on, then use Alt-Ctrl-Del to log off. It should remember state for the account.
Its usually best to avoid registry hacks if possible. You can use the following Windows Script, name it numlock.vbs, to control numlock:

set WshShell = CreateObject("WScript.Shell")
WshShell.SendKeys "{NUMLOCK}"

For an individual user, copy numlock.vbs to the user's startup folder. To get the script to run for all users, put the script in the Startup folder in the All Users profile.
In a Windows 2000 environment, you can control this functionality with Group Policy.