Bluetooth Tethering for Blackberry 8830

I feel stupid today… I finally got around to setting up my Bluetooth and Blackberry connection. I have a IBM Thinkpad T43 what does not come with built in Bluetooth transmitter. So, I found a Zoom USB Bluetooth adapter for 19 bucks at Microcenter and plugged it in. Bam installed no fuss no drivers needed.

For years I have been tethering my Laptops to my Blackberry’s with a USB cable because I thought that was the only way that was supported (worked). Not so. I thought this because I had tried with an earlier version of the Blackberry and the DUN was disabled. Well, the 8830 is apparently turned on and I was able to connect using the following setup:

Install IBM ThinkPad USB Software 7jba10ww.exe from Lenovo site. 100+MB. I then plugged in my Zoom Bluetooth adapter and paired my devices. You have to goto BB first and say pair, put in passcode which can be anything, then enter that same passcode on the Laptop. Enable Dialup Networking Service in BlueTooth Config.

Once everything is paired, you just need to add a Dialup connection using the Blackberry DUN.

Control Panel / Network Connections / Add new connection / Dialup

phone number = #777
user = [email protected]
pw = vzw

That’s it. I guess it pays to to a little digging.

8703e Blackberry Tethering with Ubuntu 8.10 (Verizon)

[ad#header]Wow, this was a good one, kept me going for a good 2 days!  So I’ve been using the VZAccess software for Windows for some time now and it’s pretty solid. The operating system however is not, so I’ve loaded Ubuntu 8.10 on my Lenovo Thinkpad T400. This kernel had the Wireless capabilities I needed. So let’s get to it:

First make sure you have all these packages from SPM

libtool autoconf automake cvs libglib2.0-dev libxml2-dev libssl-dev libopensync0-dev libxt-dev x11proto-print-dev libxmu-dev libxft-dev libfreetype6-dev libXp-dev flex byacc libgd2-xpm-dev libc6-dev g++ gcc make build-essential libxaw7-dev

Next you need to download the following packages:

openmotif-2.3.0.tar.gz

configure, make, make install

Xlt-13.0.13.gz

configure, make, make install

xmblackberry-0.3.0.gz

configure, make, make install

Then you need to create the communication scripts

/etc/chatscripts/blackberry
with the contents;

ABORT BUSY ABORT ‘NO CARRIER’ ABORT VOICE ABORT ‘NO DIALTONE’ ABORT ‘NO DIAL TONE’ ABORT ‘NO ANSWER’ ABORT DELAYED ABORT ERROR
SAY “Initializingn”
” ATZ
OK-AT-OK ATDT#777
CONNECT dc

And then
/etc/ppp/peers/blackberry
with,

debug debug debug
nodetach
/dev/pts/1
115200
connect “/usr/sbin/chat -f /etc/chatscripts/blackberry”
nomultilink
defaultroute
noipdefault
ipcp-restart 7
ipcp-accept-local
ipcp-accept-remote
# added this, so that it doesn’t disconnect after few mn of innactivity
lcp-echo-interval 0
lcp-echo-failure 999
modem
noauth
nocrtscts
noipdefault
novj # refused anyway, no point in trying every time
usepeerdns
user [email protected]
password Your10digitnumber

(*The /dev/pts/1 from above depends on what device you Blackberry is connecting to. This is displayed when you successfully run the XmBlackberry for the first time)

To be continued….

DSEE 6.3 Windows Server 2003 Installation

DSEE 6.2 Windows Server 2003 Installation Notes

DSEE 6.2 Windows Server 2003 Installation Notes

Obtain the zip file from here

  1. Unpack the DSEE6.2 zip file… c:TempDSEE62 using folder names
  2. c:TempDSEE62dsee_deploy install –install-path c:DSEE62 –no-inter
  3. C:DSEE62ds6bin>dsadm create -p 44444 -P 44445 c:DSEE62sedemo
    Choose the Directory Manager password:
    Confirm the Directory Manager password:
    Use ‘dsadm start ‘c:DSEE62sedemo” to start the instance
  4. C:DSEE62ds6bin>dsadm start c:DSEE62sedemo
    Waiting for server to start…
    Waiting for server to start…
    Server started: pid=8132
  5. C:DSEE62ds6bin>dsadm stop c:DSEE62sedemo
    Server stopped
  6. C:DSEE62ds6bin>dsadm enable-service –type WIN_SERVICE c:DSEE62sedemo
    Instance c:/DSEE62/sedemo registered in WIN_SERVICE
  7. Deploy the DSCC
    Stop Tomcat
    Copy C:DSEE62vardscc6dscc.war to Tomcats webapps folder
    Start Tomcat
  8. C:DSEE62dscc6bin>dsccsetup initialize
    ***
    DSCC Application cannot be registered because it is not installed
    ***
    DSCC Agent is already registered
    ***
    Choose password for Directory Service Manager:
    Confirm password for Directory Service Manager:
    Creating DSCC registry…
    DSCC Registry has been created successfully
    ***
  9. C:DSEE62dscc6bin>dsccreg add-server -d SEDemo_Directory c:DSEE62sedemo
    Enter DSCC administrator’s password:
    c:DSEE62sedemo is an instance of DS
    Enter password of “cn=Directory Manager” for c:DSEE62sedemo:
    Enter password of “cn=Directory Manager” for c:DSEE62sedemo:This operation will restart c:DSEE62
    sedemo.
    Do you want to continue ? (y/n) y
    Starting c:/DSEE62/sedemo
    Connecting to c:/DSEE62/sedemo
    Enabling DSCC access to c:/DSEE62/sedemo
    Restarting c:/DSEE62/sedemo
    Registering c:/DSEE62/sedemo in DSCC on localhost.

Trac Installation with Postgresql

Multiple Jboss Instances on one server

This works for JBOSS 4.0.5.GA! hopefully, it will work on some other versions. The important thing is to change the port number for the services you are running in your application – http, rmi, jndi, Webservice e.t.c. You will find these in the following xml files -All xml are in the server directory JBOSS.

Leave the first instance of your JBoss unchanged. In the 2nd instance, for example, update the xml files as described below:

…<jboss folder>…/server/default/deploy/jbossweb-tomcat55.sar/server.xml:
update 8080 to 18080

…<jboss folder>…/server/default/conf/jboss-service.xml:
update 1099 to 11099
update 1098 to 11098
update 4445 to 14445
update 4444 to 14444

…<jboss folder>…/server/default/conf/jboss-minimal.xml:
update 1099 to 11099
update 1098 to 11098
…<jboss folder>…/server/default/deploy/jms/uil2-service.xml – update 8093 to 18093

…<jboss folder>…/server/default/conf/jboss-service.xml – update 8083 to 18083