Aug 26, 2005 - General, Scripting, Windows XP    1 Comment

How do I disable the Windows XP balloon tips?

To disable the Windows XP Notification Area balloon tips:

1. Use the registry editor to navigate to HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionExplorerAdvanced.

2. on the Edit menu, press New and DWORD value.

3. Type a Value Name of EnableBalloonTips.

4. Double-click EnableBalloonTips and type 0.

Alternately, open a CMD.EXE window and type:

REG ADD “HKCUSoftwareMicrosoftWindowsCurrentVersionExplorerAdvanced” /V EnableBalloonTips /T REG_DWORD /F /D 0

How can I determine which groups I’m a member of for my current logon session?

You can use the whoami command with the /groups switch to display all the groups in the currently logged on user token as the following command and output show:

whoami /groups

C:Documents and Settingsali>whoami /groups

[Group 1] = “UKDomain Users”
[Group 2] = “Everyone”
[Group 3] = “MERCURYDebugger Users”
[Group 4] = “BUILTINAdministrators”
[Group 5] = “BUILTINUsers”
[Group 6] = “UKDomain Admins”
[Group 7] = “UKEnterprise Admins”
[Group 8] = “UKSchema Admins”
[Group 9] = “LOCAL”
[Group 10] = “NT AUTHORITYINTERACTIVE”
[Group 11] = “NT AUTHORITYAuthenticated Users”

Why do 10 million people play World Of Warcraft ?

An excellent article on lesessais.com about the issues dealt with people trying to quit this game:

Here. Bear with me. Let me describe an emotional state, and you come up with the cause. First, emptiness. Emptiness like hunger, ravenous hunger; emptiness like the blackness that descends behind closed eyelids at the crepuscule before sleep; emptiness as need; emptiness as blind desire; emptiness visualized as a gaping hole where the heart once held court. Then, regret. Regret for loss, regret that the emptiness exists, regret that the memory of what once filled the hole—the heart, now, the heart, remember—lies dead and dies more each and every passing day; regret that the knowledge of what other people do to fill up their life has been lost along countless missteps and misspent hours trying to find the path on which you once, as a child, so deftly picked your way; regret that something is gone and has left an emptiness as deep as the blackest reaches of outer space. Anger, next. Anger that emptiness is remembered with regret; anger at the witless world that allowed such a gain that could become a loss that could be defined as emptiness with vast regret; anger that you, who once were so strong, so supple, so springboard-ready to bounce back to a mean emotional state, a psychical purpose, can see yourself suffering and maundering over the black heart, its regretful state, and your pointless rage. Despair, finally, that you will ever be another way.

Love, you say? If you did, and I hope you did, then you got it right, at least in purpose and point of origin, for though it smacks of the lovelorn puppy dog ministrations of a mooney-eyed lover, the emotional state I described was of an addict’s absence of soul, of spirit, of the will to experience. Which is to say, they are not all that different.

Unhealthy obsessions, selfish solipsism…the fables and myths that give us succor and teach us morals warn against anything so monomaniacal: it is hardly necessary to think of Narcissus to extend any story’s teleology to death by personal infirmity, moral laxity, or, quite simply, gazing too long at a mirrored self. Love, the quaint excuse for the angst-ridden teen’s outrageous outcries—the union of two souls! Death by dissolution! Not life, no, but bliss!—is seldom more than a mirror made to trick the viewer into seeing a better self. What of other mirrors? Other tricks? What of those that mask the truth but lightly, and in the dancing points of light you can see the fiction, the misdirection, life not lived but carefully avoided, painted in unearthly colors and brighter, happier, than even the most stunted man-child could ever want life to be? We could say that the infirmity is weaker, the morals ignored with more purpose and pain, the waters of immurement approached with more knowledge, dire knowledge, that it is death the soul seeks.

All this is pretty heavy-handed for someone talking of love. Still more for someone speaking of a video game. But there it is. Here. Where love once filled the hours of thousands of men and women who had nothing else to divert their attention away from the painful, plodding progress of life as we know it, we have a game. To be sure, there are other diversions, some do drugs, others take to drink, but for general amusement, for avoiding thinking, there have always been games and activities meant to satisfy other base yearnings—accomplishment, pride, mental facility, physical prowess, social adaptability—but no game quite like this…

