Fireworks Auto-Kern bug: Vista issues

Adobe Fire­works is a pretty bril­liant pro­gram for rapidly devel­op­ing web lay­outs in a kind of best-of-both-worlds way that enjoys the ben­e­fits of both vec­tor and bitmap design, with­out all the frus­tra­tions that come along with smart objects. Its text han­dling is also superb, offer­ing a whole lot of cus­tomis­able set­tings that are very use­ful for mock­ing up web designs, not read­ily avail­able in either Pho­to­shop or Illustrator.

How­ever, it is not with­out its faults. On Vista, when typ­ing text in Fire­works things can occa­sion­ally go very, very wrong. The solu­tion at least ini­tially is to turn off the “Auto Kern” option in the Prop­er­ties dia­log — but this removes one of the big ben­e­fits of using Fire­works in the first place!

There are other options. The prob­lem will go away (some­times) when the file is closed and Fire­works is restarted — this is hit and miss. More per­ma­nently, dis­abling Vista’s fancy-pants Aero theme (the thing that makes all win­dow bor­ders trans­par­ent, gives that snazzy Start + Tab effect, etc.) will ensure you have a glitch-free Fire­works font experience.

The real solu­tion? Sneak into Adobe HQ and write a patch to fix the stu­pid thing!

In support of piracy

I am rein­stalling Win­dows on a few of the sys­tems here tonight and things are rapidly get­ting ridicu­lous. This is a not-altogether-abnormal house­hold in terms of com­puter own­er­ship (def­i­nitely on the upper side of own­er­ship, but I know fam­i­lies with­out geeks who have sim­i­lar num­bers of com­put­ers, just on a one-per-person basis), and it’s actu­ally get­ting impos­si­ble to keep track of things. Microsoft don’t offer domes­tic site licens­ing. But, damn, they should. I’m using Pro­duKey to audit licenses because I’m never going to affix those ridicu­lous OEM stick­ers to any­thing (so bite me, I’m a crim­i­nal) when they’re licensed with what­ever dodgy hard drive or net­work card I bought them with. Accord­ingly, I’ve lost the key (yeah, $AU200 value) of one sys­tem, and con­fused the keys of three oth­ers — because, get this, we paid for three legit aca­d­e­mic licenses which LOOK EXACTLY THE SAME AND DON’T HAVE STICKERS. So com­pli­ance on at least three sys­tems is ren­dered damn near impos­si­ble, even if you do fol­low all of their ridicu­lous rules to the letter.

Not to men­tion the OEM copy of XP MCE sit­ting in a draw that I’d lost track of (I think the sys­tem is now using a reg­u­lar XP Pro license) or the mis­cel­la­neous sys­tems that have affixed OEM licenses but for which there is no (mis­placed) phys­i­cal media.

Accord­ingly, if I want to obey the OEM sticker direc­tive, I’ve got to down­load a CD ISO from a tor­rent site (because I don’t fork out for MSDN). But MSDN is increas­ingly attrac­tive; it effec­tively offers the desired out­come. Unli­censed, unac­ti­vated sys­tems that work per­fectly well on a sub­scrip­tion basis… sure, subs suck, but when­ever they stop their XP acti­va­tion servers we’re all going to be screwed, any­way, so it hardly matters.

Mean­while, I’m sit­ting here mak­ing a list (on paper, which I’ll store with the phys­i­cal media) of all the licenses in use, and roughly where. Thanks to the unau­tho­rised rebuild­ing of sys­tems that I own and have built from scratch so often (resource­ful­ness in any­one else’s book, evil work of a pirate to the dra­con­ian OEM over­lords) what­ever descrip­tions are attached to afore­men­tioned sys­tems is likely to be ren­dered com­pletely untrue in eigh­teen months time when I once again get around to the whole­sale slaugh­ter rebuild­ing of them all. Inter­mit­tent rein­stalls will prob­a­bly hap­pen, too, unless I’m dri­ven so insane by the inabil­ity to dis­cern one license from another I end up, as I do now, sim­ply tak­ing out the lot and shoot­ing them all a new install.

To Microsoft: whatthe­hell­doy­ouwant­metodo? I am so not fork­ing out the at-least-$2000 you would have me pay for retail Vista licenses for this lot – it’s that much because Vista Busi­ness retail licenses come in at a deli­cious $500 each. Say it with me: hell no. I’ve heard from a reli­able sys­tem builder source that you’ve been telling them that the new OEM rules work in their favour as it’ll bring them more busi­ness. Sure, but it’s pretty crappy busi­ness if I don’t say so myself. I have absolutely no inter­est in becom­ing a Microsoft cer­ti­fied sys­tem any­thing, sim­ply because it’d mean deal­ing with your crap in a pro­fes­sional capac­ity, and I deal with it quite enough in a pro­fes­sional capac­ity try­ing to do other sorts of devel­op­ment as my job, thanky­ou­very­much. I’m not going to pay a Microsoft tax twice (first for cer­ti­fi­ca­tion, sec­ond for indi­vid­ual licenses) just because you claim that your crappy sys­tem builders do it bet­ter than DIY-ers.

