I have some tech stuff to blog about:

CISSP

First, as some of you know, I’ve been studying very hard for the past few months for the CISSP examination, which turned out to be a big waste of time since most of what I studied was material NOT on the exam. I woke up early this morning, drove to San Antonio, sat down to take the test at 8:45 AM and didn’t leave till 2:30 PM. It is by far the hardest written exam I’ve ever taken. Also, they must have recently changed the structure of the exam because I was expecting to see a lot more technical questions, and there were around 5 out of 250. At least I know I got 5 of the questions right! I won’t find out what my score is for a while. They told me up to 6 weeks, but I’m sure I’ll blog or twit about it as soon as the results come in.

Secondly, I have to apologize for the most recent podcast.  I forgot that my R-09 was set to record to MP3 instead of WAV. This got changed when I used it to record a practice for the upcoming Austin Jazz Music Festival gig next weekend and I needed extra recording time. Of course, an R-09HR with a 32GB SD Card would fix this. Okay, I pledge to use any donations minus 10% for tithe towards the purchase of one! 🙂 I’ve been listening to the podcast as I write this post and I’ve noticed that it has a darker sound than my previous podcasts. I had the R-09 positioned like I always do. It either had to be converting MP3 to WAV while importing the audio into Logic Pro, then back to MP3 for the post, or the way the R-09 handles recording to MP3. There may have been some stuff I could have done with EQ, but initially I didn’t really hear any difference on my studio monitors. I should have done a comparison with previous podcast audio prior to bouncing… Lesson learned.

Lastly, as you may have heard, the iPhone 3G signal problem has been narrowed down to the Infineon chipset used in the manufacturing of the new iPhone. Apple has been very quiet about this whole thing, but Steve Jobs wrote a letter to some complaining customers that this issue affects approximately 2% of iPhone 3G owners which comes out to around 60,000 iPhones. Personally, I believe it’s much more than that since I haven’t seen an iPhone 3G that didn’t have the same issue as mine, plus like I mentioned before, I’m on my 3rd one. On a positive note, Jobs assured the customers in the letter that this issue can be resolved with a firmware update. Unfortunately, the recent 2.0.2 update didn’t resolve it, although it did fix some problems I was having with software hanging and GPS seems to come up faster. I really want my 3G though! Come on Apple – help out a loyal fan!