Posts Tagged ‘windows’

Virtual Desktops for Windows » Dexpot

Tuesday, September 2nd, 2008

Ages ago I started writing an article about things that Windows should blatantly steal for Windows 7.  I never actually finished it, which is why I’ve never published it here, but one of the list I’ve wanted for ages is Virtual Desktops, similar to Linux.

Well, there’s a small freeware (€10 for commercial use) application called “Dexpot” which pretty much does just that.  Almost exactly what it says on the tin, in fact.  It even lets you customise the desktop icons of the running programs too.  Pretty cool.

Oh and for those of you running Windows NT 4 or 2000 still (and why not - they still work), you’ll be glad to know that Dexpot is happy running on both those operating systems  :-)

Think inside the bochs

Friday, August 8th, 2008

Bochs logoOriginally started by Kevin Lawton, the bochs project - whose motto is “Think inside the bochs” - maintains the bochs emulator. Bochs aims to emulate - at a reasonable speed and with a fair degree of accuracy - an x86-based 32-bit PC with the AMD 64-bit extensions. It can run most operating systems inside it (as “guest operating systems”, if you prefer the VMWare term), such as Windows (3.1, 95, Vista…), Linux, Minix or one of the BSDs. (They even collect disk images as well). In addition, Bochs also runs on loads of operating systems as well - Windows, BeOS, OSX, Irix, Solaris… (more…)

Three for tonight: Java, dot Net and Flash

Wednesday, August 6th, 2008

Last night I had a hankering to watch the excellent Danny Kaye movie The Court Jester again. Hence the title: “Plan one,” says Basil Rathbone’s fiendish Ravenhurst: “The untimely demise of my lords Brockhurst, Finsdale, and Pertwee.” “Three for tonight,” Kaye replies, in his hypnotic state. “Proceed.”

Well, here’s my three for tonight: kind of in response to Cracked’s rather wonderful Tech Zombies: 6 technologies that don’t know they’re dead (and hey - I use the phonebook frequently), here’s three that ought to be dead.

dot Net

Maybe surprising this, as it’s one of the ways I make a living. But the truth is that Microsoft has been plugging this so hard they haven’t stepped back to examine whether the game is worth the candle. .Net is so slow that it has made using Windows, Office and other Microsoft products feel as slow as they ran on Windows 3.1 - and that isn’t a compliment. (Note to MS: still haven’t found any function I need in Word that wasn’t there in Word 2.0c, by the way.)

It gets worse. With Windows moving to 64-bit, the poor 64-bit support for the .Net platform is not only irritating, but a serious mistake. To run .Net applications on 64-bit operating systems without them crashing, you need to recompile them, preferably using a later version of the .Net framework. Fine if it’s a homebrew app but if you don’t have the sourcecode for your mission-critical application that runs your company… (And another note to MS: does Visual Studio 2008 do 64-bit .Net debugging yet? I haven’t tried it as so many features I need are missing from 2008 that I use daily in 2005).

Deploying ASP.Net applications is horrendous as well. ASP would just copy pages and run - .Net requires sever-level configuration. Whereas previously you could almost rely on ftp to manage an ASP site, with ASP.Net you often need to call some overstressed sysadmin to make a change in the IIS metabase XML to get things working. That feels like we’re back to OS/2’s cryptic configuration files again to me.

I won’t even go into Microsoft’s excrescent .Net-based attempt to compete with Flash (SilverBlight) because that’s pretty moribund already and only kept alive, albeit on life support, by being free - and therefore about a grand cheaper than Flash studio (although their exclusive deal to stream the Olympics is kill or cure - it’s bound to annoy every single Mac user, Windows 2000 user and non IE/Firefox user on the planet so it’s likely to make a few more enemies as of next week.)

The proper course of action would be for Microsoft to take .Net down to the vets and have it put to sleep, then announce its peaceful demise by desupporting it. Of course, what they will probably do is to bet the company on it and then sit around scratching their heads wondering why Windows is losing market share hand over fist.

Java

Write once, run anywhere. That was the slogan. Except it didn’t actually work like that.

First of all, there are so many gotchas in the JRE and the class library that you need a specific configuration of the JRE for each application. (I have known of a very well-known and respected application vendor that required a version of the JRE that was four years out of date for their application to run properly. This isn’t an uncommon scenario, either: for a while a major UK bank required using the Microsoft JVM to run their Internet banking - for almost a year after Microsoft were forced by Sun’s lawsuit to desupport it and stop offering it for download.)

Then there’s the enormous size of Java these days. Okay, so .Net tips in at 35MB, but the last JRE update I downloaded was over 100MB. Now, my ISP’s download limit is fairly generous, but come on guys - hard disks fill up quicker and quicker these days than they ever did!

Again, the best course of action Sun could take would be to wipe their hands clean of Java, desupport it and consign it to the dustbin of history. Fortunately, they haven’t bet the company on it, and aren’t likely to, but because Java runs in so many mobile phones and runs so many mobile applets - where the specific version of Java is less a problem than the specific phone - it’s likely to be around for a long time to come. Unfortunately.

Flash

Where do you start with Flash? Over the years it’s had several owners: FutureWave Software, Macromedia, and now Adobe. It started as a competitor to Macromedia’s ShockWave player, believe it or not (anyone use ShockWave any more?), was acquired by Macromedia and developed into the huge monster we know and presumably love.

It now encompasses everything: vector-based animation, movie playing, menus… in fact if you want to make your site look “cool and groovy”, the general knee-jerk reaction is to get out the Flash API and start coding.

