Forgot Administrator Password on XP

1. Restart your computer
   
2. When booting, press F8 and select "Safe Mode"
   
3. After getting to the user menu. Click on a user and this time it will not ask you for a password 
   
4. Go to Start>Run and type "CMD" (without the quotes).
   
5. At command prompt type in "cd C:\Windows\System32" (without the quotes), I am assuming C is your System/Windows Drive
   
6. For safety purposes first make a backup of your Logon.Scr file..
   
7. You can do this by typing in "Copy to Logon.scr to Logon.bak" (without the quotes)
   
8. Then type "copy CMD.EXE Logon.scr"(without the quotes)
   
9. Then type this command, I will assume that you want to set Administrator's password to "MyNewPass" (without the quotes)
   
10. Now, type this in (I am assuming that you are still in the directory C:\Windows\System32), "net user administrator MyNewPass" (without the quotes)
    
11. You will get a message saying that it was successful, this means Administrator's new password is "MyNewPass" (without the quotes)
    
12. Restart the PC and you will login as Administrator (or whatever you chose to reset) with your chosen password and Enjoy!
    

Read More......

Sharing Internet on XP

We can sharing internet information through (by) internet XP.
From My computer click right, in tab Computer Name a change : Computer name typing the computer name (ext : PC1) , Member of take Workgroup (ext : MIS).

From the computer to sharing

• From My Network place
• Choose Set up a home or small office network (next)

• Select a connection method, take number 1 (this computer connects directly to the internet. the other computers on my network connect to the Internet throught this computer) (Next)
  

• Select your internet conection
  

• Just Next and next till finish.
  

From Computer client

• From My Network place
• Set up home or small office Network (Next)
• Select a connection method, take number 2 ( This computer connects to the Internet a residential gateway or throught another computer on my network)
• Computer name : Take your computer name. (next)
  

• Name your Network, Workgroup name :..(enter your group name)
• Just Next and next till finish.

Read More......

Mail Merge Word 2007

Mail Merge Wizard

To start the Mail Merge in the new Word 2007, click on the Mailings tab. The Ribbon, the groups of commands you see on each tab, replaces the toolbars and menus. Commands are organized in groups related to activities such as you see below in the Create, Start Mail Merge, and Write & Insert Fields groups on the Mailings tab.

When you click on the arrow beside Start Mail Merge, a drop-down list appears as shown below. Select the last option, “Step by Step Mail Merge Wizard.”

This brings up the task pane as shown below. Select Letters (or whatever type you want) as the type of document and then click on the “Next: Starting document” link at the bottom of the task pane to go to the next step to select your starting document.

Selecting a Template

You have options to use the current document you have open, to select a template, or to browse to an existing document not open. For this practice, select “Start from a template.” This brings up a link you click on to “Select template.”

This opens the “Select Template” dialog box shown. Select the “Letters” tab and choose “Oriel Merge Letter.” Click on OK.

This takes you to Step 3 in the Mail Merge process in which you “Select recipients.”

Selecting Recipients

Select “Use an existing list” and click on the “Browse” link. Locate and open the file containing your data source. For this exercise, use the MailMergeList.xls.

This opens the following dialog box in which you select the table (the named range defined within Excel) containing the mail merge recipients info you want to pull into the merge fields in your document. Select “seminar” or “training” or whatever you named the range in your spreadsheet containing the names and addresses you want to use for the mail merge ("attendees" is the defined range selected as shown below).

Make sure to check the box indicating that the “First row of data contains column headers” so that the field labels (Last Name, First Name, Address1, etc.) on your spreadsheet won’t be mistaken for data.

This opens the Mail Merge Recipients dialog box shown below. Here you can select which recipients to include or deselect by unchecking the check box by the name.

You can sort and filter the list using the drop-down list located on each field name indicated by the triangular black arrow. Note there are also links to Sort and Filter or Find Duplicates and recipients in the “Refine recipient list” section.

