|
Must we continue this NON "midrange technical" conversation"? Ron Adams Information Technology Group Crane Valves 9200 New Trails Dr. Suite 200 The Woodlands, TX 77385 |---------+------------------------------------> | | Vern Hamberg | | | <vhamberg@centerfieldtech| | | nology.com> | | | Sent by: | | | midrange-l-bounces@midran| | | ge.com | | | | | | | | | 09/02/2004 08:43 AM | | | Please respond to | | | Midrange Systems | | | Technical Discussion | | | | |---------+------------------------------------> >-------------------------------------------------------------------------------------------------------------------------| | | | To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> | | cc: | | Fax to: | | Subject: RE: The 666 mark | >-------------------------------------------------------------------------------------------------------------------------| The morbid interest of technical folk in this arcania is shown in that the main executable for dBase-III+ (at least) has something like "666 the mark of the beast" in the middle of it. At 08:29 AM 9/2/2004, you wrote: >Then shouldn't the number of the beast be 4095? > >Regards, > >Scott Ingvaldson >iSeries System Administrator >GuideOne Insurance Group > >-----Original Message----- >date: Wed, 1 Sep 2004 23:08:04 -0500 >from: "Milt Habeck" <mhabeck@xxxxxxxxxx> >subject: The 666 mark > ><Snip> >A subtle point: the Holy Bible was written in Hebrew & Greek and those >languages use letters to represent numbers. Sort of like A = 1, B = 2, >C = 3, D = 4, E = 5, and F = 6 (using the English alphabet as just an >illustration). So, the mark to look for isn't really "666" rather, it's >three >letters: like maybe "FFF" or it's equivalent in Hebrew or Greek. ></Snip> > >God bless, >Milt Habeck >Unbeaten Path >(888) 874-8008 >www.unpath.com > > >This message and accompanying documents are covered by the Electronic >Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and contains information >intended for the specified individual(s) only. This information is >confidential. If you are not the intended recipient or an agent responsible >for delivering it to the intended recipient, you are hereby notified that >you have received this document in error and that any review, dissemination, >copying, or the taking of any action based on the contents of this >information is strictly prohibited. If you have received this communication >in error, please notify us immediately by e-mail, and delete the original >message. > >-- >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list >To post a message email: MIDRANGE-L@xxxxxxxxxxxx >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/mailman/listinfo/midrange-l >or email: MIDRANGE-L-request@xxxxxxxxxxxx >Before posting, please take a moment to review the archives >at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.