MoonPoint Support Logo


Shop Amazon Warehouse Deals - Deep Discounts on Open-box and Used ProductsAmazon Warehouse Deals

Advanced Search
Sun Mon Tue Wed Thu Fri Sat

Sun, Mar 29, 2009 9:29 pm

Live Messenger Scene

Windows Live Messenger (version 2009 and likely other versions) stores "scenes" in a scenes.mct file, usually in C:\Program Files\Windows Live\Messenger. If you want to create your own "scene" for use with Windows Live Messenger, you may want to create the image in a size that matches what is used for the scenes in scenes.mct, which is just a CAB file containing graphics files

[ More Info ]

[/network/chat/live_messenger] permanent link

Sat, Mar 28, 2009 10:25 am

Customizing the Start Menu

In Windows XP, if there are certain programs that you use quite frequently and would like to have immediately accessible when you click on the Windows Start button, you can add them to the Start menu, which is the menu that appears when you click on that button.

Normally, you will see your default email client and web browser at the top of the start menu. There may also be other items already on the menu.

Start Menu - before

If you want to add another item at the top of the start menu in the same section as the shortcuts for your default email client and web browser, all you need to do is click on Start, select All Programs and then locate the the program you wish to add to the menu. Right-click on that program and select Pin to Start menu. In the example below, Windows Live Messenger has been selected to be added to the Start menu.

Start Menu - pin Windows Live Messenger

You will then see the program on the upper-left side of the Start menu. You can now run the program by clicking on the Start button and selecting the program from that location.

Start Menu - after

If you ever want to remove the program from the Start menu, click the Start button, right-click on the program, and choose Unpin from the Start menu.

Start Menu - unpin Windows Live Messenger

  1. Customize your Start menu
    Published: September 7, 2006
    Microsoft Corporation

[/os/windows/xp] permanent link

Fri, Mar 27, 2009 5:07 pm

Qpopper 4.0.16 Upgrade on a Solaris 5.7 System

For anyone who might be encountering problems building Qpopper or other software on a Solaris system and seeing a checking size of unsigned long int... configure: error: cannot compute sizeof (unsigned long int), 77 error message at the configure stage or seeing ld: fatal: Symbol referencing errors at the make stage, try running configure with CFLAGS=-gstabs+, i.e. try ./configure CFLAGS=-gstabs+. Since Solaris uses shadow passwords, you should also use the --enable-specialauth option as well, i.e. use the following configure command:

./configure --enable-specialauth CFLAGS=-gstabs+

Otherwise, Qpopper won't likely accept an account's password when you try to download email. Using those options at the configure step allowed me to resolve issues I was having installing Qpopper 4.0.16 on a Solaris 5.7 system.

[ More Info ]

[/network/email/qpopper] permanent link

Thu, Mar 26, 2009 6:14 pm

SunOS 5.7: jsh, rsh, ksh, rksh, sh Patch

I installed the SunOS 5.7: jsh, rsh, ksh, rksh, sh Patch on a Solaris 2.7 system.

I first checked to see whether the patch was already installed with showrev -p. It was not installed.

# showrev -p | grep 108162

If a patch is installed, you would see something like the following:

# showrev -p | grep 106938-09
Patch: 106938-09 Obsoletes: 107018-04, 107332-04, 108412-01 Requires:  Incompati
bles:  Packages: SUNWcsu, SUNWcslx, SUNWcsl, SUNWarc, SUNWarcx, SUNWscpux, SUNWs

I placed the .zip patch file I downloaded into /var/spool/patch, unzipped it and installed the patch with patchadd.

# unzip
   creating: 108162-08/
  inflating: 108162-08/.diPatch
  inflating: 108162-08/patchinfo
   creating: 108162-08/SUNWcsr/
  inflating: 108162-08/SUNWcsr/pkgmap
  inflating: 108162-08/SUNWcsr/pkginfo
   creating: 108162-08/SUNWcsr/install/
  inflating: 108162-08/SUNWcsr/install/checkinstall
  inflating: 108162-08/SUNWcsr/install/copyright
  inflating: 108162-08/SUNWcsr/install/i.none
  inflating: 108162-08/SUNWcsr/install/patch_checkinstall
  inflating: 108162-08/SUNWcsr/install/patch_postinstall
  inflating: 108162-08/SUNWcsr/install/postinstall
  inflating: 108162-08/SUNWcsr/install/preinstall
   creating: 108162-08/SUNWcsr/reloc/
   creating: 108162-08/SUNWcsr/reloc/sbin/
  inflating: 108162-08/SUNWcsr/reloc/sbin/jsh
   creating: 108162-08/SUNWcsu/
  inflating: 108162-08/SUNWcsu/pkgmap
  inflating: 108162-08/SUNWcsu/pkginfo
   creating: 108162-08/SUNWcsu/install/
  inflating: 108162-08/SUNWcsu/install/checkinstall
  inflating: 108162-08/SUNWcsu/install/copyright
  inflating: 108162-08/SUNWcsu/install/i.none
  inflating: 108162-08/SUNWcsu/install/patch_checkinstall
  inflating: 108162-08/SUNWcsu/install/patch_postinstall
  inflating: 108162-08/SUNWcsu/install/postinstall
  inflating: 108162-08/SUNWcsu/install/preinstall
   creating: 108162-08/SUNWcsu/reloc/
   creating: 108162-08/SUNWcsu/reloc/usr/
   creating: 108162-08/SUNWcsu/reloc/usr/bin/
  inflating: 108162-08/SUNWcsu/reloc/usr/bin/jsh
  inflating: 108162-08/SUNWcsu/reloc/usr/bin/ksh
  inflating: 108162-08/README.108162-08
# patchadd 108162-08

Checking installed patches...
Verifying sufficient filesystem capacity (dry run method)...
Installing patch packages...

Patch number 108162-08 has been successfully installed.
See /var/sadm/patch/108162-08/log for details

Patch packages installed:

I checked the installation log file in /var/sadm/108162-08 and saw the following.

# cat /var/sadm/patch/108162-08/log

This appears to be an attempt to install the same architecture and
version of a package which is already installed.  This installation
will attempt to overwrite this package.

Dryrun complete.
No changes were made to the system.

This appears to be an attempt to install the same architecture and
version of a package which is already installed.  This installation
will attempt to overwrite this package.

Dryrun complete.
No changes were made to the system.

This appears to be an attempt to install the same architecture and
version of a package which is already installed.  This installation
will attempt to overwrite this package.

Installation of <SUNWcsr> was successful.

This appears to be an attempt to install the same architecture and
version of a package which is already installed.  This installation
will attempt to overwrite this package.

Installation of <SUNWcsu> was successful.

I then checked on the patch with showrev -p.

# showrev -p | grep 108162-08
Patch: 108162-08 Obsoletes: 108416-02 Requires:  Incompatibles:  Packages: SUNWc
su, SUNWcsr

[/os/unix/solaris/5_7] permanent link

Thu, Mar 26, 2009 5:12 pm

SunOS 5.7: packaging utilities patch