Click on the link “Next: Write your letter” to go on to the next step to edit the mail merge template letter content.

Inserting Merge Fields

Notice that the Address Block and Greeting Line fields are already inserted into this template letter. If you weren’t using a preformatted mail merge letter, you would just simply click on the links on the right to insert the Address block, Greeting line, or more items (more merge fields). You also have these same options on the Mailings toolbar at the top—you don’t have to use the wizard each time you do a mail merge. Pick the date and replace the letter content with your own and then go on to the next step to preview your letters by clicking on the link at the bottom of the task panel.

Matching Fields

When you click on the Address block link, the following dialog box appears in which you can choose the format of the address. Also, you can click on the Match Fields button to match the missing address field (the Match Fields button is also on the Mailings tab in the "Write and Insert Fields" grouping).

Clicking on the Match Fields button brings up the following dialog box. Use the Address 1 drop-down list to select the Street field name from the Excel spreadsheet.

Previewing Results

You have buttons on both the Preview Results group on the Mailings ribbon as well as the task pane to look at different recipient info before going on to the next step to complete the merge.

Completing the Merge

When you click on the link, “Next: Complete the merge,” the following appears:

Click on the link “Edit individual letters” which you can see from the screen tip is the link to “Merge to new document.” This is also a button on the "Finish & Merge" dropdown list on the Mailings Ribbon.

The Print link on the Task Pane or Print Documents on the Ribbon dropdown list allows you to merge directly to the printer. When you click on the link to edit the letters, the following dialog box appears:

You can choose whether to merge all or selected records. Click OK and then a new merged document entitled Letters1 is created. It contains the individual letters for each recipient. If you look at the status bar, you will see that it indicates multiple letters.

Saving

Save your work by clicking on the new Office button which replaces the file menu.

Select "Save As" to view the new options for saving in different formats.

The new "default" file format is .docx, a new file format for Word documents. It is one of the new Office XML formats. You also have the option to save in the Word 97-2003 format so that your file is compatible with those versions and can be opened in them. However, with earlier versions of Word, you can open a file created in the 2007 version by going to theDownload Center at the Microsoft site and downloading the Microsoft Office Compatibility Pack for 2007 Office Word, Excel and PowerPoint File Formats.

Read More......

Change Path Drive on XP

If you use eksternal drive (ex. Flash Disk), we still recornized and change path drive which you want....

Follow these steps:

1. Find "My Computer" Icon, right click and choose "manage"

2. Double click "Disk Management"


3. Select drive/disk you want and right click, choose "Change Drive Letter and Paths..."


4. Selet tab "Change" and assign your new following drive letter


5. Clik "OK" and close "Computer Management" window

Read More......

Computer POST / beep codes

POST ABCs
The computer POST (Power On Self Test) tests the computer, insuring that it meets the necessary system requirements and that all hardware is working properly before starting the remainder of the boot process. If the computer passes the POST the computer will have a single beep (with some computer BIOS manufacturers it may beep twice) as the computer starts and the computer will continue to start normally. However, if the computer fails the POST, the computer will either not beep at all or will generate a beep code, which tells the user the source of the problem.

The steps of a POST
Each time the computer boots up the computer must past the POST. Below is the common steps a POST performs each time your computer starts.

1. Test the power supply to ensure that it is turned on and that it releases its reset signal.
   
2. CPU must exit the reset status mode and thereafter be able to execute instructions.
   
3. BIOS checksum must be valid, meaning that it must be readable.
   
4. CMOS checksum must be valid, meaning that it must be readable.
   
5. CPU must be able to read all forms of memory such as the memory controller, memory bus, and memory module.
   
6. The first 64KB of memory must be operational and have the capability to be read and written to and from, and capable of containing the POST code.
   
7. I/O bus / controller must be accessible.
   
8. I/O bus must be able to write / read from the video subsystem and be able to read all video RAM.
   

