Uravugal Thodarkathai

உறவுகள் தொடர்கதை உணர்வுகள் சிறு கதை

ஒரு கதை என்றும் முடியலாம்

முடிவிலும் ஒன்று தொடரலாம்

இனியெல்லாம் சுகமே

உன் நெஞ்சிலே பாரம் உனக்காகவே நானும்

சுமை தாங்கியாய் தாங்குவேன்

உன் கண்களின் ஓரம் எதற்காகவோ ஈரம்

கண்ணீரை நான் மாற்றுவேன்

வேதனை தீரலாம் வெறும் பனி விலகலாம்

வெண்மேகமே புது அழகிலே நானும் இணையலாம்

உறவுகள் தொடர்கதை உணர்வுகள் சிறு கதை

ஒரு கதை என்றும் முடியலாம்

முடிவிலும் ஒன்று தொடரலாம்

இனியெல்லாம் சுகமே

வாழ்வென்பதோ கீதம் வளர்கின்றதோ நாணம்

நாள் ஒன்றிலும் ஆனந்தம்

நீ கண்டதோ துன்பம் இனி வாழ்வெல்லாம் இன்பம்

சுக ராகமே ஆரம்பம்

நதியிலே புது புனல் கடலிலே கலந்தது

நம் சொந்தமோ இன்று இணைந்தது இன்பம் பிறந்தது

உறவுகள் தொடர்கதை உணர்வுகள் சிறு கதை

ஒரு கதை என்றும் முடியலாம்

முடிவிலும் ஒன்று தொடரலாம்

இனியெல்லாம் சுகமே

Forgot your XP Administrator password? Recover XP Administrator password

Have you forgotten your Windows Xp Administrator Password, cant remember even after many tries?
Well you can easily change or wipe out your Administrator password during Windows XP Repair. Here's step-by-step description of Repair process.

1. Place your XP CD in your rom and start your computer(it' s assumed that you have your bios set to "Boot from CDrom")
2. Select - Press any key to boot from CD
3. The first screen will indicate that Setup is inspecting your system and loading files.
4. Press ENTER to Setup Windows now
5. The Licensing Agreement comes next - accept it.
6. The next screen is the Setup screen which gives you the option to do a Repair, press R to begin the Repair process.
7. Setup will now check your disks and then start copying files
8. After the Copying Files stage, you will be required to reboot.
9. During the reboot, do not make the mistake of "pressing any key" to boot from the CD again! Setup will resume automatically with the standard billboard screens and you will notice Installing Windows is highlighted.
10. Keep your eye on the lower left hand side of the screen and when you see the Installing Devices progress bar, press SHIFT + F10. This is the Security hole! A command console will now open up giving you the potential for wide access to your system.
11. At the prompt, type NUSRMGR.CPL and press Enter. You will gain graphical access to your User Accounts in the Control Panel.
12. Now simply pick the account you need to change and remove or change your password as you prefer. After you've made your changes close the window, exit the command box and continue on with the Repair.
13. Once the Repair is done, you will be able to log on with your new password. Your programs and personalized settings should remain intact.

By,
Lokesh G _L-
"Nobody is Perfect,
I AM A LEARNER"

Increase your hard disk speed....

To speed up your hard disk speed we need to configure a special buffer in the computer's memory in order to enable it to better deal with interrupts made from the disk.

This tip is only recommended if you have 256MB RAM or higher.

Follow these steps:

1) Run SYSEDIT.EXE from the Run command.

2) Expand the system.ini file window.

3) Scroll down almost to the end of the file till you find a line called [386enh].

4) Press Enter to make one blank line, and in that line type

Irq14=4096

Note: This line IS CASE SENSITIVE!!!

Click on the File menu, then choose Save.

Close SYSEDIT and reboot your computer.

Done. Speed improvement will be noticed after the computer reboots.

By,
Lokesh G _L-
"Nobody is Perfect,
I AM A LEARNER"

Outlook Sends duplicate mails multiple copies

Hi,

Sometimes we face issue in Outlook. Outlook sends same mail multiple times to user and it will not go out from outbox.

Cause:
Outlook sends the same mail multiple times to the receiver and will not go out from your outbox.

