code65536

New version: 3.1.21.3 (based on 3.1.21-rc2) The major changes in this version are upstream: updating the base Scintilla version to the latest CVS pull and the base NP2 version to rc2 (although it's "rc", Florian made some nice changes, including the very useful splitting of the Find button into Find Next and Find Prev). Update: Florian just released RC3, which disables a new behavior introduced in RC2. This new behavior in RC2 caused problems for people who use Notepad2 as a Notepad replacement. I noticed this problem during testing, and my 3.1.21.3 build already addresses this problem if you replaced Notepad using my registry-based replacement method (which is what you get if you use my installer). So unless someone uses the old clobber-the-old-file method, the fix in RC3 is effectively already in 3.1.21.3. As a result, I plan on skipping RC3 (since this is the only change that was made in RC2->RC3). However, if there is demand for it, I can spin a 3.1.21.4 to pick up this change... (basically, does anyone use a method of Notepad replacement other than the registry-based one that my installer uses?)

Why Notepad2? Florian Balmer's Notepad2 is, in my opinion, the best text editor. Ever. All the text editors that I have tried (and I have tried a lot of them!) are either fully-featured but slow and bloated, or fast and lean but useless. Notepad2 is the best of both worlds: it is fast and lean (even on an antiquated 8-year-old laptop, it starts up as quickly as Windows Notepad!) and it has a ton of useful features. It is the ultimate Notepad replacement. Why this version of Notepad2? This is not the official Notepad2 build. Instead, this is a modified build of Notepad2. This version has the same speed and small footprint as the official version, and it has some extra features: Code folding (screenshots: 1, 2) Pristine, hassle-free replacement of Windows Notepad: this will replace Windows Notepad without overwriting any system files, which means that this will not run into problems with Windows File Protection, and the replacement can be undone by changing just one registry key Support for more formats: NFO files (it can serve as your NFO viewer!), AutoIt3, Bash, NSIS, Inno, and LaTeX Native x86-64 support Download the Addon (version 4.0.22.5, based on 4.0.22-beta5) Link: Download MD5: 72336b7a169d4f3758cdb9d4cd2b26b8 Size: 0.24 MiB μArch: x86-32 (do not use on 64-bit systems) Languages: en Link: Download MD5: 98325f33b036932e60ef4858f4f7f571 Size: 0.30 MiB μArch: x86-64 Languages: en Download the Addon (version 3.1.21.7, based on 3.1.21-final) Link: Download MD5: f87529c3b353d8d369c6c23ad02771ac Size: 0.24 MiB μArch: x86-32 (do not use on 64-bit systems) Languages: en Link: Download MD5: d8217e96882347aa065ea3e9ca574fc8 Size: 0.30 MiB μArch: x86-64 Languages: en Note: This addon is compatible with both the RVM Integrator and with nLite.

/me is surprised that nobody has considered that this could just be the unintentional result of a bug. I've seen this sort of weird key before. And I've seen similar random garbage keys in XP, too. Chances are, some program passed a stale pointer (very easy mistake to make if pointer lifetimes are not perfectly managed) when setting a registry key, and instead of pointing to a valid string value, it pointed to garbage, and garbage was what was set in the registry (if you pass garbage as a subkey name, you'll also get the garbage location as shown). This theory might not be correct, but sure seems plausible (likely, even). But I admit, the conspiracy theories are amusing.

Update: 2009/01/14 - Refreshed the installer to fix a minor bug that prevented the temp files used by the installer from being cleaned up after install in certain cases. No other changes were made, and the binaries within the installer are unchanged.

Update: 2009/01/14 - Refreshed the installer to fix a minor bug that prevented the temp files used by the installer from being cleaned up after install in certain cases. No other changes were made, and the binaries within the installer are unchanged.

There is a version column in the add/remove programs box, but by default, Vista hides this column (XP did not hide this information). If you right-click on the column headers and select "More", you can turn on the Version column, and you'll be able to see then version numbers.

IIRC, CreateWindow calls WndProc with WM_CREATE before returning. Also, if you create your RichEdit text box with CreateWindow(Ex)W, then it's a Unicode text box. Create it with CreateWindow(Ex)A, then it's non-Unicode. There's really no reason you should be using non-Unicode in this day and age. All the APIs in WinNT are natively Unicode, so you are incurring extra thunking costs every time you use one of those outdated "A" APIs.

What is this thing? This is an enhanced version of your typical "Open Command Window Here" addon: Can open a command prompt in any number of selected directories Can open a command prompt from the current directory, without having to navigate up a level Can open elevated command prompts on NT6+ (Vista, Win7, etc.) Supports many different languages Supports 32-bit and 64-bit Windows Tiny footprint (on 32-bit systems, the final installed size is less than 16KB) Open-source Screenshot Details Website: Open Command Prompt Shell Extension Install Location: %SystemRoot%\System32\ShellExt Uninstallable: Yes Download (version 2.0.3) Links: Download MD5: 0304948809aac35026f7e88b7c4ead1b Size: 0.01 MiB μArch: x86-32, x86-64 (single installer for both x86-32 and x86-64) Languages: en, de, el, es, fr, it, ja, nl, no, pl, pt-BR, pt-PT, ro, ru, sh, sr, tr, uk, zh-CN, zh-TW (Translation Info) Note: This addon is compatible with both the RVM Integrator and with nLite.

What is this thing? This is a fun toy to have on any system. It's a little like HashTab... except with more features... and better usability... and a much less bloated footprint. HashCheck gives you a hashes tab in the file properties dialog, but it lets you hash more than one file at once (and even entire directory trees). And it can create checksum files (like the .sfv files that accompany some torrents or the .md5 files that I often use). It can load and verify checksum files. And all for a final installed size of less than 100 KB. Supports both x86-32 and x86-64 systems. Screenshots Details Website: HashCheck Shell Extension (Bugs/Suggestions) Install Location: %SystemRoot%\System32\ShellExt Uninstallable: Yes Download (version 2.1.11) Links: Download MD5: 66e838262e3b71bb567df42e2f064f33 Size: 0.05 MiB μArch: x86-32, x86-64 (single installer for both x86-32 and x86-64) Languages: en, cs, de, el, es, fr, it, ja, ko, nl, pl, pt-BR, pt-PT, ro, ru, sv, tr, uk, zh-CN, zh-TW (Translation Info) Note: This addon is compatible with both the RVM Integrator and with nLite.

Microsoft just decided to change the date to 24 Aug for the fun of it; same hash, same digital signature. I had reported the bad catalog problem to Microsoft. Their response was that they couldn't reproduce it and that I should give them details on how to reproduce the problem. So I told them something to the effect of, download, install, run sfc /scannow, look at the pretty errors (erm, how else would you reproduce it?!). Anyway, one of their dev leads responded today (29 Aug), saying that they are now able to reproduce the problem, that they have "figured out the problem and will release new packages shortly." So I guess they were oblivious to the problem until now? Oh well; at least it's (going to be) fixed now.

Yea, I can confirm that this update is FUBAR. Microsoft somehow messed up the security catalog, so the only option is to wait for them to re-release this. Either that, or wait for SP3.