Monday, July 13, 2009

“Windows XP OS is booting but not getting the Desktop”

“Windows XP OS is booting but not getting the Desktop”
------------------------------------------------------------------------------------------------
Hardware Details/OS : Desktop/ Windows XP,
Problem : Desktop is not coming. Only mouse cursor is coming, after giving
Username and password, just cursor is coming.








Solution

-----------
1. Boot through Windows XP CD using repair option come to recovery console.
2. This problem is caused due to missing or corrupted explorer.exe and browseui.dll ; we have to copy explorer.exe and browseui.dll to their respective path.
3. After coming to console go to Drive Letter of CD example E:\ and go to i386 directory.
4. From there give command as follows,
E:\expand explorer.ex_ c:\windows
After this new file explorer.exe will be extracted to windows directory
5. Then with same procedure extract browseui.dll
E:\expand browseui.dl_ c:\windows\system32
Now Browseui.dll file is extracted.
6 Reboot the machine from hard disk in single user mode
6. After doing these 2 steps, Windows started fine and desktop is coming.


Value Addition
--------------------

Explorer.exe

Explorer.exe is the Windows Program Manager or Windows Explorer
The Windows Explorer debuted in Windows 95 as a replacement for the older Windows 3.x File Manager. It could be accessed by double-clicking the new My Computer desktop icon, or launched from the new Start Menu (which succeeded the earlier Program Manager). There is also a shortcut key combination – Windows key + E. Successive versions of Windows (and in some cases, Internet Explorer) introduced new features and capabilities, removed other features, and generally progressed from being a simple file system navigation tool into a task-based file management system.
While “Windows Explorer” is a term most commonly used to describe the file management aspect of the operating system, the Explorer process also houses the operating system’s search functionality and File Type associations (based on filename extensions), and is responsible for displaying the desktop icons, the Start Menu, the Taskbar, and the Control Panel. Collectively, these features are known as the Windows Shell.
In the Explorer window, Files and Folders are displayed by a ListView component (SysListView32) making up the majority of the window. When a user chooses to “Explore” the left hand side will display a TreeView, showing the folder structure

BrowseUI.dll

BrowswUI.dll is the one of the major five components of Internet Explorer
Internet Explorer uses a componentized architecture built around the Component Object Model (COM) technology. As said it is made up of five major components, each of which are contained in a separate .dll and expose a set of COM interface that enables them to be hosted by the Internet Explorer main executable, iexplore.exe
WinInet.dll
WinInet.dll is the protocol handler for HTTP and FTP. It handles all network communication over these protocols.
URlMon.dll
URLMon.dll is responsible for MIME-type handling and download of web content.
MSHTML.dll
MSHTML.dll houses the Trident rendering engine which is responsible for displaying the pages on-screen and handling the Document Object Model of the web pages. MSHTML.dll parses the HTML/CSS file and creates the internal DOM tree representation of it. It also exposes a set of APIs for runtime inspection and modification of the DOM tree. The DOM tree is further processed by a layout engine which then renders the internal representation on screen. Internet Explorer does not include any scripting functionality natively. Rather MSHTML.dll exposes another set of APIs that allow any scripting environment to be plugged-in and access the DOM tree. Internet
Explorer 8 includes the bindings for the Active Scripting engine (which is a part of Microsoft Windows) is provided, which allows any language implemented as an Active Scripting module to be used for client-side scripting. By default, only the JScript and VBScript modules are provided; third party implementations like ScreamingMonkey (for ECMAScript 4 support) can also be used. Microsoft also makes available the Microsoft Silverlight runtime that allows CLI languages, including DLR-based dynamic languages like IronPython and IronRuby, to be used for client-side scripting.
ShDocVw.dll
ShDocVw.dll provides the navigation, local caching and history functionalities for the browser.
BrowseUI.dll
BrowseUI.dll is responsible for the browser user interface, including the browser chrome, which houses all the menus and toolbars.

FYI.................Naresh !!!

0 comments:

Post a Comment