If the computer does not pass any of the above tests, your computer will receive an irregular POST. An irregular POST is a beep code that is different from the standard one or two beeps. This could be either no beeps at all or a combination of different beeps indicating what is causing the computer not to past the POST.

If you're receiving an irregular POST document CH000607 contains all the steps a user can do to resolve the issue or help determine what hardware has failed in the computer so it can be replaced. If you're getting a beep code the remainder of this page contains a listing of each of the major manufacturers beep codes and what they each mean. Index

AMI BIOS beep codes
Below are the AMI BIOS Beep codes that can occur. However, because of the wide variety of different computer manufacturers with this BIOS, the beep codes may vary.

• 1 short - DRAM refresh failure - CH000996
  
• 2 short-  Parity circuit failure - CH000607
  
• 3 short - Base 64K RAM failure - CH000996
  
• 4 short - System timer failure - CH000607
  
• 5 short - Process failure - CH000607
  
• 6 short - Keyboard controller Gate A20 error - CH000383
  
• 7 short - Virtual mode exception error - CH000607
  
• 8 short - Display memory Read/Write test failure - CH000607
  
• 9 short - ROM BIOS checksum failure - CH000607
  
• 10 short - CMOS shutdown Read/Write error - CH000239
  
• 11 short - Cache Memory error - CH000607
  
• 1 long, 3 short - Conventional/Extended memory failure - CH000996
  
• 1 long, 8 short - Display/Retrace test failed - CH000607
  

AWARD BIOS beep codes
Below are Award BIOS Beep codes that can occur. However, because of the wide variety of different computer manufacturers with this BIOS, the beep codes may vary.

• 1 long, 2 short - Indicates a video error has occurred and the BIOS cannot initialize the video screen to display any additional information - CH000607
  
• Any other beep(s) - RAM problem - CH000996
  

If any other correctable hardware issues, the BIOS will display a message.

IBM BIOS beep codes
Below are IBM BIOS Beep codes that can occur. However, because of the wide variety of models shipping with this BIOS, the beep codes may vary.

• No Beeps  - No Power, Loose Card, or Short.  - CH000312
  
• 1 Short Beep - Normal POST, computer is ok.  - No problem
  
• 2 Short Beep - POST error, review screen for error code.  - See screen
  
• Continuous Beep - No Power, Loose Card, or Short.  - CH000607
  
• Repeating Short Beep - No Power, Loose Card, or Short. - CH000607
  
• One Long and one Short Beep - Motherboard issue. - CH000607
  
• One Long and Two Short Beeps - Video (Mono/CGA Display Circuitry) issue. - CH000607
  
• One Long and Three Short Beeps. - Video (EGA) Display Circuitry. - CH000607
  
• Three Long Beeps - Keyboard / Keyboard card error. - CH000304
  
• One Beep, Blank or Incorrect Display - Video Display Circuitry. - CH000607
  

Macintosh startup tones

• Error Tone. (two sets of different tones) - Problem with logic board or SCSI bus.
  
• Startup tone, drive spins, no video - Problem with video controller.
  
• Powers on, no tone. - Logic board problem.
  
• High Tone, four higher tones. - Problem with SIMM.
  

Phoenix BIOS beep codes
Below are the beep codes for PHOENIX BIOS Q3.07 OR 4.X

• 1-1-1-3 = Verify Real Mode.
  
• 1-1-2-1 = Get CPU type.
  
• 1-1-2-3 = Initialize system hardware.
  
• 1-1-3-1 = Initialize chipset registers with initial POST values.
  
• 1-1-3-2 = Set in POST flag.
  
• 1-1-3-3 = Initialize CPU registers.
  
• 1-1-4-1 = Initialize cache to initial POST values.
  
• 1-1-4-3 = Initialize I/O.
  
• 1-2-1-1 = Initialize Power Management.
  
• 1-2-1-2 = Load alternate registers with initial POST values.
  
• 1-2-1-3 = Jump to UserPatch0.
  
• 1-2-2-1 = Initialize keyboard controller.
  