When­ever the time comes around to upgrade to Vista, if I ever deem it worth­while on the other home desk­tops here not for any com­mer­cial pur­suits (still run­ning Busi­ness in response to the crip­pling net­work­ing capa­bil­i­ties of all Home line prod­ucts), I’ll be mak­ing a trip to my local store, who, for what it’s worth, don’t even offer retail Vista Busi­ness for sale on their web­site, but men­tion the OEM edi­tion an awful lot, with the token “(only sold w/ new sys­tem or to a sys­tem builder)” tacked on to pla­cate any­one from offi­cial­dom who comes look­ing. I haven’t had the plea­sure of break­ing OEM conditions-of-sale (that’s all they are… are such things even legally enfor­ca­ble in this coun­try?!) just yet, but have no doubts there will be ample places that want to take my money when and/or if I do.

I’m actu­ally in the posi­tion of hav­ing one spare XP license (two if you count XP MCE) at this point, but am sorely tempted to install Linux on at least one of the three sys­tems I’m tak­ing care of tonight just to avoid hav­ing to deal with these mediocre attempts at extor­tion in the future. It’s not morally defen­si­ble to refuse to acknowl­edge sys­tem builders as “orig­i­nal equip­ment man­u­fac­tur­ers” when they are, in fact, con­duct­ing exactly the same tasks as their so-called ‘cer­ti­fied’ builders. Clearly, it’s not being pur­sued for retail sale: the only retail prod­ucts that belong in an oper­at­ing sys­tem prod­uct mix are upgrades for peo­ple who enjoy hav­ing com­put­ers that don’t work (i.e. most of the pop­u­la­tion, anyway).

It’s an indict­ment upon the dif­fi­culty of upgrading/reinstalling Win­dows that so few peo­ple take this route: quite frankly, the prod­ucts don’t work. Every­one who is unqual­i­fied (in the lit­eral, capable-of sense, not some arbi­trary dida­course, paidMS­somem­o­ney sense) to build a com­puter, in my expe­ri­ence, is unqual­i­fied to suc­cess­fully install Win­dows inde­pen­dently. Even if they suc­ceed at boot­ing from a CD, nego­ti­at­ing the installer prompts (admit­tedly bet­ter than they used to be), man­u­ally answer­ing ques­tions about day­light sav­ings and other such things that should long since have been dealt with automag­i­cally (c’mon, we’ve had GeoIP prod­ucts for what, ten years now? Longer?), or at least cor­rect from the out­set (two HP machines last week were insis­tent the default time­zone should be Sin­ga­pore. They shipped in Aus­tralia. Is it so bloody hard to pick a pop­u­lous east-coast state zone as the default?), chances of users cor­rectly installing things such as dri­vers in post-install stages are slim to none. Nearly all phone a tech-saavy friend (I know no-one who’s ever called the Microsoft sup­port line for OS installs… more should, but few do).

The point stands: retail licenses are for new­bies, OEM licenses should be acces­si­ble to every­one who doesn’t give a crap about shiny pack­ag­ing, man­u­als, and shoot­ing their wal­let to bits.

Here endeth the rant.

Some numbers from Vista’s crash reporting

Win­dows Vista ships with a delight­ful tool by the aid of which it reg­u­larly digs itself a grave. Here are some find­ings after three months of use, sorted by num­ber of crashes.

Microsoft Inter­net Explorer 92
Win­dows Prob­lem Reporting 52
Appli­ca­tion Launcher 17
Win­dows Explorer 12
Adobe Pho­to­shop CS3 8
Microsoft Out­look 6
Microsoft Zune 4
Mobile Net­work­ing Wizard 4
Skype 4
Win­dows Media Player 4
Adobe Bridge CS3 3
Adobe Illus­tra­tor CS3 3
Adobe Dreamweaver 8 3
Fire­fox 3
Sync man­ager 3
Win­dows Task Manager 3
Adobe Pre­miere Pro CS3 2
Eclipse 2
Gephex 2
Win­dows Live Messenger 2
Adobe OnLo­ca­tion CS3 1
Adobe Pho­to­shop CS2 1
Dri­ver soft­ware installation 1
Filezilla client 1
Microsoft Pow­er­point 1
VLC 1

By ven­dor, that con­sti­tutes 176 crashes/hangs/‘not-respondings’ of Microsoft soft­ware to 21 of Adobe soft­ware over the same period. Now, it feels like I’m cheat­ing the num­bers here by report­ing Win­dows Prob­lem Report­ing itself, because prob­a­bly 90% of its crashes occur when report­ing on Inter­net Explorer, but hey — these are the num­bers Microsoft’s soft­ware itself gave me, so who’s complaining?