When checking SunSolve for available patches for a Solaris 5.7 system, I found a SunOS 5.7: packaging utilities patch. I unzipped the file I downloaded in /var/spool/patch and then used patchadd to install it, but received a message that another patch was required to be installed prior to this one.
# unzip
   creating: 107443-24/
  inflating: 107443-24/.diPatch
  inflating: 107443-24/patchinfo
   creating: 107443-24/SUNWarc/
  inflating: 107443-24/SUNWarc/pkgmap
  inflating: 107443-24/SUNWarc/pkginfo
   creating: 107443-24/SUNWarc/install/
  inflating: 107443-24/SUNWarc/install/checkinstall
  inflating: 107443-24/SUNWarc/install/copyright
  inflating: 107443-24/SUNWarc/install/i.none
  inflating: 107443-24/SUNWarc/install/patch_checkinstall
  inflating: 107443-24/SUNWarc/install/patch_postinstall
  inflating: 107443-24/SUNWarc/install/postinstall
  inflating: 107443-24/SUNWarc/install/preinstall
   creating: 107443-24/SUNWarc/reloc/
   creating: 107443-24/SUNWarc/reloc/usr/
   creating: 107443-24/SUNWarc/reloc/usr/lib/
  inflating: 107443-24/SUNWarc/reloc/usr/lib/libpkg.a
   creating: 107443-24/SUNWcsu/
  inflating: 107443-24/SUNWcsu/pkgmap
  inflating: 107443-24/SUNWcsu/pkginfo
   creating: 107443-24/SUNWcsu/install/
  inflating: 107443-24/SUNWcsu/install/checkinstall
  inflating: 107443-24/SUNWcsu/install/copyright
  inflating: 107443-24/SUNWcsu/install/i.none
  inflating: 107443-24/SUNWcsu/install/patch_checkinstall
  inflating: 107443-24/SUNWcsu/install/patch_postinstall
  inflating: 107443-24/SUNWcsu/install/postinstall
  inflating: 107443-24/SUNWcsu/install/preinstall
   creating: 107443-24/SUNWcsu/reloc/
   creating: 107443-24/SUNWcsu/reloc/usr/
   creating: 107443-24/SUNWcsu/reloc/usr/bin/
  inflating: 107443-24/SUNWcsu/reloc/usr/bin/pkginfo
  inflating: 107443-24/SUNWcsu/reloc/usr/bin/pkgmk
  inflating: 107443-24/SUNWcsu/reloc/usr/bin/pkgparam
  inflating: 107443-24/SUNWcsu/reloc/usr/bin/pkgproto
  inflating: 107443-24/SUNWcsu/reloc/usr/bin/pkgtrans
   creating: 107443-24/SUNWcsu/reloc/usr/sadm/
   creating: 107443-24/SUNWcsu/reloc/usr/sadm/install/
   creating: 107443-24/SUNWcsu/reloc/usr/sadm/install/bin/
  inflating: 107443-24/SUNWcsu/reloc/usr/sadm/install/bin/pkginstall
  inflating: 107443-24/SUNWcsu/reloc/usr/sadm/install/bin/pkgname
  inflating: 107443-24/SUNWcsu/reloc/usr/sadm/install/bin/pkgremove
   creating: 107443-24/SUNWcsu/reloc/usr/sadm/install/scripts/
  inflating: 107443-24/SUNWcsu/reloc/usr/sadm/install/scripts/cmdexec
  inflating: 107443-24/SUNWcsu/reloc/usr/sadm/install/scripts/i.awk
  inflating: 107443-24/SUNWcsu/reloc/usr/sadm/install/scripts/
  inflating: 107443-24/SUNWcsu/reloc/usr/sadm/install/scripts/i.sed
  inflating: 107443-24/SUNWcsu/reloc/usr/sadm/install/scripts/r.awk
  inflating: 107443-24/SUNWcsu/reloc/usr/sadm/install/scripts/
  inflating: 107443-24/SUNWcsu/reloc/usr/sadm/install/scripts/r.sed
   creating: 107443-24/SUNWcsu/reloc/usr/sbin/
  inflating: 107443-24/SUNWcsu/reloc/usr/sbin/installf
  inflating: 107443-24/SUNWcsu/reloc/usr/sbin/pkgadd
  inflating: 107443-24/SUNWcsu/reloc/usr/sbin/pkgchk
  inflating: 107443-24/SUNWcsu/reloc/usr/sbin/pkgmv
  inflating: 107443-24/SUNWcsu/reloc/usr/sbin/pkgrm
  inflating: 107443-24/README.107443-24
  inflating: 107443-24/LEGAL_LICENSE.TXT
# ls 107443-24
LEGAL_LICENSE.TXT  SUNWarc            patchinfo
README.107443-24   SUNWcsu
# patchadd /var/spool/patch/107443-24

Checking installed patches...
ERROR: This patch requires patch  107332-03
which has not been applied to the system.

Patchadd is terminating.

The 107332 patch was available from the SunSolve site, but its status was listed as "obsolete". That patch was obsoleted by patch 106938-07, which was in turn obsoleted by patch 106938-08, which was itself obsoleted by patch 106938-09, which has a title of "SunOS 5.7: libresolv, in.named, libadm, & nslookup patch".

I downloaded the SunOS 5.7: libresolv, in.named, libadm, & nslookup patch into /var/spool/patch and uncompressed it.

