If you’re still reading this, you have the old URL for my blog.
Where before it used to say http://xqrx.com/wp/, it should now say http://xqrx.com/pop/.
Please update your bookmarks and RSS feeds.
If you’re still reading this, you have the old URL for my blog.
Where before it used to say http://xqrx.com/wp/, it should now say http://xqrx.com/pop/.
Please update your bookmarks and RSS feeds.
I’ve been busy with the local community theatre group here in Lloydminster. We go on stage this weekend for three nights. The first night was completely sold out, so they added another night before the first night, which is almost sold out. The second date, which became the third date, is the matinee, and is almost halfway booked. We anticipate walk-ins on that day through word of mouth from the first two nights.
Here’s the latest press, which includes me in the photo.
A shot from a dress-rehearsal
I’m off Facebook.
I joined in (I think) 2006 and after the latest changes, combined with their increasingly bizarre opinion on privacy, I decided to run for the hills.
The hills of Google+.
Ironically, I wrote an article some time ago about Google and its potential to know everything about you. I may have even mentioned Big Brother.
I’m also fully aware that Eric told everyone that if they don’t want people finding out stuff about them, they shouldn’t be doing it in the first place.
And yet, I trust Google+ more than Facebook. Perhaps it’s because we know they’re an advertising company already. Perhaps it’s because while Larry and Sergey are smug and own planes, they seem somehow less smug than Zuck.
I have a friend who is in a relationship with a Facebook engineer. As far as I can tell, said engineer is respected in his field. I don’t begrudge him for being a Facebook employee either, because everyone has to eat.
But I don’t think I’ll be returning to Facebook.
Google+ is what I wanted Twitter to be like when it grew up. I have over 350 people in my circles. Most of what I post is public. Like Twitter, most of what I post is reposting what someone else said, that I find interesting or controversial and think my followers would enjoy.
I think rationalising social networks is a mistake. We need to talk to others. I squee when Jeri Ryan comments on a comment I made. I like that Edward J Olmos follows me on Twitter. I do it because it’s fun and I can do it on my own terms.
Facebook seems to be forcing people to have fun on its own terms. And then it wants to sell you stuff.
Just because 800 million people are doing it, doesn’t make it right.
That’s how wars get started.
I was at first jubilant to hear that Julius Malema is now banned from singing Dubul’ibhunu (translated as “Shoot the Boer”).
And then I realised that a court judging this as hate speech is setting a dangerous precedent. How quickly I forget that my own uncle had to flee South Africa in the Apartheid years for writing something the government didn’t like.
Where do we draw the line? I think the ANC should have asked him to stop. But it shouldn’t have gone to court.
I’ve taken the plunge after trying it out on Facebook and Twitter for a few months, to change my surname to “West”. This is a shortening of my husband’s surname to be more palatable to the Canadians. Plus it’s two letters shorter than my old one.
There are at least three ways to change your last name, and I’m using the “common usage” method. I get everyone to call me by my new name, and in time I’ll ask the government to change my ID documents to match the new name. It’s fairly straight forward.
Recently I decided to install Windows 7 on my iMac. I have the 27″ Core i5 model, which is a whole lot of screen and power.
Unfortunately, Boot Camp’s drivers for the screen brightness were abysmal, and I ended up getting a severe migraine after playing a game for two hours because it was too bright.
Enter ATI Catalyst Control Center, the alleged savior. Except for some reason, version 11 doesn’t seem to want to install anything that lets me manipulate the brightness.
I eventually found a program (free of charge, no longer supported) called Desktop Lighter 1.4. It is superb. I am now running it at 5% brightness and now it looks like my OS X brightness.
The small matter of the mouse not obeying the brightness rules was remedied by enabling mouse trails, with the short setting, and now I can enjoy the vast expanse of Borderlands on my 27″ screen.
NCANE.COM is five years old this month. What started out as a side project grew astronomically with the advent of Twitter, and as a result, I was deluged with spam and shut it down to unregistered users. You know, you guys.
So I do apologise about that. Seriously.
What I’m planning to do now is shut it down permanently. I did what I needed to with the project, which was to advance my PHP and MySQL skill levels. I even open-sourced the project under the MIT license (that’s more open than my own blog).
As for the over thirty-thousand URLs that were created, I haven’t decided yet. Some people rely on these links to this day (I’m one of them), and because of the generous pass-through image handling I built into the engine, that could break a lot of websites. I don’t want to do that.
I am also considering releasing the links to the public (with the originating IP addresses removed for protection of the guilty). As 30 000 isn’t really that many, it could easily fit in a CSV or XML document which will compress down very nicely.
Thoughts and comments are welcome.
I’ve installed WPtouch on this blog now, to allow mobile users to get a properly formatted experience. I apologise for not doing this sooner. I think it looks awesome on my phone.
Holy hell, it’s hard to recover mail from an Exchange server if you’ve lost your domain controller. But I’ve done it. Once again, I’m a legend.
On Monday, a customer’s Windows 2003 Small Business Server went down due to a planned power outage. When it came back up again, the drives were corrupt. Their most recent backup was over a year old, and the RAID mirror had replicated the corruption.
I spent the better part of Monday and Tuesday fighting with the machine. Before I did anything, though, I imaged the data. I then replaced the existing drives with new 1TB drives to eliminate hard drive failure, and then began the arduous process of rebuilding data.
Active Directory was gone. I was able to log into the server using cached credentials. All attempts at either backing up or repairing the NTDS folder failed miserably. I reimaged the new drives probably four times.
Then on Wednesday morning, the server stopped booting. My boss and I decided to replace the hardware and begin rebuilding the server from scratch. This is an extremely painful process, because it means literally recreating years of configuration, certificates, licencing, e-mail and user data in a few days.
I was able to repair the Exchange database, using the built-in command-line tools. I made a backup of the EDB and STM files on a separate partition, along with the user shares and the Intranet website files (and SQL database), to prepare for the server rebuild.
Yesterday, Thursday, it became clear that Windows 2003 was not going to run on the new hardware we specified. What ever I tried, Active Directory kept failing. Whether at the initial AD setup phase, or during the Exchange 2003 installation, we got error after error.
So it was with a bold and insecure step that we decided to put our faith back in the original server. As the hard drives had already been replaced, I decided to replace the power supply as well.
As of right now, the server is still going strong. I believe that the power outage caused damage to the power supply in the server, which in turn caused corruption on the drives. With a new supply, the server has been performing admirably (despite being a Dell).
Tonight, I decided that I would spend some time this long weekend to recover the Exchange mailboxes. If you know anything about Exchange, you’ll know that it is deeply tied to Active Directory. Since I’ve had to rebuild the server (and change the domain name to avoid conflict when we reconnect the server to the network), all associations between the old Exchange database and the new domain are severed.
There are tools that Microsoft provides, to allow reconnection of the Exchange store. However, there are some steps one must follow:
1. Ensure that you’re logged in as a Domain Admin. It’s the right thing to do in this case.
2. Shut down the MSExchangeIS service and swap the EDB and STM files with the ones you’ve recovered from the old server.
3. Restart the Information Store service, and mount the store you’ve switched in.
4. Make sure the user has full rights on the Mail store, including Receive As and Send As permissions.
5. Now the fun part: if you’ve changed permissions, you should restart Windows. It’s quicker than waiting for the AD to replicate permissions (usually 15 minutes, but can take longer). I was fortunate in that I set up a LAN consisting of only one machine: the server.
6. Once in Exchange System Manager again, hook up the Administrative Group display. It gives you more options. You’ll have to go out and come back in again.
7. Now create some AD users. Make sure you do not give them email addresses, or associate them with Exchange. The reason is simple: you want to assign the old mailboxes with the new users.
8. In the mail store, set the Limits to 9999 days for keeping items. This will bring across every item associated with the old mailbox for the user.
9. In the Mailbox Recovery Center, hook up your mail store. You may need to refresh something, or run the Cleanup Agent or something. I forget now.
10. Right click on an account, and Find Match. If the AD user you’ve created has the same name, you’re in luck. You can then Reconnect it and it’ll be happy.
11. Once you’ve reconnected all of the mailboxes, start up Exmerge. This tool allows you to export and import mailboxes in PST format. Very nice. Very useful.
12. Using the two-step process, export all the mailboxes from the mail store to a folder on your hard drive. Make sure the errors are managed accordingly.
13. Shut down the Information Store again, and switch back the new files.
14. Restart the Information Store and mount the store if necessary.
15. Using Outlook from each users’ machines, import each PST file back into Exchange. Personally, I’d do this route instead of maintaining the old mailboxes, because you can take this opportunity to clean up each mailbox.