"Sharon F" <sharonfDEL[ at ]ETEmvps.org> wrote in message news:OPEBoI7sHHA.4236[ at ]TK2MSFTNGP05.phx.gbl...
[Quoted Text] > On Tue, 19 Jun 2007 05:13:43 GMT, Melinda Meehan wrote: > >> What is it about the Quick Launch bar that makes it disappear whenever >> the >> WinXP OS locks up and has to be rebooted? >> >> Is there something really really special about the QuickLaunch bar that >> is >> related to booting WinXP that every other Windows interface doesn't have >> (or does have)? >> >> For example, if the software locks up and I have to shut windows down >> with >> the power button, invariable, the Windows Quick Launch bar disappears - >> yet >> all the other interfaces such as the pop-up menus, the start menu, the >> control panel, etc. work just fine. >> >> What is so special (or badly written) about the Windows QuickLaunch bar >> that only this one GUI component disappears whenever the Windows machine >> is >> shut down unnaturally? >> >> What is it about the Quick Launch bar that is so sensitive to boot >> Windows >> operation that all the other GUIs don't have? > > Where do you keep your Quick Launch (QL)? If not on the taskbar, it is > viewed as window. Forcing a Windows shutdown gives QL a "closed window" > state. It will not reappear until you turn it back on and reposition it on > the desktop. > > If you keep QL on the taskbar, beats me why it doesn't reappear. > > Wild guesses: It is a per user item. Perhaps it's lack of appearance is a > sign that there's some troubles with your user account settings. > > QL is also a part of "active desktop." Active Desktop is always on with XP > (unless turned off in policy) and a part of Internet Explorer's shell > integration. If the system is locking, Explorer (and IE shell components) > are involved so the disappearance could just be an offshoot of the > underlying problems that are causing the repeated lockups. > > -- > Sharon F > MS-MVP ~ Windows Shell/User
Actually the Quick Launch can be a bar on any edge of the screen. Unfortunately, I don't know the answer to the problem, which I have never experienced.
-- Frank Saunders, MS-MVP OE/WM Do not send mail.
|