Okay, I think that I might be the only person in Christendom who isn't impressed with the movie. I think it was well enough made, but it wasn't "all that"! Don't get me wrong, I enjoyed the movie (I saw it twice in the theater) but I walked away disappointed by the CGI during the combat sequences. Unfortunately, as one of only two really good epic Christian fiction/fantasy stories, we have to compare it to it's contemporary...Lord of The Rings. Oops!
While I felt that most of the CGI was well done, I can't help but feel that the combat scenes at the end were rushed and not very believable. The combat scenes from LoTR were fairly believable (understanding of course that Orcs and such don't really exist) and well integrated into the real world. The computer generated and the living world were messed so well in LoTR that it really raised the bar for all future CGI enhanced films. We have a higher standard and it will be hard to break if you are on a budget.
I understand, of course, that the producer of the movie isn't flush with money like Peter Jackson's production company is. Hopefully, the second Narnia movie will benefit from increased media exposure, that there will be sufficient money brought in from the profits from the first Narnia movie, and that Disney will infuse the production with lots of money and technical expertise. That should help it be a much better movie on par with the LoTR movies.
One can only hope. Until then, I will enjoy the DVD that my wife bought last night and continue treasuring the books and my overactive imagination.
Cheers
Friday, April 07, 2006
Wireless Networking
Well, I have just ordered a 512mb RAM module for my Apple iBook G3/600 (with 16 vram). That will max it out (640mb of RAM is going to be sweet!). I also ordered a usb wireless networking device (802.11g)...it doesn't have drivers for Unix-type OSes but the chipset maker does. I am really excited about being able to 'finally' connect to my wireless network (my wife's Dell has had that capability for seven or eight months!).
Speaking of wireless networks...I just secured the Netgear wireless router last week. What a pain. Well, setting it up wasn't the pain. The string that you have to add to a computer that connects wirelessly is the pain. I had a Microtel computer wired into the router and used it to set the system up. So, the string was visible when I set my wife's Dell up. No big deal, except that you have to add the string twice. Since it is obscured by ****, you can't verify that you've correctly inputted the string. Loads of fun. I then installed a wireless PCI card to the Microtel and had to log onto the router via the Dell. That took longer than I anticipated. After entering the security string about six or seven times, I as able to connect, wirelessly, to the internet...what joy! Of course, after I installed the drivers from the CD, I found out that the drivers conflict with Windows XP Service Pack 2. Nice. So, I tried downloading the drivers from the Netgear website...only, the computer kept rebooting automagically after about five minutes. Since the drivers weren't correct, the network connection speeds were miserable and the signal strength was pathetic (low strength and the computer was literally less than three feet away from the router!). So, using my brain, I booted the Dell, downloaded the drivers and transferred them to a 1 gig USB drive. After waiting for the Microtel to reboot (again), I transferred the drivers and unzipped them. Now I have to admit, Netgear has their stuff together. When you click on the install program, it asks you if you want to uninstall the drivers. Once it does that you have to click on the install program again to install the fresh drivers. That is a good idea. You don't have to worry about the old drivers hanging around somewhere causing conflicts with the new drivers. Well done, Netgear. Now the system is stable and the connection is fast. Sweet!
Well, that is it for now.
Cheers
Speaking of wireless networks...I just secured the Netgear wireless router last week. What a pain. Well, setting it up wasn't the pain. The string that you have to add to a computer that connects wirelessly is the pain. I had a Microtel computer wired into the router and used it to set the system up. So, the string was visible when I set my wife's Dell up. No big deal, except that you have to add the string twice. Since it is obscured by ****, you can't verify that you've correctly inputted the string. Loads of fun. I then installed a wireless PCI card to the Microtel and had to log onto the router via the Dell. That took longer than I anticipated. After entering the security string about six or seven times, I as able to connect, wirelessly, to the internet...what joy! Of course, after I installed the drivers from the CD, I found out that the drivers conflict with Windows XP Service Pack 2. Nice. So, I tried downloading the drivers from the Netgear website...only, the computer kept rebooting automagically after about five minutes. Since the drivers weren't correct, the network connection speeds were miserable and the signal strength was pathetic (low strength and the computer was literally less than three feet away from the router!). So, using my brain, I booted the Dell, downloaded the drivers and transferred them to a 1 gig USB drive. After waiting for the Microtel to reboot (again), I transferred the drivers and unzipped them. Now I have to admit, Netgear has their stuff together. When you click on the install program, it asks you if you want to uninstall the drivers. Once it does that you have to click on the install program again to install the fresh drivers. That is a good idea. You don't have to worry about the old drivers hanging around somewhere causing conflicts with the new drivers. Well done, Netgear. Now the system is stable and the connection is fast. Sweet!
Well, that is it for now.
Cheers
Subscribe to:
Posts (Atom)