Solution:
This happens because .ost or .pst corrupt.
1. .ost --> Offline store.
2. .pst --> Personal store.

Here, .ost we use when we configure outlook as Exchange mode.
.pst is for POP3 and SMTP

So the following steps will guide to resolve this problem.

.ost Issue:

1. Clearing by Offline date will resolve this issue, to clear offline data, right click on your mailbox and select Properties.
2. You will find Clear Offline Items command button. Click on this.
3. If this is not solving your purpose, try the other option.
4. By recreating your account setting will solve this issue, to recreate the account follow the below steps.
5. Goto Tools-->Email Accounts. Select View or change existing e-mail account radio button and say Next.
6. Highlight Microsoft Exchange Server and say Remove. Now you have removed your e-mail account, let we recreate account.
5. Repeat the step 5 and select server type as Microsoft Exchange server say next.
6. Here type your exchange Server name and Username and say checknames to find the name.
7. Finally say Next and Finish.

Now the issue has been resolved.

.pst Issue:

1. In this case better you can create a new .pst file (i.e., new personal folder). To create personal folder follow the following steps.
2. Goto File--> Data File Management. Here Click Add to create new Personal folder.
3. Select Office Outlook Personal folders file(.pst) and say ok.
4. Select the path where you want to keep the file.
5. Give the name for your new personal folder and say ok.
6. Now your personal folder has been sucessfully created. Now your mails has to deliver automatically into this folder, to setup this follow the below steps.
7. Goto Tools --> E-mail Accounts and select view or change your e-mail accounts.
8. Here select drop down menu under Deliver new e-mail to the following location, and select your personal folder.
9. Finally click finish.
10. Goto File --> Data File Management and select your personal folder and say make as default delivery location.

Now I hope your Problem has been resolved.

By,
Lokesh G _L-
"Nobody is Perfect,
I AM A LEARNER"

How to use the Sysprep tool to automate successful deployment of Windows XP

Requirements for running the Sysprep tool

Before you can use the Sysprep tool, your computer hardware and related devices must meet the following requirements:

•	The reference and destination computers must have compatible HALs. For example, Advanced Programmable Interrupt Controller (APIC)–based MPS (multiprocessor systems) must use the same APIC HAL. A standard HAL Programmable Interrupt Controller (PIC)–based system is not compatible with either the APIC HAL or the MPS HAL.
•	The reference and destination computers must have the same Advanced Configuration and Power Interface (ACPI) support.
•	The Plug-and-Play devices on the reference and destination computers, such as modems, sound cards, network adapters, and video cards, do not have to be from the same manufacturer. However, the drivers for these devices must be available.
•	Third-party disk-imaging software or disk-duplicating hardware devices are required. These products create binary images of a computer's hard disk and either duplicate the image to another hard disk or store the image in a file on a separate disk.
•	The size of the hard disk on the destination computer must be at least the same size as the hard disk on the reference computer. If the destination computer has a larger hard disk, the difference is not included in the primary partition. However, you can use the ExtendOemPartition key in the Sysprep.inf file to extend the primary partition if it was formatted by using the NTFS file system.

Prepare a reference computer for Sysprep deployment

To prepare a reference computer for Sysprep deployment in Windows XP, follow these steps:

1.	On a reference computer, install the operating system and any programs that you want installed on your destination computers.
2.	Click Start, click Run, type cmd, and then click OK.
3.	At the command prompt, change to the root folder of drive C, and then type md Sysprep.
4.	Insert the Windows XP operating system CD into the appropriate CD-ROM or DVD-ROM drive, and then open the Deploy.cab file in the \Support\Tools folder. Note To make sure that you are using the correct version of the Deploy.cab file for your service pack, use the Deploy.cab file that is distributed with that service pack.
5.	Copy the Sysprep.exe file and the Setupcl.exe file to the Sysprep folder. Note If you use the Sysprep.inf file, copy this file to the Sysprep folder also. For the Sysprep tool to function correctly, the Sysprep.exe file, the Setupcl.exe file, and the Sysprep.inf file must all be in the same folder.
6.	Remove the Windows XP operating system CD.
7.	At the command prompt, type cd Sysprep to change to the Sysprep folder.
8.	To run the Sysprep tool, type the following command at the command prompt: Sysprep /optional parameter Note For a list of parameters, see the "Sysprep parameters" section. If you run the Sysprep.exe file from the %systemdrive%\Sysprep folder, the Sysprep.exe file removes the whole folder and the contents of the folder after it finishes.
9.	Microsoft recommends that after you run the Sysprep.exe file on a reference computer, isolate the reference computer from the local network where the image will be subsequently deployed to avoid any NetBIOS conflicts. This permits the Sysprep tool to complete the Setup program, join the domain that is specified, and use the new computer name that is specified in the Sysprep.inf answer file.

