diff --git a/assets/wganuninst.zip b/assets/wganuninst.zip new file mode 100644 index 0000000..aa5bee4 Binary files /dev/null and b/assets/wganuninst.zip differ diff --git a/index.html b/index.html index 326e8e8..6f4ca04 100644 --- a/index.html +++ b/index.html @@ -6,7 +6,17 @@ layout: default diff --git a/know-how/software/nagios/_posts/2014-03-31-kernel-modules.md b/know-how/software/nagios/_posts/2014-03-31-kernel-modules.md new file mode 100644 index 0000000..15ee206 --- /dev/null +++ b/know-how/software/nagios/_posts/2014-03-31-kernel-modules.md @@ -0,0 +1,39 @@ +--- +title: Kernel Module Check for Nagios +layout: default +created: 2014-03-31 16:59:17 +0200 +updated: 2014-03-31 17:00:17 +0200 +toc: false +tags: + - know-how + - software + - nagios +--- +`mod_loaded`: + +{% highlight bash %} +#!/bin/sh +if [ "$1" = "" ] +then + echo "USAGE:" + echo "$0 " + exit 99 +fi + +MOD=$1 + +STATUS=`lsmod | grep "$MOD"` +if [ -z "$STATUS" ]; then + echo "CRITICAL - Kernel module $MOD not loaded!" + exit 2 +fi + +DATA=( $STATUS ) + +echo "OK - ${DATA[0]} has ${DATA[2]} instances, ${DATA[1]} bytes.|instances=${DATA[2]}, memory_usage=${DATA[1]}" +exit 0 +{% endhighlight %} + +For Check_MK add this to the `/etc/check_mk/mrpe.cfg`: + + DigiPort_KernelMod /usr/local/nagios/plugins/mod_loaded dgrp diff --git a/know-how/software/openwrt/_posts/2014-05-26-sysupgrade-with-extroot.md b/know-how/software/openwrt/_posts/2014-05-26-sysupgrade-with-extroot.md new file mode 100644 index 0000000..831b52b --- /dev/null +++ b/know-how/software/openwrt/_posts/2014-05-26-sysupgrade-with-extroot.md @@ -0,0 +1,39 @@ +--- +title: sysupgrade with ExtRoot +layout: default +created: 2014-05-26 22:30:20 +0200 +updated: 2014-05-26 22:47:49 +0200 +toc: false +tags: + - know-how + - software + - openwrt +--- +Run `sysupgrade` or upload the new file with LuCI. + +

+When upgrading with ExtRoot mounted, your configuration in ExtRoot will be saved and **restored to the `overlay` in +Flash memory**. So if you have a specific emergency configuration, be sure to boot without ExtRoot before starting the +upgrade. +

