How did I add scroll functionality for my mouse?

Again about my Solaris 10 x86, this time is about my mouse, an optical Logitech mouse. I can't scroll webpages with it!
I've configured it by adding package I found by searching google. But it didn't help. My mouse still can't scroll webpages!
Finally, I recognized that Solaris 10 x86 is using XSun by default, but it also has Xorg. Then I decided to switch to Xorg, which to me it supports better devices. ( At least than XSun :) )
I did these following steps:
#kdmconfig //choose Xorg
#/usr/bin/X11/Xorg -configure //configure it, then you'll have a sample configuration file for Xorg in your $HOME dir
and then edit file $HOME/xorg.conf.new, and what I did was change "InputDevice" Section :
----xorg.conf.new-----
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/kdmouse"
Option "Emulate3Buttons" "false"
Option "ZAxisMapping" "4 5"
EndSection
----xorg.conf.new-----
You can test your new configuration file to sure it can run smoothly with:
#/usr/bin/X11/X -xf86config $HOME/xorg.conf.new
Final test is copy it to /etc/X11/xorg.conf:
#cp $HOME/xorg.conf.new /etc/X11/xorg.conf
Hope this helps somebody.
Please comment this blog if something is wrong!

Gimp2.0 in JDS 3, Solaris 10 x86 seems to be lost!

I saw in the Desktop Overview document included by default with Solaris 10 x86 that it says "Graphics Menu" has Image Editor (that is Gimp 2.0) with description "GNU Image Manipulation Program that enables you to edit images". But when opened the Graphics Menu from Launch/Applications/Graphics, I didn't see Image Editor item there.
I've read the JDS 3 Documentation, there says that is a bug with JDS 3, and gives me a work-arround:
Edit the file /usr/share/applications/gimp-2.0.desktop and change the TryExec, Exec lines to:
TryExec=/bin/gimp2.0
Exec=/bin/gimp-remote-2.0 %u
And oops, it appears magically in Launch/Applications/Graphics menu.

Problem login with Java Desktop System, Release 3 on Solaris 10 x86

According to my project in the laboratory I seem to have to switch to use Solaris, because I have to work on portlets in Sun One Portal Server. My guider decided that I have to work with Sun One Portal Server in Solaris.
So I installed Solaris 10 x86, which comes with JDS 3. It looks so great, +1 to Solaris guys. But I soon encountered a problem with login into JDS 3: when I logined, I usually received such error messages:
"There was a problem registering the panel with the bonono-activation server.
The error code is: 3.
The panel will now exit"
and
"Nautilus can't be used now, due to unexcepted error from Bonono when attempting to register the file manager view server."
And then I can't use my JDS 3, the screen was freezing!
I've asked people in newsgroup comp.unix.solaris, but I solved that problem before receiving the solutions.
That is I have to delete all file in directory /var/tmp, then everything becomes normal again! Yeah!
But I also received a good solution from comp.unix.solaris which helps me get out of this problem forever :)
Just change the evironment variable TMPDIR to /tmp :
Add this line to the file ~/.dtprofile:
export TMPDIR=/tmp

Integrate IL Disassembler into VS.NET 2003

I've read this tip on Weblog C# FAQ at http://blogs.msdn.com/csharpfaq/rss.aspx (RSS-2.0), and think it's useful:
"VS .NET allows you to add any number of external tools to the Tools menu. One very helpful technique is to configure ildasm.exe to automatically load up the current assembly being compiled. While VS .NET 2003 sets this up automatically, VS .NET 2002 may update the Tools menu manually. To do so, activate the Tools -> External Tools menu item. The 'Title' edit field allows you to supply the display name of your new menu item. In the 'Command' filed, type in the path to ildasm.exe (for example, C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\Bin\ildasm.exe). Finally, and most importantly, be sure to specify $(TargetPath) in the 'Arguments' field. Once you have done so, you can simply activate this menu item and the assembly under development will automatically be loaded into ildasm.exe."