Well,

this is some kind of a weird post, as it's not really a professional material.
We recently got a JATY Bluetooth Hands Free Kit for the car, Model JBHW-0310C.
No Manual, It got lost in the installation.

We tried to pair it with my Nokia mobile phone, but failed to make it "publish" itself in pairing mode.
Even when calling Cellcom support, and got redirected to their Internet support (*320),
They just told as that it will enter pairing mode when pressing the + button for a few seconds,
Which did not work.
I decided to search for the manual on the net, but failed to find it,
even in the Korean company itself.

I finally managed to find a hard copy manual, which solved the problems
(Pairing mode is started by pressing "Send" + "End" for 3 seconds.)
I decided to scan it and upload it here so the mighty Google will bring it to the next person who needs it.

Some relevant data regarding pairing from the manual:

*What is Pairing?
- Pairing is the process of establishing device addresses
and connection parameters for the devices so that they
automatically connect when required.
Pairing need only be done once for each device.
- So, before you use Bluetooth Car Kit, you must link it to your phone.
Once the Car Kit and phone are paired, the Car Kit will automatically connect to your phone
every time you start your vehicle or power.

Pairing and Connect the phone.
Before you use Handsfree Kit, you must link it to your phone.

1) Please press send and end button together for 3 seconds to go to pairing mode and than,
the pairing mode keep 60 Seconds.
2) Start pairing with your phone (refer to your phones manual)
3) Password for the pairing is "0000"

Example:
Note: These instructions may differ from your phone but will be the same process
(1) Put the Handsfree kit into Pairing mode as in section above.
(2) In your phone's Menu find Bluetooth and turn On.
(3) Search for a New Paired device.
(4) Select JBHW-G508" and enter password 0000'.
(5) Next select options for "JBHW-G508" and select Connect (Required for some phones only)

Auto Connection
1) When you turn on the Car Kit. Car kit will search for the last 3 devices.
It takes 6 second for each devices.
2) If auto connection fail, there will be a short beep sound.
3) If there's no paired information stored, Handsfree Kit will go to the Paring Mode.
4) If you press End button for 4 second, you call disconnect the phone from the Handsfree Kit.
Note: Some phone needs authorize for the auto connection.

Deleting Paired Devices

If your kit will not connect or if you pair using the wrong mode,
try deleting all stored paired information and then Re-Pair your devices.

1) Press and hold Volume Up(+) and Volume down(-) button for 5 seconds.
Note: You can pair the JBHW-G508 With up to 8 different phones.
ie... The JBHW-G508 can stove connection information for 8 devices,
but can connect with only one phone at a time.

The full manual can be downloaded here:
JBHW-0310C – PDF Format
JBHW-0310C – Zipped JPEGs

Eli.

Hi all,

About 3 months ago I was privileged to hear David S Platt's "Why Software Sucks" show.
During the show (Which is both interesting & fun!) David gave an example of Backup software,
telling the story about how his hard drive crashed with no updated backup…
This brought me to wonder …
When did I last back up all my latest photos, documents and PST to a DVD?
I really couldn't remember, which told me it's probably not too good…
David demonstrated some screenshots from Carbonite,
An online backup software he seems to admire, after using it for quite a while.
When I got home, I Googled for Carbonite, and found out that for less than 50$/year I can backup
all my data with no limitations…
At first I was a bit skeptic about the idea…
My backup size is above 25GB… but I decided to give it a try.
They give you 2 weeks of free trial, which is quite enough to feel it…
After 2 weeks I managed to backup over 10GB of data in low bandwidth priority
over a 1.5Mb/128Kb line …
I decided to subscribe.



Now, 3 months after, I can say I am very happy!
All my documents, photos, mail & even my home videos are regularly backed up without
needing to do much, and I am now over 27GB!
I was impressed that during this time Carbonite never crashed or gave me trouble,
and even the Email support I got to use once for asking a question was prompt.

