What To Talk About?

Even though it's been a couple of weeks since I've last posted, I can't seem to think of something to talk about in this post. I think I'll just talk about what I've done this past week and what I've accomplished. This introduction doesn't seem to be getting any longer, so I guess I'll just head right into the meat of this post. Actually, I think what I'll do is start each paragraph with Sunday, Monday, Tuesday, Wednesday, etc., and then say what I did on that day.

Sunday: On Sunday, I helped out at my church's annual Fall Festival, and I worked with some other people at the produce stand outside by the CCD building. It was pretty boring, as I worked second shift, and there wasn't too much of a rush during that time. I got there around 1 PM, and I was done at about 4 PM. People mostly arrived in waves. It consisted of about 10-15 minutes of just standing there, and then 5 minutes of people standing all over it and looking to see what they wanted to purchase. The only thing that really sucked about the job was that half of the produce doesn't have a price label, so then about half the time people ask what the price of something is, I could do nothing but say "I'm sorry, I don't know.", even though I was working there. So, that was my Sunday, besides watching some football afterwards.

Monday: On Monday evening (being as Monday was school) I watched the Green Bay Packers take on the Seattle Seahawks on Monday Night Football. Without a doubt, that game was one of the worst-refereed games ever. Before that game started, however, was when I had found out the official referees were on strike and were negotiating a better contract with the NFL commissioner, so all current games were being reffed by replacement refs. Monday night was when it hit rock bottom. Almost all of the penalties called were called on the wrong team. Most of them were pass interference plays, and they were all against the Packers, when they were clearly against the Seahawks. The very last play of the game, the Seahawks QB threw a 20-some-yard Hail Mary TD, and there were 4 or 5 players that all went for it at once. M.D. Jennings and Golden Tate were the two closest players to the ball, and Jennings caught the ball, with Tate wrapping his right arm around it soon after. That is what I think confused the referees when they were determining if it was a touchdown or touchback, which would give GB the win. The one ref called a TD, while the other called a TB (touchback). I don't understand why the TD signal over-ruled the touchback. signal. They both raised their hands for their signals at roughly the same time, yet the TD won it somehow. Anyway, it was a bad play that caused the Packers to lose 12-14. I also went to the SLW before the game started.

Tuesday: On Tuesday, not a whole lot went on. I went to school, worked, did my band lesson, went home and did all the usual stuff. Nothing too exciting.

Wednesday: On Wednesday, we had a half day of school, so that was nice. At 6 PM I went to Pit Orchestra rehearsal until 9 PM, and I learned my part much better.

Thursday: Thursday wasn't too exciting either. I don't feel like writing much anymore, lol.

Friday: Well, today is Friday, and I've been doing a ton of coding for my site. I'm attempting to completely re-design it, and I'm in the process of that. So... yeah, that's all!

Mac vs. PC

One question that has always been unanswered for me is this: If a Macintosh can run the Windows OS legally, why can't a PC do the same thing? Of course, you can go right ahead and perform a hackintosh on your PC if you want to go through all of that trouble, but I just don't get why you can't legally run Mac OS X on a PC. Since it's not possible legally, I feel that Microsoft should be able to restrict Windows to only be run on PC's. Apple does the exact thing to Mac OS X, so why the hell can't Microsoft do the same for their OS? That whole deal makes no sense. 

What confuses me even more is Apple's Mac Mini. I don't understand if you can simply hook that up to a PC and simply install OS X on it, or what. If so, that's contradicting what Apple says in their EULA, with their system not being on PCs. If you read my post about my terrible hackintosh experience, I'll probably never go back to that ever again. I did find out about a YouTuber by the name of "cpukid00", and he knows pretty much everything there is to know about a hackintosh and how to make it work right. Even so, with all of his video tutorials showing you just how to install Snow Leopard with iBoot and all of those other programs, I don't know that I'd want to re-visit that world. Plus, I did some other research on if you can be caught by Apple for running a hackinstosh, and someone said that once in a while Macs will send information about the user's IP and whatnot, which would lead to Apple possibly finding out about it. 

Now, I may sound like an idiot, and that what I just said is not possible, as there are millions of people that run hackinstoshes day in and day out. The main reason why I wouldn't want to attempt another hackinstosh is because it takes too much knowing what you're doing while installing OS X and all of the post-installing shit that makes me not want to do it. For example, after you install all of it, when the computer restarts, you have to put the iBoot CD in quick enough to be able to actually boot into Snow Leopard, otherwise the computer won't boot into anything. The problem I had when I tried the process out, was that I had completely left out the fact that I needed to set up a bootloader that would tell the computer what to do before boot-up, therefore allowing me to boot into either Windows or Mac OS X. At the time, I had no idea what the hell a bootloader was, so I was freaking out when I got an error message when constantly rebooting after it didn't work. 

The guy who did all of those hackinstosh videos, Bob Roche, said that laptops are especially not good for hackinstoshing, as you can't very well handle a hard drive fail or get more hard drive space, like you could easily do with a desktop. Obviously, it's been done on laptops before, but you've really gotta be knowing your shit the entire time. I didn't, and that's what messed me up. I did maybe two or three web searches before I actually went through with it all. Roche also said that you need to be willing to tinker with your computer hardware and knowing what might go wrong and how to fix it. The most I know about computers is the actual OS and how it works, not so much with the hardware. Plus, I was too stupid to know that my Netbook would have never handled the Mac OS, as it's a Netbook - they barely handle Windows 7. Putting Mac on a Netbook like mine would be like trying to play GTA IV on it; it would freeze the second it's loaded up. 

Anyway, that's my side of Mac and why all of the legal stuff pisses me off.