I put the milk in the freezer for the week we were gone. When I got home I put it back into the fridge. It ended up taking 2 days to completely thaw. But the important question, what did it taste like? It tasted like it always does. I couldn't taste a difference, the texture was the same. So as far as I'm concerned, if you need to freeze skim milk it comes out fine in the end. Maybe if you freeze it for more than a week problems develop (such as funky flavors from the freezer). Also, make sure the container you freeze in has enough head room as most liquids expand when you freeze them.
Monday, December 31, 2012
Freezing Skim Milk
One of my favorite things in life is milk. There's nothing like a tall glass of cold milk. And one of the worst things is wasted milk. We recently left town for the holidays, but the day we left I still had several cartons of milk in the fridge. They were going to be bad by the time we got back, we couldn't take it with us, and I can't drink that much milk before we left. So I Googled to see if you could freeze milk. A lot of people said it worked, but that it changed the texture of the milk, giving it a grainy texture. But these people also said that it was the fat in the milk that caused this. Well I drink fat free (a.k.a. skim) milk. With no fat it should be fine, right? I figured it was worth a try.
Repairing Scratched Discs
Recently I bought a used Wii game, but when I tried the game out it wouldn't load. Looking at the disc is had quite a few scratches on the disc. Am I out of luck, or is there anything I can do to fix this? I've seen tons of fixes on the Internet using polish, toothpaste, wax, etc. I've tried some on the past with no success, so I wasn't wanting to try that again. But I have seen sellers on eBay that use professional machines to resurface damaged discs. I decided to give this a try and blog the results.
The process is simple. You buy the auction on eBay, they give you an address to mail your scratched disc to, they resurface the disc and mail it back to you. Pretty simple, and the turn around was quick too. I got my disc back in a few short days. But would it work? I put the disc back into my Wii and it works perfectly! Looking at the disc I'm not surprised it works, the process took away every single scratch. I wish I took a before picture, but now the disc looks brand new.
The best part is, this process is pretty cheap. It only costs $2.50 which includes resurfacing the disc and mailing it back to you. There are several sellers on eBay that offer this service, but I went with "euro-am." If you have scratched discs, keep this in mind as a relatively cheap way to fix the disc.
The process is simple. You buy the auction on eBay, they give you an address to mail your scratched disc to, they resurface the disc and mail it back to you. Pretty simple, and the turn around was quick too. I got my disc back in a few short days. But would it work? I put the disc back into my Wii and it works perfectly! Looking at the disc I'm not surprised it works, the process took away every single scratch. I wish I took a before picture, but now the disc looks brand new.
The best part is, this process is pretty cheap. It only costs $2.50 which includes resurfacing the disc and mailing it back to you. There are several sellers on eBay that offer this service, but I went with "euro-am." If you have scratched discs, keep this in mind as a relatively cheap way to fix the disc.
Sunday, December 30, 2012
SSID - to hide or not to hide?
If you have a home wireless network then you're probably familiar with the SSID field, and most wireless routers offer the option to hide the SSID for increased security. But is this really worth it?
When it comes to computers in general, and wireless networks specifically, I prefer to have as strong a security as possible. So I always use the most secure encryption and long complex passwords. By the same token I would choose to hide my SSID (or network name). I would never rely on a hidden SSID alone, as security through obscurity is not sufficient. But is a hidden SSID really any more secure? I've recently found programs like Inssider that will show you all networks in range, whether or not they are broadcasting their SSID. So a hidden SSID does not mean no one else can see your network nor does it mean they can't try and hack in.
So a hidden SSID is not any more secure. And as it turns out, a hidden SSID has negative side-effects.
1. Connection time
When your laptop, phone, tablet, etc. connects to the network it can actually take longer. This is because the device has to try additional tests to make sure the hidden network is indeed the network it's trying to connect to.
2. Battery life
It sounds odd at first, but hidden networks can actually use up more battery in your device. Your device is constantly searching for hidden networks that match the list of known hidden networks and trying to cnnect to them. This consumes processing power and wastes precious battery life.
Given this I've recently switched from hidden SSIDs to publicly visible SSIDs. Since the SSID is visible, I would make a recommendation. Don't put your name and/or street address in the SSID. If someone else sees a network "JamesSmith" or "17ElmStreet" then they know exactly whose network it is. Choose something obscure like "DeathStar" or "CherrySoda."
When it comes to computers in general, and wireless networks specifically, I prefer to have as strong a security as possible. So I always use the most secure encryption and long complex passwords. By the same token I would choose to hide my SSID (or network name). I would never rely on a hidden SSID alone, as security through obscurity is not sufficient. But is a hidden SSID really any more secure? I've recently found programs like Inssider that will show you all networks in range, whether or not they are broadcasting their SSID. So a hidden SSID does not mean no one else can see your network nor does it mean they can't try and hack in.
So a hidden SSID is not any more secure. And as it turns out, a hidden SSID has negative side-effects.
1. Connection time
When your laptop, phone, tablet, etc. connects to the network it can actually take longer. This is because the device has to try additional tests to make sure the hidden network is indeed the network it's trying to connect to.
2. Battery life
It sounds odd at first, but hidden networks can actually use up more battery in your device. Your device is constantly searching for hidden networks that match the list of known hidden networks and trying to cnnect to them. This consumes processing power and wastes precious battery life.
Given this I've recently switched from hidden SSIDs to publicly visible SSIDs. Since the SSID is visible, I would make a recommendation. Don't put your name and/or street address in the SSID. If someone else sees a network "JamesSmith" or "17ElmStreet" then they know exactly whose network it is. Choose something obscure like "DeathStar" or "CherrySoda."
Monday, December 17, 2012
XBox controller - Windows driver
In my last post I showed how I modded an original XBox controller for use on a PC. In this post I'll talk about the Windows driver. When you connect the controller to a computer, Windows recognizes the USB device but without a driver the controller is useless. If you search on the Internet you'll quickly find XBCD by redcl0ud. This is the original XBox controller driver, currently at version 1.07. According to the author this driver works on Windows XP, which is my OS of choice. So I downloaded the driver and tried it out. Unfortunately, the driver wouldn't load for me. XP accepted the driver, but after installation it said there was a problem with the device. I was convinced my soldering was fine, something must be wrong with the driver itself.
As it happens, the author provides the source code for the driver, and at work I recently had to write a device driver, so I have all the tools necessary to compile the driver. The first thing I noticed is the source is rather old - it hasn't been updated since 2005. Even if the driver works on XP, I can guaranty the driver won't work on 64-bit Windows. I decided to take the time to update the driver and produce version 1.08. Using newer tools from Microsoft I was able to fix a few problems in the driver's source code, correct issues in the driver INF file, and recompile for both 32-bit and 64-bit Windows. This updated driver works, I've tested it on XP, 2003, Vista, and Windows 7, both 32-bit and 64-bit. I'll make this new driver available to anyone who wants a copy, including the updated source code. You can download the driver here (link updated). This 7Zip file contains the unsigned 32 and 64-bit versions, the modified source code, and the tools necessary to sign the driver if you have your own digital certificate (read on).
No discussion of the driver would be complete without mentioning 64-bit drivers. Starting with Vista, Microsoft made a change to 64-bit Windows. All device drivers must be digitally signed using a what's called a cross-certificate. These certificates cost at least $100, and quite frankly I'm not going to spend my own money for a certificate so I can sign a free driver. So if you want to run this driver on 64-bit Windows Vista, 7, or 8 then you have two choices.
As it happens, the author provides the source code for the driver, and at work I recently had to write a device driver, so I have all the tools necessary to compile the driver. The first thing I noticed is the source is rather old - it hasn't been updated since 2005. Even if the driver works on XP, I can guaranty the driver won't work on 64-bit Windows. I decided to take the time to update the driver and produce version 1.08. Using newer tools from Microsoft I was able to fix a few problems in the driver's source code, correct issues in the driver INF file, and recompile for both 32-bit and 64-bit Windows. This updated driver works, I've tested it on XP, 2003, Vista, and Windows 7, both 32-bit and 64-bit. I'll make this new driver available to anyone who wants a copy, including the updated source code. You can download the driver here (link updated). This 7Zip file contains the unsigned 32 and 64-bit versions, the modified source code, and the tools necessary to sign the driver if you have your own digital certificate (read on).
No discussion of the driver would be complete without mentioning 64-bit drivers. Starting with Vista, Microsoft made a change to 64-bit Windows. All device drivers must be digitally signed using a what's called a cross-certificate. These certificates cost at least $100, and quite frankly I'm not going to spend my own money for a certificate so I can sign a free driver. So if you want to run this driver on 64-bit Windows Vista, 7, or 8 then you have two choices.
- The follow website has 4 different methods of loading uncertified drivers under Windows. The intent is this is used by developers who need to test their code. So it's up to you to make these changes to your own system. http://www.raymond.cc/blog/loading-unsigned-drivers-in-windows-7-and-vista-64-bit-x64/
- You can sign the driver yourself. Assuming you have access to a valid certificate, cross certificate from Microsoft, and know how to use the signtool.exe application then you can sign your own driver.
Sunday, December 16, 2012
XBox controller modded for PC use
Recent I was given an original XBox controller, specifically the Contoller S for XBox. This is the model 2 controller for the original XBox, the second model was slightly smaller and more ergonomic. The thing is, I don't have an XBox nor do I know anyone with an XBox, so I wasn't sure what to do with it. What's more, this controller lacked the other half of the breakaway cable, so it's not very useful even if I had an XBox. But then I learned the original XBox controllers are basically a USB controller and it's really easy to mod the controller for use on a computer. All you need to do is add a USB connector and load up a special driver.
To add the connector, there are several options. You can cut the cable and solder in a new end. You could solder in an entirely new cable. You could get the breakaway cable and solder in a new connector on that end. Looking in my box of spare parts I found a USB cable from an old keyboard, so I decided to solder in a completely new cable. After opening the controller you'll find the connector on the circuit board from the cable. The wires will be red, white, green, yellow, black (thin), and black (thick) in that order. If you look at a standard USB cable it will have red, white, green, black, and black. Literally you wire up the new connector color for color - i.e. red to red, white to white, and so on. As for the yellow cable which is a part of the XBox cable but not in a USB cable, you leave that wire empty. Lastly, not all USB cables will have two black wires, and that's alright. The black wires are the ground wires. If your USB cable doesn't have two black wires, just connect the one black wire you have to the controller. It doesn't matter which of the two you connect to.
Here's a picture of the controller after I soldered in the new wire. You can see the empty slot where the yellow wire was.
And here's a picture of the back side of the board, again note the empty hole where the yellow wire was.
Here's what the finished product looks like - an XBox controller with a USB plug.
In my next post I'll talk about loading the driver for Windows to recognize the controller.
To add the connector, there are several options. You can cut the cable and solder in a new end. You could solder in an entirely new cable. You could get the breakaway cable and solder in a new connector on that end. Looking in my box of spare parts I found a USB cable from an old keyboard, so I decided to solder in a completely new cable. After opening the controller you'll find the connector on the circuit board from the cable. The wires will be red, white, green, yellow, black (thin), and black (thick) in that order. If you look at a standard USB cable it will have red, white, green, black, and black. Literally you wire up the new connector color for color - i.e. red to red, white to white, and so on. As for the yellow cable which is a part of the XBox cable but not in a USB cable, you leave that wire empty. Lastly, not all USB cables will have two black wires, and that's alright. The black wires are the ground wires. If your USB cable doesn't have two black wires, just connect the one black wire you have to the controller. It doesn't matter which of the two you connect to.
Here's a picture of the controller after I soldered in the new wire. You can see the empty slot where the yellow wire was.
And here's a picture of the back side of the board, again note the empty hole where the yellow wire was.
Here's what the finished product looks like - an XBox controller with a USB plug.
In my next post I'll talk about loading the driver for Windows to recognize the controller.
Wednesday, December 12, 2012
Sugar
With kids in the house I find I'm more careful about reading labels in the grocery store. No big surprise, pretty much everything has too much sugar in it. But I recently came across several food items that shocked me.
Applesauce
I was shocked to learn that most applesauce brands add sugar. It's so bad in fact that it's very difficult to find applesauce without added sugar or corn syrup, unless you're shopping at a healthfood store or someplace like Trader Joes. Seriously, why do they add sugar to applesauce? Isn't applesauce sweet enough without added sugar? I guess the answer is no or else they wouldn't do it.
Peanut Butter
For a long time now I've only used "natural" peanut butter. Natural peanut butter can be made with a single ingredient - peanuts. Although sometimes they add salt or even a little bit of oil (to help stabilize it). I was recently on a trip shopping in a major chain grocery store for peanut butter. One major brand of natural peanut butter (I don't remember which one) boasted on the front of the label that it contained 90% peanuts. Um, natural peanut butter should be 100% peanuts, so what is this other 10%, and why are they so proud of it? Reading the ingredients the other 10% was sugar! Seriously, they put sugar in peanut butter!?! I couldn't believe it.
Applesauce
I was shocked to learn that most applesauce brands add sugar. It's so bad in fact that it's very difficult to find applesauce without added sugar or corn syrup, unless you're shopping at a healthfood store or someplace like Trader Joes. Seriously, why do they add sugar to applesauce? Isn't applesauce sweet enough without added sugar? I guess the answer is no or else they wouldn't do it.
Peanut Butter
For a long time now I've only used "natural" peanut butter. Natural peanut butter can be made with a single ingredient - peanuts. Although sometimes they add salt or even a little bit of oil (to help stabilize it). I was recently on a trip shopping in a major chain grocery store for peanut butter. One major brand of natural peanut butter (I don't remember which one) boasted on the front of the label that it contained 90% peanuts. Um, natural peanut butter should be 100% peanuts, so what is this other 10%, and why are they so proud of it? Reading the ingredients the other 10% was sugar! Seriously, they put sugar in peanut butter!?! I couldn't believe it.
Subscribe to:
Posts (Atom)