# unzip
   creating: 106938-09/
  inflating: 106938-09/.diPatch
  inflating: 106938-09/patchinfo
   creating: 106938-09/SUNWarc/
  inflating: 106938-09/SUNWarc/pkgmap
  inflating: 106938-09/SUNWarc/pkginfo
   creating: 106938-09/SUNWarc/install/
  inflating: 106938-09/SUNWarc/install/checkinstall
  inflating: 106938-09/SUNWarc/install/copyright
  inflating: 106938-09/SUNWarc/install/i.none
  inflating: 106938-09/SUNWarc/install/patch_checkinstall
  inflating: 106938-09/SUNWarc/install/patch_postinstall
  inflating: 106938-09/SUNWarc/install/postinstall
  inflating: 106938-09/SUNWarc/install/preinstall
   creating: 106938-09/SUNWarc/reloc/
   creating: 106938-09/SUNWarc/reloc/usr/
   creating: 106938-09/SUNWarc/reloc/usr/lib/
  inflating: 106938-09/SUNWarc/reloc/usr/lib/libadm.a
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-l300.ln
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-l300s.ln
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-l4014.ln
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-l450.ln
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-lTL.ln
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-ladm
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-ladm.ln
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-laio.ln
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-lauth.ln
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-lbsm.ln
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-lc.ln
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-lc2stubs.ln
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-lcmd.ln
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-lcurses.ln
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-ldevice.ln
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-ldoor.ln
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-lkstat.ln
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-lkvm.ln
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-lmtmalloc.ln
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-lnls.ln
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-lnsl
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-lnsl.ln
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-lpam.ln
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-lplot.ln
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-lrac.ln
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-lresolv
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-lresolv.ln
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-lsec.ln
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-lthread.ln
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-lvolmgt.ln
  inflating: 106938-09/SUNWarc/reloc/usr/lib/llib-lvt0.ln
   creating: 106938-09/SUNWarc/reloc/usr/xpg4/
   creating: 106938-09/SUNWarc/reloc/usr/xpg4/lib/
  inflating: 106938-09/SUNWarc/reloc/usr/xpg4/lib/llib-lcurses.ln
   creating: 106938-09/SUNWarcx/
  inflating: 106938-09/SUNWarcx/pkgmap
  inflating: 106938-09/SUNWarcx/pkginfo
   creating: 106938-09/SUNWarcx/install/
  inflating: 106938-09/SUNWarcx/install/checkinstall
  inflating: 106938-09/SUNWarcx/install/copyright
  inflating: 106938-09/SUNWarcx/install/i.none
  inflating: 106938-09/SUNWarcx/install/patch_checkinstall
  inflating: 106938-09/SUNWarcx/install/patch_postinstall
  inflating: 106938-09/SUNWarcx/install/postinstall
  inflating: 106938-09/SUNWarcx/install/preinstall
   creating: 106938-09/SUNWarcx/reloc/
   creating: 106938-09/SUNWarcx/reloc/usr/
   creating: 106938-09/SUNWarcx/reloc/usr/lib/
   creating: 106938-09/SUNWarcx/reloc/usr/lib/sparcv9/
  inflating: 106938-09/SUNWarcx/reloc/usr/lib/sparcv9/llib-l300.ln
  inflating: 106938-09/SUNWarcx/reloc/usr/lib/sparcv9/llib-l300s.ln
  inflating: 106938-09/SUNWarcx/reloc/usr/lib/sparcv9/llib-l4014.ln
  inflating: 106938-09/SUNWarcx/reloc/usr/lib/sparcv9/llib-l450.ln
  inflating: 106938-09/SUNWarcx/reloc/usr/lib/sparcv9/llib-ladm.ln
  inflating: 106938-09/SUNWarcx/reloc/usr/lib/sparcv9/llib-laio.ln
  inflating: 106938-09/SUNWarcx/reloc/usr/lib/sparcv9/llib-lbsm.ln
  inflating: 106938-09/SUNWarcx/reloc/usr/lib/sparcv9/llib-lc.ln
  inflating: 106938-09/SUNWarcx/reloc/usr/lib/sparcv9/llib-lcmd.ln
  inflating: 106938-09/SUNWarcx/reloc/usr/lib/sparcv9/llib-lcurses.ln
  inflating: 106938-09/SUNWarcx/reloc/usr/lib/sparcv9/llib-ldevice.ln
  inflating: 106938-09/SUNWarcx/reloc/usr/lib/sparcv9/llib-ldoor.ln
  inflating: 106938-09/SUNWarcx/reloc/usr/lib/sparcv9/llib-lkstat.ln
  inflating: 106938-09/SUNWarcx/reloc/usr/lib/sparcv9/llib-lkvm.ln
  inflating: 106938-09/SUNWarcx/reloc/usr/lib/sparcv9/llib-lmtmalloc.ln
  inflating: 106938-09/SUNWarcx/reloc/usr/lib/sparcv9/llib-lnls.ln
  inflating: 106938-09/SUNWarcx/reloc/usr/lib/sparcv9/llib-lnsl.ln
  inflating: 106938-09/SUNWarcx/reloc/usr/lib/sparcv9/llib-lpam.ln
  inflating: 106938-09/SUNWarcx/reloc/usr/lib/sparcv9/llib-lplot.ln
  inflating: 106938-09/SUNWarcx/reloc/usr/lib/sparcv9/llib-lrac.ln
  inflating: 106938-09/SUNWarcx/reloc/usr/lib/sparcv9/llib-lresolv.ln
  inflating: 106938-09/SUNWarcx/reloc/usr/lib/sparcv9/llib-lsec.ln
  inflating: 106938-09/SUNWarcx/reloc/usr/lib/sparcv9/llib-lthread.ln
  inflating: 106938-09/SUNWarcx/reloc/usr/lib/sparcv9/llib-lvolmgt.ln
  inflating: 106938-09/SUNWarcx/reloc/usr/lib/sparcv9/llib-lvt0.ln
   creating: 106938-09/SUNWarcx/reloc/usr/xpg4/
   creating: 106938-09/SUNWarcx/reloc/usr/xpg4/lib/
   creating: 106938-09/SUNWarcx/reloc/usr/xpg4/lib/sparcv9/
  inflating: 106938-09/SUNWarcx/reloc/usr/xpg4/lib/sparcv9/llib-lcurses.ln
   creating: 106938-09/SUNWcsl/
  inflating: 106938-09/SUNWcsl/pkgmap
  inflating: 106938-09/SUNWcsl/pkginfo
   creating: 106938-09/SUNWcsl/install/
  inflating: 106938-09/SUNWcsl/install/checkinstall
  inflating: 106938-09/SUNWcsl/install/copyright
  inflating: 106938-09/SUNWcsl/install/i.none
  inflating: 106938-09/SUNWcsl/install/patch_checkinstall
  inflating: 106938-09/SUNWcsl/install/patch_postinstall
  inflating: 106938-09/SUNWcsl/install/postinstall
  inflating: 106938-09/SUNWcsl/install/preinstall
   creating: 106938-09/SUNWcsl/reloc/
   creating: 106938-09/SUNWcsl/reloc/usr/
   creating: 106938-09/SUNWcsl/reloc/usr/lib/
  inflating: 106938-09/SUNWcsl/reloc/usr/lib/
  inflating: 106938-09/SUNWcsl/reloc/usr/lib/
  inflating: 106938-09/SUNWcsl/reloc/usr/lib/
   creating: 106938-09/SUNWcslx/
  inflating: 106938-09/SUNWcslx/pkgmap
  inflating: 106938-09/SUNWcslx/pkginfo
   creating: 106938-09/SUNWcslx/install/
  inflating: 106938-09/SUNWcslx/install/checkinstall
  inflating: 106938-09/SUNWcslx/install/copyright
  inflating: 106938-09/SUNWcslx/install/i.none
  inflating: 106938-09/SUNWcslx/install/patch_checkinstall
  inflating: 106938-09/SUNWcslx/install/patch_postinstall
  inflating: 106938-09/SUNWcslx/install/postinstall
  inflating: 106938-09/SUNWcslx/install/preinstall
   creating: 106938-09/SUNWcslx/reloc/
   creating: 106938-09/SUNWcslx/reloc/usr/
   creating: 106938-09/SUNWcslx/reloc/usr/lib/
   creating: 106938-09/SUNWcslx/reloc/usr/lib/sparcv9/
  inflating: 106938-09/SUNWcslx/reloc/usr/lib/sparcv9/
  inflating: 106938-09/SUNWcslx/reloc/usr/lib/sparcv9/
   creating: 106938-09/SUNWcsu/
  inflating: 106938-09/SUNWcsu/pkgmap
  inflating: 106938-09/SUNWcsu/pkginfo
   creating: 106938-09/SUNWcsu/install/
  inflating: 106938-09/SUNWcsu/install/checkinstall
  inflating: 106938-09/SUNWcsu/install/copyright
  inflating: 106938-09/SUNWcsu/install/i.none
  inflating: 106938-09/SUNWcsu/install/patch_checkinstall
  inflating: 106938-09/SUNWcsu/install/patch_postinstall
  inflating: 106938-09/SUNWcsu/install/postinstall
  inflating: 106938-09/SUNWcsu/install/preinstall
   creating: 106938-09/SUNWcsu/reloc/
   creating: 106938-09/SUNWcsu/reloc/usr/
   creating: 106938-09/SUNWcsu/reloc/usr/sbin/
  inflating: 106938-09/SUNWcsu/reloc/usr/sbin/in.named
  inflating: 106938-09/SUNWcsu/reloc/usr/sbin/nslookup
   creating: 106938-09/SUNWscpux/
  inflating: 106938-09/SUNWscpux/pkgmap
  inflating: 106938-09/SUNWscpux/pkginfo
   creating: 106938-09/SUNWscpux/install/
  inflating: 106938-09/SUNWscpux/install/checkinstall
  inflating: 106938-09/SUNWscpux/install/copyright
  inflating: 106938-09/SUNWscpux/install/i.none
  inflating: 106938-09/SUNWscpux/install/patch_checkinstall
  inflating: 106938-09/SUNWscpux/install/patch_postinstall
  inflating: 106938-09/SUNWscpux/install/postinstall
  inflating: 106938-09/SUNWscpux/install/preinstall
   creating: 106938-09/SUNWscpux/reloc/
   creating: 106938-09/SUNWscpux/reloc/usr/
   creating: 106938-09/SUNWscpux/reloc/usr/ucblib/
   creating: 106938-09/SUNWscpux/reloc/usr/ucblib/sparcv9/
  inflating: 106938-09/SUNWscpux/reloc/usr/ucblib/sparcv9/llib-lucb.ln
   creating: 106938-09/SUNWsra/
  inflating: 106938-09/SUNWsra/pkgmap
  inflating: 106938-09/SUNWsra/pkginfo
   creating: 106938-09/SUNWsra/install/
  inflating: 106938-09/SUNWsra/install/checkinstall
  inflating: 106938-09/SUNWsra/install/copyright
  inflating: 106938-09/SUNWsra/install/i.none
  inflating: 106938-09/SUNWsra/install/patch_checkinstall
  inflating: 106938-09/SUNWsra/install/patch_postinstall
  inflating: 106938-09/SUNWsra/install/postinstall
  inflating: 106938-09/SUNWsra/install/preinstall
   creating: 106938-09/SUNWsra/reloc/
   creating: 106938-09/SUNWsra/reloc/usr/
   creating: 106938-09/SUNWsra/reloc/usr/ucblib/
  inflating: 106938-09/SUNWsra/reloc/usr/ucblib/llib-lucb.ln
  inflating: 106938-09/README.106938-09