• 1-2-2-3 = BIOS ROM checksum.
  
• 1-2-3-1 = 8254 timer initialization.
  
• 1-2-3-3 = 8237 DMA controller initialization.
  
• 1-2-4-1 = Reset Programmable Interrupt Controller.
  
• 1-3-1-1 = Test DRAM refresh.
  
• 1-3-1-3 = Test 8742 Keyboard Controller.
  
• 1-3-2-1 = Set ES segment to register to 4 GB.
  
• 1-3-3-1 = 28 Autosize DRAM.
  
• 1-3-3-3 = Clear 512K base RAM.
  
• 1-3-4-1 = Test 512 base address lines.
  
• 1-3-4-3 = Test 512K base memory.
  
• 1-4-1-3 = Test CPU bus-clock frequency.
  
• 1-4-2-4 = Reinitialize the chipset.
  
• 1-4-3-1 = Shadow system BIOS ROM.
  
• 1-4-3-2 = Reinitialize the cache.
  
• 1-4-3-3 = Autosize cache.
  
• 1-4-4-1 = Configure advanced chipset registers.
  
• 1-4-4-2 = Load alternate registers with CMOS values.
  
• 2-1-1-1 = Set Initial CPU speed.
  
• 2-1-1-3 = Initialize interrupt vectors.
  
• 2-1-2-1 = Initialize BIOS interrupts.
  
• 2-1-2-3 = Check ROM copyright notice.
  
• 2-1-2-4 = Initialize manager for PCI Options ROMs.
  
• 2-1-3-1 = Check video configuration against CMOS.
  
• 2-1-3-2 = Initialize PCI bus and devices.
  
• 2-1-3-3 = Initialize all video adapters in system.
  
• 2-1-4-1 = Shadow video BIOS ROM.
  
• 2-1-4-3 = Display copyright notice.
  
• 2-2-1-1 = Display CPU type and speed.
  
• 2-2-1-3 = Test keyboard.
  
• 2-2-2-1 = Set key click if enabled.
  
• 2-2-2-3 = 56 Enable keyboard.
  
• 2-2-3-1 = Test for unexpected interrupts.
  
• 2-2-3-3 = Display prompt "Press F2 to enter SETUP".
  
• 2-2-4-1 = Test RAM between 512 and 640k.
  
• 2-3-1-1 = Test expanded memory.
  
• 2-3-1-3 = Test extended memory address lines.
  
• 2-3-2-1 = Jump to UserPatch1.
  
• 2-3-2-3 = Configure advanced cache registers.
  
• 2-3-3-1 = Enable external and CPU caches.
  
• 2-3-3-3 = Display external cache size.
  
• 2-3-4-1 = Display shadow message.
  
• 2-3-4-3 = Display non-disposable segments.
  
• 2-4-1-1 = Display error messages.
  
• 2-4-1-3 = Check for configuration errors.
  
• 2-4-2-1 = Test real-time clock.
  
• 2-4-2-3 = Check for keyboard errors
  
• 2-4-4-1 = Set up hardware interrupts vectors.
  
• 2-4-4-3 = Test coprocessor if present.
  
• 3-1-1-1 = Disable onboard I/O ports.
  
• 3-1-1-3 = Detect and install external RS232 ports.
  
• 3-1-2-1 = Detect and install external parallel ports.
  
• 3-1-2-3 = Re-initialize onboard I/O ports.
  
• 3-1-3-1 = Initialize BIOS Data Area.
  
• 3-1-3-3 = Initialize Extended BIOS Data Area.
  
• 3-1-4-1 = Initialize floppy controller.
  
• 3-2-1-1 = Initialize hard-disk controller.
  
• 3-2-1-2 = Initialize local-bus hard-disk controller.
  
• 3-2-1-3 = Jump to UserPatch2.
  
• 3-2-2-1 = Disable A20 address line.
  
• 3-2-2-3 = Clear huge ES segment register.
  