+ +After the reboot, you will be in the base system (that is, your configuration, but without ExtRoot). Run these commands +to get back on track: + + opkg update + opkg install block-mount + opkg install kmod-fs-ext4 + opkg install kmod-usb-storage + mount /dev/sda1 /mnt + rm /mnt/etc/.extroot-uuid + reboot + +After this reboot, either everything will be working again (/dev/sda1 mounted to `/overlay`) or - if there was a new +kernel in that upgrade - /dev/sda1 might be mounted to `/overlay-disabled`. In that case, you have to recreate ExtRoot +(save your configuration first). + +If your previous ExtRoot mounted fine, you might want to update your packages there. It is important to **NOT** upgrade +kernel modules as this might break things. The [ExtRoot Wiki Page](http://wiki.openwrt.org/doc/howto/extroot#old.notes) +lists a command to only update non-kernel-packages: + + opkg upgrade $(opkg list-upgradable | awk '($1 !~ "^kmod|Multiple") {print $1}') diff --git a/know-how/software/windows/_posts/2008-07-15-ansi.md b/know-how/software/windows/_posts/2008-07-15-ansi.md new file mode 100644 index 0000000..ee1ec42 --- /dev/null +++ b/know-how/software/windows/_posts/2008-07-15-ansi.md @@ -0,0 +1,17 @@ +--- +title: ANSI codes in COMMAND.COM +layout: default +created: 2008-07-15 00:05:00 +0200 +updated: 2008-07-15 00:05:00 +0200 +toc: false +tags: + - know-how + - software + - windows +--- +To enable ANSI control codes in `command.com`, add the following line to `%SystemRoot%\system32\CONFIG.NT`: + + DEVICE=%SystemRoot%\system32\ANSI.SYS + + +*[ANSI]: American National Standards Institute diff --git a/know-how/software/windows/_posts/2008-07-15-devmgr.md b/know-how/software/windows/_posts/2008-07-15-devmgr.md new file mode 100644 index 0000000..ac53447 --- /dev/null +++ b/know-how/software/windows/_posts/2008-07-15-devmgr.md @@ -0,0 +1,15 @@ +--- +title: Device Manager Hacks +layout: default +created: 2008-07-15 00:08:39 +0200 +updated: 2008-07-15 00:08:39 +0200 +toc: false +tags: + - know-how + - software + - windows +--- +To show a 'Details' tab in device's properties, add the system environment variable `DevMgr_Show_Details` and set it +to "1". + +To also show non-active devices, add `DevMgr_Show_NonPresent_Devices` and also set it to "1". diff --git a/know-how/software/windows/_posts/2008-07-15-max-10-smb-connections.md b/know-how/software/windows/_posts/2008-07-15-max-10-smb-connections.md new file mode 100644 index 0000000..6299c66 --- /dev/null +++ b/know-how/software/windows/_posts/2008-07-15-max-10-smb-connections.md @@ -0,0 +1,33 @@ +--- +title: Max 10 simultaneous SMB-connections +layout: default +created: 2008-07-15 22:02:53 +0200 +updated: 2008-07-15 22:02:53 +0200 +toc: false +tags: + - know-how + - software + - windows + - samba + - smb +--- +Windows XP Professional only allows 10 simultaneous connections to shares and printer spoolers. The eleventh user gets +a *System error #71* message. The unused connections get freed after 30 minutes which is a bit late since often you +just need a few files or to print some pages but this blocks the connection for 30 minutes. + +To make things better, you can issue the command + + net config server /autodisconnect:3 + +which sets the limit to 3 minutes. You can even set this to `0` to free a slot almost instantly. + +This value can also be changed in the registry. The key is `HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters`. + +More information can be found at [KB138365](http://support.microsoft.com/kb/138365). + + +The really evil can fly to [Google Cache](http://66.102.9.104/search?q=cache:kHQ_0PQXJDQJ:tachyon.zapto.org/binaries/antiwpa/LanServerNoConnLimit/patched.txt+srvsvc.dll+%226a+0a%22&hl=en&ct=clnk&cd=3) +and get a disassembled part of the `srvsvc.dll` with the needed changes to disable the limit. (Only works for XP-SP2!) + +The last resort is to upgrade to *Windows Server*. Another thought might be to connect to the shares from a Linux box +and let the clients connect to this Linux machine. diff --git a/know-how/software/windows/_posts/2008-07-15-profilestate.md b/know-how/software/windows/_posts/2008-07-15-profilestate.md new file mode 100644 index 0000000..55c3023 --- /dev/null +++ b/know-how/software/windows/_posts/2008-07-15-profilestate.md @@ -0,0 +1,20 @@ +--- +title: Backup-Userprofile as active profile +layout: default +created: 2008-07-15 00:06:44 +0200 +updated: 2008-07-15 00:06:44 +0200 +toc: false +tags: + - know-how + - software + - windows +--- +Check registry key: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList` for needed profile. + +Change `State` value to following: + +| Value|Meaning | +|------:|:-------------| +| `100`h|logged on user| +| `104`h|normal profile| +|`8100`h|backup profile| diff --git a/know-how/software/windows/_posts/2008-07-15-srvany.md b/know-how/software/windows/_posts/2008-07-15-srvany.md new file mode 100644 index 0000000..ef389cb --- /dev/null +++ b/know-how/software/windows/_posts/2008-07-15-srvany.md @@ -0,0 +1,16 @@ +--- +title: SrvAny / WinServ +layout: default +created: 2008-07-15 00:07:31 +0200 +updated: 2008-07-15 00:07:31 +0200 +toc: false +tags: + - know-how + - software + - windows + - services +--- +SrvAny.exe doesn't recognize when the launched application exits. Windows still thinks that the service (`SrvAny.exe`) +is running and so error handling (restart app, restart windows, etc.) doesn't occur. + +Winserv doesn't have this problem. Get it from . diff --git a/know-how/software/windows/_posts/2009-02-02-remove-wgan.md b/know-how/software/windows/_posts/2009-02-02-remove-wgan.md new file mode 100644 index 0000000..2b6f741 --- /dev/null +++ b/know-how/software/windows/_posts/2009-02-02-remove-wgan.md @@ -0,0 +1,55 @@ +--- +title: Remove WGA Notification +layout: default +created: 2009-02-02 19:49:08 +0100 +updated: 2009-02-02 19:49:08 +0100 +toc: false +tags: + - know-how + - software + - windows + - wga +--- +Microsoft distributes the *Windows Genuine Advantage Notification Tool (KB905474)* through the WindowsUpdate mechanism. +This tool should detect fake Windows serial numbers and nag the user. Interestingly, Microsoft hid a small paragraph in +their EULA after that the tool sends daily(!!) reports to Microsoft. According to MS this "is neccessary" since the +tool is BETA and MS needs to be able to react if it goes crazy. Yeah … sure! + +Sadly, if you installed it by accident, there's no easy way to remove it. No entry in the *Add/Remove Programs* window. +You could restore a backup of your disk or use *System Restore*, but after some Google'ing I found [this site](http://www.mydigitallife.info/2006/04/26/disable-and-remove-windows-genuine-advantage-notifications-nag-screen/) +which lists 16 ways to remove the WGAN. + +The first method seemed to be the best and so I used [AutoHotkey](http://www.autohotkey.com/) and automated it. + +**Download here:** [wganuninst.zip]({{ site.url }}/assets/wganuninst.zip) + + +How it works +============ + +1. the files `WgaLogon.dll` and `WgaTray.exe` get moved out of `%WINDIR%\system32` and `%WINDIR%\system32\dllcache`, + renamed and marked for deletion upon next boot +1. the running process `WgaTray.exe` gets killed (if the file would still be in `system32`, it would get restarted + through the `WgaLogon.dll`) +1. the 2 uninstall entries and the `WLNotify` entry get deleted from the registry +1. Now everything should be as it was before the WGAN infected your PC. + +Reboot and everything should be fine again. + +To not get the tool again through the automatic WindowsUpdate, set the update to *Notify but don't download* and when +it asks for the WGAN, de-select it and choose *Don't show again*. + + +Alternative +=========== + +Using [muBlinder](http://www.p2plife.com/forums/Official_muBlinder_Page-t320.html) you can patch your +`LegitCheckControl.dll` with new version data so that the WGAN thinks everything is fine. After 3 or 4 reboots, the +warning messages should be gone. If not, muBlinder can also remove it. + + +WindizUpdate +============ + +Users of *Firefox* or *Opera* can get WindowsUpdates without any WGA testing through [WindizUpdate](http://windizupdate.com/). +You even get updates for Mozilla-components or some hardware. diff --git a/know-how/software/windows/_posts/2009-02-19-harddisk-pio.md b/know-how/software/windows/_posts/2009-02-19-harddisk-pio.md new file mode 100644 index 0000000..371194e --- /dev/null +++ b/know-how/software/windows/_posts/2009-02-19-harddisk-pio.md @@ -0,0 +1,31 @@ +--- +title: HD uses PIO instead of DMA +layout: default +created: 2008-07-15 00:10:30 +0200 +updated: 2009-02-19 22:06:02 +0100 +toc: false +tags: + - know-how + - software + - windows + - hardware + - hdd +--- +If Windows uses PIO mode instead of DMA, it probably have slowed down due to reading errors. To fix the slow-down, find +the registry key: + + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318} + +This contains the subfolders `0000`, `0001` and `0002`. `0001` is the primary IDE port and `0002` is the secondary. But +watch the entries in there and you'll get the idea. + +The important values are `MasterIdDataChecksum` and `MasterDeviceTimingModeAllowed` as well as `SlaveIdDataChecksum` +and `SlaveDeviceTimingModeAllowed`. Delete the keys and reboot. Windows will re-detect the speed and should be back at +full DMA speed. + +Usually, this should be fixed since SP2, but it seems to not work everywhere. You could try to force a retry by adding +a DWORD-entry `ResetErrorCounterOnSuccess` with a value of `1` to that key. + + +*[PIO]: Programmed Input/Output +*[DMA]: Direct Memory Access diff --git a/know-how/software/windows/_posts/2009-03-03-missing-wzc.md b/know-how/software/windows/_posts/2009-03-03-missing-wzc.md new file mode 100644 index 0000000..e0a99be --- /dev/null +++ b/know-how/software/windows/_posts/2009-03-03-missing-wzc.md @@ -0,0 +1,24 @@ +--- +title: Missing Wireless Zero Configuration +layout: default +created: 2009-03-03 00:47:50 +0100 +updated: 2009-03-03 00:47:50 +0100 +toc: false +tags: + - know-how + - software + - windows + - wifi +--- +If you are missing the *Wireless Zero Configuration* (in German: *Konfigurationsfreie drahtlose Verbindung*), you might +have installed a D-Link driver. + +To get the Windows tool back, there's a nice manual at [practicallynetworked.com](http://www.practicallynetworked.com/qa/qa20040311.shtml): + +1. go to *Start* → *Connect to* → *Show all* (or: *Control Panel* → *Networking*) +1. right-click any device and choose *Properties* +1. click the *Install…* button +1. choose category **Service** +1. click *Have Disk…* +1. select the path `C:\WINDOWS\inf` and click **OK** +1. choose the *Wireless Zero Configuration* and confirm all dialogs diff --git a/know-how/software/windows/_posts/2009-03-18-microsoft.com-not-working.md b/know-how/software/windows/_posts/2009-03-18-microsoft.com-not-working.md new file mode 100644 index 0000000..6cdb428 --- /dev/null +++ b/know-how/software/windows/_posts/2009-03-18-microsoft.com-not-working.md @@ -0,0 +1,19 @@ +--- +title: microsoft.com not working +layout: default +created: 2009-03-18 20:05:52 +0100 +updated: 2009-03-18 20:05:52 +0100 +toc: false +tags: + - know-how + - software + - windows +--- +If you have a router and Internet works with any application/site but you can't connect to any `microsoft.com` site +(e.g. *WindowsUpdate*, *Windows Live Messenger* [error code: 81000306], etc.) you might have your MTU set to a too high +value. The default MTU for ethernet devices is **1500** but since the PPPoE header adds 8 Bytes to the packets, they +get fragmented. And the `microsoft.com` servers seem to not accept fragmented packets. + +So the solution is to set your MTU to the best value for PPPoE: **1492**. To do this, use a tool like the [TCP Optimizer](http://www.speedguide.net/downloads.php) +to set the MTU for your ethernet device to 1492. After a reboot, all `microsoft.com` pages should work again - +including *Windows Live Messenger*. diff --git a/know-how/software/windows/_posts/2009-06-05-license-keys.md b/know-how/software/windows/_posts/2009-06-05-license-keys.md new file mode 100644 index 0000000..8259e47 --- /dev/null +++ b/know-how/software/windows/_posts/2009-06-05-license-keys.md @@ -0,0 +1,22 @@ +--- +title: Windows License keys +layout: default +created: 2008-08-11 01:23:00 +0200 +updated: 2009-06-05 12:33:39 +0200 +toc: false +tags: + - know-how + - software + - windows +--- +At [My Digital Life](http://www.mydigitallife.info/2007/04/24/search-for-genuine-and-free-windows-product-keys-online-with-google/) +you can read about [Belarc Advisor](http://www.belarc.com/free_download.html) spreading Windows license keys. Advisor +is a system profiler which also includes the Windows key in its reports. Users posting them to the Internet also +publish their Windows key. A common string of Advisor reports is "*Belarc Advisor Current Profile*". Together with the +desired Windows version you can easily find license keys: + + + +This also works with [EVEREST](http://www.lavalys.com/): + + diff --git a/know-how/software/windows/_posts/2009-10-24-install-wubildr.md b/know-how/software/windows/_posts/2009-10-24-install-wubildr.md new file mode 100644 index 0000000..6ba136b --- /dev/null +++ b/know-how/software/windows/_posts/2009-10-24-install-wubildr.md @@ -0,0 +1,26 @@ +--- +title: Install wubildr +layout: default +created: 2009-10-24 23:49:15 +0200 +updated: 2009-10-24 23:49:39 +0200 +toc: false +tags: + - know-how + - software + - windows + - ubuntu + - wubi +--- +The loader for a convenient [wubi](http://www.wubi-installer.org/)-installation of Ubuntu, can be easily re-added to +the Windows Vista/Windows 7 bootloader. + +After you have transferred all Ubuntu related files to the new root drive (*files:* `wubildr` and `wubildr.mbr` and the +`ubuntu` *directory*), open a new Console **as Administrator** and run the following commands to add Ubuntu to the boot menu: + +* `bcdedit /create /d "Ubuntu" /application bootsector` + This will return an identifier in the form of a GUID - in the following commands, replace `{ID}` by that identifier! +* `bcdedit /set {ID} device partition=C:` +* `bcdedit /set {ID} path \wubildr.mbr` +* `bcdedit /displayorder {ID} /addlast` + +Done. Upon the next boot, a new entry *Ubuntu* should appear in your boot menu. diff --git a/know-how/software/windows/_posts/2009-12-05-dv-camera.md b/know-how/software/windows/_posts/2009-12-05-dv-camera.md new file mode 100644 index 0000000..6bd4b60 --- /dev/null +++ b/know-how/software/windows/_posts/2009-12-05-dv-camera.md @@ -0,0 +1,22 @@ +--- +title: Aquire video from DV-camera +layout: default +created: 2009-12-05 14:08:00 +0100 +updated: 2009-12-05 14:08:00 +0100 +toc: false +tags: + - know-how + - software + - windows + - camera +--- +If you can't aquire any video from a DV camera connected via Firewire/IEEE1394, check if you have these symptoms: + +* *Windows Live Movie Maker* says "The device is already in use." +* other programs (e.g. *NeroVision*) show a black box but let you control the camera + +The reason seems to be a faulty IEEE1394 driver in *Windows 7* 64-bit. Check the *Device Manager* whether you have the +*Texas Instruments 1394 Controller* installed. If so, right-click and choose *Update driver…*, search your computer for +drivers, install manually from a list and select the **OHCI-compliant 1394 Host controller (Legacy)** driver. + +After it is installed, you should be able to capture video again. diff --git a/know-how/software/windows/_posts/2010-01-28-gain-admin-access.md b/know-how/software/windows/_posts/2010-01-28-gain-admin-access.md new file mode 100644 index 0000000..435b69c --- /dev/null +++ b/know-how/software/windows/_posts/2010-01-28-gain-admin-access.md @@ -0,0 +1,51 @@ +--- +title: Gain Admin Access +layout: default +created: 2010-01-28 19:40:15 +0100 +updated: 2010-01-28 20:24:21 +0100 +toc: false +tags: + - know-how + - software + - windows + - hacking +--- +To get access to a Windows PC as an *Administrator* user, there is a very brute security hole which you can use. The +only thing is: You need physical access to the machine. + +The procedure is as follows: + +1. use a Linux Boot-CD (e.g. [BackTrack 4](http://www.backtrack-linux.org/) or the [System Rescue CD](http://www.sysresccd.org/Download)) + or a Windows Installation disc (of the same version as installed!) + * **Linux Boot-CD:** (there's also a nice screencast over at [offensive-security.com](http://www.offensive-security.com/videos/owning-windows-vista-video/hacking-vista-with-backtrack.html)) + 1. if not already, mount the Windows partition + 1. go to `Windows/system32/` + 1. rename the file `Utilman.exe` to `Utilman.exe.bak` and copy `cmd.exe` to `Utilman.exe`: + + # mv Utilman.exe Utilman.exe.bak + # cp cmd.exe Utilman.exe + + 1. reboot the machine into Windows + * **Windows Boot-CD:** + 1. select your Windows version to "repair" + 1. if it asks whether you want to do use *System Rescue*, say "No" + 1. after it has given up trying to repair your system, click the small link *Advanced Recovery Options* + 1. select *Command Prompt* + 1. now go to your Windows drive, for me it was `D:` + 1. do a `cd \Windows\system32` + 1. now rename the file `Utilman.exe` to `Utilman.exe.bak` and copy `cmd.exe` to `Utilman.exe`: + + D:\>ren Utilman.exe Utilman.exe.bak + D:\>copy cmd.exe Utilman.exe + + 1. reboot the machine into the regular Windows +1. on the Logon screen of Windows, press Win+U - this would normally open the [Utility Manager](http://www.microsoft.com/enable/training/windowsxp/openutilitymanager.aspx) + aka. `Utilman.exe`, but now, the *Command Prompt* should show up +1. you have `SYSTEM` rights, so you can easily add a new Administrator user: + + C:\>net user BadGuy GoodPassword /add + C:\>net localgroup Administrators BadGuy /add + + This will add the user `BadGuy` with the password `GoodPassword` and make him a member of the *Administrators* group. +1. Login with the newly created user `BadGuy` +1. Remember to delete the fake `Utilman.exe` and rename `Utilman.exe.bak` back to `Utilman.exe` diff --git a/know-how/software/windows/_posts/2010-07-13-restore-win7-mbr.md b/know-how/software/windows/_posts/2010-07-13-restore-win7-mbr.md new file mode 100644 index 0000000..0f322e6 --- /dev/null +++ b/know-how/software/windows/_posts/2010-07-13-restore-win7-mbr.md @@ -0,0 +1,29 @@ +--- +title: Restore Windows 7 MBR +layout: default +created: 2010-07-13 23:29:17 +0200 +updated: 2010-07-13 23:29:17 +0200 +toc: false +tags: + - know-how + - software + - windows +--- +If you installed *Windows XP* **after** *Windows 7*, you're left with the XP-MBR on your drive and thus only XP is +booting. + +If you happen to have hardware, which produces the [Code 5](http://www.unawave.de/windows-7-tipps/code5-error.html?lang=EN) +error upon trying to boot from the Win7-DVD, you can do the following to restore the Win7-MBR from within XP: + +1. boot into XP and insert the Win7-DVD +1. open a *Command Prompt* +1. navigate to the `?:\boot\` directory of the Win7-DVD (with `?` being the letter of your DVD drive) +1. run the following command: (with `C:` being the drive where *Windows 7* is installed) + + bootsect.exe /nt60 C: /mbr +1. reboot and use [EasyBCD](http://neosmart.net/software.php) to add *Windows XP* to the Win7-Bootloader + +

+On [unawave.de](http://www.unawave.de/windows-7-tipps/code5-error.html?lang=EN) you'll find instructions on how to +create a Win7-DVD with the Vista-Bootloader so that you don't get the `Code 5` anymore. +

diff --git a/know-how/software/windows/_posts/2011-01-10-dv-capture-64bit.md b/know-how/software/windows/_posts/2011-01-10-dv-capture-64bit.md new file mode 100644 index 0000000..b9fe063 --- /dev/null +++ b/know-how/software/windows/_posts/2011-01-10-dv-capture-64bit.md @@ -0,0 +1,31 @@ +--- +title: No DV capture possible on Windows 7 64bit +layout: default +created: 2011-01-10 21:24:19 +0100 +updated: 2011-01-10 21:25:07 +0100 +toc: false +tags: + - know-how + - software + - windows + - video +--- +On a Windows 7 64bit, I was not able to capture any DV video from a video camera connected via Firewire IEEE1394. I was +able to control the camera from the capture program (tried *NeroVision* and *magix Video Deluxe*) but only got a black +screen and no audio. + +After a little search, I found [this forum post](http://www.sevenforums.com/music-pictures-video/12371-cant-capture-my-dv-camera.html) +which suggests to switch the IEEE1394 driver from the automatically detected *Texas Instruments* one to the +***1394 OHCI Compliant Host Controller (Legacy)*** one. After that change, everything worked as expected. This seems +to only affect 64bit systems. + +To switch the driver, do the following: + +1. press Win+R to get to the *Run…* dialog, type `devmgmt.msc`, click **OK** +1. in the *Device Manager*, find the **IEEE 1394 Bus Host Controllers** group, expand it +1. right-click the **Texas Instruments…** entry +1. select **Update driver software…** +1. click **Browse my computer for driver software** +1. click **Let me pick from a list of device driver on my computer** +1. select the **1394 OHCI Compliant Host Controller (Legacy)** (that *(Legacy)* is important!) +1. click **Next** diff --git a/know-how/software/windows/_posts/2014-02-25-tango-colours-console.md b/know-how/software/windows/_posts/2014-02-25-tango-colours-console.md new file mode 100644 index 0000000..006ed1b --- /dev/null +++ b/know-how/software/windows/_posts/2014-02-25-tango-colours-console.md @@ -0,0 +1,52 @@ +--- +title: Tango colours in command prompt +layout: default +created: 2012-12-18 16:19:12 +0100 +updated: 2014-02-25 16:48:12 +0100 +toc: false +tags: + - know-how + - software + - windows +--- + + +Import this registry file: + +{% highlight registry %} +Windows Registry Editor Version 5.00 + +[HKEY_CURRENT_USER\Console] +; Black +"ColorTable00"=dword:00000000 +; Blue +"ColorTable01"=dword:00a46534 +; Green +"ColorTable02"=dword:00069a4e +; Cyan +"ColorTable03"=dword:009a9806 +; Red +"ColorTable04"=dword:000000cc +; Magenta +"ColorTable05"=dword:007b5075 +; Yellow +"ColorTable06"=dword:0000a0c4 +; White +"ColorTable07"=dword:00cfd7d3 +; Dark Gray (Light Black) +"ColorTable08"=dword:00535755 +; Light Blue +"ColorTable09"=dword:00cf9f72 +; Light Green +"ColorTable10"=dword:0034e28a +; Light Cyan +"ColorTable11"=dword:00e2e234 +; Light Red +"ColorTable12"=dword:002929ef +; Light Magenta +"ColorTable13"=dword:00a87fad +; Light Yellow +"ColorTable14"=dword:004fe9fc +; Light White +"ColorTable15"=dword:00eceeee +{% endhighlight %} diff --git a/know-how/software/windows/_posts/2014-05-29-reduce-winsxs-size.md b/know-how/software/windows/_posts/2014-05-29-reduce-winsxs-size.md new file mode 100644 index 0000000..616ca6f --- /dev/null +++ b/know-how/software/windows/_posts/2014-05-29-reduce-winsxs-size.md @@ -0,0 +1,16 @@ +--- +title: Reduce size of WinSxS folder +layout: default +created: 2014-05-29 17:35:19 +0200 +updated: 2014-05-29 17:35:19 +0200 +toc: false +tags: + - know-how + - software + - windows +--- +See [here](http://www.t-online.de/computer/software/windows-7/id_51447012/winsxs-mysterioeser-platzfresser-unter-windows-7-und-windows-vista.html). + +1. Start → Command Prompt → RIGHT CLICK +1. "Run as administrator" +1. `DISM.exe /Online /Cleanup-Image /spsuperseded`