I then installed both patches with patchadd.

# patchadd -M /var/spool/patch 106938-09 107443-24

Checking installed patches...
Verifying sufficient filesystem capacity (dry run method)...
Installing patch packages...

Patch number 106938-09 has been successfully installed.
See /var/sadm/patch/106938-09/log for details

Patch packages installed:

Checking installed patches...
Verifying sufficient filesystem capacity (dry run method)...
Installing patch packages...

Patch number 107443-24 has been successfully installed.
See /var/sadm/patch/107443-24/log for details

Patch packages installed:

When patchadd installs patches, it creates a directory of the form /var/sadm/patch/patch_id, where patch_id is the id for the patch, e.g 107443-24. It copies the README file there and creates a log file for the patch installation in that directory.

# ls /var/sadm/patch/107443-24
README.107443-24  log
# ls /var/sadm/patch/106938-09
README.106938-09  log

Files Included in the 107443-24 Patch:


ReadMe for Patch 107443-24

Files Included in the 106938-09 Patch: 

ReadMe for Patch 106938-09

  1. patchadd(1M) - apply a patch package to a system running the Solaris operating environment
    Sun Microsystems Documentation
  2. Solaris Patch Installation
    Developer Resources for Java Technology

[/os/unix/solaris/5_7] permanent link

Thu, Mar 26, 2009 4:42 pm

SunOS 5.7: nawk Patch

I checked SunSolve for available patches for a Solaris 5.7 system. I installed the SunOS 5.7: nawk Patch on the system. I unzipped the file I downloaded in /var/spool/patch and then used patchadd to install it.
# unzip
   creating: 111113-02/
  inflating: 111113-02/.diPatch
   creating: 111113-02/SUNWesu/
  inflating: 111113-02/SUNWesu/pkgmap
  inflating: 111113-02/SUNWesu/pkginfo
   creating: 111113-02/SUNWesu/install/
  inflating: 111113-02/SUNWesu/install/checkinstall
  inflating: 111113-02/SUNWesu/install/copyright
  inflating: 111113-02/SUNWesu/install/i.none
  inflating: 111113-02/SUNWesu/install/patch_checkinstall
  inflating: 111113-02/SUNWesu/install/patch_postinstall
  inflating: 111113-02/SUNWesu/install/postinstall
  inflating: 111113-02/SUNWesu/install/preinstall
   creating: 111113-02/SUNWesu/reloc/
   creating: 111113-02/SUNWesu/reloc/usr/
   creating: 111113-02/SUNWesu/reloc/usr/bin/
  inflating: 111113-02/SUNWesu/reloc/usr/bin/nawk
  inflating: 111113-02/README.111113-02
# cd 111113-02
# ls
README.111113-02  SUNWesu
# patchadd /var/spool/patch/111113-02

Checking installed patches...
Verifying sufficient filesystem capacity (dry run method)...
Installing patch packages...

Patch number 111113-02 has been successfully installed.
See /var/sadm/patch/111113-02/log for details

Patch packages installed:

Files Included in this Patch:
Problem Description:
4451613 *nawk* record limit corrupts patch checking when installing patch

ReadMe for Patch 111113-02

[/os/unix/solaris/5_7] permanent link

Tue, Mar 24, 2009 9:38 pm

Furl Disappearing

I've been using Furl for maintaining online bookmarks. Furl allows you to maintain your own copy of a webpage online and to categorize and tag webpages you save through Furl. Unfortunately, Furl is disappearing. I've been wondering how long Furl would last, since it didn't show me ads when I visited my Furl archive nor when I bookmarked sites, so I didn't know how Furl was funding its continued operations.

Furl is offering one the capability to transfer one's Furl bookmarks to Diigo, so I signed up for a Diigo account and requested the transfer of my bookmarks. I've also downloaded my archived webpages from Furl.

[/network/web/archiving/furl] permanent link

Tue, Mar 24, 2009 8:41 am

HTML Validation

If you want to check your HTML code to ensure that it is correct, you can use The W3C Markup Validation Service. The service is free and will point out lines in your code with errors. Even though a page may look correct when you view it in your browser, it may still contain errors; the particular browser you are using may compensate for the incorrect code or just happen to present it in the way you expect, but other browsers may not be so forgiving, so not everyone who visits your site may see the page as you see it, if it has errors in the HTML code. Of course, due to to variations in the way browsers interpret the code, the page may not look exactly the same to all visitors even if the code is valid, but you are, hopefully, reducing the chance of problems by correcting the code.

[/network/web/html] permanent link

Mon, Mar 23, 2009 11:37 am

OpenSSL 0.9.8j and OpenSSH 5.2p1 Upgrades on Solaris 2.7 System

When I checked the version of OpenSSL on a Sun SPARC system running Solaris 2.7, I found it was out-of-date.
# ssh -V
OpenSSH_4.7p1, OpenSSL 0.9.8f 11 Oct 2007
# /usr/local/ssl/bin/openssl version
OpenSSL 0.9.8f 11 Oct 2007

Version 0.9.8j is currently available, so I downloaded it from The site provides the following information for OpenSSL 0.98j for the SPARC platform:

openssl-0.9.8j-sol7-sparc-local.gz openssl is an open source toolkit implementing the Secure Sockets Layer (SSL v2/v3) and Transport Layer Security (TLS v1) protocols as well as a full-strength general purpose cryptography library - installs in /usr/local/ssl. Note to users with sun4m machines. The openssl package here was built on a sun4u system and will not work on your machines. The one built for Solaris 2.5 was built on a sun4m machine and has been tested and does work. If you do uname -a and you get sun4m in the result, install the Solaris 2.5 openssl package instead. The configure option used for making openssl was solaris-sparcv9-gcc shared. You may also need to install either gcc-3.4.6 or libgcc-3.4.6 to obtain the library. openssl is often used to make machines more secure. Make sure you know what you are doing. Any security problems are your responsiblitiy. See our Disclaimer.

openssl-0.9.8j.tar.gz Source Code. [Details]

I unzipped the file I downloaded and installed the package.

# gunzip openssl-0.9.8j-sol7-sparc-local.gz
# pkgadd -d ./openssl-0.9.8j-sol7-sparc-local

The following packages are available:
  1  SMCossl     openssl
                 (sparc) 0.9.8j

Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]: 1

Processing package instance <SMCossl> from </tmp/openssl-0.9.8j-sol7-sparc-local>

(sparc) 0.9.8j
The OpenSSL Group
Using </usr/local> as the package base directory.
## Processing package information.
## Processing system information.
   771 package pathnames are already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.

Installing openssl as <SMCossl>

## Installing part 1 of 1.
<text snipped>
[ verifying class <none> ]

Installation of <SMCossl> was successful.

I then verified the new version was installed.

# /usr/local/ssl/bin/openssl version
OpenSSL 0.9.8j 07 Jan 2009

When I then ran the ssh command, I realized I needed to upgrade ssh as well.

# ssh -V
OpenSSL version mismatch. Built against 908070, you have 9080af listed the current OpenSSH version as 5.2p1.

openssh-5.2p1-sol7-sparc-local.gz Openssh is an open source version of the SSH secure shell system - installs in /usr/local. PAM support is included and requires its own configuration. Openssh also requires the installation of the packages openssl-0.9.8j (do not use the older openssl packages), zlib, gcc-3.4.6 or libgcc-3.4.6, prngd and optionally, but highly recommended, the perl, egd and tcp_wrappers packages. You MUST read the OpenSSH installation page for installation details and helpful web sites. For example, the /usr/local/etc/sshd_config file may need to be edited. openssh is often used to make machines more secure. Make sure you know what you are doing. Any security problems are your responsiblitiy. The main ssh web site is at the [Details] link below. It is also important that you read our Disclaimer.

openssh-5.2p1.tar.gz Source Code. [Details]

So I downloaded and installed the latest OpenSSH package from as well.

# wget -q
# gunzip openssh-5.2p1-sol7-sparc-local.gz
# pkgadd -d ./openssh-5.2p1-sol7-sparc-local

The following packages are available:
  1  SMCosh521     openssh
                   (sparc) 5.2p1

Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]: 1

Processing package instance <SMCosh521> from </tmp/openssh-5.2p1-sol7-sparc-local>

(sparc) 5.2p1
The OpenSSH Group
Using </usr/local> as the package base directory.
## Processing package information.
## Processing system information.
   16 package pathnames are already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.

The following files are already installed on the system and are being
used by another package:
<text snipped>

Do you want to install these conflicting files [y,n,?,q] y
## Checking for setuid/setgid programs.

Installing openssh as <SMCosh521>

## Installing part 1 of 1.
<text snipped>
[ verifying class <none> ]

Installation of <SMCosh521> was successful.

I then rechecked the version of ssh on the system. The version was now up-to-date.

# ssh -V
OpenSSH_5.2p1, OpenSSL 0.9.8j 07 Jan 2009

The OpenSSH installation page stated "It has been noted that on some Solaris systems, scp and sftp may not work unless /usr/local/bin in in your PATH before /usr/bin. The older scp that comes with Solaris may conflict with the new openssl packages." So I tested sftp and scp to ensure they worked by transferring a file to another system.

[/os/unix/solaris] permanent link

Sun, Mar 22, 2009 11:45 am

Viewing the Registy with BartPE

To view registry values for the version of Microsoft Windows on a system's hard drive using a Bart's Preinstalled Environment (BartPE) bootable live windows CD/DVD boot disc take the following steps:
  1. Boot the system from the BartPE disc.
  2. Click on Go and select Command Prompt (CMD) .
  3. At the command prompt, type regedit.
  5. From the File menu, choose Load Hive.

    A series of message boxes may appear that state that the folder cannot be found and that the location is unavailable. Ignore these messages and click OK when they appear.

    The Load Hive dialog box appears.

  6. In the Files of type box, select All Files .
  7. Navigate to the registry location on your target device.

    For example, if Windows is on drive C, navigate to C:\WINDOWS\system32\config.

  8. In the config folder, select the hive you want to edit. The choices are as follows:
    • SAM
    • SYSTEM
    Select a file with one of the above names without an extension (you may also see .sav and .log files in the directory).
  9. Click on OK.
  10. In the Load Hive dialog box type a Key Name. For example, Drive_C.

    To load more hives, repeat the previous steps.

  11. Choose HKEY_LOCAL_MACHINE, and then choose the new registry key(s) you created.
  12. Edit or view the registry keys.
  13. When you have completed your reg key changes, choose HKEY_LOCAL_MACHINE and a key you created within it, e.g. HKEY_LOCAL_MACHINE\Drive_C
  14. Choose the File menu, and then choose Unload Hive When prompted as to whether you are sure you want to unload the current key and all of its subkeys, choose Yes.

[/os/windows/utilities/diagnostic/bartpe] permanent link

Sun, Mar 22, 2009 10:52 am

Determining Device Driver Locations Used During Setup

To determine where Microsoft Windows will look for device driver files during the Windows setup process, you need to examine the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion.

[ More Info ]

[/os/windows/registry/devicepath] permanent link

Sat, Mar 21, 2009 7:21 pm

Belkin F5D7230-4 DHCP Range Error

I have a Belkin wireless router, model F5D7230-4 6000 router with firmware version F5D7230-4_US_8.01.07. I found that oftentimes I couldn't ping the router from a system. I finally realized the source of the problem today. When I clicked on LAN Settings, I saw the router had an IP address of with a subnet mask of, yet the system from which I couldn't ping any other system connected to the router and which had no network access, had an IP address of assigned via DHCP from the router. With a subnet mask of, the host address range would be through, since the router is using and is the broadcast address. Yet when I attempted to change the IP address range the router used for its DHCP assignments, it kept resetting the IP pool ending address to after I set it to I would set the starting address to and the ending address at then click on Apply Changes. The router would reboot and I would find it had reset the last address to be assigned by DHCP to again. I tried setting the ending addres to 5 with the same results.

So I changed the subnet mask to, which provides an address range of 16 addresses (14 usable for hosts, since is the subnet id and is then the broadcast address). I then tried setting the ending IP address for the DHCP server built into the router to 7. When the router rebooted that address was back at 12 again. This time I just left it, since at least this time all of the addresses the built-in DHCP server would assign will be within the subnet range.

[/hardware/network/switch/belkin] permanent link

Sat, Mar 21, 2009 2:27 pm

Changing the IP address of a Dell PowerConnect 3024 Switch

