sgiitk

Right now it is first Gen - so high prices, long term reliability a ? This is why I said wait for a couple of generations.

The future will be LED. However, wait for another generation to come before taking the plunge. CRT is obsolescent - the biggest problem is distortion esp. as the set ages. LC v Plasma :Plasma is brighter and having more contrast. But is real terms in a normal room (as against a dark room) any contrast about 5000 is irrelevant. Plasma has a faster response (however whether the eye can respond is a moot point), and Plasma has a life on only about 5 years. I was quite happy with Cable. Replaced my CRT TV (Sony > Samsung, after 10 years on the former). Suddenly the picture became bad. Got Satellite. The image quality forced me to go to LCD.

I wonder whether RGSM is just a bargaining ploy for negotiating with Qualcomm.

There are some questions which come to mind : 1. What is going to be the modus operandi of switching from CDMA to GSM and vice versa for existing subscribers. Issues in addition to tariff will be number portability/change, etc. This is prompted by two reasons: much better selection is GSM handsets than in CDMA units (esp. Nokia). 2. Will the GSM network support Edge etc? 3. In terms of coverage how does the GSM network compare with the CDMA network?

Looks very interesting. How is the User Interface. I had the original DAPO from Samsung. Interface was not too bad. Then I switched to a colour LG, again a reliance Offer. I found the user interface a 'pain in the ...'. Sold it and got a nokia (3125?) and now have a 6275. How is the user interface vis a vis Nokia. My usage is almost totally Phone & sms.

Did you put the same files, as befoe on. If so then there may be a bug or something in one of the files. To find the bad file proceed as follows. If the number of files is small put them in one at a time and check. If the number is large then you can save time and effort by using a 'binary search'. Here you put in half the files. If the unit behaves than this half is Ok. Put in a half of the remainder, and so on until you find the culprit. If it does not behave with the first half then you clear the card and load 1/4 (half of half). This way you will find the bad file very fast. For 1000 files you will need only 10 trials!

Till recently there was no CDMA Blackberry. So looking at all the talk of old models ... have RIM achieved the ultimate miracle - CDMA on a GSM phone?! On the Web I see 7130e and 7250 as CDMA Blackberry's.

My own experience shows that the standby life is about 4-5 days before a recharge. However, when I just got the phone it was barely a day and a half, so obviously the story that the battery takes some time to 'come up' is probably true. I have had the phone for almost four weeks. I see no straight reason as to why has Nokia reduced the charging capacity of the charger. Older phones were also using BL6C so I do not buy the story that the a higher charging rate will be harsh on the battery. Is it simply Nokia saving a few paise/cents/euros or whatever by providing a smaller capacity charger?

and... when will that happen? All the news of Reliance going GSM have faded from the past many weeks. I thought that the GSM thing was a red herring just to drive a had bargain with Qualcomm.

I would seriousy look only at cameras which use standard cells - say AA. Otherwise two or three years down to line when your battery runs out you may not be able to find a new one. With standard cells you will always be able to find the AA (or whatever) in the market. Driver compatibility does not bug me since you can just take the memory card out, and plug it into your computer. Most laptops have these adapters built-in, otherwise you can buy one for about 200 rupees. We have been particularly fond of Canon since we find their picture quality is probably the best. As for the MP part we are in a world of overkill. To get an excellent A4 printout you need about 3MP. Say add another MP for cropping etc. This takes you to 4MP. Thus unless you are seriously planning large poster sized prints anything above this is irrelevant. Any decent camera today has 5MP or more. I find most people with 6 or 7MP cameras running them in lower resolution modes to conserve memory. At 4MP a full resolution picture (jpg) takes just over 2MB. What I find desirable is a minimum optical zoom of 3X. zoom ranges of 10x or 12x may again be more for marketing. These often have small maximum apertures. Also, my experience with film cameras suggests that very long zoom ranges require large 'nose extensions'. These lead to more flexure (and hence failure) of the wiring inside the lens. Zoom ranges of much over 5X only invites camera shake unless you have a very steady perch or use a tripod.

12VDC 0.5A from a car should be a cinch. Please check what you get from the wall charger. As far as I know these are nothing more than a transformer + rectifier + filter. I would suspect that you are should be getting something like 16-18V (12 x root 2). Teh phone should then be happy with a nominal 12V supply. If this is the case then you need nothing more than a wire (with a filter) to plug into the car power (say a cigarette lighter) and with a suitable jack for the phone. You find that the car voltage will be in the 13.5 to 14.5V region. If it is 12VAC then it is a different story.

