• St. Basil 02

    From Dave Drum@1:3634/12 to All on Thu Mar 21 06:05:00 2019
    MMMMM----- Recipe via Meal-Master (tm) v8.06

    Title: Basil Pesto
    Categories: Sauces, Herbs, Cheese, Nuts, Citrus
    Yield: 16 Servings

    2 tb Pine nuts; toasted
    2 lg Garlic cloves
    2 3/4 c Fresh basil leaves
    2 tb Grated fresh Parmesan cheese
    2 ts Lemon juice
    3 tb Extra-virgin olive oil

    Drop pine nuts and garlic through food chute with food
    processor on, and process until minced. Add basil, cheese,
    and lemon juice; process until finely minced. With
    processor on, slowly pour oil through food chute; process
    until well-blended. Spoon into a zip-top heavy-duty
    plastic bag; store in refrigerator.

    Yield: 1 cup (serving size: 1 tablespoon).

    Recipe By: Cooking Light, Sept. 1995

    Uncle Dirty Dave's Kitchen

    MMMMM

    ... If all is not lost, then where is it?
    --- MultiMail/Win32 v0.49
    * Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)
  • From Mike Powell@1:2320/105 to Dave Drum on Fri Mar 22 18:24:00 2019
    @MSGID: <5C94F8DA.26.ham-tech@capitolcityonline.net>
    MMMMM----- Recipe via Meal-Master (tm) v8.06

    * Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

    For some reason, these are showing up in the HAM TECH echo here?

    Mike

    ---
    * SLMR 2.1a * Can you repeat the part after 'Listen very carefully'?
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)
  • From Mark Lewis@1:3634/12.73 to Mike Powell on Sat Mar 23 11:57:12 2019

    On 2019 Mar 22 18:20:00, you wrote to DAVE DRUM:

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

    * Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

    For some reason, these are showing up in the HAM TECH echo here?

    my system added new message areas which knocked a few QWK areas to a different area number... dave just didn't catch the change bulletin which was probably my fault because it is displayed during logon all the time right now instead of only when new areas have been added...

    i'm not sure how to handle that yet but more code will have to be employed to check the user's last logon date/time with the date/time of something else, maybe the "bulletin" itself, indicating when the change too place so it is only displayed to users that haven't seen it...

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... Mashed potatoes with skim milk is like a sports car with an automatic.
    ---
    * Origin: (1:3634/12.73)
  • From Tony Langdon@3:633/410 to Mark Lewis on Sun Mar 24 08:24:00 2019
    On 03-23-19 11:53, mark lewis wrote to Mike Powell <=-



    my system added new message areas which knocked a few QWK areas to a different area number... dave just didn't catch the change bulletin
    which was probably my fault because it is displayed during logon all
    the time right now instead of only when new areas have been added...

    Hmm, you need to setup static conferences numbers on your QWK hub?


    ... God is dead. But don't worry - the Virgin Mary is pregnant again.
    === MultiMail/Linux v0.51
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From Mark Lewis@1:3634/12.73 to Tony Langdon on Sun Mar 24 13:01:02 2019

    On 2019 Mar 24 08:34:00, you wrote to me:

    my system added new message areas which knocked a few QWK areas to a
    different area number... dave just didn't catch the change bulletin
    which was probably my fault because it is displayed during logon all
    the time right now instead of only when new areas have been added...

    Hmm, you need to setup static conferences numbers on your QWK hub?

    i'm not a QWK hub... it was a user uploading QWK mail before checking that the conference numbers were still accurate for the areas they were posting in... i don't even know what numbers they have without going into scfg and wading through all the areas looking specifically for them...

    static would be good, though... i'm concerned with how they would be listed on the user's end when i insert new areas into the config in alphabetical order... then there's the same problem but in reverse when areas are removed...

    these two problems (above) are one of the main reasons why i much prefer FTN echotags over QWK area numbers... the numbers can change but with echotags it doesn't matter what order they are in, the tag is always used so adding/removing areas doesn't lead to messages being posted into the wrong areas...

    we probably should move this over to one of the sbbs areas, though...

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... It is better to die on your feet than to live on your knees.
    ---
    * Origin: (1:3634/12.73)
  • From Richard Menedetter@2:310/31 to Mark Lewis on Sun Mar 24 22:45:54 2019
    Hi mark!

    24 Mar 2019 12:57, from mark lewis -> Tony Langdon:

    these two problems (above) are one of the main reasons why i much
    prefer FTN echotags over QWK area numbers...

    I could not agree more.

    CU, Ricsi

    ... When the gods want to punish you, they answer your prayers. -O. Wilde
    --- GoldED+/LNX
    * Origin: A good husband should be deaf and a good wife blind. (2:310/31)
  • From Tony Langdon@3:633/410 to Mark Lewis on Mon Mar 25 09:34:00 2019
    On 03-24-19 12:57, mark lewis wrote to Tony Langdon <=-

    i'm not a QWK hub... it was a user uploading QWK mail before checking
    that the conference numbers were still accurate for the areas they were posting in... i don't even know what numbers they have without going
    into scfg and wading through all the areas looking specifically for them...

    Ahh, OK, that'll do it too. I've done that to myself by accident a couple of times lol

    static would be good, though... i'm concerned with how they would be listed on the user's end when i insert new areas into the config in alphabetical order... then there's the same problem but in reverse when areas are removed...

    I add new areas at the end where possible. I still use dynamic conference numbers for non networked nets and use static numbers for the QWK networks.

    these two problems (above) are one of the main reasons why i much
    prefer FTN echotags over QWK area numbers... the numbers can change but with echotags it doesn't matter what order they are in, the tag is
    always used so adding/removing areas doesn't lead to messages being
    posted into the wrong areas...

    You can set your QWK numbers to be static. And don't use consecutive numbers, if you want to be able to insert conferences between them.

    we probably should move this over to one of the sbbs areas, though...

    Feel free to, I am linked up. :)


    ... If everything seems to go right, check your zipper.
    === MultiMail/Win v0.51
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)