New MS Windows System

Original written for 32-bit XP installs, now being used for 64-bit Windows7
I use these notes as a guide both for home and work machines


in rough order of importance:

  • Avira - anti-virus
  • Spybot Search & Destroy - malware remover/blocker
  • ProcessExplorer
  • FireFox
    • TODO: fresh install config notes
    • TODO: these notes should be under Firefox, and referenced or included, here
    • Sync notes
    • maximize display (not just for netbooks)
    • about:config - (etc)
  • DropBox
  • Executor (launcher)
  • AutoHotkey
  • GnuWin32 tools
  • EmacsW32
    • install package
    • get cygwin running first [hrm. not so sure I need this anymore]
    • config dropbox-awareness
    • point to shared lisp files in dropbox
  • confirm bulk of .emacs file loads
  • TODO: redo .emacs file into sub-files, so can be more easily included/excluded on ceratin systems (say, when Cygwin, Perl, etc. is not [yet] installed)
  • Screenshot tool
  • CygWin
    • TODO: rxvt installation notes, misc packages to install, etc)
    • packages: rxvt, zip
    • update .bashrc and add curr dir to PATH
  • Conkeror [via FireFox/XulRunner] - Cygwin is often a pre-requistite, if using git to pull the project
  • Pdf Reader (foxit)


(the below are not in order)


  • FileZilla
  • 7zip - open source file archiver with a high compression ratio.


Associate apps with 7zFM.exe - the 7zip File Manager (GUI)


How to split a large file using 7zip


7Zip command-line examples





  • OpenSSL - for FF extension-dev
    • uh, which I’m not currently doing



Misc set-up tasks:
swap-caps-lock & Ctrl (on a per-user basis)
create shortcuts/”shorts” folder & create PATH entry
update win-shell w/ decent properties




Install Chocolatey, and apps installed via Chocolatey
See Chocolatey
See some notes at for his bundle of apps, and how easy it was with Chocolatey.



Install NodeJs

And installs for npm
TODO: notes, or include
TODO: script it



global installs on a new system

npm -i -g eslint - EsLint?
npm -i -g http-server - Server
npm -g -g jake - Jake



Visual Studio

Install express, or whatever you’ve got
Export settings, and import on target machine
Export and import Visual Studio 2010 extensions

  1. Copy %localappdata%\microsoft\VisualStudio\10.0\Extensions to the same directory on the new machine.
    • it may be a different folder, if you changed default install settings
    • on one machine, I found it @ d:\dev\Microsoft_Visual_Studio_10.0\Common7\IDE\Extensions
      • uh, this note may be incorrect. I think I was looking in the wrong area. try localappdata FIRST
  2. Open VS on the new machine, go to the extension manager, and Enable all the extensions.
    • By default, VS disables extensions that just appear in that directory but it didn’t put there.




Getting Cygwin shells to use normal Perl

L--d knows how I got this working, because it ain’t on my netbook. Cygwin Perl isn’t even installed, but something weird happens there.


So, look at my main-install Path settings? which looks like crap....


C:\Documents and Settings\OtherMichael\shortcuts;
C:\Program Files\RCS\bin\win32;
C:\Program Files\Common Files\GTK\2.0\bin;
C:\Program Files\FileZilla;
C:\Program Files\Putty\;
C:\Program Files\lispbox-0.7i;
c:\Program Files\Mozilla\Firefox;
C:\Program Files\7-Zip;
C:\Program Files\Java\jdk1.5.0_01\bin;;


Using AS Perl with Cygwin -- has a bash-script intermediary....



Misc dev apps


WinMerge - for diff/compare, etc.


Both links have essentially the same steps (see below); the first is from the official WinMerge site; the second has more screenshots and info on one page (instead of being elsewhere in the manual).


  1. In Visual Studio, navigate to the Tools → Options... menu.
  2. Under Source Control, find the Visual Studio Team Foundation Server options.
  3. Click the Configure User Tools... button.
  4. Click the Add... button.
  5. Type in the following options in the Configure Tool.
Extension: .*
Operation: Compare
Command: {Path to WinMerge}\WinMergeU.exe
Arguments: /e /u /dl %6 /dr %7 %1 %2


  • Where {Path to WinMerge} is the path were WinMerge is installed.



See Also




Category tags

Programming installation



No comments yet.



Add Comment

 Your Message
 Enter value ← Have you entered the code number?