![\"clip_image001\"](\"http:\/\/www.jerrypournelle.com\/chaosmanor\/wp-content\/uploads\/2015\/07\/clip_image00116.gif\" "\\"clip_image001\\"")
<\/a><\/p>\nThis morning Precious, the Surface Pro 3, said she had another update, but it was dated from long ago (March or so) and had to do with firmware; why it had never asked for this update may have to do with experimental Windows 10. It may not. Anyway I told it to go ahead, and as always it took a while, the percentage done estimate sitting unmoved and no indication other than its existence that anything was going on; then the percentage would jump and we\u2019d have another wait. Eventually it was all downloaded and I was told that a reset would happen at 3 AM unless rescheduled. I told it to do it now, and some minutes later I had new wallpaper, but still Build 10159. A quick check showed I could log on to Swan, a Windows 8.1 system, and Bette, my Windows 7 former main machine; but it could not see Alien Artifact, the current Windows 7 main machine. I experimented and made sure I could transfer files to and from the machines I could see, and went back to work on the substantial amount of text Steve Barnes sent last night: essentially Part One of the new novel, along with an even larger \u201cEncyclopedia Avolonia\u201d, the story bible. I did some adjustments to the bible, and went to bed. It\u2019s good stuff, and I feel like writer again, adding some details and generally having fun before plunging into the real work of contributing to the text; it\u2019s character development time.<\/p>\n
But while doing that I had the nagging feeling that it all needs backup, and Precious is one logical place for backups; so this morning when Precious said she wanted a long overdue update, it seemed reasonable to see if that changed Alien Artifact\u2019s visibility. But nothing changed: Precious could see several machines including the ThinkPad portable, and had mapped drives to several of them, and that all worked; but not a sign of Alien Artifact, alas.<\/p>\n
Next step: can Alien Artifact see Precious? And indeed he could, and clicking on Precious in My Computer on Alien Artifact immediately gave me access to Precious, root and branch. I could transfer files from Precious to Alien Artifact, and I could create Folders on Precious, so I did so, making a Master folder with sub folders for the each project I\u2019m working onto Precious. I used Norton Commander as a file manager, and all worked perfectly. Well, perhaps not perfectly because the default library system of Windows has been a bit of a mystery ever since my brain cancer nearly a decade ago: but I was able to create a system I can find easily, so it doesn\u2019t matter. I\u2019ll use Commander to straighten it all out and put Mamelukes on Precious as well. Time to work on that also, but it\u2019s in a master folder called WinWord, which has a hundred folders of all my projects including some I haven\u2019t worked for years, and yes, even though disk space is cheap and redundancy is good, I admit I have about three incompatible organization schemes, and it\u2019s getting absurd. But that\u2019s for another time.<\/p>\n
Meanwhile, I had established that Alien Artifact could see Precious; he couldn\u2019t, last night before the update. That\u2019s progress. Now I went to Precious, hit Winkey e, open This Computer, and Lo! I could see Alien Artifact. I tried to map Alien Artifact D Drive to Precious, and two things happened: suddenly I could see that Precious drive Z was already mapped to Alien Artifact D \u2013 and Precious wanted a password for Alien Artifact. And when I gave it, it was rejected. Now clearly it must have accepted it in the past, but not now.<\/p>\n
Still, if Precious can see Alien Artifact, and receive files from him, eventually Eric or Alex or I will figure out what to do next; it\u2019s already possible to back up everything one way or another, and transfer files (with an intermediary copy to either Swan or Bette) so everything I need to do is possible. What Microsoft needs to do is make their new security system usable by users. Now it\u2019s only useful to hackers, which someone at Microsoft will eventually is not the goal.<\/p>\n
Now back to work on the new text. Progress is being made, and it\u2019s good stuff. If you liked Beowulf\u2019s Children, you will love this.<\/p>\n
1515 I find that Build 10162 is now available, and I am downloading it now. Perhaps this will take care of the situation. I continue to this stuff so you don\u2019t have to.<\/p>\n
This update was available earlier \u2013 by Thursday night \u2013 but for some reason my visit to updates today didn\u2019t see it until I had downloaded the hardware stuff, which was a month old. But we\u2019re 90% done with the update to a new build.<\/p>\n
1730 The new build has downloaded and I am resetting. Eric warns me to be sure that network discovery is turned on, but I can\u2019t see why that would change what it would see if it could be seen at all, or see anything at all. But we\u2019ll find out. The installation is taking considerable time so I can’t test anything. Precious is resetting as I write this\u2026 ah, 60% done. More later. <\/p>\n
<\/p>\n
Ah. I now have Build 10162, but it says it needs some new installation and it\u2019s updating again. Fortunately I don\u2019t use that machine (Precious) for anything critical although I want to; I make no doubt that there\u2019s a stable operating system out there that can wait for Windows 10. All the Microsoft gurus are using the Surface Pro 3, so there\u2019s an incentive. Me. I keep doing the experimental OS because that\u2019s sort of what I do. And updates are installing as I write this; whether it\u2019s yet another build I don\u2019t know. Fun, ain\u2019t it?<\/p>\n
1830: Well, I have build 10162 and it no longer wants updating. Everything seems to work but I do not have the \u201ccredentials\u201d to allow Precious to connect to Alien Artifact; the problem is the user name, which wants some domain name rather than just the login name. I\u2019m sure this is solvable, but Microsoft just improved things when we didn\u2019t ask for the improvement, and made it unusable. <\/p>\n Eric reminds me that we will shortly have a raid backup system that should solve all the backup problems,<\/p>\n I will shortly have more to say about the Register article, but it is getting to dinner time. <\/p>\n <\/p>\n win10 wifi access sharing thought <\/p>\n Jerry,<\/p>\n So apparently win10 isn’t going to share a plaintext wifi password. Instead, it will be sharing what is effectively a magic spell, unpronounceable to mortal humans, that does the EXACT SAME THING as the password, namely getting access into a password protected system.<\/p>\n And somehow this is more OK than just giving out the password instead of a “hash” (i.e.. Magic spell) that does the same dang thing that the password does.<\/p>\n Nope, still not ok. I put passwords on things that I don’t want to share. I’m totally not ok with my OS sharing magic spells (hash, whatever) that bypass my password security.<\/p>\n It’s a bit like selling a car that would automatically unlock all its doors on the command of any other person who doesn’t have an actual key, as a default behavior. Why would anyone want such a thing?<\/p>\n Sean<\/p>\n<\/blockquote>\n I asked for the source and got<\/p>\n win10 wifi access sharing thought <\/p>\n http:\/\/www.theregister.co.uk\/2015\/06\/30\/windows_10_wi_fi_sense\/<\/a><\/p>\n There is some discussion on a handful of tech forums as well.<\/p>\n Sean<\/p>\n<\/blockquote>\n And then turned to my advisors.<\/p>\n Peter Glaskowsky says<\/p>\n It\u2019s a real feature. It\u2019s been in Windows Phone 8.1 since last year.<\/p>\n It\u2019s described on Microsoft\u2019s own Windows Phone website:<\/p>\n https:\/\/www.windowsphone.com\/en-us\/how-to\/wp8\/connectivity\/wi-fi-sense-faq<\/a><\/p>\n And it\u2019s been covered by reasonably responsible industry websites, for example:<\/p>\n http:\/\/www.windowscentral.com\/wi-fi-sense-windows-phone-81<\/a><\/p>\n As well as the article Mr. Long mentions from the infamous scare-mongers at the Register.<\/p>\n As Microsoft says, it\u2019s basically a way to \u201ccrowdsource\u201d access to Wi-Fi to help more people get on Wi-Fi more easily. It helps access public Wi-Fi hotspots, as well as privately managed ones, and it\u2019s those privately managed hotspots that are the only issue being raised here.<\/p>\n It\u2019s opt-in on a per-user, per-network basis. There\u2019s also a terribly awkward opt-out option that protects you even if someone else who has your Wi-Fi password decides to share it using Wi-Fi Sense. (That, to me, is the worst problem, but it\u2019s unavoidable in any shared-password system.)<\/p>\n I\u2019m a bit curious about some of the limitations they say they can impose on the Wi-Fi network, such as limiting guests using shared passwords to Internet access only, preventing them from accessing LAN resources like printers or webcams. I don\u2019t think there\u2019s any way to do that with older Wi-Fi access points that have an all-or-nothing security model, so maybe Wi-Fi Sense only works with newer routers. I\u2019d like to get that answer, at least.<\/p>\n I have no idea what the underlying security model is, so I don\u2019t trust it, and I wouldn\u2019t use it, but it\u2019s hardly evil for a \u201cdeal killer.\u201d Just another misguided Microsoft attempt to make their ecosystem more attractive to users.<\/p>\n . png<\/p>\n<\/blockquote>\n I should have known that, I expect, but I don\u2019t keep up as much as I would like.<\/p>\n Peter adds<\/p>\n As a postscript, btw, I got into a long email bickering contest with an editor at The Register over that original misleading article. I got them to make two sets of changes during our exchange (which I documented by saving PDFs), but he wouldn\u2019t yield on the deceptive headline. Even the changes in the body were basically minimal and inadequate.<\/p>\n He wanted to hide behind an assertion that “All the facts are in the article,\u201d so a person could figure out what was actually going on by carefully reading the article and the Microsoft pages it links to.<\/p>\n I tried to explain that this wasn\u2019t good enough since most people, reading articles the way they usually do, would come away with the wrong impression. At that point he just stopped responding.<\/p>\n A big change from the old days under Mike Magee, who enjoyed such verbal fencing but was reasonably good at fixing anything that was actually wrong.<\/p>\n I suppose any publication that makes Mike Magee look relatively responsible must be doing something wrong…<\/p>\n . png<\/p>\n<\/blockquote>\n As Peter says, bottom line, Microsoft isn\u2019t always as good at explaining what they are doing as they would like to be. My own observation is that without Bill Gates there\u2019s no one in charge to set goals, so different parts of Microsoft set off in different directions; and if it takes a while to turn big ships, it takes longer to redirect a fleet of big ships\u2026<\/p>\n Freedom is not free. Free men are not equal. Equal men are not free. <\/p>\n Chaos Manor View, Saturday, July 04, 2015 This morning Precious, the Surface Pro 3, said she had another update, but it was dated from long ago (March or so) and had to do with firmware; why it had never asked for this update may have to do with experimental Windows \u2026 Continue reading <\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n\n
\n
\n
\n
<\/a><\/p>\n
<\/a><\/p>\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"