• Meal-Master

    From Dave Drum@1:3634/12 to Sean Dennis on Sat Feb 5 05:55:00 2022
    Sean Dennis wrote to Dave Drum <=-

    You left off a couple letters there. Bv)>

    I'm the moderator so I try to be a good example but yes, those letters were assumed. <G>

    I thought I had a recipe somewhere for good ol' SOS but this will have
    to do for now:

    MMMMM----- Recipe via Meal-Master (tm) v8.06

    Title: Hen on a Shingle
    Categories: Chicken
    Yield: 8 Servings

    Here's a recipe for *real* SOS for your collection (although it isn't
    called SOS) ...

    MMMMM----- Recipe via Meal-Master (tm) v8.06

    Title: Creamed Chipped Beef *
    Categories: Beef, Dairy, Breads
    Yield: 4 Servings

    2 tb Butter
    2 tb A-P flour
    1 1/2 c Milk
    2 1/4 oz Jar ARMOUR STAR Sliced Dried
    - Beef; rinsed, chopped
    1/2 ts Prepared yellow mustard
    8 sl White bread; toasted

    * Known in the US military services worldwide as
    Foreskins on Toast

    Melt butter in saucepan. Add flour and cook 1 minute.
    Add milk all at once. Cook and stir until thickened
    and bubbly. Add beef and mustard and heat through.

    Serve over toast with a side of corned beef hash.

    Makes 1 1/2 cups

    FROM: http://www.armour-star.com

    Uncle Dirty Dave's Kitchen

    MMMMM


    ... I went to a White People's restaurant; the mayo was so mayonnaisey.
    --- MultiMail/Win v0.52
    * Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)
  • From Sam Penwright@1:123/120 to Dave Drum on Sat Feb 5 10:14:56 2022
    I'm the moderator so I try to be a good example but yes, those
    letters
    were assumed. <G>
    I thought I had a recipe somewhere for good ol' SOS but this will
    have
    to do for now:

    MMMMM----- Recipe via Meal-Master (tm) v8.06
    Hmm wrong board for this isnt it 8)
    Sam


    Bye for now...
    Sam

    --- Ezycom V3.00 01FB064B
    * Origin: Deep Space Gateway BBS Running EZYCOM V3.0 (1:123/120)
  • From mark lewis@1:3634/12.73 to Sam Penwright on Sun Feb 6 06:01:10 2022

    On 2022 Feb 05 10:14:56, you wrote to Dave Drum:

    MMMMM----- Recipe via Meal-Master (tm) v8.06
    Hmm wrong board for this isnt it 8)

    this was a classic QWK areas shifting problem that happens when areas are added or moved... if QWK used actual area tags instead of numbers, this wouldn't happen but it is long past the time when this could have been fixed in the implementation...

    )\/(ark

    "The soul of a small kitten in the body of a mighty dragon. Look on my majesty, ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a shiny thing!"
    ... Senior Campbell's NEW Large Type Alphabet Soup!!!
    ---
    * Origin: (1:3634/12.73)
  • From August Abolins@1:153/757.21 to mark lewis on Sun Feb 6 13:24:00 2022
    Hello mark!

    ** On Sunday 06.02.22 - 06:01, you wrote to Sam Penwright:

    MMMMM----- Recipe via Meal-Master (tm) v8.06
    Hmm wrong board for this isnt it 8)

    this was a classic QWK areas shifting problem that happens
    when areas are added or moved... if QWK used actual area
    tags instead of numbers, this wouldn't happen but it is
    long past the time when this could have been fixed in the implementation...

    QWK system/distribution has "classic" problems? I thought that
    QWKnet was promoted as perfection. ;) :/ :D



    --
    ../|ug

    --- OpenXP 5.0.51
    * Origin: My Westcoast Point (1:153/757.21)
  • From mark lewis@1:3634/12.73 to August Abolins on Mon Feb 7 02:40:20 2022

    On 2022 Feb 06 13:24:00, you wrote to me:

    MMMMM----- Recipe via Meal-Master (tm) v8.06
    Hmm wrong board for this isnt it 8)

    this was a classic QWK areas shifting problem that happens when areas
    are added or moved... if QWK used actual area tags instead of
    numbers, this wouldn't happen but it is long past the time when this
    could have been fixed in the implementation...

    QWK system/distribution has "classic" problems?

    it is a long-standing (aka classic) problem for QWK setups... QWK uses message area numbers to identify message areas... if a BBS adds a message area, all the areas after it are pushed down another number... so when a user has written a message in area #4 and the BBS has added a new area as #3, the user's message is posted to the new #4 instead of the old one which is now #5...

    eg:
    original:
    area#1
    area#2
    area#3
    area#4
    area#5

    now insert a new #3...

    area#1 -> area#1
    area#2 -> area#2
    new#3 -> area#3 or area#3 -> area#3
    area#3 -> area#4 or new#3 -> area#4
    area#4 -> area#5
    area#5 -> area#6

    you get the same type of problem when areas are removed, too... it is especially noticible on systems that prefer to have their areas listed alphabetically instead of in creation order...

    I thought that QWKnet was promoted as perfection. ;) :/ :D

    while i understand your statement is a joke, QWKNetworking is not the same thing... it may have similar problems with message area numbers but it is used for BBS<->BBS message exchanges... not BBS<>user exchanges...

    )\/(ark

    "The soul of a small kitten in the body of a mighty dragon. Look on my majesty, ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a shiny thing!"
    ... Tradition is a guide and not a jailer.
    ---
    * Origin: (1:3634/12.73)
  • From Rob Swindell@1:103/705 to mark lewis on Mon Feb 7 01:17:22 2022
    Re: a classic QWK areas shifting problem
    By: mark lewis to August Abolins on Mon Feb 07 2022 02:40 am


    On 2022 Feb 06 13:24:00, you wrote to me:

    MMMMM----- Recipe via Meal-Master (tm) v8.06
    Hmm wrong board for this isnt it 8)

    this was a classic QWK areas shifting problem that happens when areas
    are added or moved... if QWK used actual area tags instead of
    numbers, this wouldn't happen but it is long past the time when this
    could have been fixed in the implementation...

    QWK system/distribution has "classic" problems?

    it is a long-standing (aka classic) problem for QWK setups... QWK uses message area numbers to identify message areas... if a BBS adds a message area, all the areas after it are pushed down another number... so when a user has written a message in area #4 and the BBS has added a new area as #3, the user's message is posted to the new #4 instead of the old one which is now #5...

    Some BBSes may work that way, but not all. Synchronet, for example, has long supported 'static QWK conference number' assignment, so re-arrangement of message areas by the sysop does not have to mess-up users' (or QWKnet nodes') pending REP packets (resulting in the problem you described).
    --
    digital man (rob)

    This Is Spinal Tap quote #25:
    Viv Savage: Have... a good... time... all the time. That's my philosophy. Norco, CA WX: 60.1øF, 18.0% humidity, 0 mph NE wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From August Abolins@1:153/757.21 to mark lewis on Mon Feb 7 09:46:00 2022
    Hello mark lewis!

    ** On Monday 07.02.22 - 02:40, mark lewis wrote to August Abolins:

    .. QWK uses message area numbers to identify message
    areas... if a BBS adds a message area, all the areas after
    it are pushed down another number... [...]

    eg: [...]

    Thx for illustrating that.

    ..QWKNetworking is not the same thing... it may have
    similar problems with message area numbers but it is used
    for BBS<->BBS message exchanges... not BBS<>user
    exchanges...

    My bad. I assumed that the "problem" would then traverse the
    network. But it's really just one BBS encountered the shift
    problem.


    --
    ../|ug

    --- OpenXP 5.0.51
    * Origin: My Westcoast Point (1:153/757.21)
  • From August Abolins@1:153/757.21 to Rob Swindell on Mon Feb 7 09:49:00 2022
    Hello Rob Swindell!

    ** On Monday 07.02.22 - 01:17, Rob Swindell wrote to mark lewis:

    QWK system/distribution has "classic" problems?

    it is a long-standing (aka classic) problem for QWK
    setups... QWK uses message area numbers to identify message
    areas... if a BBS adds a message area, all the areas after
    it are pushed down another number...

    Some BBSes may work that way, but not all. Synchronet, for
    example, has long supported 'static QWK conference number'
    assignment, so re-arrangement of message areas by the
    sysop does not have to mess-up users' (or QWKnet nodes')
    pending REP packets (resulting in the problem you
    described). --

    Ah.. then I must update my commentary: Synchronet-QWKnet
    systems are near perfection. ? :D

    --
    ../|ug

    --- OpenXP 5.0.51
    * Origin: My Westcoast Point (1:153/757.21)
  • From Rob Swindell@1:103/705 to August Abolins on Mon Feb 7 12:36:57 2022
    Re: a classic QWK areas shifting problem
    By: August Abolins to Rob Swindell on Mon Feb 07 2022 09:49 am

    Ah.. then I must update my commentary: Synchronet-QWKnet
    systems are near perfection. ? :D

    I went to up-vote your message, but alas, FTN doesn't support message-voting. :-)
    --
    digital man (rob)

    Rush quote #3:
    The men who hold high places must be the ones who start... Closer to the Heart Norco, CA WX: 75.6øF, 13.0% humidity, 1 mph E wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)