During the course of my career, I’ve had to deal with some quite bizarre things jumping out at me from the source of pages. One developer I know, from a well-respected firm (to spare your blushes I won’t link to it, Kev) is in the habit of using <div id="mchammer">
“because it’s a wrapper”) but I think such oddities, which don’t break any SGML or XML parser, have pretty much broken me. I was briefly stymied this morning by the following querystring (identifying information stripped out):
http://app.whitelabeldating.com/api/wld.cfm?siteid=XXXX&apikey=XXXXXXXX-XXXX-XXXX-XXXXXXXXXXXXXXX&method=latest_members&gender=2&maxage=90&limit=3
At first glance, I briefly found myself wondering, “A pikey? What’s a pikey got to do with it?”
Like many IT professionals, I’m still heavily involved in deploying and supporting Windows XP. While most of the compatibility and performance problems with Vista have been addressed in SP1, there is still a clear case for a lot of businesses to run XP for a variety of reasons, mainly revolving around compatibility with third-party applications.
I’d like to share one caveat I’ve recently discovered while setting up an editing workstation on XP to run Avid Xpress Pro.
The system had already been set up with a Vista Ultimate in line with the company’s migration policy, however it had to dual-boot into XP Pro 32-bit in order to run Avid, which relies on kernel-mode drivers that remain incompatible with Vista. It is my normal practice to slipstream all available service packs onto the install disc to cut down on install time, however during the process of the install I discovered that there is no way to install the Realtek HD Audio drivers after SP3 has been installed. So the procedure can best be summed up as:
- Install XP SP2
- Install all hardware drivers
- Patch to SP3 using a separate disc
- Install updates post-SP3.
Apparently Microsoft is aware of the issue, but given their retirement of XP to OEM channels on 30th June, I very much doubt that they will devote much effort to resolving it.
So, here endeth my hacking of Wordpress. For now.