Tuesday, June 11, 2013
Saturday, May 25, 2013
Sound Card Stereo Channel Mysteriously Dies
The left channel of my Sound Blaster X-Fi Xtreme Audio sound card decided to die.
I carefully smoothed my headset cabling in case a break had developed in the typically very fine stranded wiring of the headphones, and also tried removing the plug with an MP3 playing and noticed that only one channel was being played back, the right with the plug fully inserted, left if I just slightly unplugged it. Just in case I plugged the headphones into my laptop; perfect stereo sound, so something's definitely up with the card.
I popped open the computer and examined the headphone jacks on the card. They appeared to be made of plain copper, and they seemed to have oxidation, much like an old penny.
I took a flat-bladed screwdriver from an eyeglass repair kit and carefully scraped away at the copper surface, revealing shiny metal underneath, then blasted away any residue with some canned air.
Now my music is once again in glorious stereo!
I carefully smoothed my headset cabling in case a break had developed in the typically very fine stranded wiring of the headphones, and also tried removing the plug with an MP3 playing and noticed that only one channel was being played back, the right with the plug fully inserted, left if I just slightly unplugged it. Just in case I plugged the headphones into my laptop; perfect stereo sound, so something's definitely up with the card.
I popped open the computer and examined the headphone jacks on the card. They appeared to be made of plain copper, and they seemed to have oxidation, much like an old penny.
I took a flat-bladed screwdriver from an eyeglass repair kit and carefully scraped away at the copper surface, revealing shiny metal underneath, then blasted away any residue with some canned air.
Now my music is once again in glorious stereo!
Labels:
audio,
Sound Blaster,
troubleshooting,
workaround
Friday, May 10, 2013
Sony SMP-N200 Streaming Media Player Review
This marks the 1-year anniversary since ditching DirecTV for the Sony SMP-N200 streaming media player.
The device features HDMI, optical, and RCA jacks, as well as an ethernet port.
So far, the experience has been great! Rather than paying around $900 a year for satellite, I'm paying just what I'd been paying before for internet, around $40 monthly, a decent compromise.
The interface of the player is very similar to that of Sony's Bravia series of TVs.
The remote enables navigation to the various options and settings. A great thing about this little black box is that you can browse the web, grabbing either streaming video from YouTube and elsewhere, or just general browsing. However, one trick is to use a smartphone app, Sony Media Remote, so that you gain the benefit of a keyboard; trying to "type" using the Sony's remote is an exercise in aggravation, to say the least.
For over-the-air TV, a Winegard antenna hung up near the ceiling of the living room plus a signal amplifier has managed to pull in 8 stations, six broadcast in my immediate area, and two more from towers about 40 miles away.
With the Sony SMP-N200 I can also stream downloaded video over my home's wireless network. To do this, I first needed to enable Homegroup on my Windows 7 desktop PC, and then I installed Nero MediaHome to act as a server for the Sony. Most any popular encoding format (AVI, MPG, MKV, WMV, and more) can stream from my computer to my TV with very little effort.
All in all, aside from the clunky remote, I'd give it a solid 4 out of 5 stars for the money I've saved thus far over cable or satellite.
The device features HDMI, optical, and RCA jacks, as well as an ethernet port.
So far, the experience has been great! Rather than paying around $900 a year for satellite, I'm paying just what I'd been paying before for internet, around $40 monthly, a decent compromise.
The interface of the player is very similar to that of Sony's Bravia series of TVs.
The remote enables navigation to the various options and settings. A great thing about this little black box is that you can browse the web, grabbing either streaming video from YouTube and elsewhere, or just general browsing. However, one trick is to use a smartphone app, Sony Media Remote, so that you gain the benefit of a keyboard; trying to "type" using the Sony's remote is an exercise in aggravation, to say the least.
For over-the-air TV, a Winegard antenna hung up near the ceiling of the living room plus a signal amplifier has managed to pull in 8 stations, six broadcast in my immediate area, and two more from towers about 40 miles away.
With the Sony SMP-N200 I can also stream downloaded video over my home's wireless network. To do this, I first needed to enable Homegroup on my Windows 7 desktop PC, and then I installed Nero MediaHome to act as a server for the Sony. Most any popular encoding format (AVI, MPG, MKV, WMV, and more) can stream from my computer to my TV with very little effort.
All in all, aside from the clunky remote, I'd give it a solid 4 out of 5 stars for the money I've saved thus far over cable or satellite.
Tuesday, May 7, 2013
The "GenerateResource" Task Failed Unexpectedly
Shortly after setting up a RAM disk using the freeware version of Dataram RAMDisk to see whether Visual Studio 2010 might compile a huge solution faster, I began getting the following errors after relocating the system's temp files to the root of the RAM drive:
I dug around and found numerous references to existing bug reports and a few workarounds. I tried unsetting the readonly file system attribute in my solution folder, setting the GenerateResourceNeverLockTypeAssemblies property in my project file to true or false to downgrade some security parameters, but ultimately it was the top answer here that did the trick.
I had set the environment variables for the RAM drive initially to just R:\, referencing the root of the drive. Apparently VS 2010 doesn't like this, so I simply created a new folder on my ram disk named TEMP, and then updated the environment variables accordingly:
Just to rule it out, and also because I hadn't rebooted Windows in a while, I also opened Control Panel => Programs and Features, and performed a Repair on Microsoft .NET Framework 4 Client Profile just in case the framework files might've gotten corrupted somehow, and then restarted.
Problem solved! Now on to see whether Joseph Fluckiger's experimentation which returned lukewarm results on performance of building to a RAM disk holds water for a solution with, say, dozens of projects.
The "GenerateResource" task failed unexpectedly.
System.TypeInitializationException: The type initializer for 'Microsoft.Build.Utilities.FileTracker' threw an exception. ---> System.NullReferenceException: Object reference not set to an instance of an object.
I dug around and found numerous references to existing bug reports and a few workarounds. I tried unsetting the readonly file system attribute in my solution folder, setting the GenerateResourceNeverLockTypeAssemblies property in my project file to true or false to downgrade some security parameters, but ultimately it was the top answer here that did the trick.
I had set the environment variables for the RAM drive initially to just R:\, referencing the root of the drive. Apparently VS 2010 doesn't like this, so I simply created a new folder on my ram disk named TEMP, and then updated the environment variables accordingly:
Just to rule it out, and also because I hadn't rebooted Windows in a while, I also opened Control Panel => Programs and Features, and performed a Repair on Microsoft .NET Framework 4 Client Profile just in case the framework files might've gotten corrupted somehow, and then restarted.
Problem solved! Now on to see whether Joseph Fluckiger's experimentation which returned lukewarm results on performance of building to a RAM disk holds water for a solution with, say, dozens of projects.
Labels:
C#,
RAMdisk,
troubleshooting,
Visual Studio 2010,
windows 7
Wednesday, February 20, 2013
Left and Right Double Quotation Marks
Often I find myself wanting to use left and right double quotation marks rather than the generic ones.
Especially if you happen to be quoting someone, it adds a touch of class to use these rather than their boring unicode counterparts. This site outlines the differences between the two, and for convenience I'm posting each here so that either one can be easily copied and pasted:
Below is as an animated GIF showing each of the left and right double quotation marks as well as the plain old unicode ones in CharMap, and keystrokes you can use to type the former if you're so inclined:
Especially if you happen to be quoting someone, it adds a touch of class to use these rather than their boring unicode counterparts. This site outlines the differences between the two, and for convenience I'm posting each here so that either one can be easily copied and pasted:
“
Left quotation mark. Hold down ALT and hit 0147 on your numeric keypad.
”
Right quotation mark. Hold down ALT and hit 0148 on your numeric keypad.
Below is as an animated GIF showing each of the left and right double quotation marks as well as the plain old unicode ones in CharMap, and keystrokes you can use to type the former if you're so inclined:
![]() |
| A handy animated GIF outlining them all. |
Labels:
ASCII,
CharMap,
double quotation marks,
quotes,
Unicode
Saturday, February 16, 2013
Block Reddit Ads, Part Deux
In my previous post I outlined a method to block Reddit ads.
It worked, until I tried hitting Reddit early this morning.
It appears that the ad structure is slightly different, now the following element hiding rule in the Element Hiding Helper of AdBlock Plus should do the trick:
This ought to work until they decide to change up their site structure once again.
UPDATE: Apparently, the developer of AdBlock Plus has decreed that Reddit ads will from this point forward be whitelisted, stating that Reddit ads meet their 'acceptable ads' guidelines, necessitating custom rules like I describe above. To me, this is a bad idea, especially since even bigtime advertisers like Yahoo, Fox, and Google have inadvertently helped malware procreate through ads.
It worked, until I tried hitting Reddit early this morning.
It appears that the ad structure is slightly different, now the following element hiding rule in the Element Hiding Helper of AdBlock Plus should do the trick:
reddit.com###siteTable_organic.organic-listing
This ought to work until they decide to change up their site structure once again.
UPDATE: Apparently, the developer of AdBlock Plus has decreed that Reddit ads will from this point forward be whitelisted, stating that Reddit ads meet their 'acceptable ads' guidelines, necessitating custom rules like I describe above. To me, this is a bad idea, especially since even bigtime advertisers like Yahoo, Fox, and Google have inadvertently helped malware procreate through ads.
Labels:
adblock plus,
advertising,
block ads,
element,
firefox,
reddit
Friday, February 15, 2013
Block Reddit Ads
Reddit recently introduced an update to their ads which eludes AdBlock Plus.
Instead of a simple element ID denoted as a sponsored link, their page uniquely identifies it according to a link to the comments for a given ad posting. Ads annoy me, and as my previous post on blocking Reddit ads attests, even their minimal advertising is an unwanted distraction.
However, using the Element Hiding Helper, it's trivial to block the new ad scheme. If you're already familiar with hiding elements, all you need to do is add an element hiding rule like this:
If you want a more detailed procedure which might help you block other unwanted web content, read on.
In Firefox, tap the ALT key to display the menu, then click Tools => AdBlock Plus => Select an element to hide (or alternatively hit CTRL-SHIFT-F3). This brings up the element selection dialog that lets you pick and choose items on the web page to hide.
Now a red selection box will outline and identify elements of the page as your mouse cursor hovers over them. If you hover over the sponsored link area, you should see something like this:
Note the entire ad post is surrounded, with a tag in the lower-left indicating the post is within a DIV element. Click on the tag for this area, and you'll open the Compose element hiding rule dialog.
This is the Basic view, but we need to go deeper, so click on the Advanced view button.
By default, when you clicked to select the ad, the element hider chose that specific DIV element. However, blocking this won't do, as each ad will have a unique identifier (in this case, 17aahm) which will foil the filter.
To get around this, first click on the checkbox beside the option that begins "class: thing id-..." to uncheck it, and then click on the DIV in the list which is the parent to this one, just above the default selection. Then, click the checkbox beside siteTable_promoted so that it's checked, and then click the Add element hiding rule button.