You can change the IP address of a Dell PowerConnect 3024 switch by taking the steps below.
  1. Connect to the system via telnet. From the initial welcome screen you must enter a password to proceed, if password protection is enabled. If password protection is disabled, the main menu is displayed. By default, password protection is disabled. If password protection is enabled, the default password is switch.
                W     W
                W  W  W  EEEEEE  L        CCCC    OOOO   M    M  EEEEEE
                W  W  W  E       L       C    C  O    O  MM  MM  E
                W  W  W  EEEEE   L       C       O    O  M MM M  EEEEE
                W  W  W  E       L       C       O    O  M    M  E
                W  W  W  E       L       C    C  O    O  M    M  E
                 WW WW   EEEEEE  LLLLLL   CCCC    OOOO   M    M  EEEEEE
    Enter password:
  2. From the main menu, select System Manager.
                                   PowerConnect 3024
                                       Main Menu
                                 a. System Manager
                                 b. Port Manager
                                 c. Address Manager
                                 d. Spanning Tree
                                 e. VLAN and CoS Setup
                                 f. Port Trunking
                                 g. Port Mirroring
                                 h. SNMP Management
                                 i. Multimedia Support
                                 j. Statistics
                                 k. Save Configuration
    Hit <Enter> to configure General, IP, Password, NVRAM, Firmware, or Reset
                                                    <Ctrl-L> Refresh  <Ctrl-W> Save
  3. Then select IP Settings.
                                   PowerConnect 3024
                                     System Manager
                                   a. General Info
                                   b. IP Settings
                                   c. Security Admin
                                   d. Firmware Update
                                   e. Reset
    Hit <Enter> to configure the IP Address, Gateway Address, or Network Mask
    <ESC> Back                                      <Ctrl-L> Refresh  <Ctrl-W> Save
  4. Change the IP address, subnet mask, and gateway address to the appropriate values for your LAN.
                                   PowerConnect 3024
                               System Manager/IP Settings
                                 IP Address:  
                               Network Mask:
                            Default Gateway:
    Enter this switch's IP address
    <ESC> Back                                      <Ctrl-L> Refresh  <Ctrl-W> Save

    Note: if you hit enter the values are changed, but not saved, so you can revert to the previous values by powering off the switch and powering it back on. If you are changing the address, such that the new address is no longer in the same subnet as the existing address and the gateway IP address will also change, rather than just changing from an address in the same subnet to another, I would suggest changing the gateway address first, because you can't change the IP address and then use the cursor keys to move to other fields. When you type in the new IP address, you can hit Escape to undo the change or Enter to accept it. If the change would place the switch in a different subnet than the system from which you have connected to the switch by telnet, you will be immediately disconnected when you hit Enter.

    But, if you change the gateway address first and hit Enter, the cursor will automatically jump to the IP address field, where you can then change the IP address. You will still be disconnected as soon as the IP address is changed to one that isn't in the same subnet as the connecting system, but then you've got both values changed.

  5. If you are just changing the IP to one in the same subnet, hit Ctrl-W to save the new configuration. If you've been disconnected, because you changed the IP address to one in a different subnet, reconfigure the connecting system, log back into the PowerConnect 3024 and save the configuration.

[/hardware/network/switch/dell] permanent link

Sun, Mar 15, 2009 11:33 pm

Steps for Creating Your Own Drupal Smiley Pak

I wanted to create a Calvin and Hobbes smiley pack for Drupal (I'm using Drupal 6), since Calvin and Hobbes is my favorite comic. Within the /modules/smileys/packs/ directory beneath the directory where Drupal was installed, I created a Calvin directory. I put the following GIF images in that directory:

# ls
angry.gif  goofy.gif    not-again.gif  oops.gif       sour.gif   yell.gif
geez.gif   nah-nah.gif  omg.gif        pick-nose.gif  tired.gif  yuck.gif

But Drupal won't be able to use those emoticons unless you create a .pak file, e.g. Calvin.pak and place it in the same directory.

To get an idea of what should go into that file, you can take a look at the Example.pak file in the /modules/smileys/packs/Example directory. That file contains the following lines:

barf.gif=+:Barf!=+::sick: :barf:
cool.png=+:Cool=+:8) 8-) :cool:
puzzled.png=+:Puzzled=+::? :-? :puzzled:
shock.png=+:Shocked=+::O :-O :shocked:
tongue.png=+:Sticking out tongue=+::P :-P :tongue:
evil.png=+:Evil=+:}:) }:-) :evil:
lol.png=+:Laughing out loud=+::D :-D :lol:
sad.png=+:Sad=+::( :-( :sad:
wink.png=+:Eye=+:;) ;-) :wink:
smile.png=+:Smiling=+::) :-) :smile:

If I look at the files in the Example directory, I see the following files.

barf.gif          cool.png  Example.pak  puzzled.png  shock.png   wink.png
blank-blue.png    die.gif   jawdrop.gif  README.txt   smile.png
blank-yellow.png  evil.png  lol.png      sad.png      tongue.png

So I can see that there is a line in Example.pak for every graphics file, in this case .gif and .png files, in the Example directory. At the end of each line is a descriptive code in the form of :emoticon:, i.e. a colon followed by a name for the emoticon followed by another colon, e.g. :tongue:.

For the "sticking out tongue" emoticon, I see the following line:

tongue.png=+:Sticking out tongue=+::P :-P :tongue:

I could just click on the emoticon to insert it in a posting, if I had enabled the use of the "smiley select box" (see Smileys Module for Drupal for instructions on how to enable that select box). Or, by using the codes shown on the entry for tongue.png in the Example.pak file, if I edited a forum posting and typed :tongue: and then previewed or saved the posting, where I had inserted :tongue: the emoticon Tongue Sticking Out 
Emoticon with a tongue sticking out would be displayed. I could also use :-P or just :P to insert the emoticon. I.e., I could use any of the codes that appear after the +:Sticking out tongue=+: part of the entry for tongue.png.

If I look at the Jawdropping entry, I see the following:


In that case, there is only one text code to insert the jawdropping smiley, i.e. :jawdrop:.

So now I think I see how to set up the entries in a Calvin.pak file. These are the entries I placed in that file:

angry.gif=+:Calvin angry=+::calvin-angry:
geez.gif=+:Calvin Geez=+::calvin-geez:
goofy.gif=+:Calvin Goofy=+::calvin-goofy:
nah-nah.gif=+:Calvin Nah-nah=+::calvin-nah-nah:
not-again.gif=+:Calvin Not-again=+::calvin-not-again:
omg.gif=+:Calvin OMG=+::calvin-omg:
oops.gif=+:Calvin Oops=+::calvin-oops:
pick-nose.gif=+:Calvin Pick-nose::calvin-pick-nose:
sour.gif=+:Calvin Sour=+::calvin-sour:
tired.gif=+:Calvin Tired=+::calvin-tired:
yell.gif=+:Calvin Yell=+::calvin-yell:
yuck.gif=+:Calvin Yuck=+::calvin-yuck:

The format I used for each entry is as follows:


I.e. I put the name of the image as the first part of the line. Next comes a description for it beginning with an equal sign, then a plus sign and then a colon. Next comes the descriptive text for the image, then an equal sign, followed by a plus sign and then a colon. After that I put the code that can be typed in a posting that will be translated to the image when the posting is previewed or saved. E.g. :calvin-yell: will produce Calvin Yelling Emoticon, the emoticon for a yelling Calvin.

