Month: August 2004

jdk 5.0 performance tools

Tool Name Brief Description

jconsole		 Experimental: J2SE Monitoring and Management Console –
JMX-compliant graphical tool for monitoring a Java virtual machine.
It can monitor both local and remote JVMs.

jps		 Experimental: JVM Process Status Tool –
Lists instrumented HotSpot Java virtual machines on a target system.

jstat		 Experimental: JVM Statistics Monitoring Tool –
Attaches to an instrumented HotSpot Java virtual machine and collects and logs
performance statistics as specified by the command line options.

jstatd		 Experimental: JVM jstat Daemon –
Launches an
RMI server application that monitors for the creation and termination of
instrumented HotSpot Java virtual machines and
provides a interface to allow remote monitoring tools to attach to
Java virtual machines running on the local system.

broken .exe association

things were running too smoothly, so sharpreader decided to take over the .exe extension. it took me a while to fix it (what with #reader trying to open all programs..), but eventually, the following registry entries for xp helped:
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\.exe]
@="exefile"
"Content Type"="application/x-msdownload"
[HKEY_CLASSES_ROOT\.exe\PersistentHandler]
@="{098f2470-bae0-11cd-b579-08002b30bfeb}"
[HKEY_CLASSES_ROOT\exefile]
@="Application"
"EditFlags"=hex:38,07,00,00
"TileInfo"="prop:FileDescription;Company;FileVersion"
"InfoTip"="prop:FileDescription;Company;FileVersion;Create;Size"
[HKEY_CLASSES_ROOT\exefile\DefaultIcon]
@="%1"
[HKEY_CLASSES_ROOT\exefile\shell]
[HKEY_CLASSES_ROOT\exefile\shell\open]
"EditFlags"=hex:00,00,00,00
[HKEY_CLASSES_ROOT\exefile\shell\open\command]
@="\"%1\" %*"
[HKEY_CLASSES_ROOT\exefile\shell\runas]
[HKEY_CLASSES_ROOT\exefile\shell\runas\command]
@="\"%1\" %*"
[HKEY_CLASSES_ROOT\exefile\shellex]
[HKEY_CLASSES_ROOT\exefile\shellex\DropHandler]
@="{86C86720-42A0-1069-A2E8-08002B30309D}"
[HKEY_CLASSES_ROOT\exefile\shellex\PropertySheetHandlers]
[HKEY_CLASSES_ROOT\exefile\shellex\PropertySheetHandlers\PEAnalyser]
@="{09A63660-16F9-11d0-B1DF-004F56001CA7}"
[HKEY_CLASSES_ROOT\exefile\shellex\PropertySheetHandlers\PifProps]
@="{86F19A00-42A0-1069-A2E9-08002B30309D}"
[HKEY_CLASSES_ROOT\exefile\shellex\PropertySheetHandlers\ShimLayer Property Page]
@="{513D916F-2A8E-4F51-AEAB-0CBC76FB1AF8}"

Origin of stupid nicknames

It’s _really_ amusing to look at AOL today and say “I know why users are limited to 10-character names.“, and see many other elements of the original PlayNet design unchanged (even though the reason for them is LONG gone). For example, the 10-character name limit was largely based on how many screen names we could display in the room header in chat within 4(?) 40-character lines on a C64 screen. Ditto the screen-name defaults (I remember us sitting around BS’ing about how we’d handle that, and conflicts- so now you have JoeS12345.)