Create the Sysprep.inf answer file

The Sysprep.inf answer file is a text file that scripts the answers for a series of graphical user interface (GUI) dialog boxes. To create a Sysprep.inf answer file that is used by the Sysprep tool, you can use a text editor or you can use the Setup Manager tool that is included on the Windows XP CD and is also included with the Microsoft Windows XP Resource Kit. The answer file must be renamed to Sysprep.inf, and must reside in the Sysprep folder in the root of the drive where Windows XP is installed, or these files can reside on a floppy disk. If the Sysprep folder is named differently, the Setup program ignores it. There is not a parameter for specifying the Mini-Setup Wizard answer file.

Sysprep.inf answer file format and parameters

•

The Sysprep.inf answer file format and parameters are the same as the Unattended.txt file for Windows XP, but only the following sections and parameters are supported: [Unattended] ExtendOemPartition OemPnPDriversPath OemSkipEula InstallFilesPath KeepPageFile ResetSourcePath UpdateHAL UpdateUPHAL UpdateInstalledDrivers TapiConfigured [GuiUnattended] AdminPassword Autologon AutoLogonCount OEMDuplicatorString OEMSkipRegional OEMSkipWelcome TimeZone [UserData] Supports the same set of entries as the Unattend.txt file. [LicenseFilePrintData] Supports the same set of entries as the Unattend.txt file. [GuiRunOnce] Supports the same set of entries as the Unattend.txt file. [Display] Supports the same set of entries as the Unattend.txt file. [RegionalSettings] Supports the same set of entries as the Unattend.txt file. [Networking] Supports the same set of entries as the Unattend.txt file. [Identification] Supports the same set of entries as the Unattend.txt file. [TapiLocation] [Sysprep] Automatically generates the entries in the [SysprepMassStorage] section. [SysprepMassStorage] Allows you to use the same image on computers with different mass-storage devices.

Use the Setup Manager tool to create the Sysprep.inf answer file

To install the Setup Manager tool and to create an answer file, follow these steps:

1.	Open My Computer, and then open the Support\Tools folder on the Windows XP CD.
2.	Double-click the Deploy.cab file to open it.
3.	On the Edit menu, click Select All.
4.	On the Edit menu, click Copy To Folder.
5.	Click Make New Folder. Type the name that you want for the Setup Manager folder, and then press ENTER. For example, type setup manager, and then press ENTER.
6.	Click Copy.
7.	Open the new folder that you created, and then double-click the Setupmgr.exe file. The Windows Setup Manager Wizard starts.
8.	Follow the instructions in the wizard to create an answer file.

Sysprep parameters

You can use the following optional parameters with the Sysprep command in Windows XP:

