The Windows operating system.

Useful jEdit Registry Files

jEdit used to include a Windows installer that allowed integration with the Windows shell. Unfortunately they no longer include these registry entries.

So here they are, useful jEdit registry entries. Note that you'll need to replace ensure that the paths listed below are correct for your system. The Java path is for the default install location at "C:\Program Files\Java" for JDK version 1.5.0_07. The jEdit path is "C:\Program Files\jEdit" and will also need to be editted to point to the correct path.

You can also download a .REG file containing the contents listed below - remember, this file assumes you're using Java 1.5.0_07 installed at "C:\Program Files\Java" and that jEdit is installed at "C:\Program Files\jEdit". You'll need to edit it if these paths aren't correct.


Windows vs Linux Boot Time

So I recently switched my work laptop over to Linux, because Windows XP was running incredibly slowly. Now I know that the usual cause of "Windows XP is running incredibly slowly" is simply "spyware" but in this case, it's "corporate required spyware" (Norton Antivirus, asset tracking software, etc.). It's slowing the thing to a freaking crawl.

It turns out that there's an official way you can get out of having to run the asset software and all that other corporate software: run Linux. (This also gets you out of having a supported PC, but I can cope.)

So I installed Debian Testing on it. And the laptop boots much, much faster now. (We're talking a good two minutes to load everything versus something like 20 minutes under Windows. Not kidding.) It runs faster. About the only thing slower is that, for some reason, GNOME feels slower than Windows. (KDE too, but Debian defaulted to GNOME, and I haven't decided to change it yet. Eclipse and Firefox both use GTK+, so, I'm basically just using GNOME software anyway.) But it's really not that big a deal, because minor things like compiling and running the software are faster.


CMD Sucks

C:\>REM CMD Sucks.

C:\>SET EnvVar = 1

C:\>ECHO %EnvVar%

C:\>ECHO %EnvVar %


"This device can go faster"

So I have an iPod Mini, and a laptop that runs Windows XP. Windows XP correctly detects that the iPod Mini is a USB 2.0 device, and that I plugged it into a USB 1.1 port. It then informs me of that fact.

Nice, right? Except that I have no USB 2.0 ports on this laptop! I plugged it into a USB 1.1 port because that's all there is - I can't plug it into a USB 2.0 port. The device can't perform faster, there's no faster port to use!

Every single time I plug it in, "This device can go faster" - thanks, Windows, but if you bothered to check (and it does, because it'll display a list of USB ports available if you click on the message), you'd discover that while the device may be able to go faster, the computer can't!


Get the Facts

This is actually a really old post that never made it to my webpage, but I'm going to post it now.

Well, as some people know, Microsoft has released a Get the Facts on Windows and Linux advertising campaign explaining why Microsoft Windows is better than Linux in the server arena.

(Please note that said servers - a lot of people have managed to misunderstand that and keep on bringing Internet Explorer into the conversation, which as absolutely nothing to do with Microsoft Windows as a server platform. From now on, whenever anyone talks about Internet Explorer security holes when talking about Linux vs. Windows as a server platform, I'm going to bring up spatial Nautilus and explain how that proves that Apache sucks.)


Compiling Mozilla (well, Firefox) Under Windows for Free

Compiling Mozilla under Windows requires a C++ compiler. Previously the only way to compile Mozilla under Windows without having to pay big bucks for the Visual C++ environment was to use the free Cygwin utilities, but those didn't include all the features that Microsoft's compiler did and didn't offer all the features that Mozilla has to offer under Windows.

Microsoft has since released the build environment (but not the GUI tools) to allow developers to write software under Windows without paying large amounts of money for Visual Studio. However, the process for doing this is fairly poorly explained. (And for good reason, it's long, annoying, and impossible unless you do some extra credit which is dubiously legal.)

Thanks, Visio

OK, so I created a simple test file in Visio. No big deal. I'm done with it so I go off to close it, and get...

Visio internal error: #2222
Action 1361: Close Window

First try closing and reopening the file.  Next try restarting Visio.

First, note the action: "Close Window." Next note the helpful suggestion of "closing and reopening the file."



Subscribe to RSS - Windows