I finally decided to try out Boxee on my Apple TV and I will have to say I am very pleased. What is nice is how easy it was to get it installed. I didn’t have to take apart my Apple TV to get the software on there I just had to load the software with the patchstick then restart.
First thing I did updated my Apple TV to the latest update which was 2.3. Then I created the patchstick on my 2gb Samsung flash drive (I picked that up when I was in Korea last year). I did find a forum of a list of flash drives to use or not use. They say you should use better quality flash drives. I am not really sure why I guess maybe because the Apple TV boots off of the flash drive and the i/o reads need to have fast response times? Regardless many folks in the forum said that they were able to get the patchstick to work on the usb drives that were on the fail list so not sure what to really believe. Regardless mine worked fine.
Here is a video that shows you how to create a patchstick.
I used atvusb-creator-1.0.b10 to create my patchstick. After that was complete I followed the instructions from this video to get it on my Apple TV.
So after I let my Apple TV boot off of my patchstick then restarted I went and installed the latest code from Boxee. The one thing that wasn’t mentioned in the last video was that if you are running on Apple TV 2.3 you need to install the Launcher 2.3 software. You will see that on the same screen when you go and install Boxee. After I did that it all worked just fine. There are the usual bugs were if you try and quit Boxee my Apple TV might freeze or something so I just restarted it. Usual problems you might see during an alpha software base. Hulu streams seemed a little choppy but CBS stream was great. I haven’t had a chance to try anything else yet. ABC streams are on the Mac OSX version of Boxee and will be on the Apple TV version soon.
The Problem: Java project will not compile in Rational Application Developer due to a Internal error – the selected file is a system file that cannot be modified. It will be hidden.
All software has bugs in it but some can drive you crazy and create extra frustration and lose more of your valuable time. After moving all my source code into a new project in RAD I imported all my projects and added them to ClearCase. Next I tried to compile them getting a 3 similar errors. (Note: First lesson read the error carefully. Often while rushing through something to get it complete I don’t read the full error which would save me time.) Anyway when trying to compile I kept on getting this error.
The project was not built due to “Internal error – the selected file is a system file that cannot be modified. It will be hidden.”. Fix the problem, then try refreshing this project and building it since it may be inconsistent.
After about 30 mins of frustration and almost ready to shutdown for the night I found a little file in the directory where the java class files were suppose to be named copyarea.db which was put there by ClearCase. ClearCase makes this file ReadOnly thus not allowing RAD to delete it when it tries to compile my java code.
The Fix: Simple delete the file and refresh the project.
The Reason This Happened: I am not 100% certain but when I dumped all my code into the new project in RAD, ClearCase wanted to add all the code to the source repository so I let it the problem was it selected all the files which included the compiled class files. Since I didn’t want or need those files in ClearCase I chose to remove them from the repository by deleting the classes directory but it left the copyarea.db file in the parent directory. I am no expert on ClearCase but I couldn’t find a real easy way to remove the class files from the ClearCase server so I deleted the files through the ClearCase prospective view in RAD. This unloaded the files from ClearCase but also deletes the files on the local filesystem. If anyone knows a better way to remove them from ClearCase without deleting the files on the local system let me know. Of course like always I made a copy of the files before deleting so I could restore them.
Suggestion: At least name the file that RAD is having problems deleting then I can go straight to the file the error never mentions the name of the file or the directory.
Recent Comments