User talk:ShankarSG

NETWORK CABLE UNPLUGGED Workaround 1. Run regsvr32 netshell.dll, Click Ok for the file succeeded window. 2. Run regsvr32 netcfgx.dll, Click Ok for the file succeeded window. 3. Run regsvr32 netman.dll, Click Ok for the file succeeded window. 4. Restart Computer. 5. There will be no network icon on the task bar but the network will work. 6. If this doesn't work then a 32 bit diags is done. 7. If 32 bit diags pass we do a OS Reinstall. - Using the Tool Download and install the Windows Debugger from the Microsoft Web Site.

NOTE: If you use Google to search for "windows debugger," the first link returned will be the Windows Debugger home page.

Once installation completes, click Start → All Programs → Debugging Tools for Windows → WinDbg to open the debugger. Configure the symbol path used by the debugger to turn addresses in the memory dump file into meaningful location names: expand the File menu → select Symbol File Path → type "SRV*c:\debug_symbols*http://msdl.microsoft.com/download/symbols" in the dialog box → click OK. Open a minidump file: expand the File menu → select Open Crash Dump → select the desired dump file → and click Open.

NOTE: The system usually stores minidump files in: C:\WINNT\Minidump\ or C:\Windows\Minidump\. The files will be named miniMMDDYY-NN.dmp, where MM is the month, DD is the day, and YY is the year in which the dump file was created. NN is the sequence the dump files were created in if multiple dumps were generated on the same day (the first crash dump on a given day will be numbered 01, the second 02, etc.). The debugger will open the dump file and give a brief description of what caused the system to crash. NOTE: The first time you use the Debugger to open and dump file on a system, it will take a few minutes to download symbol information in the background before it returns any information. - MS OFFICE 2007 Product Ky cperroni@ku.edu CHRISTINNA

J9Y6K C37JF RXM9B BWWH3 84TKJ --- CTS OFFER Total- 280005 1 Basic 5,458 65,496. 2 Conveyance Allowance * 800 9,600. 3 House Rent Allowance * 3,275 39,298. 4 Special Allowance* 9,846 118,152. 5 Medical Allowance * 1,250 15,000. 6 Shift Allowance ** 550 6,600. 7 Employer’s Contribution to Provident Fund 655 7,860. 8 Incentive (Per Annual)*** 18,000. Annual Total Compensation 280,005.

CTS
Total- 280005 1 Basic 5,458 65,496.

2 Conveyance Allowance * 800 9,600.

3 House Rent Allowance * 3,275 39,298.

4 Special Allowance* 9,846 118,152.

5 Medical Allowance * 1,250 15,000.

6 Shift Allowance ** 550 6,600.

7 Employer’s Contribution to Provident Fund 655 7,860.

8 Incentive (Per Annual)*** 18,000.

Annual Total Compensation 280,005.

624686764 JIM MARTIN 9193956080 OSRI b4 dispatch --- EmpID	Badge	Last Name	First Name	Email Address	DCSE TECH ID IN031704	489772	Subramanyam	 Gopi Shankar	GopiShankar_S@SUTH.COM 527395

How to avoid OSRI

Make sure you run the PSA before you do.

I get this error message: Unmountable boot volume When booting up to Windows XP you may get an error that reads: Unmountable Boot Volume.

This is probably because your boot.ini file is messed up. Here is a possible remedy:

1.    Start Windows XP with the Windows XP CD in your CD/DVD drive.

2.    Once you see the "Welcome to setup" message, press the letter 'R' on your keyboard to enter the Recovery Console.

3.    Select the Windows installation to be repaired (you will need to know the administrator password.

4.    You will then get a DOS prompt. from here, type: chkdsk /p [Enter]

5.    When that is done type: fixboot  [Enter]

6.    Type: Y at the next prompt  [Enter]

7.    Then type: exit  [Enter]

8.    The system will now reboot into Windows.

If for some reason that didn't work, you can boot to the recovery console (example above).

Type: "chkdsk /r" [Enter]

When done type: exit [Enter].

This takes a bit longer, but the system should boot back into Windows.

If you get an error that NTLDR is not found during bootup If you have FAT32 partitions, it is much simpler than with NTFS. Just boot with a Win98 floppy and copy the NTLDR or NTDETECT.COM files from the i386 directory to the root of the C:\ drive.

For NTFS:

1.    Insert and boot from your Windows XP CD.

2.    At the first R=Repair option, press the R key

3.    Press the number that corresponds to the correct location for the installation of Windows you want to repair. Typically this will be #1

4.    Enter in the administrator password when requested

5.    Enter in the following commands (X: is replaced by the actual drive letter that is assigned to the CD ROM drive)

·        COPY X:\i386\NTLDR C\:

·        COPY X:\i386\NTDETECT.COM C\:

6.    Take out the CD and type exit

NTOSKRNL Missing or Corrupt If you get an error that NTOSKRNL not found:

Insert and boot from your WindowsXP CD. At the first R=Repair option, press the R key Press the number that corresponds to the correct location for the installation of Windows you want to repair. Typically this will be #1 Change to the drive that has the CD ROM. CD i386 expand ntkrnlmp.ex_ C:\Windows\System32\ntoskrnl.exe If WindowsXP is installed in a different location, just make the necessary change to C:\Windows Take out the CD ROM and type exit

HAL.DLL Missing or Corrupt If you get an error regarding a missing or corrupt hal.dll file, it might simply be the BOOT.INI file on the root of the C: drive that is misconfigured

Insert and boot from your WindowsXP CD. At the first R=Repair option, press the R key Press the number that corresponds to the correct location for the installation of Windows you want to repair. Typically this will be #1 Type bootcfg /list to show the current entries in the BOOT.INI file Type bootcfg /rebuild to repair it Take out the CD ROM and type exit

Corrupted or Missing \WINDOWS\SYSTEM32\CONFIG If you get the error:

Windows could not start because the following files is missing or corrupt \WINDOWS\SYSTEM32\CONFIG\SYSTEM or \WINDOWS\SYSTEM32\CONFIG\SOFTWARE

Insert and boot from your Windows XP CD. At the first R=Repair option, press the R key Press the number that corresponds to the correct location for the installation of Windows you want to repair. Typically this will be #1 Enter in the administrator password when requested cd \windows\system32\config Depending on which section was corrupted: ren software software.bad or ren system system.bad Depending on which section was corrupted copy \windows\repair\system copy \windows\repair\software Take out the CD ROM and type exit

My system shows I am missing some files, how can I replace them? If you are missing files of a Windows component, then you can run the System File Checker. Windows File Protection only monitors and maintains XP system components. If it is a 3rd party application, you may need to reinstall that application to restore the missing files.

Method #1:

To run Windows System File Checker:

Go to Start>> Run, type in: sfc /scannow [Enter]

Windows may require you to insert your XP CD.

Method #2:

You can also use System Restore to recover your system back to date before the files were missing. To activate System Restore:

Go to Start>> All Programs>> Accessories>> System Tools>> System Restore. Active Directory, LDAP, Kerberos, LDAP protocol, Group Policy Objects (GPOs, Organizational Units (OUs), domain controllers,  SRV resource records,  Remote Procedure Calls,