New
#440
I really have to say I had not a minute's worth of trouble from the October release...but...I wasn't running One Drive, either--or else an older, non-updated version of One Drive. From what I read about the October-release pulls and reissues, One Drive interoperability problems with the October update build were the chief culprits--problems I never did see myself, for obvious reasons. Ran like a top for me since the initial installation--but, again, I hadn't befouled my system with One Drive for many, many moons. A fact which dovetails nicely with this next bit...
Over the years the biggest bugaboo in Microsoft's ongoing software development strategy *cough* is the fact that the left hand never seems to talk to the right hand during build/feature/application development--and so weird, easily preventable problems like "Why doesn't this version of Office work with the latest version of Win10?" and etc. etc., ad infinitum--are always popping up here and there. Because--yes--the right hand really does *not know* what the left is doing inside Microsoft application development! For years in my younger days I frequently made the cardinal mistake of assuming that "they would never be so negligent and operate so carelessly" when it comes to the interoperability of their own programs running on their own OSes! Man, was I wrong!...;) It wasn't just egg but the whole darned chicken farm on my face in those days! Oh, yes...;) "They" would certainly do that and "they" have been doing that for years!
"Why?" is the most rational response. Why do they partition off each development team into its own light-proof, sound-proof partition during development, where the slogan is: see no other Microsoft program, hear no other, and talk to no other Microsoft development team in the interests of non-interoperability among Microsoft programs! Perhaps the Insiders program is Microsoft's answer--maybe so. User feedback of programs and operating systems can be a rich source of bug-smashing, but I still think a lot more cooperation among the various Microsoft development teams during key developmental stages would be even better!
Yesterday, because of the problems I described in an earlier post in this thread--I was "this close" to reverting to 18317. But since the obvious steps I took in trying to correct those problems seem for the moment to have borne fruit--I'm holding off. But, these days I feel no shame in either reverting or restoring from a backup I know works as advertised. None at all. I'm less inclined to hunt and peck around these days with these builds. Better things to do, I s'pose...;) Like pocket-pool *cough* or Mah-Jongg? Maybe try Reading Fundamentals Volume XXXVIV.4...?...Arrrgggghghghg...! ;)
Yeah. I don't think we will be bored when the next Skippy build drops. I'm figuring I probably will do a reset of this build before installing the Skippy as my partition for this is at 85%. Linux is in an interesting state because Linux released kernel 5.0.0 and along with the fact that the Linux compiler is now at 9.0.0 and bash itself is at 5.0.0 VMware WS won't compile smf VB has its problems as well. I think it likely that I will need to break the nice software RAID I have which I correctly, but inconvientily formated as XFS. I did reactivate my ESXi server and it has the latest Windows (i.e. this current build we are using) Fedora Rawhide and Ubuntu Disco but its a 10 year old HP Proliant with 10GB memory. My wife lost her machine to the Windows October surprise and seems content for now with tablets. All in all I am living in interesting times and we all know what that means. So hang in geeks we are due for a "custom", bumpy ride.
------------------------------
Just used ImDisk utilities (free) to create a 2 GB RAM drive and mounted the 18323 ISO which is on Onedrive for further use. Seems a little late for either a Fast (will use a VM) or a Skippy so I back to Fedora. I'll see you Skippy geeks on the other side.
As long as they get it runnin on all 8 cylinders and not just applying pin-striping!!!