Now the ad should be hidden, either immediately or after your next refresh of Reddit's page.
Instead of a simple element ID denoted as a sponsored link, their page uniquely identifies it according to a link to the comments for a given ad posting. Ads annoy me, and as my previous post on blocking Reddit ads attests, even their minimal advertising is an unwanted distraction.
However, using the Element Hiding Helper, it's trivial to block the new ad scheme. If you're already familiar with hiding elements, all you need to do is add an element hiding rule like this:
reddit.com###siteTable_promoted > *
If you want a more detailed procedure which might help you block other unwanted web content, read on.
In Firefox, tap the ALT key to display the menu, then click Tools => AdBlock Plus => Select an element to hide (or alternatively hit CTRL-SHIFT-F3). This brings up the element selection dialog that lets you pick and choose items on the web page to hide.
Now a red selection box will outline and identify elements of the page as your mouse cursor hovers over them. If you hover over the sponsored link area, you should see something like this:
Note the entire ad post is surrounded, with a tag in the lower-left indicating the post is within a DIV element. Click on the tag for this area, and you'll open the Compose element hiding rule dialog.
This is the Basic view, but we need to go deeper, so click on the Advanced view button.
By default, when you clicked to select the ad, the element hider chose that specific DIV element. However, blocking this won't do, as each ad will have a unique identifier (in this case, 17aahm) which will foil the filter.
To get around this, first click on the checkbox beside the option that begins "class: thing id-..." to uncheck it, and then click on the DIV in the list which is the parent to this one, just above the default selection. Then, click the checkbox beside siteTable_promoted so that it's checked, and then click the Add element hiding rule button.
Now the ad should be hidden, either immediately or after your next refresh of Reddit's page.
Labels:
adblock plus,
advertising,
block ads,
element,
firefox,
reddit
Tuesday, February 5, 2013
Foscam FI9821 Wireless Workaround
In my abortive attempt to review the Foscam FI9821, I mentioned the complete inability for the camera to find let alone connect to mine nor any wireless networks in my neighborhood. This precluded my ability (and desire) to review the camera any further.
Now, however, the camera sees and connects successfully to my wireless network.
After my issues with the late Foscam FI9820 with its poor daytime image quality and anemic firmware, I already experienced RMA hell and didn't want to go through it again. Thus, being handy with electronics, I decided to try an off the wall suggestion found in Foscam's support forum.
Note that the following steps may VOID the manufacturer warranty.
1. Power off the FI9821 and disconnect all cables.
2. Remove the rubber feet on the underside of the camera, this should reveal a couple of screws. Remove them. There are also two screws located on the underside beneath one round laser QA label and another beneath a round paper label. Remove the labels and then the screws as well.
3. Carefully remove the bottom of the camera and follow the wire that runs from behind where the antenna screws in to the camera to a metal "post" on the circuitboard, similar to the one depicted here:
4. Remove the connector, then reconnect it, and as you do so wiggle it, just a little bit.
5. Reverse the steps above and reassemble the camera.
6. Connect the power and ethernet cables, and proceed to configure the camera to connect to your wireless network if you haven't already. Be sure to save the settings!
7. From the camera's web interface, on the Wireless Settings screen click the Scan button. Your wireless network should appear similarly as shown below:
8. Unplug the ethernet cable and wait a minute or so, then try browsing to the camera's IP address. With luck, the camera will have switched to wireless mode and you should then be connected wirelessly, at last!
Why does this work?? It could be due to insulation which is sometimes used to coat electronics, such as that used to coat thin wire that's used for coils. Perhaps in the manufacturing process, the post got sprayed with insulation by accident, leading to a poor connection with the antenna wire connector. Wiggling the connector around on the post may've scraped away any insulation, leading to a solid connection.
Regardless, releasing a $150+ camera so hurriedly with a problem like this, one that some simple quality assurance practices could've caught and fixed, is ridiculous. Although again I applaud Foscam for their responsive customer service and providing me with a free upgrade to the newest model of their camera, shame on them for not catching this frustrating little glitch!
I will review the camera in earnest in the near future, now that its wireless connectivity, a core feature in my eyes, is operational at last.
Now, however, the camera sees and connects successfully to my wireless network.
After my issues with the late Foscam FI9820 with its poor daytime image quality and anemic firmware, I already experienced RMA hell and didn't want to go through it again. Thus, being handy with electronics, I decided to try an off the wall suggestion found in Foscam's support forum.
Note that the following steps may VOID the manufacturer warranty.
1. Power off the FI9821 and disconnect all cables.
2. Remove the rubber feet on the underside of the camera, this should reveal a couple of screws. Remove them. There are also two screws located on the underside beneath one round laser QA label and another beneath a round paper label. Remove the labels and then the screws as well.
3. Carefully remove the bottom of the camera and follow the wire that runs from behind where the antenna screws in to the camera to a metal "post" on the circuitboard, similar to the one depicted here:
4. Remove the connector, then reconnect it, and as you do so wiggle it, just a little bit.
5. Reverse the steps above and reassemble the camera.
6. Connect the power and ethernet cables, and proceed to configure the camera to connect to your wireless network if you haven't already. Be sure to save the settings!
7. From the camera's web interface, on the Wireless Settings screen click the Scan button. Your wireless network should appear similarly as shown below:
8. Unplug the ethernet cable and wait a minute or so, then try browsing to the camera's IP address. With luck, the camera will have switched to wireless mode and you should then be connected wirelessly, at last!
Why does this work?? It could be due to insulation which is sometimes used to coat electronics, such as that used to coat thin wire that's used for coils. Perhaps in the manufacturing process, the post got sprayed with insulation by accident, leading to a poor connection with the antenna wire connector. Wiggling the connector around on the post may've scraped away any insulation, leading to a solid connection.
Regardless, releasing a $150+ camera so hurriedly with a problem like this, one that some simple quality assurance practices could've caught and fixed, is ridiculous. Although again I applaud Foscam for their responsive customer service and providing me with a free upgrade to the newest model of their camera, shame on them for not catching this frustrating little glitch!
I will review the camera in earnest in the near future, now that its wireless connectivity, a core feature in my eyes, is operational at last.
Labels:
FI9821,
Foscam,
troubleshooting,
wireless,
workaround
Subscribe to:
Comments (Atom)