One thing I must say: If you have a large backup store like mine
(Most people don't in my opinion), bare a bit with the software until if finishes
the first upload… my suggestion is to let it run in full capacity during the night,
and in law priority when you are using the PC.
After the initial backup, only diffs are uploaded, even if the files are in use (like a PST)
which is not noticeable.
It's even better then a DVD, as the data is stored many miles away,
which is like a nice data DRP backup site…

There are other similar solutions over the internet, in different levels,
Starting with Mozy, and even Amazon's S3, but this was the cheapest service
I could find for large backup stores (Over 2 GB) which is both friendly & simple.

If you want to give it a try, you can use this referral link.
If you get to purchase a subscription after the trial like I did, you will get an extra month bonus
period and me too J

Eli.

Hi,

Lately we ran into a weird problem when using Enterprise Library 3.1 in the Intranet environment,
Where Internet connection is not available.

The symptom was a slow loading of the referenced assemblies during the application startup.
We managed to reproduce the problem using a simple console application:

________________________________________________________________________________________________

using System;
using System.Diagnostics;
using System.Collections.Generic;
using System.Text;

namespace TestCrlSample
{
class Program
    {
        staticvoid Main(string[] args)
    {
        Console.WriteLine("Started at:" + DateTime.Now.ToString());
        Debug.WriteLine("Started at:" + DateTime.Now.ToString());

        Stopwatch sw = new Stopwatch();
        sw.Start();
        DoSignedLibWork();
        sw.Stop();

        Console.WriteLine("Total Time elapsed(Milliseconds):" + sw.ElapsedMilliseconds);
        Console.WriteLine("Ended at:" + DateTime.Now.ToString());
        Debug.WriteLine("Ended at:" + DateTime.Now.ToString());
        Console.WriteLine("Press any key to exit...");

        Console.ReadLine();
}

    publicstaticvoid DoSignedLibWork()
    {
        Console.WriteLine("Before Work at:" + DateTime.Now.ToString());
        Debug.WriteLine("Before Work at:" + DateTime.Now.ToString());
        Microsoft.Practices.EnterpriseLibrary.Data.ConnectionString cs = new
Microsoft.Practices.EnterpriseLibrary.Data.ConnectionString("Data Source=DBSRV;Initial
         Catalog=Repository;Integrated Security=True", "Admin", "Bla");
        Console.WriteLine("After Work at:" + DateTime.Now.ToString());
        Debug.WriteLine("After Work at:" + DateTime.Now.ToString());
    }

    }
}

________________________________________________________________________________________________

Here are some test results we got when diagnosing the problem:

Running the program as usual in an Intranet environment, no Internet connection at all:

___________________________
Started at:22/07/2007 18:16:47
Before Work at:22/07/2007 18:16:56
After Work at:22/07/2007 18:16:56
Total Time elapsed(Milliseconds):9234
Ended at:22/07/2007 18:16:56
Press any key to exit...
___________________________

Notice how long it took this simple program to run… almost 10 seconds !
We ran Microsoft Network Monitor during the test to check what's going on behind.

This is the Netmon output:

_____________________________________________________________________________________
111    5.019387        DNS    DNS: QueryId = 0xAEAE, QUERY (Standard query), Query for crl.microsoft.com of type Host Addr on class Internet
112    5.024270        DNS    DNS: QueryId = 0xAEAE, QUERY (Standard query), Response - Server failure
113    5.024270        DNS    DNS: QueryId = 0xAEAE, QUERY (Standard query), Query for crl.microsoft.com of type Host Addr on class Internet
123    6.024270        DNS    DNS: QueryId = 0xAEAE, QUERY (Standard query), Query for crl.microsoft.com of type Host Addr on class Internet
124    6.024270        DNS    DNS: QueryId = 0xAEAE, QUERY (Standard query), Response - Server failure
125    6.024270        DNS    DNS: QueryId = 0xAEAE, QUERY (Standard query), Query for crl.microsoft.com of type Host Addr on class Internet
126    6.024270        DNS    DNS: QueryId = 0xAEAE, QUERY (Standard query), Query for crl.microsoft.com of type Host Addr on class Internet
127    6.024270        DNS    DNS: QueryId = 0xAEAE, QUERY (Standard query), Query for crl.microsoft.com of type Host Addr on class Internet
128    6.024270        DNS    DNS: QueryId = 0xAEAE, QUERY (Standard query), Query for crl.microsoft.com of type Host Addr on class Internet
129    6.024270        DNS    DNS: QueryId = 0xAEAE, QUERY (Standard query), Response - Server failure
130    6.024270        DNS    DNS: QueryId = 0xAEAE, QUERY (Standard query), Response - Server failure
131    6.024270        DNS    DNS: QueryId = 0xAEAE, QUERY (Standard query), Response - Server failure
184    10.024270        DNS    DNS: QueryId = 0xAEAE, QUERY (Standard query), Query for crl.microsoft.com of type Host Addr on class Internet
227    14.025102        DNS    DNS: QueryId = 0xB6AF, QUERY (Standard query), Query for crl.microsoft.com.myorg.com of type Host Addr on class Internet
228    14.030961        DNS    DNS: QueryId = 0xB6AF, QUERY (Standard query), Response - Name Error
229    14.030961        DNS    DNS: QueryId = 0xBFAC, QUERY (Standard query), Query for crl.microsoft.com.myorg.com of type Host Addr on class Internet
230    14.035844        DNS    DNS: QueryId = 0xBFAC, QUERY (Standard query), Response - Name Error
_____________________________________________________________________________________

Notice how the DNS requests for "crl.microsoft.com" took almost 9 seconds !
This was very funny, so we googled for this symptom.

Internet research shows these results:

Support Certificates In Your Applications With The .NET Framework 2.0:
http://msdn.microsoft.com/msdnmag/issues/07/03/NETSecurity/default.aspx

Microsoft, VeriSign, and Certificate Revocation:
http://amug.org/~glguerin/opinion/revocation.html

How Office Performs Certificate Revocation:
http://office.microsoft.com/en-us/ork2003/HA011403081033.aspx

This one is talking about IE slowness:
http://www.wilderssecurity.com/archive/index.php/t-47121.html

Management Studio slowness:
http://weblogs.sqlteam.com/tarad/archive/2006/10/05/13676.aspx
http://blogs.msdn.com/dtjones/archive/2006/08/23/714738.aspx
talking about the similar symptoms, only when using MS SQL Management Studio.
The cause of the problem is the same…

FAQ, Why does SSMS take 45s to start up?
http://blogs.msdn.com/euanga/archive/2006/07/11/662053.aspx

Why does the .NET Runtime Optimization Service keep trying to use the internet:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=522726&SiteID=1

so, what have we got here?
It seems that Microsoft added a mechanism to the .Net CLR that checks every signed assembly when loading it
against an online revocation list.
When working in an intranet environment with IP segments
that are no defined as local Intranet, the mechanism is trying to locate the crl server for 9 seconds before it
gives up, delaying the assembly loading.

When checking the Enterprise Library Common assembly,
We see that is indeed signed using a Microsoft Certificate:



How do we work around it you say ?
Well, there are several options.
The easiest one is to disable the crl check. Oddly it is done from the Internet Options dialog available from Internet Explorer:



Now, let's run our test program again:

Running the program after removing the check:

__________________________
Started at:22/07/2007 18:17:47
Before Work at:22/07/2007 18:17:47
After Work at:22/07/2007 18:17:47
Total Time elapsed(Milliseconds):147
Ended at:22/07/2007 18:17:47
Press any key to exit...
__________________________

Notice that this time we are down to a total of 147 milliseconds, which is much more reasonable.
What about the netmon output ? Well, since there is no check
Netmon output is empty !

What about security you say?
If you are canceling the crl check, you are exposed to bogus certifications.
My answer to that is: If you are already disconnected from the Internet,
then you are just exposed as before, only this time you are not slowing down your applications for nothing.

A questions might be asked about situations where Internet connection is partly available through a firewall.
In this situation you might consider asking the network administrator to allow connections to the crl server,
Or if you which, make it fail the requests immediately, so you don't need to configure the Internet Options for every node.

Another optional workaround is to define the crl address in the etc/hosts file pointing it to localhost (127.0.0.1),
which will quickly fail every crl request it gets.

Let's run our test again, this time without removing the revocation check, but defining the crl address in the hosts file:

Running the program after redirecting the dns name to localhost:

___________________________
Started at:22/07/2007 18:18:37
Before Work at:22/07/2007 18:18:37
After Work at:22/07/2007 18:18:37
Total Time elapsed(Milliseconds):219
Ended at:22/07/2007 18:18:37
Press any key to exit...
___________________________

Notice that this time we are using 219 milliseconds, which is a bit more then the first workaround, but still reasonable.
What about the netmon output? Well, since there is no outside communication
Netmon output is empty in this case too!

Conclusion:

When working with signed assemblies having no Internet connection to crl.microsoft.com,
you need to consider the loading delay time for the assemblies, Or work around them as suggested above.

Good Luck,

Eli.

• Changes we made in order to make the code compile with no Errors or Warnings:
  • Major Changes:
    • The usage of XML Schemas has changed. The new framework uses a class called XmlSchemaSet which represents a collection of schemas which compile together to a single logical unit.
    • The usage of XML Readers has changed. The new framework makes the XmlValidatingReader obsolete. Instead, we now need to work directly with the XML Reader, supplying it with an object of type XmlReaderSettings which defines some attributes on the reader we have created.
    • Compile-time error identification of unmanaged resources usage problems. I must say we liked this new feature a lot. the new framework identifies in compile time bad usage of Finalizers and reports on it. We encountered only one instance of this case in the system and replaced it with a correct implementation. Coolness.
  • Minor Changes:
    • The Assembly signature method has changed. in CLR 1.1 we signed the Assemblies using the AssemblyKeyFile Attribute usually found in the AssemblyInfo.cs file. Instead, the new framework makes as use  Project Level definition. This is not so bad, only it was frustrating to change it manually to our 70 assemblies. in VS2003 we could select multiple projects and change a property for all of them at the same time. In 2005 The GUI did not let me select multiple projects for the Project properties dialog. I wonder why.
    • The usage of Path.InvalidPathChars was replaced with the Path.GetInvalidPathChars() method.
    • The Certificates usage was changed. The new framework defines a delegate method on ServicePointManager for Certificate validations instead of the class usage which replaces the standard behavior of the Certificates Control.
    • Form.AutoScaleBaseSize used to be an int value. In the new framework it was replaced with Form.AutoScaledimensions which is a float.
    • The AppDomain.GetCurrentThreadId() Method was replaced with CurrentThread.ManagedThreadID.
    • The SmtpMail class is now obsolete. there is a new class which replaces it. we decided to remove the entire code that uses SMTP which implemented special critical error log reporting using email, since we never used it in the past 3 years.
    • The Dns.GetHostName() method was replaced with Dns.GetHostEntry() method.
    • Parameter.Add() method was replaced with Parameter.AddWithValue() method.
• Changes due to runtime errors:
  • This is a new cool feature of the runtime. The new Framework identifies at runtime of objects trying to access  other objects from a Non GUI thread to a GUI Thread object without a proper Invoke. It throws a proper Exception. we identified only one case in the system (Bad code in the Client's Splash Screen). This is very cool, because such code can ofthen create random results, and hard to re-create bugs. Other instances of the problem might come up when the system will be sent to QA for a proper regression test.
  • Microsoft score again. Another cool feature ! The runtime now identifies inconsistencies between XSD Schemas of Datasets, against the real Database Types ! When the runtime encounters an inconsistency, it thrown an exception. The the system we encountered 2 instances of the problem, and the Schemas were corrected according o the DB Types. I guess it happened when someone changes the DB without changing the DAL Code properly.
• Changes made due to Unit Test Failures:
  • The new framework adds the `xml:space="preserve"` Attribute when it finds an empty node in the XML Document. We added the new attribute to the proper places in the XML files.
• Some Unresolved Issues we decided to let go for now:
  • The client application had a special mechanism that used a special "Home made" Semaphore ( CLR 1.1 didn't have a built in one, CLR 2.0 does). the implementation was bad and we knew it for some time now. it caused a some bugs in the GUI, but they were very rare. When running on CLR 2.0 for some reason the mechanism stopped working almost completely. We did not try to fix or search why, as the proper action here is to re-write the entire mechanism correctly.
  • The server Application started to load very slowly. Short investigation discovered that there is a problem the the Assemblies loading phase that causes some kind of a deadlock. The runtime releases the deadlock somehow after 20 seconds and everything goes on well. It's mainly annoying for debug time to wait these extra 30 seconds each time we start the server process...
  • The Client Splash Screen started to appear in the top left corner of the screen instead of the center. We didn't bother to check why for now.