Click here for full article and the source

Also ….
PICTURE: What will a World Of Warcraft player look like in the year 2030?

Jul 28, 2005 - General    4 Comments

Propagate Public Folder Permissions On Exchange 2003

You can use Exchange System Manager to propagate permissions for public folders using the following steps:

  • Exchange System Manager
  • Goto the public folder you want to adjust permissions on
  • Properties
  • Permissions
  • Hold Ctrl while clicking Client Permissions

You should now be able to set permissions to public folders and propagate to child objects

Un-hide Components from Add/Remove List

Most Windows components can be uninstalled by going to Add/Remove Windows Components in the Control Panel. But what about ones that you don’t find? You know that they’re on there somewhere, so how do you get rid of them? Well, it’s actually not too hard to bring these out of hiding.

Hidden in the C:WINNTINF directory is a file called sysoc.inf (for XP replace winnt with windows).

Lets say you want to hide the IIS components from Add/remove programs.
Simply add the word “hide” here:

iis=iis.dll,OcEntry,iis.inf,hide,7

If you want to unhide, just remove the “hide” from any component you wish.

Jul 13, 2005 - General    1 Comment

SysPrep and RipRep behavior changes on Windows Server 2003 Service Pack 1?

When you deploy a SysPrep or RipRep image on a computer that is running Windows Server 2003 with SP1, you may notice that customizations that you made to the default user account are missing AND/OR customization that you made to the Administrator account appear in new user accounts AND/OR modifications that you made to the default user by editing the register (Load Hive) at %SystemDrive%:Documents and SettingsDefault UserNtuser.dat are missing.
These problems occur because Mini-Setup has been modified in SP1 so that the default behavior includes copying any customizations from the local Administrator account to the default user account.

NOTE: The default user account is used to create new user profiles when they first log on.

To workaround this behavior, open the Sysprep.inf file and add the following entry in the [UNATTENDED] section:

UpdateServerProfileDirectory=0

Jul 13, 2005 - General    No Comments

When my Dfs clients running Windows XP open an executable from a domain-based Dfs path, the user is prompted to confirm whether to run the executable file. How can I stop this behavior?

The client receives this warning because the Dfs path contains a Fully Qualified Domain Name (FQDN) as its Active Directory (AD)-stored root. Actually, this message is displayed any time a path to a resource contains a FQDN, not just Dfs paths. To avoid the message, add the domain to the client’s list of trusted local intranet zones in Microsoft Internet Explorer (IE). To do so, perform these steps:

Open IE and from the Tools menu, select Internet Options.
Select the Security tab.
Select “Local intranet” and click Sites.
Enter the name of the internal domain (e.g., for all hosts in the savilltech.com domain, I would add *.savilltech.com). Click Add.
Click Close, then click OK to the main options screen.

You should no longer receive the confirmation prompt when opening an executable

Jul 13, 2005 - General    No Comments

When my Dfs clients running Windows XP open an executable from a domain-based Dfs path, the user is prompted to confirm whether to run the executable file. How can I stop this behavior?

The client receives this warning because the Dfs path contains a Fully Qualified Domain Name (FQDN) as its Active Directory (AD)-stored root. Actually, this message is displayed any time a path to a resource contains a FQDN, not just Dfs paths. To avoid the message, add the domain to the client’s list of trusted local intranet zones in Microsoft Internet Explorer (IE). To do so, perform these steps:

Open IE and from the Tools menu, select Internet Options.
Select the Security tab.
Select “Local intranet” and click Sites.
Enter the name of the internal domain (e.g., for all hosts in the savilltech.com domain, I would add *.savilltech.com). Click Add.
Click Close, then click OK to the main options screen.

You should no longer receive the confirmation prompt when opening an executable

Related Posts Plugin for WordPress, Blogger...
Pages:«1...567891011...31»