Once I have the images in place and the .pak file created, I can log into Drupal as an administrator, click on Administer, Site configuration, Smileys, and then click on Import at the top of the page. I now see Calvin listed as a smiley pack that can be installed (it won't show up until you have created the .pak file for it). I can click on Install to enable use of the smileys in that pack.

If I click on List at the top of the page, I will see the Calvin smileys.

Calvin Smileys Imported

I can see the yelling Calvin emoticon on the left. I see :calvin_yell: listed as an acronym and the description is "Calvin Yell" with the Category listed as "Calvin". If you don't see pictures with any of the emoticons, make sure you haven't misspelled the file name. If you have misspelled one of the file names, correct the misspelling; you may have to click on Import, select Uninstall for the smiley pack and then click on Install to reinstall it

Download Calvin Smiley Pack for Drupal
View Calvin Smiley Pack emoticons


  1. Adding Smiley Packs to Drupal
    Date: March 15, 2009
    MoonPoint Support
  2. Smileys Module for Drupal
    Date: March 15, 2009
    MoonPoint Support
  3. Smileys
    Drupal Modules - Search, Rate, and Review Drupal Modules

[/network/web/cms/drupal] permanent link

Sun, Mar 15, 2009 9:26 pm

Adding Smiley Packs to Drupal

If you wish to add additional smileys, aka emoticons, to Drupal, you can do so in a fairly straightforward way (note: these steps have been tested on Drupal version 6, so may not work on other versions).

First you need to have downloaded, installed, and enabled the smileys module. If you haven't already done so, you can use the instructions at Smileys Module for Drupal to do so.

Once you've enabled smiley support, download the smiley pack that you wish to use. In this example, I'm going to use the animatedFUN pack available from Smiley Packs ( phpBB pak packages) for Drupal.

I moved the zip file I downloaded in this case to the modules/smileys/packs directory beneath the directory where Drupal is installed on the website. I then unzipped it. This particular zip file created a __MACOSX subdirectory as well, which isn't needed, so I deleted it.

# unzip
# rm -f --recursive __MACOSX/animatedFUN/
# rmdir __MACOSX
# ls animatedFUN/
animatedFUN.pak       give.gif         iloveyou.gif          respect.gif
attention.gif         happy.gif        Iloveyou-marquee.gif  rose.gif
cat_angry.gif         hellowoman.gif   nihao.gif             shotgun.gif
cordialgreetings.gif  hugsnkisses.gif  no.gif                threat.gif
dog_exiting.gif       iamcrying.gif    read.gif

Once the smiley pack is extracted to a modules/smileys/packs directory, you can take the following steps:

  1. Click on Administer
  2. Click on Site configuration.
  3. Click on Smileys.
  4. Click on Import, which appears near the top of the page.

    Import Smiley Pack into Drupal

  5. Locate the Smiley Pack you wish to import and then click on Install. Under the Operations column, the status of the pack should change from "Install" to "Uninstall", indicating the pack has been successfully installed.

If you then click on Administer, Site configuration, and Smileys, you should see the new smiley pack smileys displayed.

Import Smiley Pack into Drupal

If you decide that you don't really like the smiley pack you've installed and want to remove it, take the following steps:

  1. Click on Administer
  2. Click on Site configuration.
  3. Click on Smileys.
  4. Click on Import, which appears near the top of the page.
  5. Click on Uninstall next to the smiley pack you wish to uninstall. Its status should change to "Install".


  1. Smileys Module for Drupal
    MoonPoint Support
  2. Smiley Packs (phpBB pak packages) for Drupal
    By: Gurpartap Singh | jack of everything, master of none

[/network/web/cms/drupal] permanent link

Sun, Mar 15, 2009 8:52 pm

Using Avatars in a Drupal Forum

To allow the use of avatars, which Drupal refers to as "user pictures" in a Drupal forum and elsewhere, take these steps.

[/network/web/cms/drupal] permanent link

Sun, Mar 15, 2009 5:12 pm

Smileys Module for Drupal

To add smileys, aka emoticons to Drupal, I downloaded a smileys module from the Drupal website at Smileys. The module poster provides the following information for it:

A filter that substitutes ASCII smileys with images. Also known as Emoticons, Smilies, Icons.

The package includes phpBB smileys pack import/export module. I'm maintaining a page for Smiley packs at: Create an issue if you want to host your own pack; or you may comment with the link over there.

Since I had Drupal version 6 on the webserver where I wanted to use them, I downloaded the version 6 filter. I unzipped and untarred the contents of the file I downloaded in the /tmp directory on the system.

# gunzip smileys-6.x-1.0-alpha5.tar.gz
# tar -xvf smileys-6.x-1.0-alpha5.tar
At the tar -xvf step a smileys directory is created. I then copied that directory to the modules directory beneath the directory where Drupal was installed.
# cp --recursive /tmp/smileys .

I then logged into Drupal as the administrator for the site, selected Administer, Site Building, then Modules. Under Core - required, I now saw Smileys. I clicked on Smileys, then enabled Smileys and Smileys Import. I then clicked on Save Configuration.

X Smileys 6.x-1.0-alpha5 Replaces smileys inside posts with images.
Required by: Smileys Import enabled)
X Smileys
6.x-1.0-alpha5 Import Smiley packages.
Depends on: Smileys enabled)

I then clicked on Administer, Site Configuration, and Smileys. I could then see 40 emoticons. I clicked on Settings at the top of the page. I enabled smileys for Nodes and Comments and on the following node types:

Blog entry
Book page
Forum topic

I left "expand select-box fieldset by default", "enable smileys dialog window", and "enable titles in dialog window" checked and clicked on Save Configuration.

I then went to Administer, Site configurationand Input formats. The default format ws "Filtered HTML". I clicked on Configure for it. Under the "Filters" section, I clicked on Smileys to enable the filter to replace smileys inside posts with images. I then clicked on Save configuration.

At that point someone making a posting to a forum would be able to type ;) and have the wink.png image Wink Emoticon appear in the posting in place of the ;) when the posting is previewed or saved.

But it would be nice to give users the option of viewing the available emoticons and selecting the one they want just by clicking on it. To make the list of available emoticons visible, click on Administer, select User management, then Permissions. Then in the Smileys section of the permissions webpage, check "use smiley select box" for "anonymous user" and/or "authenticated user". Click on Save Permissions to save the change.

After taking the steps above, when I then edited a forum entry that I had already posted, I was able to pick a smiley for the posting by clicking on it. I saw :) appear in the posting when I clicked on the smiley. But when I clicked on Preview, I saw the smiley image appear in the posting.

Download Smiley Module

Drupal - modules for Drupal versions 5 and 6
MoonPoint - 6.x-1.0-alpha5 (January 5, 2009)

[/network/web/cms/drupal] permanent link

Sun, Mar 15, 2009 1:58 pm

Drupal 6 on Linux

I installed Drupal 6 on a Linux server. I encountered some problems during the setup process, so I've documented my steps here, so that I can more easily accomplish the setup process for future installations and should anyone else encounter similar problems.

[/network/web/cms/drupal] permanent link

Sun, Mar 15, 2009 11:24 am

List of Number-One Hits

If you want to know what song was number one in the U.S. on a particular day, such as the day you were born, check List of number-one hits (United States) on Wikipedia.