• 3-2-3-1 = Search for option ROMs.
  
• 3-2-3-3 = Shadow option ROMs.
  
• 3-2-4-1 = Set up Power Management.
  
• 3-2-4-3 = Enable hardware interrupts.
  
• 3-3-1-1 = Set time of day.
  
• 3-3-1-3 = Check key lock.
  
• 3-3-3-1 = Erase F2 prompt.
  
• 3-3-3-3 = Scan for F2 key stroke.
  
• 3-3-4-1 = Enter SETUP.
  
• 3-3-4-3 = Clear in-POST flag.
  
• 3-4-1-1 = Check for errors
  
• 3-4-1-3 = POST done--prepare to boot operating system.
  
• 3-4-2-1 = One beep.
  
• 3-4-2-3 = Check password (optional).
  
• 3-4-3-1 = Clear global descriptor table.
  
• 3-4-4-1 = Clear parity checkers.
  
• 3-4-4-3 = Clear screen (optional).
  
• 3-4-4-4 = Check virus and backup reminders.
  
• 4-1-1-1 = Try to boot with INT 19.
  
• 4-2-1-1 = Interrupt handler error.
  
• 4-2-1-3 = Unknown interrupt error.
  
• 4-2-2-1 = Pending interrupt error.
  
• 4-2-2-3 = Initialize option ROM error.
  
• 4-2-3-1 = Shutdown error.
  
• 4-2-3-3 = Extended Block Move.
  
• 4-2-4-1 = Shutdown 10 error.
  
• 4-3-1-3 = Initialize the chipset.
  
• 4-3-1-4 = Initialize refresh counter.
  
• 4-3-2-1 = Check for Forced Flash.
  
• 4-3-2-2 = Check HW status of ROM.
  
• 4-3-2-3 = BIOS ROM is OK.
  
• 4-3-2-4 = Do a complete RAM test.
  
• 4-3-3-1 = Do OEM initialization.
  
• 4-3-3-2 = Initialize interrupt controller.
  
• 4-3-3-3 = Read in bootstrap code.
  
• 4-3-3-4 = Initialize all vectors.
  
• 4-3-4-1 = Boot the Flash program.
  
• 4-3-4-2 = Initialize the boot device.
  
• 4-3-4-3 = Boot code was read OK.

Read More......

Bad Diskette Data Recovery

Here's a fairly standard way of recovering data from diskettes that have bad sectors:

1: Protect the diskette
Windows 9x will write to every diskette it sees, even if you don't do so yourself. Specifically, it writes a tracking ID to the boot record of the diskette, so it can determine whether a different diskette is in the drive. Should the drive be faulty or misaligned, or the diskette be frail, this process could corrupt the first track and render the diskette unreadable. I don't know whether NT
(including Windows 2000 and XP) behave the same way as Win9x in this regard.
So the first thing to do is to open the write-protect tab in order to prevent further damage! As a general rule, I treat the write-protect tab much as I would the safety catch on a gun; it stays "safe" unless I'm planning on writing to it.

2: Get out of Windows
Windows is generally a bad place to attempt anything that involves potential hardware error conditions. You'd think after two decades of writing Disk Operating Systems, Microsoft would be able to handle disk errors gracefully, but Win9x tends to lose its marbles in cases where DOS would have thrown up an ARF message and carried on truckin'.
What comes next requires direct (raw) disk access anyway, which modern Windows precludes - so get thee to DOS mode!

3: Prepare a target diskette
Format an error-free blank diskette, then fill this diskette with a single large file. The easiest way to do that is to start an archive to the diskette that would span multiple diskettes, then abort this after the diskette is filled.
If you anticipate holes in the data cluster area of the original diskette, then you can do yourself a favor by filling the data cluster area of the target diskette with a repeated unique string, e.g. "!!_BAD_SECTOR_!!" - i.e. something that a Find won't find anywhere under normal circumstances, and that will align nicely in 512 bytes (e.g. this 16-byte example).

