在此祝贺一下.
其实已经超过1年了. 由于遭受黑客攻击, 大约有半年的日志全部没了.
在此也哀悼一下丢失的半年日志.
电话（手机）的“呼叫转移”功能可以很方便地将来电转移到另外一部电话（或手机）上，如果手机没电、外出时，可以设置呼叫转移，从而不漏掉任何重要的电话。设置前需要确认是否已经开通这项功能，另外呼叫转移是通话是要收费的，如果手机A转到B，呼叫A时，B接通，这时AB同时计费（如果B是固定电话、小灵通、或者被叫免费的手机套餐是不收费的），具体的标准可以询问服务商。下面是几种常见的电话呼叫转移设置方法：
(固定电话必须提前申请开通, 手机自动开通)
固定电话、小灵通
【无条件转移】设定：*57*电话号码# 取消：#57#
【无应答转移】设定：*41*电话号码# 取消：#41#
【遇忙转移】 设定：*40*电话号码# 取消：#40#
GSM手机
【无条件转移】设定：**21*电话号码# 取消：##21#
【无应答转移】设定：**61*电话号码# 取消：##61#
【遇忙转移】 设定：**67*电话号码# 取消：##67#
CDMA手机
【无条件转移】设定：*72电话号码 取消：*720
【无应答转移】设定：*92电话号码 取消：*920
【遇忙转移】 设定：*90电话号码 取消：*900
下午slough upgrade了一个nokia n70，今天的遭遇比较掺去winsor的o2店N70没货，然后跑到slough－o2的head office 居然2个o2店也都没货。咳不得已 跑到了phones4u签了个O2-500 头3个月double mins＋double texts 每个月35磅，免费拿了个40磅的蓝牙耳机。居然哪个人半强迫我take insurance 后来想想也就算了 于是弄了保险10磅1个月，manager被我说的最后拿出10磅cash 帮我交第一个月的保险钱。^_^
今天听到一个巨大的事情，singlepoint居然被vodafone收购了，于是在我印象中乱扣人钱的singlepoint终于消失，于是立马改变了平时对phones4u的看法和态度！（phones4u服务真的很不错，每次去签手机都很开心。 去年一项调查评出phone4u 英国服务最好的1个公司）现在phones4u里面签的o2和o2店里签的o2一摸一样，帐单直接从o2寄出来，信封上画着o2的商标。不像以前，所有的帐单都是singlepoint出来的。phones4u表扬它一下！promotion很多。
事态是会变的，眼光不能呆滞，人家变，你也要跟着变！
贴点N70照片吧，首先来张和盒子的合影
再来张单身照
最后一张，全聚德！
整个学校与外部连接的网络down掉了，从周六一直到周2凌晨一直不能上外部网，只能在学校内部网逛逛。
引用it director的话：
Update at 1300
There is still no Internet access at present and Information Services apologise for the on-going disruption that this is causing.
An engineer has been on site and the problem appears to now be with the physical connection between Royal Holloway and Park Royal (our gateway with the wider network). An engineer from BT is expected on site shortly. As yet, I am unable to provide a target resolution time.
The issue has been escalated internally within BT, Thus (the partner teleco) as well as to senior management at the London Metropolitan Network.
I will keep you informed of further developments.
Adrian Ellison
IT Director
Monday 5 December, 0900
Due to a failure of the network link that connects the College with the outside world, there is currently no access to the Internet. This means that you will not be able to access the Web nor receive incoming e-mail from outside of the College. Outgoing e-mail will be queued and delivered once service is restored. The outage also means that the College currently has no external web presence. Access to on-campus resources remains unaffected.
The link is provided by the London Metropolitan Network. Information Services personnel have been working with them over the weekend to get service restored as quickly as possible, We are due to have engineers on site early this morning and I will advise you of progress as soon as I have more information (please check the Intranet for further updates). At the moment, it may be some hours before service can be resumed.
I must apologise for the serious disruption that this outage has caused.
Adrian Ellison
IT Director
几个世纪没去central london shopping了，今天实在憋不住了！比较巧，在egham车站碰到同学，于是一起china town吃饭后剪完头发开始逛街。从regent street开始，到oxford street 到new bond street 然后到bond street得时候店已经关门了。可怜得，本来打算打开杀界狠狠干一场得，结果草草收场！
在regent street的apple店里，看到了传说中的ipod nano。哇，让我吃了一惊，这么小，这么薄，还彩色屏幕，太可爱了。喜欢，毫不犹豫地买了一个。可是这个不属于我，我也不怎么用MP3。就是在高中时买了个sony的超薄卡式机，大学买了个SONY MD N1。于是没事就拿出来听，后来被父母指责，说叼尔郎当。以后就再也没有碰有耳线的东西了！（手机除外）
Ipod Nano 还是不错滴，绝对是耳机族的首选！
升級你的Dopod 696 / O2 XDA2 to Windows Mobile 5 簡體中文版
很高興已經有人釋放WM5 的 ROM給 696 / XDA2 用了
ROM 請到這裡下載 http://buzzdev.net/index.p...
希望刷了之後的朋友,還請分享你的心得喔
P.S. 下載之前, 你可能要先注冊
Again, it was Mike Calligaro, who wrote this cool article, why there is no WM5 upgrade for this or that device.
I suggest you to read that one.
WM Team RSS feed
From msdn blogs:
Why Can't I Upgrade?We released Windows Mobile 5 a few months ago and devices are starting to hit the market now. A question I've seen asked in a number of places is, "Why can't I upgrade my existing WM 2003 SE devices to WM5?"
The answer is sure to get me a bunch of angry comments from people who abbreviate our name "M$." You can choose to see this as spin from a greedy marketing wonk, or you can see it for what it is--an honest attempt from a developer to explain how this stuff works.
Possible vs. Practical
Since 2002, we've set our hardware requirements and designed our software to make it possible to upgrade any PocketPC or Smartphone at least once. And there have been a number of devices that have upgraded from one version to the next. Also, some of our partners have announced that some of their WM 2003 SE devices will be upgraded to WM5. But, by and large, the number of devices that will upgrade is pretty small.
The trouble is, while it's possible to upgrade devices, it's often not practical to do so. The reason it's not practical boils down this:
1) It costs a lot of money to upgrade a device
2) So few people upgrade that it's hard to amortize this cost
Second things First
I know that it's frustrating to want to upgrade and hear me say, "But no one upgrades." Obviously you want to upgrade. You wouldn't be reading this if you didn't. And, I'll bet you know a bunch of people who want to upgrade as well. Please understand, the companies involved do not say, "Hey, let's not bother to upgrade the device. We won't piss off too many people." Everyone wants to upgrade your devices. There are a number of reasons for this, not the least of which is that we know that providing upgrades makes customers happy. And, yes, we all like happy customers.
It's not about figuring out how many people we can get away with annoying. Upgrades don't happen due to a much simpler calculation.
(Total cost of doing the upgrade) / (number of people who will use it) = (unreasonable price)
The value of "unreasonable price" varies from situation to situation. But there have been times where it was higher than the price of a new phone. Because there have been upgrades in the past, we know how many people do them. And, even though you know a bunch of people who want to upgrade, it's still a tiny percentage of the owners of that device.
Show me the Money
So what are all these costs? The first is the cost of developing and testing all the drivers for a new version of the OS. While Microsoft writes the bulk of the software on a WM device, a significant amount of it is written by the OEM or ODM who created the hardware. And the part they do is the most complicated part of the device: the drivers, parts of the kernel, and the radio stack. On major OS revisions, many of these parts need to be changed, sometimes dramatically. And, any time they need to be changed, extensive testing needs to be done.
Another cost is associated with phone devices sold through Mobile Operators. MOs rightfully want to be sure that any device on their network doesn't interfere with other devices on their network. To do this, they put every device they plan to sell through a battery of tests that last weeks. If a significant amount of code on the device changes, it needs to be retested. And that takes away testing time from another device. The Mobile Operator needs to make a conscious decision to test an upgrade that few people will use instead of testing a sexy new phone that potentially many more will buy.
Another cost comes from how difficult it is to upgrade these devices. The steps are complicated, there are changes that users don't expect, and sometimes it doesn't work. All of those situations result in calls to product support, which are really expensive. Yes, you're capable of pulling off the upgrade. But you're techy enough to be reading an MSDN site. How do you think your grandmother would fare?
Well, what are you doing about it?
In WM5 we spent a lot of time building an infrastructure for enabling updates that anyone can do. We're heading toward a Windows Update sort of experience, where you're using your phone and it suddenly pops up a box that says something like, "An update is available, would you like to have it installed?" Then you just need to select "Yes" and it'll happen for you. How much OEMs and Mobile Operators make use of this infrastructure is up to them, but it's there now. This should solve the "could your grandmother do it?" problem, especially for smaller updates like security fixes.
Of course, to do this, we had to change a ton of stuff, which makes the first two problems even bigger for this release. No pain, no gain.
We're doing a few things to make future updates easier for OEMs and Mobile Operators. First, we're going to try to do some smaller releases that don't require changes in OEM code. If the drivers don't need to change, then it's much easier for the OEM to take an update from us and make it work. The Mobile Operators will still want to test the device, but, hopefully, if the drivers didn't change, they can have some assurance that the things they worry most about didn't change either. That should make their testing easier.
Longer term, we're looking at ways to design our OS so that even major revisions don't require significant driver changes. We don't know for sure that we'll be able to pull that off, but it's a goal we're striving toward.
No it's not just "greed"
I've seen people complain that upgrades don't happen because the parties involved are just greedy. I guess there's a fine line between "economics" and "greed" but that line does exist. The economics of the situation are that it often just doesn't make sense to provide an upgrade. We're working on both parts of that equation. We're trying to reduce the total upgrade cost, and make upgrading easy enough that more people will make use of it. Whether this work will result in more upgrades being provided in the future remains to be seen. But we hope so.
MS Windows Mobile Team
