BTSync codes

This is more for myself, but folks are welcome to use them if they find it useful. (The more nodes, the faster! Just running on a couple desktops for now, will be adding to home router/server/nas later.) The shared links are, of course, read-only.

I've been using BittorrentSync since it was in 1.x beta, great to keep a collection of files (say, troubleshooting utils, patches, ISO's, whatever) locally accessible at various locations and only updated once.

==

First up is my collection of "Live" window utils - just the things I find myself always wishing for/downloading, or a couple obscure ones. Currently just under 300 megs, it's very nice to have on phone with you. (Provided you keep a USB cable handy!)


Using their kinda-obtuse link system:
https://link.getsync.com/#f=Util_Live&sz=3E8&t=2&s=BZLMIQQGRTZCZHVOUHSR6DWKZQLDLQD3OGCAXHIZU4BNK4W44QLQ&i=CUWN3TKCMKKXNIRCOXHYAFFPE2V4PS5CY&v=2.0


And the QR for phone funsies. (I've put a copy of the code in the folder itself. SyncCeption!)

Deltacopy rsync installer script for Windows.

From the readme:

Rsync is good. BackupPC is good. Rsync on Windows is...not so good. We (small-ish IT department) decided on using the DeltaCopy version of rsync (still using Cygwin) to allow our BackupPC server(s) to backup our windows clients. It's fairly quick'n dirty but works well enough for our purposes.

I've posted it on bitbucket in all it's "glory".  (https://bitbucket.org/TechMonkey/backuppcwinclient) Of course folks are welcome to submit patches, suggest changes and the like, but this is mostly an exercise in version control...

WEI/WinSAT on Windows 10 - D3D score is bogus.

Most of us know the Windows Experience Index was removed from the GUI in Win 8, and many are familiar with calculating/getting the scores from many posts like this one.

 I can rarely remember the steps (I prefer to open admin powershell, then "winsat formal", and then "Get-WmiObject Win32_WinSAT")

Something I noticed according to this Win32_WinSAT class entry:

"After Windows 8.1, WinSAT no longer assess the three-dimensional graphics (gaming) capabilities of the computer and the graphics driver's ability to render objects and execute shaders using this assessment. For compatibility, WinSAT report sentinel values for the metrics and scores, however these are not calculated in real time."

 Indeed, on a decent older-desktop with a Radeon 4670, it returns a 9.9 for D3D:

CPUScore : 5.3
D3DScore : 9.9
DiskScore : 5.9
GraphicsScore : 6.2
MemoryScore : 5.4
TimeTaken : MostRecentAssessment
WinSATAssessmentState : 1
WinSPRLevel : 5.3

Just another tidbit/gotcha to be aware of.

Linksys WRT320/E2000 conversion missing file.

Lots of copies of (apparently) this post, but the download links for the CFE files are borked, as is the CAPTCHA on the comment field.

I found a copy for the 320/2000 CFE at http://www.dd-wrt.com/phpBB2/viewtopic.php?p=715205, same SHA-1 hash. (db2d4cd117faac4c0a330afa4cdcdb5ad133d82a)

I've made a copy available at https://drive.google.com/file/d/0B8BlCCtbBj6edVhhdnRYbjN4cGM/view

Benign event ID's 120xx on WSUS

WSUS on a Server 2012 R2 CORE, working fine, but event ID's 12052 12042 12022 12032 12012 whenever healthcheck ran.

http://jackstromberg.com/2013/10/windows-update-services-multiple-errors-in-event-viewer-event-id-1205212042-12022-12032-12012-1200213042/ had the answer.

I'm not 100% sure what it does to fix the problem, but re-running "wsusutil.exe usecustomwebsite true" worked for me.

ImageX /check vs /verify

Because I can never remember, and the Technet documentation is not helpful in this regard:

/Check - Calculate Checksums (Check.Checksum. Got it!)

/Verify - Just compares source and destination.

From http://windowsitpro.com/systems-management/deploying-and-error-checking-imagex

The /verify option works as you might imagine: It double-checks that either a capture or apply operation didn't accidentally drop any bits along the way. WIM files are pretty large, and although network and disk read/write operations already contain built-in checks, just one misplaced byte can render the image or system useless. The /verify option helps prevent that from happening. After either applying or capturing a windows image, ImageX compares the source data and its copy, searching for (and correcting) differences. ImageX enables the /verify option by default whenever applying or capturing over a network connection, but it doesn't do that when working with local external storage, so it's never a bad idea to add the /verify option. (It will, of course, slow things down a bit.)

The /check option has a similar purpose but a slightly different and perhaps more efficient approach. If you include /check when capturing an image, ImageX creates a hash of every 10MB chunk of ImageX data, then embeds those hashes in the resulting WIM. Including /check on an apply operation causes ImageX to check the applied image by re-computing hashes on that image, then comparing those computed hashes with the embedded ones. Thus, /check certifies not only that a WIM wasn't mis-copied during the apply operation but also that a WIM hasn't become corrupted while stored. Why use /verify, then? Why not just always use /check? The answer is that /check can't do its job on an apply operation if no one specified /check on the capture. If the WIM lacks embedded hashes, /check can't check the hashes. The /verify option, in contrast, doesn't need hashes, so it can always help.

ATT LG Optimus G ("Geeb" E970) data partition

For when an encrypted phone just won't recognize the PIN even though it's correct.

cat fstab.e970
# Android fstab file.
#                                            nd options>  
# The filesystem that contains the filesystem checker binary (typically /system)
 cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHEC
K

/dev/block/platform/msm_sdcc.1/by-name/boot         /boot           emmc    defa
ults                                                        defaults
/dev/block/platform/msm_sdcc.1/by-name/recovery     /recovery       emmc    defa
ults                                                        defaults
/dev/block/platform/msm_sdcc.1/by-name/system       /system         ext4    ro,b
arrier=1                                                    wait
/dev/block/platform/msm_sdcc.1/by-name/cache        /cache          ext4    noat
ime,nosuid,nodev,barrier=1,data=ordered                     wait,check
/dev/block/platform/msm_sdcc.1/by-name/userdata     /data           ext4    noat
ime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc     wait,check,encryptab
le=/dev/block/platform/msm_sdcc.1/by-name/metadata
/dev/block/platform/msm_sdcc.1/by-name/persist      /persist        ext4    nosu
id,nodev,barrier=1,data=ordered,nodelalloc                  wait
/dev/block/platform/msm_sdcc.1/by-name/modem        /firmware       vfat    ro,u
id=1000,gid=1000,dmask=227,fmask=337                        wait
/dev/block/platform/msm_sdcc.1/by-name/sns          /sns            ext4    nosu
id,nodev,barrier=1,data=ordered                             wait,check

# vold-managed volumes
/devices/platform/msm_sdcc.3/mmc_host/mmc1/         /storage/sdcard1 auto   defa
ult voldmanaged=sdcard1:auto
~ # mke2fs -t ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata
mke2fs -t ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
752192 inodes, 3008512 blocks
150425 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=3082813440
92 block groups
32768 blocks per group, 32768 fragments per group
8176 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 36 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
~ # exit
exit

Make windows recognize Android USB driver (For sideloading in Recovery)

Can't get ADB to talk to your android? Get the sad "not recognized" sound when you plug in USB in recovery mode? The trick is to check device manager and get the hardware ID, then add that to the .inf. (Using the USB driver included w/ the ADK.)

path-to-extracted-adk\sdk\extras\google\usb_driver\android_winusb.inf

Latest driver is here: http://developer.android.com/sdk/win-usb.html


I just added %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
to the "[Google.NTamd64]" section.

Info found in http://forum.xda-developers.com/showthread.php?t=2535960

Items in Google Drive folder not showing up in search results (Windows 7)

http://superuser.com/questions/485719/windows-7-index-search-does-not-work-in-google-drive-folder

(Add local SYSTEM account rights to GDrive folder.)

Windows Take Ownership right-click menu script.

http://www.howtogeek.com/howto/windows-vista/add-take-ownership-to-explorer-right-click-menu-in-vista/

"the trust relationship between this workstation and the primary domain failed" better fixes

From http://www.implbits.com/about/blog/tabid/78/post/don-t-rejoin-to-fix-the-trust-relationship-between-this-workstation-and-the-primary-domain-failed/default.aspx

This problem can be caused by various circumstances, but I most commonly run into it when I reset a virtual machine to a system snapshot that I made months or even years before.  When the machine is reset, it is missing all of the automatic password changes that it executed against the domain controller during the intervening months.  The password changes are required to maintain the security integrity of the domain.

The trick is to reset computer account password, use netdom.exe or powershell.

netdom.exe resetpwd /s:/ud: /pd:*

Reset-ComputerMachinePassword [-Credential ] [-Server ] 

Even better (For VM's), avoid the problem altogether by keeping the machine password static. (When appropriate for security, of course.)

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
Modify the DisablePasswordChange entry from 0 to 1.

(From http://9to5it.com/trust-relationship-between-workstation-and-domain-failed/)