I received a notification today of an update available for Visual Studio 2012. It was for an updated version of the Windows Library JavaScript Extensions:
VLC Media Player is currently one of the most popular and versatile media players on many platforms, and now that includes Android 4.2 or less (your results may vary with Android 4.3, although VLC v1.3 seems to be working acceptably now). Just be aware these releases are in BETA, and can be obtained via the Google Play Store. That is, with one caveat – you can’t get it in North America (Canada, United States, Mexico, etc).
However, if you are willing to risk a potentially less stable build, and are handy enough to understand how to change a security setting temporarily, you can manually download one of VideoLan’s “Nightly Build” copies of VLC Media Player for Android.
To do this, you must perform the following steps:
1) First you must go to your Android device’s SETTINGS>SECURITY(‘Personal’ group)>UNKNOWN SOURCES option and turn it on. 
2) Open your Android device’s browser, and browse to http://nightlies.videolan.org/build/armv7-android/ NOTE: the Google Nexus 7 has an ARM7 instruction set NVidia Tegra 3 processor – other devices may require the ARM6 package!
3) Select one of the build entries – generally the most recent one will be at the bottom of the list, for example today’s most recent is named VLC-debug-20130726-1426.apk. It will download the file, but not install it. Select your downloaded file from the status panel when it completes.
4) If prompted for the application to use against the file, select the Google Package Installer, click the JUST ONCE button, and let it install.
5) If prompted, decide if you want to let Google ‘periodically check your files’ for suspicious activity or something like that.
6) Lastly, you must go back to your Android device’s SETTINGS>SECURITY(‘Personal’ group)>UNKNOWN SOURCES option and turn it back off.
Once installed, you can find the VLC player icon in the main icons screen, but it did not load onto the home screen for me. Also, when playing video files from the file explorer or from launcher applications, it may now prompt you to select between the Android Video Player or VLC – I suggest using the JUST ONCE option for VLC until it comes out of Beta testing.
Also – another fun App to install is the DLNA on Android application MediaHouse UPnP / DLNA Browser found here:
https://play.google.com/store/apps/details?id=com.dbapp.android.mediahouse&hl=en
This will allow you to stream content from any device on your home network that is set up to share. Works beautifully! And with VLC on your Android, it should play virtually everything now!
Update 3 is provided as Knowledge Base item KB2835600.
Link: http://support.microsoft.com/kb/2835600
What’s in this update:
Improvements –
Team Foundation Server
Issue Fixes in categories –
I wanted to share the solutions to two frequently encountered errors for ASP.Net developers using the Microsoft Visual Studio 2012 development environment:
Error 1:
This version of SQL Server Data Tools is not compatible with the database runtime components installed on this computer
[followed by]
An incompatible DacFx version is installed
Solution 1:
The only way I was able to resolve this was by upgrading to the latest version of both Sql Server Data Tools (SSDT) and DACFx via the following links (the main MSDN links didn’t fix it for me – same problem persisted):
SSDT: http://msdn.microsoft.com/en-us/data/hh297027
DacFx: http://www.microsoft.com/en-us/download/details.aspx?id=35756
Error 2:
WebForms UnobtrusiveValidationMode requires a ScriptResourceMapping for ‘jquery’. Please add a ScriptResourceMapping named jquery(case-sensitive).
Solution 2:
First, understand that UnobtrusiveValidationMode means that the scripting logic for the validation controls is utilized from the server versus in-page scripting. This means you must have the server side script paths defined within your Web application.
However, there are two ways to fix this. Either add the server side script paths, or you can simply turn off unobtrusive validation and utilize the all-client-side in-page (obtrusive) validation scripting.
(1) Adding the jquery script path:
Add the following (Visual Basic .Net code) to your application’s Global.asax class/file (if missing, right-click your web project in Solution Explorer and select ADD>NEW ITEM>select WEB>select GLOBAL APPLICATION CLASS to add it) in the Application_Start event handler:
C#:
ScriptManager.ScriptResourceMapping.AddDefinition(“jquery”, new ScriptResourceDefinition
{
Path = “~/scripts/jquery-1.7.2.min.js”,
DebugPath = “~/scripts/jquery-1.7.2.min.js”,
CdnPath = “http://ajax.aspnetcdn.com/ajax/jQuery/jquery-1.4.1.min.js”,
CdnDebugPath = “http://ajax.aspnetcdn.com/ajax/jQuery/jquery-1.4.1.js”
});
VB:
Dim oSRD As New ScriptResourceDefinition
With oSRD
.Path = “~/scripts/jquery-1.7.2.min.js”
.DebugPath = “~/scripts/jquery-1.7.2.min.js”
.CdnPath = “http://ajax.aspnetcdn.com/ajax/jQuery/jquery-1.4.1.min.js”
.CdnDebugPath = “http://ajax.aspnetcdn.com/ajax/jQuery/jquery-1.4.1.js”
End With
ScriptManager.ScriptResourceMapping.AddDefinition(“jquery”, oSRD)
(2) Disable UnobtrusiveValidationMode –
Add the following to your application’s Web.Config file:
<add key=”ValidationSettings:UnobtrusiveValidationMode” value=”None” />
Happy coding!
Those of you utilizing Asus‘ fantastic RT-N56U wireless router for a file / media server via the 2 USB ports and flash drives are aware that you have few options if your flash drives are >32gb and you run Windows 7 as your primary OS on your main PC or laptop.
While the Asus router does recognize the NTFS file system, I’ve found it to be a VERY buggy experience with files frequently becoming corrupt and the media server often failing to index newly added files. Windows 7 GUI does not provide the FAT32 file system as another drive format option, opting instead for the exFAT file format (enhanced / extended FAT file system not subject to the FAT32 32gb limitation). But the exFAT file system is apparently not supported or recognized by the Asus router as of firmware version 3.0.0.4.360.
So what to do? Well, since the kernel of the Asus router OS is a flavor of Unix, it will recognize the EXT2 and EXT3 file systems without a hitch. But Windows does not have built-in support for the file system, and cannot read, write or format the implementation. This is where 2 products come in to save the day!
The first – a free open-source EXT2 / EXT3 Windows driver for reading these file systems like any other NTFS or FAT drive you add to your Windows machine – EXT2FSD ( http://www.ext2fsd.com/ ). With this driver added, and after a reboot, you can plug in an EXT2 or EXT3 formatted flash drive and start reading / writing files straight away. However, the ability to format a flash drive – WITHOUT EXITING WINDOWS AND USING A BOOT DISC – comes from a second product. EaseUS‘s Partition Master software ( http://www.partition-tool.com/personal.htm ) performs the EXT2/3 formatting right from the Windows application, and the functionality exists in their Freeware version too!
Between these two free tools, you can quickly get your >32gb drives (or smaller too for that matter) formatted to the best file system for your Asus RT-N56U router. Good luck!
UPDATE 7/6/2013: This issue has been resolved with Java 7 update 25!
The recent Java 7 Update 21 has some form of change that interferes with the functioning of Palo Alto / Cisco Systems NetConnect & GlobalDesktop products.
I had uninstalled all previous versions of Java and also uninstalled NetConnect, which removes the PAN Service and the desktop shortcut. When I updated the Java Virtual Machine to version 7 Update 21 Build 11 ( B11 ), the installer .msi would no longer extract properly (would create the installer msi but with a file size of 0kb) and an error “could not extract installer msi: null” would pop up.
The only way around this was to remove update 21 and go back to the previous public Java 7 release of update 17, which Oracle foolishly removed from their website but is thankfully still available from OldApps.Com:
Java 7 update 17 32-bit (x86 / i586): http://www.oldapps.com/java.php?old_java=11930
Java 7 Update 17 64-bit (x64): http://www.oldapps.com/java.php?old_java=11931
Hopefully either Oracle or Palo Alto will identify what the compatibility issue is and get it resolved soon.
This “Binary Files Differ” error/message was annoying the heck out of me, but I had been able to fix it by checking out the the offending file, opening it in TEXTPAD and saving it as format PC / ANSI, then checking it back in.
Even this work-around, however, had failed to fix one file this past week so I had to dig further. I’ve finally located an answer / fix:
“Visual source safe doesn’t always recognize text file types properly. when checking-in files using ‘auto‘ type — it treats them as binary.
“So when you compare two .sql files you might see ‘binary files differ‘ — and nothing more. (that’s how vss treats binary files).
“The solution is to change the file type using the properties context menu for the file in source safe. Change the type to text, you should be able to perform the visual comparison. You can also click on the ‘advanced’ option when checking-in the file, and manually change the selection to ‘text‘ then.
“To avoid in the future – you can add file type settings under the options menu in visual source safe, to set the default behavior for various file types there.”
The new Motorola Droid Razr MAXX HD XT926 XT926M is supposed to be nano-coated internally to avoid damage due to light liquid, but it is not very often that the liquid coming into contact with your phone is merely a splash or drizzle. Such was the case with mine. My phone sat in a dual cup-holder adjacent to a (unbeknownst to me) leaking Styrofoam soda cup. By the time I arrived at my destination, the top of my phone was submerged in over an inch of soda.
The phone worked still, although the camera had stopped functioning. By the next day, the phone had run out of battery and would no longer power up. So began my quest to crack it open and see what I could see…
DISASSEMBLING THE XT926M:
Tools:
– micro torx bits T3, T4 and/or T5 (my bits aren’t marked, but I believe these are the right classifications)
– micro screwdriver
– tough plastic prying tools
– [optional] ‘spudger’ too
STEPS:
(1) Removing the LCD Display – Touch Screen – Digitizer – Assembly
– we start by removing the only screws visible on the exterior of the phone – the two torx screws at the very bottom of the housing
– with the two screws removed, you can now carefully *SLIDE* (do not lift!) the LCD-portion of the display *BACK* (towards top of phone) from the lower half of the housing to disengage it, BUT BE AWARE IT WILL STILL BE ATTACHED BY 2 RIBBON CABLES. The LCD assembly frame has slight hook tabs which make it only possible to remove it in this slide-back manner.
– carefully unplug the two ribbon cables from the main housing by sliding them FLATLY towards the center of the phone to disengage from the main-board.
– DONE! You have removed your LCD assembly! 
To remove the front-camera, remove the two torx screws, remove the metal housing, and carefully slide the camera’s ribbon-plug UP from the LCD-board plug.
– to reinstall, just reverse the above directions.
(2) REMOVING THE PHONE MAIN-BOARD (to get to the battery):
– remove all the visible torx screws (10 total) INCLUDING those on the camera assembly (2), the ear-phone plug assembly (2) and the remaining six on the main-board itself.
– carefully unplug the small power/volume switches ribbon cable from the right side of the main-board by sliding it towards the right side
– remove the battery power cable from the bottom-left of the main-board by first removing the transparent gold protective sticker, then sliding the ribbon connector down towards the bottom of the phone.
– lastly, and most difficult, carefully dislodge the main-board from the back shell BUT also pry out the speaker from the top-left when you get room OR YOU RISK BREAKING THE SMALL CONNECTOR WIRES! You will hear a small pop as the speaker un-snaps from the housing – then it is OK to continue prying the main-board from the shell.
– Note the small vibration motor is on the back of the board near the speaker.
(3) BATTERY REMOVAL AND FLASH REMOVAL
– The battery is merely glued to the back housing, but be careful in prying it out because it IS bendable, not rigid. Keep it from bending as much as you can.
– The flash module is removed by taking out the four miniscule torx bits that hold it in. Replace it in the same manner.
 | carlupq on How To Use AdBlockPus Rule To… |
 | Sergey Sedlovsky on How To Use AdBlockPus Rule To… |
| Sergey on How To Use AdBlockPus Rule To… |
 | Michael S on Sysinternals Microsoft (http:/… |
 | Troneto on How To Use AdBlockPus Rule To… |