•	-activated - Do not reset the grace period for Windows product activation. Use this parameter only if you have activated the Windows installation in the factory. Important The product key that you use to activate the Windows installation must match the product key that is located on the COA sticker that is attached to that particular computer.
•	-audit - Restarts the computer in Factory mode without having to generate new security IDs (SIDs) or process any items in the [OEMRunOnce] section of the Winbom.ini file. Use this command-line parameter only if the computer is already in Factory mode.
•	-bmsd - Populates all the available mass storage devices in the [SysprepMassStorage] section.
•	-clean - Clears the critical devices database that is used by the [SysprepMassStorage] section in the Sysprep.inf file.
•	-factory - Restarts in a network-enabled state without displaying Windows Welcome or mini-Setup. This parameter is useful for updating drivers, running Plug and Play enumeration, installing programs, testing, configuring the computer with customer data, or making other configuration changes in your factory environment. For companies that use disk imaging (or cloning) software, Factory mode can reduce the number of images that are required. When all the tasks in Factory mode are complete, run the Sysprep.exe file by using the -reseal parameter to prepare the computer for end-user delivery.
•	-forceshutdown - Shuts down the computer after the Sysprep.exe file finishes. Note Use this parameter with computers that have an ACPI BIOS that do not shut down correctly with the default behavior of the Sysprep.exe file.
•	-mini - Configures Microsoft Windows XP Professional to use Mini-Setup instead of Windows Welcome. This parameter does not affect Microsoft Windows XP Home Edition, where the first-run experience is always Windows Welcome. Note that if you plan to use the Sysprep.inf file to automate Mini-Setup, you must either run the Sysprep tool by using the -mini switch, or click to select the MiniSetup check box in the GUI interface. By default, if you do not choose to run Mini-Setup, Windows XP Professional runs the Windows Welcome.
•	-noreboot - Modifies registry entries (SID, OemDuplicatorString, and other registry entries) without the computer restarting or preparing for duplication. This parameter is mainly used for testing, specifically to see if the registry is modified correctly. Microsoft does not recommend this option because making changes to a computer after the Sysprep.exe file has run may invalidate the preparation that was completed by the Sysprep.exe file. Do not use this parameter in a production environment.
•	-nosidgen - Runs the Sysprep.exe file without generating new SIDs. You must use this parameter if you are not duplicating the computer where you are running the Sysprep.exe file or if you are preinstalling domain controllers.
•	-pnp - Runs the full Plug and Play device enumeration and installation of previous devices during Mini-Setup. This command-line parameter has no effect if the first-run experience is Windows Welcome. Use the -pnp command-line parameter only when you must detect and install previous, non-Plug and Play devices. Do not use the sysprep -pnp Note When unsigned drivers are unavoidable, use the UpdateInstalledDrivers=yes parameter in conjunction with OemPnPDriversPath= and DriverSigningPolicy=ignore instead of the -pnp command-line parameter to provide a more seamless installation. command-line parameter on computers that only use Plug and Play devices. Otherwise, you will increase the time that it takes for the first-run experience without providing any additional benefit to the user.
•	-quiet - Runs the Sysprep.exe file without displaying onscreen confirmation messages. This is useful if you are automating the Sysprep.exe file. For example, if you plan to run the Sysprep.exe file immediately after the unattended Setup program finishes, add the sysprep -quiet command to the [GuiRunOnce] section of the Unattend.txt file.
•	-reboot - Forces the computer to automatically restart, and then starts Windows Welcome Mini-Setup, or Factory mode, as specified. This is useful when you want to audit the computer and verify that the first-run experience is operating correctly.
•	-reseal - Clears the Event Viewer logs and prepares the computer for delivery to the customer. Windows Welcome or Mini-Setup is set to start the next time that the computer restarts. If you run the sysprep -factory command, you must seal the installation as the last step in your preinstallation process. To do this, run the sysprep -reseal command or click the Reseal button in the Sysprep dialog box.

By,
Lokesh G _L-
"Nobody is Perfect,
I AM A LEARNER"

Active Directory changes do not replicate in Windows Server 2003

Hi,

When you try to replicate Active Directory directory service changes to a Microsoft Windows Server 2003-based domain controller, the replication is not completed.

In the event log, you may see events that are similar to the following:

Event Type: Warning
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 1232
Computer: Inbound_Domain_Controller
Description: Active Directory attempted to perform a remote procedure call (RPC) to the following server. The call timed out and was canceled.
Server: DSA_GUID._msdcs.DNS_Domain_Name
Call Timeout (Mins): 5
Thread ID: Thread_ID

Event Type: Warning
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 1188
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: Inbound_Domain_Controller
Description: A thread in Active Directory is waiting for the completion of a RPC made to the following domain controller: Domain Controller: DSA_GUID._msdcs.DNS_Domain_Name Operation: get change
Thread ID: Thread_ID
Timeout period (minutes): 5
Active Directory has attempted to cancel the call and recover this thread.
User Action: If this condition continues, restart the domain controller.

