I like the story of reductionist debug, how you distil the problem at each stage, partitioning into what the problem cannot be and what the problem might be. So finally you converged on the ini file, and after the fact it seems so easy to say 'well of course the problem was in the ini file', but was it? As a hardware guy I'm sure you will like the analogy of repairing a cable with break. Best bet is cut it in the middle and one part will surely work. But usually the break is near one end. But which end? Your story proves your logic and method worked, but when you nailed the sucker it was at the wrong end, and you had a whole pile of chopped up bits :)
Andy

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.