Replication History, Boot Sequence and Beep Codes

[Admin]

How to clear a replication history?

a. You will need to open your database in Lotus Notes and then you can clear replication history by following these steps:

1. Open the Lotus Notes Database (This can also be a Notes Mail File Database)

2. Select from the top menu File - Database – Properties


3. The Database Dialogue box will appear (as shown in the below). Please click on the button 'Replication History'

4. A new Window will pop-up, then please click 'Clear All'. This will clear all database replication history.


5. Click Done and then close the Database Properties dialogue box.

6. Proceed to replicate this database with the server as normal (receive mail as normal if this database is a mail database).

What is the Boot Sequence in windows XP?

1. First is the POST, this stands for Power On Self Test, for the computer. This process tests memory as well as a number of other subsystems. You can usually monitor this as it runs each test. After that is complete the system will run POST for any device that has a BIOS (Basic Input-Output System). An AGP has its own BIOS, as do some network cards and various other devices.
2. Once the POST is complete and the BIOS is sure that everything is working properly, the BIOS will then attempt to read the MBR (Master Boot Record). This is the first sector of the first hard drive (called the Master or HD0). When the MBR takes over it means that Windows is now in control.
3. The MBR looks at the BOOT SECTOR (the first sector of the active partition). That is where NTLDR is located, NTLDR is the BOOT LOADER for Windows XP. NTLDR will allow memory addressing, initiate the file system, read the boot.ini and load the boot menu. NTLDR has to be in the root of the active partition as do NTDETECT.COM, BOOT.INI, BOOTSECT.DOS (for multi-OS booting) and NTBOOTDD.SYS (if you have SCSI adapters)
4. Once XP is selected from the Boot Menu, NTLDR will run NTDETECT.COM, BOOT.INI and BOOTSECT.DOS to get the proper OS selected and loaded. The system starts in 16-bit real mode and then moves into 32-bit protected mode.
5. NTLDR will then load NTOSKRNL.EXE and HAL.DLL. Effectively, these two files are windows XP. They must be located in %SystemRoot%System32.
6. NTLDR reads the registry, chooses a hardware profile and authorizes device drivers, in that exact order.
7. At this point NTOSKRNL.EXE takes over. It starts WINLOGON.EXE that in turn starts LSASS.EXE, this is the program that display the Logon screen so that you can logon.

Beep Codes

1 short DRAM refresh failure
2 short Parity circuit failure
3 short Base 64K RAM failure
4 short System timer failure
5 short Process failure
6 short Keyboard controller Gate A20 error
7 short Virtual mode exception error
8 short Display memory Read/Write test failure
9 short ROM BIOS checksum failure
10 short CMOS shutdown Read/Write error
11 short Cache Memory error
1 long, 3 short Conventional/Extended memory failure
1 long, 8 short Display/Retrace test failed
1 long, 2 short Indicates a video error has occurred and the BIOS cannot initialize the video screen to display any additional information
Any other beep(s) RAM problem.

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