It's the week before Christmas in London's Oxford Street, and The Register is visiting a branch of Electronics Boutique to obtain £60-worth of megadeath for the little mites, bless 'em. As you'd expect of a major software store at this time of year, Electronics Boutique is throbbing - except for the check-outs, that is. As we slowly inch our way along the barely-moving queue we notice that the staff are spending an awful long time standing very still and staring at the EPOS equipment. When we get there, one of them observes that it's now averaging a minute per card validation. "ISDN?" we ask. Indeed it is, says the assistant, and it's supposed to take a maximum of 15 seconds. As The Register's plastic climbs towards a new record wait time, we chat some more. When this happens, apparently, the store staff have difficulty in getting anyone in the supply chain to own up to what's not working. It could be the EPOS equipment, it could be the lines, it could be something out there in serverland or it could be the validation networks themselves. Our first offer of plastic having climbed beyond four minutes, the transaction gets cancelled and we helpfully give them an Amex instead (Amex uses a different validation system, so this should help them isolate the problem). That won't work either, and as the salesman makes a desperate attempt at voice validation, that stops working too. Helpfully, he tilts the screen over so we can see that it's refused to validate. Not just us either. Electronics Boutique in Oxford Street in the week before Christmas is unable to take plastic. Oh dear… But there's something else on the screen that interests us some more. It's the word "Microsoft." This looks very much like the sort of NT-based EPOS system that Microsoft, in close alliance with ICL, has been pushing in the UK recently. Your EPOS equipment is basically a client on the network, so it can play a full part in your corporate Digital Nervous System. When it's not down, that is. We chat some more to the salesman as we proffer cash. "Oh, I wouldn't buy an EPOS system from them," we observe helpfully. He says he didn't ask for it (well, he wouldn't have, would he?) and tells us it now takes twice as long as previously to cash-up at night. We decide to lay off in case our enquiries start threatening the poor lad's career, and head off into the crowd, musing on the distributed computing model. ®

As we suggested almost two weeks ago, the route Microsoft has taken so far to gain compliance with Sun's preliminary injunction may not be enough. On Friday Microsoft asked the San Jose District Court to extend the time it has to modify its software to 120 days. In announcing its latest version of Java Microsoft referred to it as being "in compliance with the recent ruling in the San Jose Federal District Court." We had some doubts (Earlier story). The company currently has 90 days from 18 November to become compliant, and is appealing the court's ruling anyway. But if it wants more time to achieve compliance, then obviously Microsoft has its doubts too. It's currently giving developers the option to stick with its code or go with Sun's, which it is now also shipping. But in asking for the extension it's also asked for clarification of the injunction to allow it to distribute "independently developed" technology. So Microsoft too thinks there is a possibility that the injunction does not in fact allow it to do so. If it doesn't, then the company must currently be in breach of the injunction. Sun is meanwhile sticking to its version of the contracts, insisting that Microsoft's software should pass Sun's compatibility tests before it is shipped. Presumably what Microsoft is currently shipping won't, and if the judge agrees with Sun, then Microsoft is going to have to have another go at compliance. ® Complete Register trial coverage