Event Type: Warning
Event Source: NTDS General
Event Category: Internal Processing
Event ID: 1173
User: NT AUTHORITY\ANONYMOUS LOGON
Description: Internal event: Active Directory has encountered the following exception and associated parameters. Exception: e0010002 Parameter: 0 Additional Data Error value: 1818 Internal ID: 5000ede ----------------

Event Type: Warning
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1085
User: NT AUTHORITY\ANONYMOUS LOGON
Description: Internal event: Active Directory could not synchronize the following directory partition with the domain controller at the following network address.
Directory partition:
Network address:
If this error continues, the Knowledge Consistency Checker (KCC) will reconfigure the replication links and bypass the domain controller.
User Action
Verify that the network address can be resolved with a DNS query.
Additional Data Error value: 1818 The remote procedure call was cancelled.In this situation, you also see error 1818 in the output of the repadmin /showrepl command and in the output of the repadmin /showreps command.

Problem:

This issue may occur when destination domain controllers that are performing remote procedure call (RPC)-based replication do not receive replication changes from a source domain controller within the time that the RPC Replication Timeout (mins) registry setting specifies. You might experience this issue most frequently in one of the following situations:

•	You promote a new domain controller into the forest by using the Active Directory Installation Wizard (Dcpromo.exe).
•	Existing domain controllers replicate from source domain controllers that are connected over slow network links.

The default value for the RPC Replication Timeout (mins) registry setting on Windows 2000-based computers is 45 minutes. The default value for the RPC Replication Timeout (mins) registry setting on Windows Server 2003-based computers is 5 minutes. When you upgrade the operating system from Windows 2000 to Windows Server 2003, the value for the RPC Replication Timeout (mins) registry setting is changed from 45 minutes to 5 minutes. If a destination domain controller that is performing RPC-based replication does not receive the requested replication package within the time that the RPC Replication Timeout (mins) registry setting specifies, the destination domain controller ends the RPC connection with the non-responsive source domain controller and logs a Warning event.

Solution:

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs.

To resolve this issue, increase the bandwidth of your network connection so that the Active Directory changes replicate in the five minute timeout period. If you cannot increase the bandwidth of your network connection, edit the registry on your Windows Server 2003-based computer to increase the value of the RPC timeout for Active Directory replication. To increase the RPC timeout value, follow these steps:

1.	Start Registry Editor.
2.	Locate the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters
3.	Right-click Parameters, point to New, and then click DWORD Value.
4.	Type RPC Replication Timeout (mins), and then press ENTER to name the new value.
5.	Right-click RPC Replication Timeout (mins), and then click Modify.
6.	In the Value data box, type the number of minutes that you want to use for the RPC timeout for Active Directory replication, and then click OK. On a Windows Server 2003-based computer that is part of a Windows 2000 environment or that was upgraded from Windows 2000 Server, you may want to set this value to 45 minutes.

Note You must restart the computer to activate any changes that are made to RPC Replication Timeout (mins).

By,
Lokesh G _L-
"Nobody is Perfect,
I AM A LEARNER"

Importing a single .dbx file into outlook express

Hi,

It is not that easy to import a single .dbx file into Outlook Express. Even we have solution to do that. I hope the following procedure will solve your problem.

Procedure:

1. Right-click the Inbox, and then click Properties. Note the folder in which the Inbox.dbx file is stored.
2. Quit Outlook Express.
3. Use Microsoft Windows Explorer to copy the .dbx file that you want to import to the folder that you noted in step 1. Make sure that you give the file a unique name that does not conflict with any other .dbx file in that folder.
4. NOTE: This name becomes the name of the folder in Outlook Express.
5. In the folder that you noted in step 1, rename the Folders.dbx file to Folders.old (or) Old_Folders.old.
6. Start Outlook Express.
In the Folders pane, you see the .dbx file that you copied. You can drag items to their appropriate locations, or rename the folder.

Note: In this case your existing rules will not work.

By,
Lokesh G _L-
"Nobody is Perfect,
I AM A LEARNER"