Something is seriously wrong at MSFT.
https://www.thurrott.com/windows/windows-10/189344/windows-10-version-1809-s...
The re-release of the "Feature Update 1809" i.e., the new version of windows for September '18, hence 1809, is deleting user's data, again.
I strongly recommend you turn off Updates as best you can. I've set all our machines here to "Metered" connections and set "Feature" updates to a 365 day delay and Security updates to a 30 day delay.
I think Windows has gotten too complex for MS to understand. Shadow directories and fake redirections and everything dependent not on the OS or the File System, but the Registry, may just be a step too far.
I think Windows has gotten too complex for MS to understand. Shadow directories and fake redirections and everything dependent not on the OS or the File System, but the Registry, may just be a step too far.
What's actually happened is described pretty well in this article - basically they laid off a load of traditional QA and testing professionals in 2014 and are now relying on some sort of crowdsourced bullshit for QA, using people who are on the beta releases, i.e.e fanboys.
https://www.theregister.co.uk/2018/10/23/microsoft_windows_10_crisis/
On Wed, Oct 24, 2018 at 4:51 AM Alan Bourke alanpbourke@fastmail.fm wrote:
What's actually happened is described pretty well in this article - basically they laid off a load of traditional QA and testing professionals in 2014 and are now relying on some sort of crowdsourced bullshit for QA, using people who are on the beta releases, i.e.e fanboys.
https://www.theregister.co.uk/2018/10/23/microsoft_windows_10_crisis/
Thanks for the excellent link. Sorry to hear about the MS testers who got canned. I know the Fox engineers did some amazing work to get us a high quality product.
It's funny how Linux can ship good code with crowd-sourced testing, and Apache and OpenSSH and the open-source communities that power DNS and email and the rest. I suspect there has been a long process of developing the protocols and processes to make that a success. And also that it's not just guys living in their parent's basements: RedHat and IBM and Dell and HP contribute their own software and have pretty serious engineering efforts.
"Throw it over the wall and see how loud they scream" is not a testing methodology.
"Throw it over the wall and see how loud they scream" is not a testing methodology.
Love it!
John Weller
On 2018-10-24 04:51, Alan Bourke wrote:
I think Windows has gotten too complex for MS to understand. Shadow directories and fake redirections and everything dependent not on the OS or the File System, but the Registry, may just be a step too far.
What's actually happened is described pretty well in this article - basically they laid off a load of traditional QA and testing professionals in 2014 and are now relying on some sort of crowdsourced bullshit for QA, using people who are on the beta releases, i.e.e fanboys.
https://www.theregister.co.uk/2018/10/23/microsoft_windows_10_crisis/
I heard this happening awhile back, when they laid off John Koziol (who worked in Q/A there, didn't he?). No surprise. All that money (more money than any other company perhaps) and they're too cheap to do testing the right way. Ugh.
Testing is done differently today than it was 20 years ago.
It doesn't replace real people from final testing but it does reduce their need on early bugs that is for sure.
I don't allow your code to be saved if your code breaks the build we have in place. You get notified of it right after you submit it.
On Wed, Oct 24, 2018 at 9:07 AM mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
On 2018-10-24 04:51, Alan Bourke wrote:
I think Windows has gotten too complex for MS to understand. Shadow directories and fake redirections and everything dependent not on the OS or the File System, but the Registry, may just be a step too far.
What's actually happened is described pretty well in this article - basically they laid off a load of traditional QA and testing professionals in 2014 and are now relying on some sort of crowdsourced bullshit for QA, using people who are on the beta releases, i.e.e fanboys.
https://www.theregister.co.uk/2018/10/23/microsoft_windows_10_crisis/
I heard this happening awhile back, when they laid off John Koziol (who worked in Q/A there, didn't he?). No surprise. All that money (more money than any other company perhaps) and they're too cheap to do testing the right way. Ugh.
[excessive quoting removed by server]
On Wed, Oct 24, 2018 at 4:09 AM Ted Roche tedroche@gmail.com wrote:
I think Windows has gotten too complex for MS to understand. Shadow directories and fake redirections and everything dependent not on the OS or the File System, but the Registry, may just be a step too far.
Which means Micro$oft might need to rewrite it again? ;)
On Thu, Oct 25, 2018 at 9:28 AM Man-wai Chang changmw@gmail.com wrote:
Which means Micro$oft might need to rewrite it again? ;)
Well, they bought DOS, slapped a gui on it, sold that for nearly 20 years, moving it from 16- to 32-bit, yay Win32s!
Windows, 2.0, 3.1, 3.1, 3.11, W4Workgroups, W4Tablets, w4Work, Win95, 98, Millenium
They teamed up with IBM to write OS/2 later "WARP," using Windows New Technology with the New Technology File System.
Then they torpedoed IBM and released it as Windows NT. And that's what we are running today, Windows NT 3, 3.5, 3.51, 4, 7, Windows Vista, Windows 8, Windows 10. They've glommed a lot of stuff on top, but it's Windows NT on NTFS with its lousy security model, patched over with a new domain model and Policy enforcement, but it's the Registry and LAN Man and the same old print queue.
It's tens of millions of lines of code, written mostly by people who don't work there any more. It's huge, it's heavy, it's buggy. And it runs on Desktops. And Servers. And not much else. Not smartphones, not lightweight tables, not the internet. Ignoring Windows CE (which still exists, running my settop box -*shudder), WindowsPhone, and XBox OS, all speciality spinoffs.
Perhaps they should rewrite it. Third time's the charm, or so they mythology goes within MS.
Highly recommended: https://en.wikipedia.org/wiki/Microsoft_Windows for a refresher on the history. Good overview.
On Thu, Oct 25, 2018 at 10:53 AM Alan Bourke alanpbourke@fastmail.fm wrote:
Win32s
I remember that piece of crap - trying to get a Filemaker application working with it.
That's where I learned the term "thunk layer."
On 2018-10-25 10:34, Ted Roche wrote:
Perhaps they should rewrite it. Third time's the charm, or so they mythology goes within MS.
Highly recommended: https://en.wikipedia.org/wiki/Microsoft_Windows for a refresher on the history. Good overview.
I'm pretty safe in saying they will NEVER rewrite it from scratch. It'd take too long to deliver.
Or you might ask them why Visual Studio is only a 32 bit application.... Yes, it can build 64 bit apps, but they can't figure out how to compile it as a working 64 bit app. And if they can't fix that in all the time they have had, how would you expect them to redo windows????
Maybe they are hoping we will all move to Linux and run our apps on Azure instead.... Much less work for them to support... All I know is that they are doing their best to piss off everyone they can.
Fletcher Johnson FletcherSJohnson@Yahoo.com LinkedIn.com/in/FletcherJohnson beknown.com/FletcherJohnson twitter.com/fletcherJ twitter.com/svcsug strava.com/athletes/fletcherjohnson 408-946-0960 - work 408-781-2345 - cell
-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Ted Roche Sent: Thursday, October 25, 2018 7:34 AM To: profox@leafe.com Subject: Re: [NF] Broken Windows
On Thu, Oct 25, 2018 at 9:28 AM Man-wai Chang changmw@gmail.com wrote:
Which means Micro$oft might need to rewrite it again? ;)
Well, they bought DOS, slapped a gui on it, sold that for nearly 20 years, moving it from 16- to 32-bit, yay Win32s!
Windows, 2.0, 3.1, 3.1, 3.11, W4Workgroups, W4Tablets, w4Work, Win95, 98, Millenium
They teamed up with IBM to write OS/2 later "WARP," using Windows New Technology with the New Technology File System.
Then they torpedoed IBM and released it as Windows NT. And that's what we are running today, Windows NT 3, 3.5, 3.51, 4, 7, Windows Vista, Windows 8, Windows 10. They've glommed a lot of stuff on top, but it's Windows NT on NTFS with its lousy security model, patched over with a new domain model and Policy enforcement, but it's the Registry and LAN Man and the same old print queue.
It's tens of millions of lines of code, written mostly by people who don't work there any more. It's huge, it's heavy, it's buggy. And it runs on Desktops. And Servers. And not much else. Not smartphones, not lightweight tables, not the internet. Ignoring Windows CE (which still exists, running my settop box -*shudder), WindowsPhone, and XBox OS, all speciality spinoffs.
Perhaps they should rewrite it. Third time's the charm, or so they mythology goes within MS.
Highly recommended: https://en.wikipedia.org/wiki/Microsoft_Windows for a refresher on the history. Good overview.
On Mon, Oct 29, 2018 at 8:12 PM Fletcher Johnson FletcherSJohnson@yahoo.com wrote:
Hi, Fletcher!
Serious question, not trolling:
Or you might ask them why Visual Studio is only a 32 bit application....
How does VS being "only" a 64-bit app limit developers? VS is basically a glorified editor and project manager and front-end gui for the build and compile tools. What would it gain by going 64-bit?
Seriously curious.
Maybe they are hoping we will all move to Linux and run our apps on Azure
instead.... Much less work for them to support... All I know is that they are doing their best to piss off everyone they can.
"One Microsoft Way"
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---
It's nothing to do with not being able to do it, it's because there is no real gain from doing it. Of course they could build a 64 bit IDE if they wanted.
https://www.infoq.com/news/2016/01/VS-64-bit
Kicking an old thread back to life. MSFT continues to beat the dead horse of Windows 1809 ("the September 2018 refresh Creator's Edition Professional Update Ultimate, September, no October, no, welcome to December Update") with a set of patches that, among other things, fixed a bug that doesn't re-map drives upon login.
Cause, no one uses mapped drives any more, amirite?
https://www.zdnet.com/article/new-windows-10-1809-update-rolls-out-mapped-dr...
On Tue, Oct 30, 2018 at 7:50 AM Alan Bourke alanpbourke@fastmail.fm wrote:
It's nothing to do with not being able to do it, it's because there is no real gain from doing it. Of course they could build a 64 bit IDE if they wanted.
https://www.infoq.com/news/2016/01/VS-64-bit
-- Alan Bourke alanpbourke (at) fastmail (dot) fm
On Tue, 30 Oct 2018, at 12:12 AM, Fletcher Johnson wrote:
Or you might ask them why Visual Studio is only a 32 bit application.... Yes, it can build 64 bit apps, but they can't figure out how to compile
it
as a working 64 bit app. And if they can't fix that in all the time they have had, how would you expect them to redo windows????
Maybe they are hoping we will all move to Linux and run our apps on Azure instead.... Much less work for them to support... All I know is that they are doing their best to piss off everyone they can.
Fletcher Johnson FletcherSJohnson@Yahoo.com LinkedIn.com/in/FletcherJohnson beknown.com/FletcherJohnson twitter.com/fletcherJ twitter.com/svcsug strava.com/athletes/fletcherjohnson 408-946-0960 - work 408-781-2345 - cell
-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Ted Roche Sent: Thursday, October 25, 2018 7:34 AM To: profox@leafe.com Subject: Re: [NF] Broken Windows
On Thu, Oct 25, 2018 at 9:28 AM Man-wai Chang changmw@gmail.com wrote:
Which means Micro$oft might need to rewrite it again? ;)
Well, they bought DOS, slapped a gui on it, sold that for nearly 20
years,
moving it from 16- to 32-bit, yay Win32s!
Windows, 2.0, 3.1, 3.1, 3.11, W4Workgroups, W4Tablets, w4Work, Win95, 98, Millenium
They teamed up with IBM to write OS/2 later "WARP," using Windows New Technology with the New Technology File System.
Then they torpedoed IBM and released it as Windows NT. And that's what we are running today, Windows NT 3, 3.5, 3.51, 4, 7, Windows Vista, Windows
8,
Windows 10. They've glommed a lot of stuff on top, but it's Windows NT on NTFS with its lousy security model, patched over with a new domain model and Policy enforcement, but it's the Registry and LAN Man and the same
old
print queue.
It's tens of millions of lines of code, written mostly by people who
don't
work there any more. It's huge, it's heavy, it's buggy. And it runs on Desktops. And Servers. And not much else. Not smartphones, not
lightweight
tables, not the internet. Ignoring Windows CE (which still exists,
running
my settop box -*shudder), WindowsPhone, and XBox OS, all speciality spinoffs.
Perhaps they should rewrite it. Third time's the charm, or so they mythology goes within MS.
Highly recommended: https://en.wikipedia.org/wiki/Microsoft_Windows for
a
refresher on the history. Good overview.
-- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]
On Dec 6, 2018, at 9:53 AM, Ted Roche tedroche@gmail.com wrote:
MSFT continues to beat the dead horse of Windows 1809
Is that the distant ancestor of Windows (19)95?
-- Ed Leafe
What's old is new again :)
Microsoft stopped the numbering (3.0, 3.11, 95, 98, Millennium, WinNT3, 3.51. 4, Vista) and declared all future versions were "10" because Apple had taken the much cooler "X" years before. Now all the Windows are Windows 10, only different, and incompatible, like DLL Hell only now it's an invalid GAC cache. They came up with the genius numbering scheme of YYMM because software is always on-time and feature-complete. So the September (09) 2018 version of Windows 10, which didn't ship until October, and then was taken back, and re-released in October, and taken down, and re-released in November, is now patched in December, so the latest version of Windows 10 1809 is build 17763.168.
Hope that clears things up for you :)
"Where Do You Want To Go Today?"
On Thu, Dec 6, 2018 at 11:05 AM Ed Leafe ed@leafe.com wrote:
On Dec 6, 2018, at 9:53 AM, Ted Roche tedroche@gmail.com wrote:
MSFT continues to beat the dead horse of Windows 1809
Is that the distant ancestor of Windows (19)95?
-- Ed Leafe
[excessive quoting removed by server]
So the September (09) 2018 version of Windows 10, which didn't ship until October, and then was taken back, and re-released in October, and taken down, and re-released in November, is now patched in December, so the latest version of Windows 10 1809 is build 17763.168.
Hope that clears things up for you :)
<Raises hand> "Mr. Roche, My brain is full. May I go home now?"
--- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
On Dec 6, 2018, at 10:23 AM, Ted Roche tedroche@gmail.com wrote:
"Where Do You Want To Go Today?"
One thing for sure - I know where I *don’t* want to go!
-- Ed Leafe
Cause, no one uses mapped drives any more, amirite?
There's absolutely no reason to use mapped drives in this day and age.
But it's one of a few ridiculous issues in 1803 and 1809, my favourite is the file association mechanism being broken in some cases, for example I like to have .TXT and .CSV open with Notepad++ (what lunatic would use Excel for CSV files?) but 1803 says noooo ...
On Fri, Dec 7, 2018 at 3:10 AM Alan Bourke alanpbourke@fastmail.fm wrote:
There's absolutely no reason to use mapped drives in this day and age.
What is the current best practice for accessing shared DBFs on a server?
But it's one of a few ridiculous issues in 1803 and 1809, my favourite is the file association mechanism being broken in some cases, for example I like to have .TXT and .CSV open with Notepad++ (what lunatic would use Excel for CSV files?) but 1803 says noooo ...
Yeah, that's dumb, too.
UNC paths.
use \myserver\myshare\mytable.dbf
open data "\myserver\my share with spaces in the name\mydatabase.dbc" use mytable
and so forth.
IMHO the one advantage of a mapped drive is if you have references to full paths stored anywhere, and you are running out of disk space or otherwise need to change to a different location/server, a single change to the drive mapping handles that migration. Having said that, if you're not living in the desktop/LAN world it's not all that useful.
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Alan Bourke Sent: Friday, December 7, 2018 10:27 AM To: profoxtech@leafe.com Subject: Re: [NF] Broken Windows
UNC paths.
use \myserver\myshare\mytable.dbf
open data "\myserver\my share with spaces in the name\mydatabase.dbc" use mytable
and so forth.
-- Alan Bourke alanpbourke (at) fastmail (dot) fm
On Fri, 7 Dec 2018, at 1:56 PM, Ted Roche wrote:
On Fri, Dec 7, 2018 at 3:10 AM Alan Bourke alanpbourke@fastmail.fm wrote:
There's absolutely no reason to use mapped drives in this day and age.
What is the current best practice for accessing shared DBFs on a server?
On 12/7/2018 10:26 AM, Alan Bourke wrote:
UNC paths.
use \myserver\myshare\mytable.dbf
I do use UNC at times, but what about accessing drives that require different logon credentials? I don't think I've tried it. Does a logon dialog appear?
I imagine that probably is not an issue in a corp setting that may use Active Directory or whatever the Linux equivalent is. But from what I see, mapping drives in a corp environment is a VERY common thing.
open data "\myserver\my share with spaces in the name\mydatabase.dbc" use mytable
and so forth.
-Charlie
On Sat, 8 Dec 2018, at 4:35 PM, Charlie-gm wrote:
I do use UNC at times, but what about accessing drives that require different logon credentials? I don't think I've tried it. Does a logon dialog appear?
Yes, you would get prompted for credentials which should then get remembered - but why would this happen in a properly configured Active Directory setup? The only time I see this is where somebody is trying to use the 'workgroups' level authentication on a small network.
But from what I see, mapping drives in a corp environment is a VERY common thing.
Maybe we move in different corporate environments! At a guess those with a lot of very legacy systems might be using them more.
On Fri, 7 Dec 2018 at 08:09, Alan Bourke alanpbourke@fastmail.fm wrote:
But it's one of a few ridiculous issues in 1803 and 1809, my favourite is the file association mechanism being broken in some cases, for example I like to have .TXT and .CSV open with Notepad++ (what lunatic would use Excel for CSV files?) but 1803 says noooo ...
That could explain why I can't associate .ZIP to 7-zip on a new machine I'm setting up...
On Fri, 7 Dec 2018, at 6:22 PM, Paul Hill wrote:
That could explain why I can't associate .ZIP to 7-zip on a new machine I'm setting up...
Yeah - think I hit that one too. Apparently they re-engineered the way the associations work internally to make it more secure, and ballsed it up.
-
Alan Bourke -
Charlie-gm -
Ed Leafe -
Fletcher Johnson -
John Weller -
Man-wai Chang -
mbsoftwaresolutions＠mbsoftwaresolutions.com -
Paul Hill -
Richard Kaye -
Stephen Russell -
Ted Roche -
Vince Teachout