Then the family of Mir Shamshud din Iraqi, whose mausoleum is only few feet away from the Imambara Zadibal, lived in the place. The fifth generation of his family built their private mosque and lived nearby well into the early twenty-first century. They set aside productive land to generate money for the upkeep of the mosque. They kept the rights of ownership to themselves but allowed their neighbors to pray there.
It became the main center of learning for the the followers of Ahlul bait. The elders of Markdar families would teach about religion. They also built a Hamam to use as a guest house for travelers coming from Baltistan and other distant areas. During time of Maharaja Ghulab Singh who wanted to keep all the centers under the control of his rule through his representatives (Jalalis) so that no one could revolt against him. Then a dispute broke out between Jalalis and Markdars. It went on for 150 years.
At the time of prime minister of Kashmir Bakshi Ghulam Mohammad, the Markdars donated the Imambara to the Shia public and later on its guardianship was taken by Shia Association. The Shia Association procured the land around the Imambara from the Markdars through several different deals, including language exchanges and cash payments. Recently, the Imambara was repaired by the late Molvi Iftikhar Hussein Ansari.
Inspired by the Persian style of architecture, Imambara Zadibal is a two-storey building. It is made out of oriental bricks. Its Maharaji bricks cover an area of over 75 square meters. This shrine has various sideways floor raisings called Gulam Gardish. There is a central ground level floor called Pokhr. It also has a large gallery with four gates.
Currently, the structure is under the supervision of All Jammu and Kashmir Shia Association, who maintain it. The structure that we see today is still undergoing construction work.
Shia Muslims are a minority in Kashmir. During the first 10 days of Muharram, Imambada Zadibal becomes a centre of mourning and religious gathering in Zadibal. Shia followers join in the mourning, usually ending in the festival of Ashura, when a large procession parades through the streets of Zadibal ending at Imambada Zadibal. Mourning continues from first day of Muharram to eighth of the Islamic month Rabi al Awwal, after which Eid al Zahra, also known as Eid e Shuja, is celebrated. This marks the end of the two-month mourning period.
Immabara Zadibal has been destroyed and rebuilt many times. From the period of Sultan Nazuk Shah by Mirza Douglat in 1548 AD to the reign of Maharaja Ranbir Singh in 1872 AD, this shine was burnt down around eleven times.
At the time Imambara Zadibal was constructed, it was a majestic building and people in the Kashmir Valley were proud of it. However, Mirza Hyder Kashgari Douglat set this shrine on fire in 1548 AD. Daulat Chak began rebuilding it in 1551.
Zafar Kupawari set Imambara Zadibal on fire for the second time in 1553. It was burned down again in 1653 by enemies of Ahlul Bayt during the reign of Mughal Emperor Shah Jahan.
In 1682 AD, when Emperoro Aurangzeb Alamgir ruled, Imambara Zadibal was set on fire again. In 1719 AD, it was burned down for the fifth time during the Mukhtawi Khan clash. It caught fire for the sixth time in 1748 AD by enemies of Ahlul Bayt. They did so again in 1763. Imambara Zadibal caught fire again in June 1801, during Afghan rule in Kashmir, just before Ashura.
In July 1830, the shrine was the site of a massacre when Jammu and Kashmir were under Sikh rule. This same day, many Shias were cruelly murdered. This happened at Ali Park in Zadibal or Margibal.
Imambara Zadibal was rebuilt with financial help sent by a minister of Awadh's Sultan Nasr-ud-din. This grant was sent to Haji Baqir Khan Irani, who passed on the duty of rebuilding this structure to Hatim Mir.
In September 1872, the building was again set ablaze under the rule of Maharaja Ranbir Singh. He was a Dogra Ruler of J&K. This time, the king gave considerable financial aid of about Rs. 3 lakhs to renovate the Imambara and restore it to its current prosperous condition. Every time the shrine went through fire, followers of Prophet Mohammad and Ahlul Bayt were only more convinced to make it whole again.
Reaching this shrine is easy because it is close to Srinagar Highway. The Imambara is in the middle of Zadibal, and it is near the Khushal Sar Lake and Hari Parbat Fort that most people call Qilla. The nearest railway station is the Srinagar railway station. It is an hour's ride away by car. Sheikh ul Alam International Airport is only a few kilometers from the Imambara. Taxi services are also available within the city of Srinagar.
Windows on Windows
With computers, Windows on Windows (often shortened to WOW,) is a compatibility layer of x86 versions of the Microsoft Windows NT family of operating systems that allows many legacy 16-bit programs run that were made for Windows 3.x or before to run.
WOW allows many 16-bit Windows programs to run without changes on newer 32-bit versions of Windows. This was made to give software developers time to make their software 32-bit while people moved from Windows 3.1x to Windows 95, so the OS can be upgraded to a newer version while running most, or all of, a customer's 16-bit programs.
Windows 9x operating systems, which were made on top of DOS, had both 16 and 32-bit systems, so if it kept those 16-bit parts, the OS could run 16-bit software without emulation. NT-based versions are very different in how they run, so they need a more sophisticated solution. There are two main techniques to let 16-bit programs run on 32-bit versions of Windows (with some limitations) called thunking and shimming.
WOW "thunks" 16-bit instructions into 32-bit equivalents to permit 16-bit pointers, memory spaces, and address spaces.
16-bit programs usually run in a single virtual DOS machine, sharing memory between them. However, they can be changed to run in a private, separate memory space, where every 16-bit process has a separate process. This can reduce system crashes by not letting programs interfere with others, but it can cause reduced 16-bit inter-process communication and can use more of your computer's memory.
WOW is a part of 32-bit editions of Windows NT. 64-bit versions of Windows (including Windows Server 2008 R2 and later where they only have 64-bit versions) can not run 16-bit software without using different emulation software (for example, DOSBox).
WOWEXEC.EXE on Windows NT allows WoW to work. Windows-on-Windows can, using the WIN.COM file, emulate the Windows 3.x (for NTVDM), Windows 95 and Windows 98 kernels, which can run 16-bit DOS-powered Windows applications on Windows NT.
Problems with applications running on newer operating systems, especially with long filenames, multiple user accounts, and least privilege, may prohibit some applications from working correctly. For example, they might incorrectly think that they can write files to any part of the file system, but NTFS file permissions exist and does not allow this in many system folders. When Microsoft was building Windows 95, they had to ensure old programs still worked with 8.3 filenames to allow old applications to keep working properly. Since Windows 95, there was a feature where both a long and short file name are kept, so older applications could still use the 8.3 filenames.
Programs that try to access hardware directly can't do so. Old programs may also not work if they expect certain system configuration files from DOS and Windows 9x that are not used in Windows NT operating systems, so empty versions of files like AUTOEXEC.BAT and CONFIG.SYS exist even though Windows NT does not use them.
Many shims exist in the application compatibility layer of later versions of Windows to capture and change API calls from old applications made with different assumptions about the operating system in mind.
Duenos inscription