On Tue, 30 May 2023 09:38:37 GMT, Cindy Hamilton wrote:

> On 2023-05-29, Sqwertz <sqwertzme@gmail.compost> wrote:
>> On Mon, 29 May 2023 09:00:34 GMT, Cindy Hamilton wrote:
>>
>>> On 2023-05-29, Sqwertz <sqwertzme@gmail.compost> wrote:
>>>> On Sun, 28 May 2023 09:43:37 -0400, jmcquown wrote:
>>>>
>>>>> This one is written in my mom's handwriting on a very old small piece of
>>>>> paper scratch paper.
>>>>>
>>>>> Ham Loaf
>>>>>
>>>>> 1-1/2 lb. ground pork
>>>>> 1-1/2 lb. ground ham
>>>>> 1 c. breadcrumbs
>>>>> 1 c. milk
>>>>> 2 eggs, beaten
>>>>>
>>>>> Basting mixture:
>>>>> 1 c. brown sugar
>>>>> 1/4 c. vinegar
>>>>> teaspoon mustard
>>>>>
>>>>> Cook slow, burns easily. Baste loaf with mixture.
>>>>>
>>>>> Yeah, I definitely don't remember this. LOL
>>>>
>>>> This was probably before city hams were "fully cooked" and "Ready
>>>> to eat".
>>>>
>>>> But it still sounds pretty horrible. "Cook slow" is an
>>>> interesting term by itself. Drop the "S" and it makes a little
>>>> more sense.
>>>
>>> It makes sense as is. Have you never hear of a "slow oven"?
>>>
>>> https://www.merriam-webster.com/dictionary/slow%20oven
>>
>> The recipe says nothing about an oven - unlike your term.
>
> It's a loaf. How else would a 1950s-1960s housewife cook it?

In a Dutch oven per it's time and place of origin. And it would
work better there than in an oven.

Detroit? nah.

-sw

Sqwertz <sqwertzme@gmail.compost> wrote:

>...
> In a Dutch oven per it's time and place of origin. And it would
> work better there than in an oven.

This tread started in rec.food.cooking. Oops. Keep it there.

All other messages specified "Newsgroups: rec.food.cooking". Only for
this one of yours did the newsgroup change (to news.software.readers).
Off-topic here.

On Wed, 31 May 2023 00:07:14 -0500, VanguardLH wrote:

> Sqwertz <sqwertzme@gmail.compost> wrote:
>
>>...
>> In a Dutch oven per it's time and place of origin. And it would
>> work better there than in an oven.
>
> This tread started in rec.food.cooking. Oops. Keep it there.
>
> All other messages specified "Newsgroups: rec.food.cooking". Only for
> this one of yours did the newsgroup change (to news.software.readers).
> Off-topic here.

Suck it up. Ban me. Whatever. Dialog is acting weird lately -
like it's running on an 8086. Slow drawing the screen and slow
responding to keystrokes and mouse clicks - but not consuming any
abnormal CPU. How this got redirected is anyone's guess.

The database is small compared to what I've had in the past, but
it was just compacted for shits and grins.

Don't try my patience or I'll flounce out of here and then where
would y'all be? (that was sarcasm for the impaired).

-sw

On Wed, 31 May 2023 02:21:33 -0500, Sqwertz <sqwertzme@gmail.compost>
wrote:

>Suck it up. Ban me. Whatever. Dialog is acting weird lately -
>like it's running on an 8086. Slow drawing the screen and slow
>responding to keystrokes and mouse clicks - but not consuming any
>abnormal CPU. How this got redirected is anyone's guess.

Your PC - have you tried turning it off - waiting 10 seconds - then
turning it baxk on? :-)

Sqwertz <sqwertzme@gmail.compost> wrote:

> On Wed, 31 May 2023 00:07:14 -0500, VanguardLH wrote:
>
>> Sqwertz <sqwertzme@gmail.compost> wrote:
>>
>>>...
>>> In a Dutch oven per it's time and place of origin. And it would
>>> work better there than in an oven.
>>
>> This tread started in rec.food.cooking. Oops. Keep it there.
>>
>> All other messages specified "Newsgroups: rec.food.cooking". Only for
>> this one of yours did the newsgroup change (to news.software.readers).
>> Off-topic here.
>
> Suck it up. Ban me. Whatever. Dialog is acting weird lately -
> like it's running on an 8086. Slow drawing the screen and slow
> responding to keystrokes and mouse clicks - but not consuming any
> abnormal CPU. How this got redirected is anyone's guess.
>
> The database is small compared to what I've had in the past, but
> it was just compacted for shits and grins.
>
> Don't try my patience or I'll flounce out of here and then where
> would y'all be? (that was sarcasm for the impaired).
>
> -sw

In Dialog, and other NNTP clients, I thought the cursor was focused
where I was looking instead of where it really was. Focus was on the
Newsgroups header in the compose form, so when I went to scroll the page
it was the Newsgroup field that ended up scrolling through different
newsgroups. Plenty of ways for the user to screw up, but the client is
simply going to specify the Newsgroups value it was told to use. The
client specifies the Newsgroups header's value on its submission to the
server. Somehow you screwed up the Newsgroups header. Maybe it was
because Dialog was jittery, stalling, or for whatever was causing your
problems when using it, but the final analysis is you changed the
Newsgroups value in the compose form, so that is what Dialog used when
it specified that header value in its submit to the server.

Instead of apologizing for posting into the wrong newsgroup, you get a
holier-than-thou attitude that it could never be your fault, and surely
the fault was with the client. I suppose you could blame the NNTP
server, too. Or gamma rays from the sun flipping some bits in your TCP
packet. Nope, your fault. You could repost your article, but this time
check the Newsgroups field in the compose form before clicking Send. I
see you did half that task by changing Newsgroups to rec.food.cooking,
but you still chose to include news.software.readers. Stop trying to
pass the buck, and just repost your original article to the cooking
newsgroup, and stop posted here in the readers newsgroup. Copy your
article's body from here, go to the cooking newsgroup, click on Reply to
the appropriate thread, and paste your content into the new compose
form, and be sure to submit to the cooking newsgroup.