I had a similar experience a couple of years ago. Since then I have done some research and will like to report the following regarding the DKU5: 1. The new Nokia PC Suite does not support DKU5. However, I have managed th run Synchronise with not much trouble. Other things do not work. This was true for both the 3120 (GSM) & 3125 (CDMA). You cannot access Images, Messages, etc. 2. The problem with the 'mandi' cables is in the software. I had a similar experience and ended up returning the cable. The chips used for these are not Nokia standard. 3. You need to get the Nokia drivers (DKU5 for me) as well as the driver for the particular cable adapter chip. Many DKU5 clones use the Prolific 8303 chip. You can search for the Prolific Driver from their site and download it. It is bigger than 500kB so I cannot upload it. 4. Install the Prolific Driver, the Nokia DKU5 driver and the PC Suite. 5. You should be able to now run. One problem is the port assigned to the Prolific based cable. I find it from the Device Manager and then select it in 'Manage Connections'. Note that to run the Net browser you have to disconnect this link. 6. Prolific says that for Vista you contact the cable vendor. However, following advice on another thread I have been able to run the cable and old driver in the compatibility mode with no problem whatsoever. What appears to be hapening is that fed up with the clones Nokia is withdrawing support for DKU5 (this is for phones which are essentially serial, and is a serial to USB converter) ), DKU2 (USB-USB) etc., and going over to the CAxx types. Now that I have migrated to Bluetooth I will probably forget all this in a very short while !

Why run RConnect at all? Use the manufacturers .inf file to set up the phone as a modem. I have Nokia 3125 with a (standard Chinese) Clone DKU-5. The clone uses a Prolific Chip and the prolific site says that they do not offer Vista drivers, and advise users to contact the cable manufacturer for Vsita support. Great if you know who the cable manufacturer is. Following advice on another thread I installed the Prolific Driver (I downloaded the latest XP driver) and then the Nokia DKU5 driver. Both these had to be installed in the compatibility mode. I also configured the phone as a modem by using the Nokia modem set up file, and installed it as a modem. Using #777 I was able to connect very easily. IE runs perfectly on this. InitiallyI did have a problem of disconnected IE sessions (the link was rock solid) and traced this to the 'Web to Print' of Epson which was obviously not for Vista. After removing this everything is fine. The moral is, try the compatibility mode Also, netconnect is huge as compared to setting up the modem using the phone modem configuration file. There are plenty of download meters on the web if you want to monitor the usage.

Further to my post. The 6226 is on Vista Home Premium. I will not look at a system without Bluetooth. I have a Nokia 3125 which I plan to replace with a 6275 just for this reason. I have recently 'inherited' a Nokia 6670 GSM and find Bluetooth a real boon. Also, DKU5's using Prolific chipset (as 90% of the Chinese ones costing ~Rs.150-200 are) are not supported by Vista. After suggestions on another thread I was able to install the old drivers but the performance is patchy at best. While I am able to do a backup other features do not work or at best work intermittently. The latest PC Suite may not be supporting DKU5. Of course you can buy a Bluetooth dongle for about Rs.250-300 and plug it in. It works (at least for XP) very well.

I bought a Compaq 3149 for my daughter, and then a Pavillion 6226 for my son. The former is Turion 64x2 - XP Media and the latter Core 2 Duo. The wise men have the opinion that the AMD is near (but not quite as good as) the Core 2 Duo. One other point - unless you have Vista the advantages of a dual core CPU are not available! Of course Linux usrs may have a different story.

You should also consider AMD Turin 64x2. This is better than Core Duo but somewhat inferior to Core 2 Duo. AMD systems tend to be far cheaper. The only negative point is that they are a bit more power hungry. If you are going for Vista then remember Home Premium or higher need at least 1GB RAM and a graphics card since 'flying windows' is otherwise not usable. As one will use a laptop for about 3 years one should look at Vista (warts and all). In about 2 years time XP is likely to be on the way out. I have a Vista system and the OS sort of grows on you with time. Consider a 3-year warranty since Laptops cost a bomb to get repaired. The additional cost for extending 1 year to 3-years is typically Rs.5-6k.

This looks like a sustainable and practical plan, and is more or less in line with my observations on another thread. 1. Base tariff goes up - covers the fixed costs.Not much hanky panky of covering one thing from the other. 2. Some free incoming roaming - essentially to justify the above. Then at Re.1 per minute - i.e. as per the standard STD tariff on the 1India plan. Good, I expect some fine tuning down the line - see my comment 1 below. 3. Outgoing tariffs essentially the same as the normal rates. Good, again as it should be. I hope this a precursor to the following on all plans 1. Incoming - equal to STD rate of your plan. There is no logic in beefing up the tariff and adding some free incoming! 2. Outgoing local & STD as per your outgoing rate.