Except that it renders your site almost completely unusable on mobile phones, PDAs, and the smaller PCs that are now the coming thing. It makes your content almost unsearchable by search engines, as well as ruining any chance that your site will be accessible. So you’ve now annoyed everyone with sight/hearing problems, and rendered yourself liable under section 509 or the Disability Discrimination Act, or both, depending on where you do business. Nice move.

What Adobe should do is to just retire the Flash product line, discontinue downloads of the Flash player and say “so long suckers, thanks for all the money”. In reality, what they will do is to cling to it like a shipwrecked sailor on a piece of board, desperately trying to swim to a cash-rich shore.

So there you are - my opinion on why three widely-used technologies should be taken out the back and shot. What do you think?

FLOSS of the week: Filezilla server

Friday, June 27th, 2008

Filezilla Server

Filezilla Logo
Licence:GPL
Status:stable
Version:0.9.25
Web:Homepage

Filezilla is pretty well known as an ftp client, but the project also includes an FTP server.

Currently available for Windows only, the server has a few advantages over the IIS ftp service:

  • Security
    The Filezilla interface is not tied into the Active Directory structure. While this may make some Windows admins groan, this does eliminate one potential source of compromises and intrusions, as it means that guessing a password on the ftp service doesn’t automatically give you a password for the actual machine that it’s running on.

  • Configuration
    Configuration using Filezilla’s GUI is a bit hard to do at first, but the groups method is powerful. For example, define a group whose home directory is c:\ftp\:u, and then just create a directory of the same name as the user inside the c:\ftp directory (e.g. c:\ftp\simon.collis) and you put the user in that group, and they have a bespoke home directory - and they can’t do “cd ..” to get to other people’s home directories either, which can happen with IIS if you’re not careful!

  • Virtual file system
    Unlike IIS, aliases show up in directory listings by default. You can also add other directories and map them - using my C:\ftp alias as above, to create a directory called shared everyone can see, simply add it in somewhere else - let’s say its real location is d:\ftp_shared. Add that in - either to the user or the group - and alias it to c:\ftp\shared. Now that directory shows up in the listings, and can be used just as if it were real. This is my only gripe, actually - that aliases are real directory names, not virtual ones. Makes working out what the filing system will be a bit confusing.

  • Bandwidth throttling
    Filezilla can limit the bandwidth used by everyone, by a group, or by a user, for upload and download. So you can have “normal” users with a smaller limit, premium users with higher limits, and an admin with no limit at all! Of course, in IIS bandwidth throttling affects your websites as well - not the way to go about it if you’re trying to hosts websites on a server where more than one person will need to ftp in and out. This won’t be an issue for everybody, of course, and I’m sure there are those IIS experts who will say “just edit the metabase and everything will be fine”. Of course it will - but there’s only one global limit for IIS, not the user-level granularity you can have with Filezilla.

Filezilla users dialogFilezilla users dialog: not eye candy, just well thought-out

In conclusion, if you’re looking for an alternative to IIS’s ftp service, not only is Filezilla robust and secure (I know of at least one production site making heavy use of it on a daily basis), the price is right and the feature set is probably just what the doctor ordered!

(PS: I’m thinking about doing this every Friday - highlight a piece of free or open source software I think you’ll find useful or enjoyable. Is that a good idea or not? Let me know in the comments…)

Vista SP1 - the case for the defence

Friday, April 18th, 2008

If you’ll remember, a while ago I had a bad experience with Windows Vista Service Pack 1, release candidate 1.

Well, it certainly seems that Microsoft did quite a bit of work following that release candidate.

Since SP1 isn’t yet available via Windows Update, so I had to go through the standalone installer route (I’ll tell you where to get them later).  But first let me give you a little bit of background as to why I decided to give it another go.

Vista was starting to run really slowly.  REALLY slowly.  In fact, nearly a month after removing the release candidate of SP1, it was again unusable.  Fortunately for me, I’d backed the machine up with Norton Ghost (disclaimer: that’s an affiliate link, before you ask), so my first job was to back everything up to my external drive.

I then got out the old trusty Windows 98 bootdisk and wiped all the partitions except my clunky Vista install.  I then created a 32GB FAT32 partition and copied the Ghost image files to that.  Then I rolled back to a Vista backup from January 2008 (well, I’m skipping a step - I went back to XP for 24 hours.  I’ll tell you why I decided not to stay that way at a later date).

The installers took a long while to download, and the installation took about an hour.  It was fairly straightforward: next, next, next, next, ok, I agree, etc.  And even though it said not to run anything during installation, it didn’t complain about Spider Solitaire :-)

So what’s the outcome?

Not much has changed, except I have a solid computer again.  It does feel slightly faster - not much, I have to admit: the short time I spent back on XP felt faster for a while - but it does feel more reliable.

Most of the actual improvements - UEFI support, cryptographic improvements,

But file copy performance?  Seems a bit quicker, but then I usually use Directory Opus anyway, and I suspect some of those improvements will be in Windows Explorer.

As for the numerous minor tweaks made, and delays they’ve removed, I suspect they all go towards a psychological feeling things are working quicker - and they certainly seem to be to me - so it’s all good.

So the verdict?  No marks for RC1, but for the full release - I’d say seven out of ten.  Maybe it didn’t have all the performance improvements they were touting, but it’s worth the time and effort.

If you want to get hold of the standalone installers yourself, you can download the five-language standalone installer for 32-bit or 64-bit Vista (they’re 434MB and 726MB respectively, and cover English, French, German, Spanish and Japanese), or the all language version, again available in both 32-bit and 64-bit versions (these are 544MB and 873MB).  Alternatively, if you’ve got a lot of PCs in your firm that will need updating, you can get the installer discs - there’s a 544MB ISO image for 32-bit PCs, as well as a 1418MB DVD ISO for both 32 and 64 bit versions.