Writing ... or Just Practicing?

Random Disconnected Diatribes of a p&p Documentation Engineer

  • Writing ... or Just Practicing?

    The Network Ate My Shortcuts!

    • 0 Comments

    It's a bit scary when you turn on your computer and it's different from when you left it the day before. I don't mean it's a different computer (though sometimes that would be nice), but that something changed while you were in the land of nod.

    This happened to me last week. As I sat yawning and stretching in front of the screen waiting for some sign that the technology was also waking up from sleep, I noticed that several of the shortcuts to network resources that used to be on my Windows 7 desktop had disappeared. The first immediate panic reaction is "do I have a virus?" But a scan with a virus checker, and exploring the event logs, found nothing untoward.

    Next, try refreshing the desktop. No change. Then the trick of turning off display of icons (right-click the desktop, select View, and untick Show desktop icons) and then back on again. No luck. Next, look in the C:\Users\[user]\Desktop folder to see if the shortcuts are on the disk but not shown. Nope, not there either. Very odd...

    Maybe it's something to do with File and Print Sharing, or some domain-related issue. So I wander down to the server cabinet and start poking the domain controller. Strange - at 5:00 AM precisely that morning it had started reporting errors that there was a fault in the Active Directory. It happened immediately an automated backup started. And now the network icon in the taskbar was reporting that it was connected to an "unidentified network" rather than its own domain network.

    So I do the usual fix for that problem, disable and re-enable the network connection. Immediately it comes back with the correct network name. Except that I now have to reconnect to all the Hyper-V instances it hosts because they lost their connection when I disabled the network. And then, every six minutes, an error in the event log that Group Policy could not be processed because it can't find a domain controller. Even though it is one. The detail of the error is simply "Directory Error." Not exactly helpful.

    For a minute or so I ponder a full reboot, but that means stopping all the Hyper-V VMs. One is the proxy server, and my wife is currently in the middle of her morning Facebooking session so that's not a relationship-friendly option. The next best guess is to restart Active Directory Domain Services, which automatically stops and restarts several other important sounding services. There's heart-in-the-mouth moment when the DNS Service takes almost a minute to start up, but thankfully it all comes back with no errors in the event logs. And, magically, several hours later no more Group Policy errors either. Amazingly, I seemed to have fixed it.

    After that rather exciting start to the day, I do the research bit and discover that the shortcut issue is not my fault. According to KB 978980 on MSDN, being greedy and getting kicked for it is by design:

    "The System Maintenance troubleshooter performs a weekly maintenance of the operating system [and] either fixes problems automatically or reports problems through Action Center. When there are more than four broken shortcuts on the desktop, the System Maintenance troubleshooter automatically removes all broken shortcuts from the desktop."

    Furthermore, it says, "a broken shortcut is a shortcut to a file, folder or drive that may not always be available, for example, [...] a network folder that is currently not available due to the network not being available". I'll take a guess that being on a different network from the one the shortcut points to qualifies as "not always available." The workaround suggestion in the article is "keep the number of broken shortcuts on your desktop to four or less [or] create a folder on your desktop and move the shortcuts to that folder [which] will not be removed since they don't sit directly on the desktop."

    Or you can just disable the System Maintenance utility in Control Panel | Troubleshooting | Change settings.

    I can't help wondering how the meeting went where the Windows 7 developer team decided to include this feature:

        "Have you seen Joe's desktop recently, it's covered in shortcut icons. I'm
        sure he has no idea what they're all for!"

        "Yep, soaking up valuable resources and hiding that lovely picture of
        Niagara Falls that we went to so much trouble to include in our themes!"

        "It shouldn't be allowed. There should be someone who checks user's
        computers regularly to make sure they aren't being untidy after
        we went to all that effort to make the background pretty!"

        "Yes, but they might want to have a few shortcuts there for their favorite
        programs and regularly used files..."

        "I suppose so. How many do you reckon we should allow? Twenty? Ten?"

        "Why mess about. Let's just include a secret process that detects when
        a user is getting a bit slovenly and tidy up automatically. They'll never notice..."

    Except that, as the KB article reveals, sometimes we do...

  • Writing ... or Just Practicing?

    Do You Have a Vision?

    • 0 Comments

    In the olden days, people with a vision changed the world. Scientists such as James Clerk Maxwell kicked off the entire revolution in harnessing electricity and magnetism to build our modern world. Bardeen, Brattain, and Shockley started the silicon revolution that gave us the microchip, and Tim Berners-Lee gave us the World Wide Web. But, sometimes, you have to wonder if being a visionary is going out of fashion.

    OK, so there are plenty of people still inventing technological things, but mostly its evolution now. Some people even say that we've discovered all there is to know about physics and our planet. And lack of vision seems all-pervading when it comes to things such as politics. Where are the visionary leaders (for safety and impartiality, no names mentioned) of the past? It's pretty much an accepted fact that politics these days is a case of "going with the flow." Focus groups to tell you what policies are likely to get the most votes, and sound bites to keep the population satisfied.

    So what about in the world of computing, user documentation, and guidance that I and so many others inhabit? Is vision still alive and well? And is it really important? When did you last hear of a new computing device/service/product/accessory that was really new and ground-breaking?

    Wearable computers? I had a digital watch with a calculator in it twenty years ago. User input devices? Touch screens and motion detection have been around for ages. Mobile phones? Do you remember the eighties and brick-sized boxes? Internet TV? Windows 7 Media Center had that as a Silverlight-based add-on, and it was hardly a new concept then. Facebook and Twitter? Just evolution of CompuServe and bulletin boards. Online shopping? See How Much Computing Power Do You Need? Quantum computing? OK, so this one is relatively recent - but it's really just about moving particles around instead of electrons because we need to do things smaller, faster, and in parallel. Something we've been doing with CPUs for many years.

    Maybe we have reached the point where there is nothing really new and visionary left to be invented in the world of computing. Though there's probably more chance of actually having a vision in our industry, and implementing it, than there is in the world of politics...

  • Writing ... or Just Practicing?

    Why Is There Only One Monopolies Commission?

    • 0 Comments

    One of the old chestnuts you sometimes hear from disaffected and grumpy comedians is "How come there's only on Monopoly Commission?" They're not talking about the board game, but about the people who are supposed to guard us against being exploited by large corporations. And I'm going to hazard a guess that all these disaffected comedians are, like me, customers of our monopoly cable company here in Merry Olde England.

    I've been a cable-Internet-enabled customer of our national cable company for some four years. It would have been longer, but until the business division was surfaced as a separate entity within the all-encompassing media empire, they were seemingly unable to provide anything that resembled a business-level service of digital connectivity. And even then, as carefully documented in Cable Internet in 10 Easy Steps, the on-boarding experience was somewhat less than encouraging.

    Having said that, it's worked like a dream ever since and I've never had a complaint, except that I have to pay them extra every month just to send me a bill. But it was starting to look rather expensive, especially as we're assured that our local telephone people will have FTTC (Fibre to the Cabinet, with the chance of proper "high-speed" ADSL) working here any day now. Well, sometime, anyway. It was advertised as being August, but slipped to September, then we were assured it was definitely October. And even though it's been postponed until the end of November, I'm still optimistic we'll see it sometime this year. Or next year.

    So, anyway, I'm on the phone to a really pleasant and helpful lady at the business desk explaining that they're looking a bit pricey these days, and she tells me that I'm actually on a legacy service that's way out of date. But she can move me to a new service for free, and I'll get double the bandwidth, and it will cost about a third less! You can imagine that I asked why they didn't manage to tell me about this at the point when I became a legacy service user, but I suppose - as with all big companies - you can't expect miracles. So I agreed to be upgraded. Even when she said that, although the upgrade was free, I'd have to pay fifty pounds for a new cable modem. Oh well, I'll save that in a few months with the cheaper service.

    At this point I started to ask the technical questions. The modem lives inside my server cabinet, so I need to turn off the wireless feature. I don't really want something generating tons of radio fallout inside a big metal box full of computers. But it seems not, they say, unless I have a fixed IP address which "automatically disables the wireless" (no, I don't know why). And that's an extra on the bill, so I'd end up paying more than I do now. Probably I'll just wrap the modem in aluminium foil instead.

    And when can they do the upgrade? The lead time is 25 working days after the site survey. When will the site survey be? They can't say. Do I need one seeing as they already know what I have, and they're just going to swap the modem? No. Can they send me the modem and I'll plug it in myself? No, it has to be configured by an engineer.

    Five weeks after I placed the order I still haven't even heard when the site surveyor might arrive, so I phone again. "We're a bit busy," I'm told, "but we'll get someone there next week." Of course, the proviso is that they need to do a line test and, if it fails for the new speed, they'll need to replace the coax that connects me to their green box. And they can't do that for "a couple of weeks."

    But surely my cable will be OK? I can't say, because the engineer never turned up for the installation appointment. Obviously I immediately emailed the guy I've been talking to, the one who managed to "squeeze in" the non-arriving engineer visit. But I just got back an automatic response saying he's on holiday now for two weeks.

    Ah, but only last week I had an "out of the blue" phone call from my new "business customer personal advisor" who assures me she will be "looking after my account" and "making sure I get great service from the company." It will be interesting to see if I get any more phone calls from her after she reads the email I sent to their office on Friday evening after waiting all day for the engineer.

    Mind you, I did manage to sort out the problem with the phone line that was installed by default with my legacy package four years ago. It's an "included at no-charge" service where I pay only for any calls I make. As I can't even remember where they put the phone socket, you can tell how much use I made of that. But the interesting aspect is, because it's not free on the new package I've just signed up for, I now need to pay fifteen pounds a month for something that I never ordered, didn't want, and haven't ever used.

    Yes, I told them just to take it out (if they can remember where they put it) or disconnect it. Did I realize that there's a 90 day notice period for cancellation? Strangely, even though the phone conversation included the words "you must be joking", nobody can supposedly do anything about it. It's my fault for not initiating a disconnection notice three months before I decided on impulse to upgrade. It only took two more phone calls, seven emails, and a long online chat to convince them that they had more chance of winning the lottery than me paying them any more money. I await next month's bill with interest.

    Coincidently, there was a great article in the newspaper last week about the biggest problems facing large companies here in the UK. Surprisingly it isn't an overbearing Government, interference by the faceless bureaucrats of the People's Republic of Europe, the price of electricity, or mad taxation rules. It's poor customer service. I bet the guy who wrote it is also a customer of the cable company.

    So, in the end, I'm not the least bit concerned that there is only one Monopolies Commission. I just wish they'd do their job so there was more than one cable company to choose from...

    FOOTNOTE: In fact the engineers did turn up the following week after a very apologetic phone call from the local manager, and did an excellent job. It was the same guys who installed it four years ago, and they took extra trouble to disable the wireless and check the speed: 49.7 Meg down and 5.8 Meg up. Wonderful! Their office even phoned afterwards to make sure all was well and, as a nice bonus, offered to refund the cost of the new router. I'm a happy bunny all over again.

  • Writing ... or Just Practicing?

    A Cloud Service By Any Other Name...

    • 0 Comments

    As a firm believer in freedom of expression, I guess I can't complain about the names that the Windows Azure team give to their services and features. After all, my responsibility is just to write about them. In theory that can call them whatever they like. The problem is that they keep calling things what they literally are.

    Mind you, it's not just the Windows Azure people. The same problem seems to raise its head with many other technologies. I suppose it's just that I encounter the Windows Azure ones most often in my daily working life. And using literal names for things seems eminently sensible at first glance. For example, when Mr. Heinz started putting things in cans he used the obvious names. "Baked Beans", "Spaghetti Hoops", and "Mushroom Soup". His business may well have been less successful if he'd decided to label the tins "Whizz-bang Nice Stuff", "Delicacy Number 3", and "Supercalifragilisticexpialidocious".

    But if Bill had decided to follow the Heinz approach way back in 1985 when Windows 1.0 appeared, he would have called it "Operating System". So everything written about it since then would have referred to "The Microsoft Operating System operating system". Obviously this would have been stupid. So why am I continually having to write "...stored in a Windows Azure SQL Database database" and "...hosted in a Windows Azure Virtual Machines virtual machine"?

    I suppose giving things names that are generic descriptions makes it easier to recognize what they do. Amazon chose to give their cloud services distinctive names such as Glacier, Beanstalk, CloudWatch, Redshift, and DynamoDB. I guess I might want to store my data in a DynamoDB, or have my application monitored by a CloudWatch (unless it's actually something you wear on your wrist). But as I'm not a polar explorer, a fairy tale treasure hunter, or an astronomer I'm struggling to understand why I'd want a Glacier, Beanstalk, or RedShift.

    Perhaps the other problem is that, like domain names, the world is running out of pronounceable combinations of letters that aren't already registered, or that don't mean something rude in some countries or regions. Like the unfortunate choice by the Japanese refrigerator company Fukushima Industries that my very respectable daily newspaper recently revealed...

    Mind you, it gets even more confusing as you delve deeper into Windows Azure and try to write prescriptive guidance that is accurate to the nth degree. I recently discovered that a Windows Azure Virtual Machines virtual machine runs within a Windows Azure Cloud Services cloud service in much the same way as a Cloud Services cloud service does. And I assume that a Windows Azure Web Sites website does so as well. So now I'm having to refer to Windows Azure Cloud Services web and worker roles to differentiate the hosting platform I'm discussing from the Cloud Services cloud service that a Virtual Machines virtual machine runs in.

    Of course, at the heart of all this is the strict writing style and capitalization rules we've traditionally applied here at p&p. Thankfully Microsoft is adopting a more modern style for technical documentation, which might mean that I can get away with just talking about "a Virtual Machine" or "a Cloud Service". With luck I can just use capitalization to differentiate between a virtual machine in general terms (a non-physical server) and a Virtual Machine that is an element of Windows Azure hosting services. Though, confusingly, I'm mandated to use lower-case for "web role" and "worker role", so I might be a little too optimistic here.

    Perhaps I'll just write everything in lower-case. Microsoft Word word processor will automatically capitalize the first letter of sentences, and I'm sure my editor will look forward to sorting out the rest...

  • Writing ... or Just Practicing?

    Double Your Money

    • 0 Comments

    How would you like to be guaranteed a price for your products for the next thirty-five years, and at double the price you sell them for now? Sounds like a great idea. However, there are a couple of downsides...

    For example, you'll be allowed to sell only the lowest priced item, even if the customer wants a more expensive one. And you'll get severely castigated every time you make a profit, or when there is a shortage because you were refused permission to make any more. In addition, you'll find there might be periods of a couple of years when you aren't allowed to increase the price, but you'll get plenty of warning so that you can bump it up beforehand instead. Though every now and then you'll have to pay a dollop of cash into the official protection racket.

    Yes, it seems crazy - but this is exactly what is happening if you are an energy supplier here in the UK. Any day now the lights could go off because we forgot to build any new power stations to replace the ones that are slowly falling down or getting old. But now we've got no money to build new ones anyway, so we need to bribe other countries to pop over here and bring some with them. We pioneered commercial nuclear power generation as far back as the mid 50's, but we seem to have forgotten the recipe and so, even if we did have a few pounds hidden down the back of the sofa, it wouldn't help.

    Mind you, we have managed to rustle up the cash to build a new railway line - which it seems could cost as much as half a dozen new nuclear power stations. And we've got loads of shale underneath our seaside resorts that could be used to fuel cheap gas-driven power stations, but we're not sure if we have the nerve to dig it out.

    OK, so I've nailed solar panels all over our roof that, on a decent day, generate enough electricity to power most things in the house. Except I discovered that, when the mains electricity goes off, so do they. Something to do with not electrocuting the maintenance men from the electric company that come and dig up the street, they say. Nobody I asked can tell me why it can't be configured to disconnect from the incoming wires when the mains power dies, or why they can't wear rubber gloves and wellington boots instead.

    So I probably need to buy some new batteries for my server UPSs, keep my laptops fully charged, and check if the petrol generator hidden under a pile of rubbish at the back of the garage still works. I bought it a few years ago I when the local power company couldn't decide where the wires to our house came from, which made finding the intermittent fault (it broke when it rained, a fairly regular occurrence here in England) a somewhat long-winded (two years, in fact) process.

    Of course, what will be a real humdinger is if, when they finally get the new super-duper, high speed, all-electric railway built, they discover we don't have enough electricity to run any trains...

  • Writing ... or Just Practicing?

    Who is We?

    • 0 Comments

    Windows and its applications are getting even easier to use, and work far better than ever before for most non-technical users. It's a fact, I'm sure; but it seems to be having some unfortunate (and annoying) side effects for the more savvy members of the geekdom.

    I've been ruminating on various aspects of this since I came over all Win8ish some months back, but an event last week prompted this in-depth exploration of my opinions. A colleague reported an occurrence of the Blue Screen of Death, though now it isn't. It's a smiley face and a "Something went wrong" message. Yes, you can still get at the info previously available if you are really interested (though how many of us actually were when it happened to us?).

    I suggested that Windows can now detect your mood from the way that you type and poke at the screen, and it displays the smiley face to cheer you up when it figures you're in a bad mood. Or maybe not. Though the smiley faces really annoy me in things like Outlook Web Access (OWA) when it's so pleased to tell me I don't have any junk emails.

    But are the new "apps" easier to use than the old ones we were so used to? The issue, as far as I can see, is the limitations imposed by modern devices. In many cases the annoyance is caused by the fact that it's now customary to have everything on one "window" or "screen" and avoid opening new windows. This obviously makes a poke and swipe interface easier to use. And it's probably why many of the features I use regularly in OWA have disappeared from the latest version.

    But it aggravates that, for example, in the Mail app when I want to see details of a contact it opens in the whole screen instead of as a pop-up window that you just close to go back to where you were. And if you want to copy information from one contact to another, you can't just pop up two windows and switch between them. Though I suppose, on a tablet or phone, you wouldn't want to attempt finger-powered tasks as complicated as this anyway.

    What's clear is that Microsoft made the right decision to leave the desktop and existing apps in place underneath the new app-based UI. Inevitably I find I live in the old desktop almost all of the time, using proper "applications" instead of truncated "apps". Then, when I just want to read the news or send a couple of simple emails, I can fire up the trusty Surface RT and do wiggly finger stuff from the comfort of the sofa.

    Though I still end up gritting my teeth at some inane messages in Office 2013 and other desktop apps. "We didn't find anything to show here" when my Sent Items is empty, for example. Who is "we"? Are there little men inside the computer working the controls and running around with bundles of 1s and 0s in each hand? And Lync's "Have a good meeting!" message is even more annoying than "Have a good day!" when I buy a latte from my local coffee shop.

    But I suppose Microsoft doesn't design software just to be compatible with grumpy old men like me...

  • Writing ... or Just Practicing?

    Mister (Sometimes) Fixit

    • 2 Comments

    No I'm not talking about the clever "please mend my computer" tools that you can run on Microsoft's website. I'm talking about my regular tasks trying to fix all the things that break in our house, seemingly one per day at the moment. It's usually a wide and assorted selection of tasks; this week comprising a table lamp, a DECT phone, my fishpond filter, SQL Database, and Windows 8.

    Invariably my fixit jobs fall into two categories: "not worth the effort" and "fingers stuck together with superglue again." The second category tends to be associated with jewellery and ornament repairs (the latter typically being my fault), but the table lamp repair was in the first category - an IKEA lamp that originally cost twelve pounds new, but came from a jumble sale at a cost of two pounds. My wife had bought six new 12V halogen bulbs for it that cost more than the lamp did originally, but it refused to work. The transformer is a sealed unit, and the wiring is sealed inside the lamp. Do I spend three hours breaking it just to see what's wrong?

    But I had better luck with the DECT phone, a couple of new triple-A rechargeable batteries brought it back to life. And I managed to fix my fishpond filter using the typical handyman technique of a few bits of bent wire. These are the satisfying kind of repair jobs where you can carry around a big toolbox, and look like you know what you're doing. It works even better if you can arrange it so you didn't shave for a couple of days before.

    What's most annoying however, and has little capacity for appearing butch and manly, is the so-far-unmentioned third category of repair jobs: broken software. A year or so ago I parcelled up my locally-hosted websites and dispatched them to heaven - or, to be more precise, to live in the clouds of Windows Azure. Amongst them is our local village website, which is reasonably complex because it handles news, events, photos, and has a user registration facility.

    Yes, I know I should have adapted it to use claims-based authentication and Windows Azure Active Directory, but I just never got round to it; instead it has an ageing "aspnetdb" database sitting in SQL Database. There's only one role instance, and it works fine. Well, almost. Yes I did do comprehensive testing after deployment before the site went live, checking that I could add and edit all the items on the site, sign in and change my password, view lists of registered users, and see the error lists in the admin section of the site.

    I even made sure the site could create and remove users, and allow them to edit their details. But it turns out that my test coverage was a little less than perfect. For the first time since deployment I needed to use the functions of RoleManager to change the roles for a registered user. And everything broke. Even going into the SQL Database management portal and deleting the row in the data view of the table failed. As did executing a SQL DELETE statement in the query window.

    It took some searching based on the error message about SQL collation to find the answer. And the fix is so simple that it should painted in six inch high letters on a big piece of wood and nailed to the Azure portal. Simply open the stored procedure named aspnet_UsersInRoles_AddUsersToRoles and insert the text COLLATE Latin1_General_CI_AS into the DECLARE @tbNames... line as shown here, and then do the same with the aspnet_UsersInRoles_RemoveUsersFromRoles stored procedure.

    To get to the stored procedures, open the database management page from the main Windows Azure portal and choose the Manage icon at the bottom of the page. Sign into the SQL Database server and choose Design in the left-hand navigation bar, then choose Stored Procedures in the tabs near the top of the page. Choose the Edit icon next to the stored procedure in the list and do the edit. Then choose the Save icon on the toolbar. Repeat with the other stored procedure.

    Meanwhile, ever since I upgraded my trusty Dell E4300 to Windows 8 I've been plagued by wandering cursor disease. I'll be typing away quite happily and suddenly the letters appears in the middle of the next paragraph, or halfway along the next line. It's amazing how much something likeum. this can screw up your finely crafted and perfectly formatted text. It really is a pain in the b

    Of course, the answer is the same as most Windows 8 problems with older hardware. The jazzy new all-singing and all-dancing hardware drivers that come with Windows 8 don't always do the same as the wheezing and arthritic ones that came on a disk with the computer when you bought it. Thankfully, plenty of other people are having the same variable input position issue as me, and their posts led me to the updated Alps touchpad driver on Dell's website.

    Not that it fixes the problem - my touchpad still seems to think it's morphed into an X-Box Kinect - if I wave a hand anywhere near it the insertion point cursor leaps madly around in my Word document. But the Dell driver can detect when you plug in a proper mouse, and disables the touchpad automatically. Problem solved.

    Now I just need to prise my finger and thumb apart so I can mend a pair of my wife's earrings...

  • Writing ... or Just Practicing?

    Missing The (Access) Point...

    • 0 Comments

    Let's face it, the only proper way to connect computers together is with real wire in the form of good quality Ethernet cables and switches. The current all-encompassing drive towards wireless was, I reckoned, just fad that would soon pass. At least, that's what I though a few years ago. The reality is, of course, very different now.

    I hard-wired the whole of our house when we first moved in; it has cavity internal walls and plasterboard covered external walls so it was relatively easy to poke the wires into them and cut holes for Ethernet sockets. I even put speaker wires into each corner of the lounge so that I didn't have cables tucked under carpets or nailed to the skirting boards.

    I suppose in the US what we call plasterboard would be called drywall. Though when a colleague based in Redmond happened to mention that he had water leaks in his bathroom and was having to remove all the boards, I couldn't help asking if it was now actually wetwall.

    Anyway, a compact 16-port switch in the study connects everything together, and links into the proxy server in the server cabinet in the garage. Reliable high speed networking, and plug in anywhere - what more could you want? Though this was more than ten years ago, and the discovery that where we live there is almost no FM radio or DAB (digital audio broadcast) signal meant that Internet streaming radio was the only way to satisfy our insatiable demands for loud rock music.

    And Internet radios rarely have an Ethernet socket, and end up being located in the kitchen - the one room of the house that doesn't have an Ethernet socket. So, some seven years ago I was forced into nailing a wireless hub to one of the protruding ends of my network. And there it's been ever since, blinking soulfully at me from a high shelf and generally minding its own business.

    Of course, over the years, the number of devices it feeds has grown. As well as the high-fidelity Internet radio streams that pass through it for most of every day there are now two smartphones, a couple of tablet computers, a laptop or two, and a bird-box camera. The wireless hub uses the old steam-powered radio standards with a maximum of 54 Mbps and so it's no wonder that, some days, everything slows down.

    So I decided that the time was right for a network upgrade. The 16-port switch in the study is only 10/100 so it was replaced with a new TP-Link Gigabyte model, and I ordered a new wireless hub that does dual 2.4 MHz and 5 MHz concurrently, with up to 450 Mbps on each. That should make everything fly!

    However, nothing ever seems to be as easy as you expect. I blame the manufacturer's naming policy, though doubtless my own non-capabilities as a network administrator are partially culpable. You see, I reckoned that a wireless router was something with an ADSL or cable modem built it, so what I needed was a wireless access point. But all the ones I found seemed to be for use as repeaters with an existing wireless router. Then I found the NetGear kit that is a "wireless router" but without a modem in it. It seemed to be exactly what I needed.

    And I expected that installing it would easy, just a matter of setting the same fixed IP address, the same hidden SSID, the same security mode and passcode, and the same list of MAC addresses as the old one. Until I looked at the installation instructions. For some strange reason the first six pages are full of dire warnings to power off your ADSL or cable modem, take the batteries out, turn round three times and count to ten, and plug the wireless router into it using "the yellow cable supplied in the box." I've had "yellow wire problems" before, and for the life of me I couldn't see what all this palaver has to do with tagging a wireless hub onto the end of my network.

    Instead, I plugged it into my laptop. But which of the five ports on the router should I use? The nice bright yellow one seemed too tempting to resist, but that didn't work. Turns out that it's supposed to be LAN port 1. And, amazingly, up popped the configuration screen. Which, of course, refused to do anything at all because it couldn't detect an Internet connection. Only when I found the Advanced Setup pages could I actually do anything with it (and by that time I'd thrown the instructions away).

    Not that the instructions or the built-in configuration help notes are actually much help when you need to figure out some of the settings. For example, do I use the same SSIDs for the 2.4 MHz and 5 MHz channels or different ones? I chose to use the same on the grounds that, most days, it would be nice to just connect to anything. I don't really care which. Or even if its my neighbour's. But a search of t'Internet reveals mixed opinions on this; it mainly seems to depend on whether you want to be able to tell them apart when you connect.

    After three configuration attempts that ended with the "can't connect to router" message followed by the obligatory "go find a paper clip" (to press the reset button) activity, I finally figured out to completely ignore the tempting yellow socket and any configuration connected with "Internet". After that it all went swimmingly. It's a shame that it was only after all the fiddling about that I found this page on the NetGear site that explains how to do it all when you just want a wireless access point. OK, so it's for older models than the kit I have, but it still seemed to be relevant.

    The important bit is where you suddenly figure out that you don't use (or need) the tempting yellow socket, and that you also spent twice as much money as you needed to because what you've bought is a "Wireless Router Without A Modem Even Though The Natural Meaning Of The Term Is One With A Modem In It" instead of a "Wireless Access Point That Is Not A Wireless Repeater And Can Be Used Standalone".

    So by now I've got a wireless hub that should be able to connect to the Internet and do magic things, but can't because the tempting yellow socket is empty; will quite happily connect directly to a USB drive to stream music, and even make files accessible over the Internet, but can't because the tempting yellow socket is empty; can do firewalling and provide a guest network, but can't because the tempting yellow socket is empty; has three spare Ethernet ports to connect other stuff to, but they're empty because I already have a proper wired network; can do 450 Mbps on 2.4 GHz but that will kill all my neighbours' wireless connections; and can act as a wireless repeater, but I don't need that capability.

    After a restless night dreaming about tempting yellow sockets, the next day I dug out the full PDF manual on the CD provided with the router, convinced that it must say something useful. A search for "access point" found the following help item:

    Yep, that's all it says about it. And the option is not even on that page of the configuration interface. But there is another page called "Wireless AP" (I suppose if I'd been thinking logically I'd have realized that AP stands for Access Point). And here's what that page looks like when you select the uninformative "AP Mode" checkbox. Notice the contents of the help page - the big black rectangle at the bottom of the screen.

    Aha! When you also check the next (uncaptioned) checkbox, which magically appears after you select AP Mode, you get text boxes to enter the long-anticipated IP address, subnet mask, gateway, and DNS servers. So I fill all that in, select Apply to reboot the router, and swap my network cable to the tempting yellow socket. And it works! Even the "Internet" page in the configuration now shows "Connected" and it sets the router's clock to the correct date and time. Maybe I've solved it?

    Except now all those fancy features I paid so much extra for are disabled in the menus - but at least now I know I can't use them. However, where are the other options I expected to find in a top of the range wireless router? Such as the ability to tune the signal strength (I ran my old one at half power both to avoid annoying the neighbors and for security purposes). Or the ability to disable remote access to the configuration pages over the wireless link. Surely this is an obvious attack vector?

    And, worst of all, I discovered that none of the wireless devices in our house can actually use the 5 MHz band...

Page 5 of 40 (318 items) «34567»