A very large number of DKU5 cables are clones based on the Prolific 2303 Chip. Using them in WinXP was easy as long as you installed the Prolific Driver available from many locations, incl. the Prolific site. However, according to Prolific site they are not putting out Vista drivers for the chip and state that you contact your cable manufacturer. I do not thing most of us know or can find out as who this 'gumnaam' fellow is! Any work arounds or solutions?

I could not get it to go. It tried, failed as expected (non-Vista) and when I tried reinstalling it it came up with a message stating that the Nokia Modem is already installed. Should I delete it! I aborted here. I feel that bypassing R Connect and just setting up the Nokia 3125 as a modem may be a better idea. Then I can run the Modem through the IE. I understand that some settings may have to be changed, and (maybe) also the modem formally installed! On another thread I saw some additional startup string may have to be sent. Can anyone give the sequence of steps required.

Yes. It did work beautifully. I would never have guessed with all the noise to the contrary from Prolific. One other thing - can I use 'Connect to the Internet' from the Nokia Suite 6.83.14.1? If so how? Otherwise how do I connect to the net. Will the good old Rconnct work? Thanks

The compatibility mode is for software and not for the hardware/software interface, i.e. the drivers. Also, if this was indeed the case, one would have expected Prolific to say so, and not just sign off with such a strong statement. This hurts their (cable clone) market in a no uncertain manner. Will try it out nevertheless, even though I think the chances of it working are minimal.

Nokia had announced the CA-42 USB cable in the west about one year ago. Now looking at the support for the Nokia 3125 on the Reliance site it appears that Reliance now wants you to use the CA-42 for connectivity. It appears that the CA-42 is the 'proper' USB cable for the Nokia uinits which till now used the DKU-5. Looking at the Nokia India site one finds no information for data cable for 3125. For the sister GSM phone 3120 Nokia India still lists only the DKU-5. Searching for the CA-42 on Nokia site does give a lot of links with a connectivity table as well. Thus the information must be very new. Using my old DKU-5 (The 400 rupee Chinese clone, which can be identified by the funny expansion of the term USB on the box!) I was able to connect both the 3120 and the 3125 to the Nokia Suite, and transfer the phone book and images from the 3120 to the 3125. So obviously the DKU-5 still works. Do the RConnect drivers on the web work with the DKU-5 or are they exclusively CA-42 now? Where does one find the CA-42 and what does it cost?

This is news to me. The 3125 works with DKU5 / CA42 as it has a serial interface and not USB. Protocol conversion is necessary. I unerstand that DKU2 is pure USB!. I have used the 3125 and found it excellent in all respects. Gives 130kbps on the Net which is the maximum of CDMA using a cloned DKU5. But I must add I am partial to Nokia and have a 3120 GSM as well!

If this is the case then what do BNSL/MTNL do with their WLL customers? Dump them into the Arabian sea perhaps! Also, Reliance is shifting many fixed phones to copper as the density in locations increases and cables are laid. They want to sell them Broadband as well. Bharti in the early days (im MP) did the same. WLL units until they had enough conenctions etc. to make copper viable, and then switched the subscribers to wired lines. I hope BSNL learns that they are no longer a monopoly. Also, they should heed the discussion in parliament, telecast on some channels where Mr Ahluwalia stated : MTNL -> Mera telephone Nahin Lagta BSNL -> Bai Saheb Nahim Lagege. This I presume is in the records of the parliament.

"I successfully installed the CA-42 cable drivers...after which my laptop detected the Phone.. but when I tried installing R-Connect , first it install DKU5 Cable drivers & then goes for Modem Installation...but ..the setup stops for taking any action thereon...means it do not go ahead & install the modem...I tried this several times, but failed..." I think the problem is with RConnect Installing DKU5! You shoule be able to dial in using the dialler with the CA42/phone combo as the modem. I saw some discussion earlier (around September 2005) that you can use the PC Suite or for that matter any other tool for the connection and forget RConnect, which is a very big file. My sugegstion will be to remove RConnect/DKU5 driver, reinstall the CA42 driver, and then use the PC Suite from Nokia for the conenction. I would like to know how you get along since I am thinking of switching from a DKU5 (clone) to a CA42 soon.