Re: [NF] Broken Windows

2018-12-10 Thread Alan Bourke
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 -

Re: [NF] Broken Windows

2018-12-10 Thread Alan Bourke
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.

Re: [NF] Broken Windows

2018-12-08 Thread Charlie-gm
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

Re: [NF] Broken Windows

2018-12-07 Thread Paul Hill
On Fri, 7 Dec 2018 at 08:09, Alan Bourke 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 >

RE: [NF] Broken Windows

2018-12-07 Thread Richard Kaye
in the desktop/LAN world it's not all that useful. -- rk -Original Message- From: ProfoxTech On Behalf Of Alan Bourke Sent: Friday, December 7, 2018 10:27 AM To: profoxt...@leafe.com Subject: Re: [NF] Broken Windows UNC paths. use \\myserver\myshare\mytable.dbf open data

Re: [NF] Broken Windows

2018-12-07 Thread Alan Bourke
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

Re: [NF] Broken Windows

2018-12-07 Thread Ted Roche
On Fri, Dec 7, 2018 at 3:10 AM Alan Bourke 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

Re: [NF] Broken Windows

2018-12-07 Thread Alan Bourke
> 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

Re: [NF] Broken Windows

2018-12-06 Thread Ed Leafe
On Dec 6, 2018, at 10:23 AM, Ted Roche wrote: > > "Where Do You Want To Go Today?" One thing for sure - I know where I *don’t* want to go! -- Ed Leafe ___ Post Messages to: ProFox@leafe.com Subscription Maintenance:

Re: [NF] Broken Windows

2018-12-06 Thread Vince Teachout
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

Re: [NF] Broken Windows

2018-12-06 Thread Ted Roche
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

Re: [NF] Broken Windows

2018-12-06 Thread Ed Leafe
On Dec 6, 2018, at 9:53 AM, Ted Roche wrote: > > MSFT continues to beat the dead horse of Windows 1809 Is that the distant ancestor of Windows (19)95? -- Ed Leafe ___ Post Messages to: ProFox@leafe.com Subscription Maintenance:

Re: [NF] Broken Windows

2018-12-06 Thread Ted Roche
- cell > > > > -Original Message- > > From: ProFox [mailto:profox-boun...@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 a

Re: [NF] Broken Windows

2018-10-30 Thread Alan Bourke
e.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 wrote: > > > > > Which means Micro$oft might need to rewrite it again? ;) > >

Re: [NF] Broken Windows

2018-10-30 Thread Ted Roche
On Mon, Oct 29, 2018 at 8:12 PM Fletcher Johnson 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

RE: [NF] Broken Windows

2018-10-29 Thread Fletcher Johnson
/fletcherJ twitter.com/svcsug strava.com/athletes/fletcherjohnson 408-946-0960 - work 408-781-2345 - cell -Original Message- From: ProFox [mailto:profox-boun...@leafe.com] On Behalf Of Ted Roche Sent: Thursday, October 25, 2018 7:34 AM To: profox@leafe.com Subject: Re: [NF] Broken Windows

Re: [NF] Broken Windows

2018-10-25 Thread mbsoftwaresolutions
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

Re: [NF] Broken Windows

2018-10-25 Thread Ted Roche
On Thu, Oct 25, 2018 at 10:53 AM Alan Bourke 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." -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com --- StripMime Report

Re: [NF] Broken Windows

2018-10-25 Thread Fernando D. Bozzo
Yes, it has, it's called 7za and is open source too. El jue., 25 oct. 2018 15:27, Man-wai Chang escribió: > On Wed, Oct 24, 2018 at 9:46 AM Gene Wirchenko wrote: > > > > > > I am using PKZIP version 2.04g. At 25 years old, it may be > > older than some of those Microsoft programmers.

Re: [NF] Broken Windows

2018-10-25 Thread Alan Bourke
> Win32s I remember that piece of crap - trying to get a Filemaker application working with it. -- Alan Bourke alanpbourke (at) fastmail (dot) fm ___ Post Messages to: ProFox@leafe.com Subscription Maintenance:

Re: [NF] Broken Windows

2018-10-25 Thread Ted Roche
On Thu, Oct 25, 2018 at 9:28 AM Man-wai Chang 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,

Re: [NF] Broken Windows

2018-10-25 Thread Man-wai Chang
On Wed, Oct 24, 2018 at 4:09 AM Ted Roche 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

Re: [NF] Broken Windows

2018-10-25 Thread Man-wai Chang
On Wed, Oct 24, 2018 at 9:46 AM Gene Wirchenko wrote: > > > I am using PKZIP version 2.04g. At 25 years old, it may be > older than some of those Microsoft programmers. It might work better, too. > 7-zip is fine! I think it has a command-line version. -- .~. Might, Courage, Vision.

Re: [NF] Broken Windows

2018-10-25 Thread Ted Roche
On Wed, Oct 24, 2018 at 9:50 PM Gene Wirchenko wrote: > Gene "straight over or with a bit of a curve?" > Spin. It's all in the wrist. -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text

Re: [NF] Broken Windows

2018-10-24 Thread Gene Wirchenko
At 04:08 2018-10-24, Ted Roche wrote: [snip] "Throw it over the wall and see how loud they scream" is not a testing methodology. Sure it is. It works great for testing a heuristic-based targeting system. Sincerely, Gene "straight over or with a bit of a curve?" Wirchenko

RE: [NF] Broken Windows

2018-10-24 Thread John Weller
"Throw it over the wall and see how loud they scream" is not a testing methodology. Love it! John Weller ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list:

Re: [NF] Broken Windows

2018-10-24 Thread Stephen Russell
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

Re: [NF] Broken Windows

2018-10-24 Thread mbsoftwaresolutions
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

Re: [NF] Broken Windows

2018-10-24 Thread Ted Roche
On Wed, Oct 24, 2018 at 4:51 AM Alan Bourke 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

Re: [NF] Broken Windows

2018-10-24 Thread Alan Bourke
> 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

Re: [NF] Broken Windows

2018-10-23 Thread Gene Wirchenko
At 13:09 2018-10-23, Ted Roche wrote: Something is seriously wrong at MSFT. No VFP development. What? There is more? https://www.thurrott.com/windows/windows-10/189344/windows-10-version-1809-suffers-from-yet-another-data-loss-bug I just read another article on this and

[NF] Broken Windows

2018-10-23 Thread Ted Roche
Something is seriously wrong at MSFT. https://www.thurrott.com/windows/windows-10/189344/windows-10-version-1809-suffers-from-yet-another-data-loss-bug 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