Bible Code 2: The Countdown [Englisch] [Taschenbuch]

Why a new cover design for an old book that was already flawed? Bible Code III would have been published by now if this book did not have so many problems.

Drosnin's first Bible Code books got me so fired up about the possibility of a predictive Code that I actually quit my teaching job in Florida, and ran over to Israel and Egypt on a related expedition in 1999 (and again in 2005). Why? He claimed the future of the world, including an atomic holocaust, is encoded in Torah. As a U.S. military planner with Hebrew skills, I wanted to know if his predictions were valid. It seemed to me that if the Code were real, its most vital secret would be the location of the Ark. In 2008 I concluded that any idea of a general predictive Code needs to be modified in accordance with Talmudic principles and the concept of Free Will. Not everyone will find their name in the Bible Code. Further, Drosnin's original atomic holocaust warnings were neither statistically significant, nor accurate.

In Bible Code II, Drosnin gets hung up looking for the key to the Bible Code. He thinks it's in Lisan, Jordan (the Dead Sea area). But his supporting matrices are not significant. Nor did they include any requirement for course angles between places named to match what is seen on real world maps. In my own ARK CODE book, also available on Amazon.Com, you will fund redundant encoded maps that strongly suggest where Jeremiah hid the Ark of the Covenant when he was forced into exile in Egypt, near where local Bedouins believe Moses split the sea at Lake Bardawil. As for the Code Key that Drosnin sought, I have found matrices to indicate that he should have sought Baal Zephon (mentioned in Exodus 14:2; 14:9. and Numbers 33:7) for this purpose. The coordinates of interest for it are at 31-16 North, 33-03.5 East.

HOW MOST BIBLE CODE MAPS ARE ENCODED. Key site names are encoded in such manner as to have the angles between Jerusalem, Egyptian towns or sites, and the suspect Ark site, at 31-9 North, 33-4 East, exactly correspond to actual course headings on real world maps. The purpose of my book and web site has been to document these maps (found by myself and by Dr. Robert Haralick of the City University of New York Computer Science Graduate Studies Department), and to help facilitate actions required to investigate the site (and, of course - recover the Ark if it's there).

ARK CODE not only summarizes the ELS Maps I've found, but it also explores the expeditions I've taken to Egypt and meetings that I held with the Egyptian Government for the specific purpose of preventing the war that Drosnin warned about. There is still a good case for some predictive capability in the Torah Code, but you really have to master basic principles of statistics found in ARK CODE before running out to place any bets based on a Torah Code matrix. Drosnin supposedly has a Bible Code III book coming out, but the entire market for Bible Code books has largely dried up because he made so many wrong predictions. The future is not hard wired. If anything, actions that Drosnin took in meeting with Middle East politicians may have altered our time line and caused the world we live in to be so different from what he thought was encoded. If you must buy any Bible Code book from Drosnin, get his first book as a starting point, and note the divergence from what he predicted there for yourself. But if you really want to understand how the Code appears to work, and learn how to determine the statistical significance of a Bible Code matrix, buy ARK CODE.