Note: for dates from 1940 up through 1957, you can view a list of number-one songs in the United States during the year according to Billboard magazine. Prior to the creation of the Hot 100, Billboard published multiple singles charts each week. In 1957, the following four charts were produced:

NOTE: Billboard changed its issue dates from a Saturday to a Monday schedule on April 29, thus causing a one-week inconsistency.

[/music] permanent link

Sat, Mar 14, 2009 10:51 am


Sometimes you may have an old piece of equipment that has no information on it identifying the manufacturer. If it has an FCC ID on it, you can query the FCC's database to obtain information on the manufacturer.

For instance I have an old hub with a model number of EZHub9. I couldn't find any information on the manufacturer by doing a Google or Live Search on the model number. There was an FCC ID, KFYPEH9, listed on the bottom of the device. I went to the FCC Equipment Authorization Search page and put the first 3 characters, KFY, of the ID in the Grantee Code field and the remaining characters PEH9 in the product code page. Nothing was found when I performed the search on that FCC ID, but when I searched just on the grantee code, KFY, I found the company was Runtop, Inc., a Taiwanese company. I also found a product listed for the company with a similar model number, KFYPEH5.

Applicant NameAddressCityState CountryZipFCC IDApplication Purpose Grant Date
Runtop Inc1, Ln. 21, Hsin Hua Rd. Kueishan Industry Park Taoyuan CityN/ATaiwanN/AKFYPEH5 Original Equipment10/12/1995

[/hardware/identification] permanent link

Tue, Mar 10, 2009 10:52 pm

Adding PuTTY and Firefox Plugins to BartPE

I've started writing up steps to add plugins I find useful to a Bart's Preinstalled Environment (BartPE) bootable live windows CD/DVD.


[/os/windows/utilities/diagnostic/bartpe/plugins] permanent link

Tue, Mar 10, 2009 10:42 pm

Adding a MIME Type for Cab Files to Apache

I placed a .cab file on the website for downloading, but I found that, when I clicked on it, I got a screen full of garbled text, rather than being presented with the option to download it. I fixed the problem by adding another MIME type to the Apache webserver configuration file, httpd.conf file. I edited /etc/httpd/conf/httpd.conf and added an AddType line for the .acs file extension.
# AddType allows you to add to or override the MIME configuration
# file mime.types for specific file types.
#AddType application/x-tar .tgz
AddType application/octet-stream .cab

I then restarted the Apache webserver with apachectl restart. When I visited the URL again, I was prompted as to whether I wanted to download the file.


  1. Adding Another MIME Type to Apache
    MoonPoint Support
  2. Apache Module mod_mime
    The Apache Server Project
  3. Help: Unable to serve XBAP from Apache?
    Posted: August 29, 2006
    Vista Forums

[/network/web/server/apache] permanent link

Mon, Mar 09, 2009 9:19 pm

MapQuest Maps Won't Display in Netscape 7.2

A user complained that he could no longer obtain directions using MapQuest. He uses Netscape 7.2 as his default browser. When I checked the Netscape browser on his system, I found that instead of a local map displaying at the main MapQuest page, there was just a large empty box displayed. And clicking on "directions" produced a page with a large blank area and no discernible way to search for directions. I checked the configuration of Netscape, but found nothing amiss. The browser had a recent version of Flash installed, version 9. I verified it was configured for JavaScript support. Since I had Netscape 7.2 installed on one of my laptops, I tried accessing the MapQuest site from that system. I experienced the same problem.

When I checked MapQuest's Configuring Your Browser for MapQuest page, I didn't see configuration information listed for Netscape nor was Netscape listed on its Browsers and operating system MapQuest supports page.

Since I couldn't find a way to use MapQuest with Netscape, but someone else who used the system had already installed Firefox 3.0.6, I tried viewing the site with Firefox. I didn't have any problems using the site with that browser, so I put a shortcut on his desktop to take him to the site using Firefox, since that seemed the option to which he could most readily adjust, since he uses Netscape for his email as well as web browsing.

[/network/web/browser/netscape] permanent link

Sun, Mar 08, 2009 10:30 pm

Debugging a Minidump Dump File for a Stop 0xC2 Error

While trying to reinstall Windows on a Dell Dimension 2400 PC, I kept getting a "BAD_POOL_CALLER" BSOD with a "STOP: 0x000000C2" error. When I checked the minidump crash dump files created when the BSOD's occurred with Microsoft's WinDbg utility, it appeared they were linked to a modem driver file.

[ More Info ]

[/os/windows/debugging] permanent link

Sun, Mar 08, 2009 1:49 pm

Installing and Configuring MySQL on a Linux System

MySQL is free Database Management System (DBMS) software that runs on a variety of platforms, including Microsoft Windows, Linux, and Unix. To install and configure the software on a Linux system, so that it starts when the system boots follow these instructions. It is important to set a root password after you've started the MySQL daemon, so be sure to do so.

Once you have the software installed and configured, you can set up a new database using the instructions in Creating a MySQL Database.

[/software/database/mysql] permanent link

Fri, Mar 06, 2009 8:20 pm

Centering a Div

One of the many ways in which Firefox, Netscape, Internet Explorer, and other browsers interpret the same HTML code differently is when margin: auto is used to center a block on a webpage, such as a div section. Adding margin: auto to the style definition for a block will result in the block being centered when viewed in Firefox or Netscape, but it isn't sufficient to result in the display of a centered block in Internet Explorer. To have the block centered in Internet Explorer, you have to also add text-align: center to the style definition of the body tag.

[ More Info ]

[/network/web/html] permanent link

Fri, Mar 06, 2009 5:57 pm

Group Membership Under Unix/Linux

To see the groups to which an account belongs, you can use the command groups
# groups jsmith
staff code210

To place an account in an additional group, you can use the command usermod --groups newgroup account.

# usermod jsmith programmers


  1. Managing Group Access on Linux and Unix

[/os/unix/commands] permanent link

Mon, Mar 02, 2009 7:04 pm

Slipstreaming XP SP 3 with nLite

If you need to reinstall Windows XP on a system, it is very time consuming to have to install the operating system and then, when that process is completed, install the latest service pack and other updates for the operating system. The process is certainly much faster, if the XP installation CD you have on hand already incorporates the latest service pack. But chances are that installation CD is for the original version of XP before any service pack was released, or incoporates a prior service pack version, e.g. the installation CD may be for Windows XP Professional Service Pack 2, while Service Pack 3 is the current service pack version.

There is a way to create a new installation CD that incorporates the latest service pack into the version that came on your installation CD. The process is called "slipstreaming". There are various tools to help you create a slipstream disc; nLite, is one such tool. For instructions on how to use nLite for such a purpose, see Slipstreaming XP SP 3 with nLite.

[/os/windows/xp/slipstream] permanent link

Sun, Mar 01, 2009 9:37 pm

SoundManager 2

While looking for a method to associate sounds with links on a webpage for someone who wanted to have visitors to her website hear sounds of pages turning when they clicked on left and right arrows on the webpages, I came across SoundManager 2, which uses JavaScript and Flash to provide a method for playing sounds when someone clicks on an image, moves a mouse over it etc. The software was developed by Scott Schiller and is free.

[/network/web/browser/javascript] permanent link

Once You Know, You Newegg AliExpress by

Shop Amazon Local - Subscribe to Deals in Your Neighborhood

Valid HTML 4.01 Transitional

Privacy Policy   Contact

Blosxom logo