From: nospam <nospam@nospam.invalid>
Subject: Re: Lightroom Classic CC problem
Full headers:
From: nospam <nospam@nospam.invalid>
Subject: Re: Lightroom Classic CC problem
Date: Tue, 06 Feb 2018 13:19:57 -0500
Organization: A noiseless patient Spider
Lines: 51
Message-ID: <060220181319570370%nospam@nospam.invalid>
References: <> <p5cipj$o45$> <> <p5cre2$pc5$>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Injection-Info:; posting-host="f313d2e0ce2edb2e2e0daa63d5259352";
logging-data="20474"; mail-complaints-to="";posting-account="U2FsdGVkX18XsJ+GmVCeyO75ORM0VI/E"
User-Agent: Thoth/1.9.0 (Mac OS X)
Cancel-Lock: sha1:dh2ZT4A98eUHN4vldC08mkzI1DQ=
Print Article
Forward Article
In article <p5cre2$pc5$>, Mayayana<mayayana@invalid.nospam> wrote:

> | >   With Win10, you're running one of the test machines
> | > without getting paid for your trouble.
> |
> | True, but who would volunteer to work for a company like Microsoft
> | without getting paid?
>    You'd be surprised. I know I am. :)
>    Even with Win10 there are "early adopters" who are
> thrilled to get the latest version before anyone else
> and to imagine they're getting a pat on the head.

they're not working for microsoft.

>    Before Win10 there was no shortage of beta testers.

that's no different now.

> They feel important making bug reports. And if they
> write software then beta testing gives them early access
> to test their own product. Though that second reason
> doesn't hold water. There's little benefit in testing on
> a system that's still subject to change.


> | >   But it is worth searching. You'll find out a lot more
> | > that way then by looking specifically in Adobe forums
> | > or photo newsgroups, especially given that you don't
> | > know where the problem is coming from.
> |
> | Windows?
>    Windows. Printer drivers. Adobe software. Or 100
> other things. I once wrote a program that kept closing
> as soon as it started. I couldn't figure out why.

then you're not very good at writing or debugging software.

> It turned out the problem was that I was enumerating printer
> fonts at startup and if there was no printer connected
> that caused a crash without error. The problem is not
> always with the software that's crashing, and when it is
> the cause may be unexpected.

in other words, your bug.