In case you think this isn’t a fair com­par­i­son for rea­sons of time spent using var­i­ous pro­grammes, exclude Prob­lem Report­ing crashes (though you shouldn’t) and the Microsoft stat comes down to 124. That is, lots.

I can’t think of a day since own­ing this com­puter I wouldn’t have used at least one piece of Adobe soft­ware, most com­monly more. To be fair, Adobe soft­ware is more likely to do weird things (like, ya know, refus­ing to save) caus­ing me to restart the appli­ca­tion rather than let­ting it ‘crash’ per se… but Microsoft’s junk is vastly less likely to give me any sort of warn­ing before flak­ing out.

These crashes are reported over a three-month period span­ning Novem­ber 26 until Jan­u­ary 25.

Vista SP1 con­tin­ues to be eagerly awaited.

MS Explorer sinks

This story appeared in today’s SMH — note the erro­neous (yet highly amus­ing) cap­tion on the lead photo:

(screen­shot­ted for pos­ter­ity if they go editing)

They say they don’t know why it sunk. I blame Vista ;-)

Update:

So per­haps SMH’s typo was mixed up. ABC (Aus­tralia) are run­ning a story on their web­site wherein it’s uni­ver­sally called the MS Explorer. An ill-fated name for a ship, no doubt!

Per­haps Mid­night Com­man­der or Finder would be a more suc­cess­ful name? ;-)

# by Josh on November 24th, 2007 Tags: , , , ,
| No Comments »

Subclipse Proxy problems

Finally, Subversion’s PROPFIND is enabled on the proxy server at one place I work, but for some rea­son Sub­clipse was still being a lit­tle bit special.

Turns out it doesn’t use Eclipse’s HTTP Proxy set­tings, but needs set­ting elsewhere.

On Win­dows XP, this will be in your Appli­ca­tion Data path under Sub­ver­sion. Mine is as follows:

C:\Documents and Settings\joshs\Application Data\Subversion

I haven’t got a Vista machine to test on, but it will still be the Appli­ca­tion Data\Subversion folder within the user’s path. (I will con­firm this next time I’m on a Vista box.)

Linux users, look in ~/.subversion/

Open the file “servers” (no exten­sion) and scroll to the bot­tom sec­tion, [Global].

Un-comment and edit the http-proxy-host and http-proxy-port set­tings (and user/password if required, it wasn’t for me) as appro­pri­ate and every­thing will start work­ing. You don’t even need to reload Eclipse.

Pro­duc­tiv­ity just soared!

No Vista before SP

Appar­ently I’m not the only one think­ing this way about Vista. Though it looks awful pretty, and if I bought a PC with it installed I’d prob­a­bly have a hard time con­vinc­ing myself to buy another XP license just so I didn’t have to use Vista for a few months! On the flip side, I would def­i­nitely con­sider hold­ing off a hard­ware pur­chase that included a Vista license for a few more months, know­ing a Ser­vice Pack is imminent.

Of course, if they’d got it right from the start, I’d be run­ning Vista already… as it stands, I’m not too likely to drop $200 on some­thing that runs slower than XP, sup­ports less hard­ware, has arguably-worse power man­age­ment, and makes the occa­sion­ally excru­ci­at­ing UI mis­take (most notable is the auto­matic replace­ment of the “sleep” but­ton with “install updates and shut­down” where updates are avail­able). Really, the main rea­son I’d switch is to have con­sis­tent UI between Office 2007 and the rest of the sys­tem (instead of the presently absurd Vista-ish (but not actu­ally Vista) UI avail­able on XP), newer hard­ware (inso­far as XP isn’t avail­able), and a paid-for upgrade path… I’d rather fork out my money now and trust that another 3 ser­vice packs are com­ing, rather than pay full price for an OS and then pay full price again, and again. I acknowl­edge this is par­tially a psy­cho­log­i­cal thing stem­ming from my oppo­si­tion for pay­ing for point-releases, but even so… many of the alleged ‘upgrades’ in OS X are thor­oughly trivial.

Windows language handling sucks

The lan­guage bar will ran­domly change lan­guages, and ran­domly dis­ap­pear, and because it’s han­dled at an application-specific level (admit­tedly a largely sen­si­ble deci­sion) this means restart­ing appli­ca­tions just to change the lan­guage. This pisses me off immensely. Almost to the point of “if Vista did it bet­ter I’d con­sider switch­ing”, and I don’t even have that much to do with lan­guages other than english.

I’ve not used this much on any­one else’s sys­tem, but haven’t done any­thing par­tic­u­larly crazy with it and it still sucks… soooo… I blame Win­dows. I’m almost cer­tain main­stream Linux dis­tros can han­dle this bet­ter, but know noth­ing about how OS X deals with it… shrug.

# by Josh on May 19th, 2007 Tags: , , ,
| 2 Comments »