4: Peel off the contents of original diskette
I use "Norton" DiskEdit for this, but if you have a raw diskette copying utility that will do the job without having hissy fits about what it can't read, then use that instead. In fact, if that utility is smart enough to copy directly to another diskette while leaving any unreadable sectors untouched on the target, then you can do the next step at the same time.
I usually PgDn through the raw pysical sectors on the sick diskette until I get a disk error. I ballpoint that CHS address, then select all physical sectors up to but excluding that sector. Then I write these sectors to a file (e.g. A1.SEC) somewhere on the hard drive (e.g. C:\BAD-DISK). Then I repeat this process, noting down all bad sector addresses and saving what is good in successively-numbered files (e.g. A2.SEC, A3.SEC, A4.SEC etc.)

5: Splat the contents onto the target diskette
Taking care to do this in the right order, and to ensure each slab of saved sectors starts at the correct CHS (raw physical disk) address, I then load each of the saved files into DiskEdit and write these to the target diskette as raw sectors.
Don't confuse logical sector numbering with physical sector addressing, which is often shown in CHS form.

6: Copy off and test the files
You may still have file system issues to contend with; there may be wads of garbage in your files, and if the files on the original diskette were fragmented or oddly ordered and were chained via lost sectors in the FAT, then you may have incorrect data clusters in the files. But at least you aren't fighting two battles at the same time; logical errors plus a collapsing disk surface.

7: Resolve FAT errors
Where there were missing sectors in the FAT, but the files were unfragmented and saved in a first-to-last order with no deletions, you should find the data clusters chained into the files will be correct - because you effectively created a "flat-FAT" at step (3), and where step (5) left this FAT showing through, the chaining would have been appropriate.
However, if there are chaining errors, it is still possible to fix these, even if the corresponding sectors in both copies of the FAT are both corrupted. Any non-zero or non-"special" cluster address should occur only once in a FAT, so you can narrow down the search for loose data clusters by looking for addresses that appear both in the "flat-FAT" show-through and the real FAT as successfully lifted off the original diskette. Resolve duplicates (which are crosslinks) in favor of the original FAT, i.e. chain out what is in the "flat-FAT" so that no duplicates remain - using addresses that don't appear anywhere in the original FAT.
Some cluster addresses won't appear in the FAT because they are the first clusters of a file or subdirectory, and it's easy to look those up by looking at the root and other directories and ballpointing all the start cluster addresses there. Any addresses not accounted for in the original FAT or directory entries may be assumed to constitute the cluster chains held within the bad sectors lost from the original FAT.

8: Spot and fix missing data sectors
You can load the salvaged files into an ASCII viewer, and look for the unique string you used in step (3). You should find 512-byte wads of these wherever a data sector could not be read off the original diskette, leaving the filled data cluster contents from step (3) in place.
If there are multiple similar copies of the same file on the diskette (e.g. BLAH.DOC and BLAH.BAK), then you can lift the corresponding sector from the heathier file and paste it into the hole in the damaged one. The chances of successfully fixing binary files (such as spreadsheets) via such shenannigans are small, but at least with a word processor document file, you can load it into Edit and strip out binary stuff to leave editable text.

Read More......

Fixing UNMOUNTABLE_BOOT_VOLUME on Windows XP

It failed with UNMOUNTABLE_BOOT_DEVICE STOP: 0x000000ED
(0xaddress,0xC0000006,0x00000000,0x000000)

I searched the net. Found several articles but not really anything that seem 'correct'. Finally, I found an article on Experts-Exchange.com. Well, I could not get to the answers as I do not have an account, but sometime Google's caching feature are very useful...

So this is how I did it based on the answers I found - Start the recovery console. If you do not have it installed - or when that version does not work - like in this case, boot from an installation CD and select R for repair. You can easily mix languages - I used an English CD on
a Danish Windows

Run these command -
chkdsk c: /r /p
fixmbr
exit (to reboot)

That is it. Read More......