Brad Wardell's Blog


WinCustomize Tray 1.0 released!

Published on Monday, October 6, 2003 By Brad Wardell In WinCustomize News

If you have a premium WinCustomize subscription you can now download the new WinCustomize Tray 1.0.

It sits in the system tray and lets you know when new skins and themes are added to WinCustomize and makes downloading and applying them very easy.

Check out these screenshots:

https://www.wincustomize.com/wcmag/Sept2003/wc-oct03.jpg

https://www.wincustomize.com/wcmag/Sept2003/wc-octo3a.jpg

WinCustomize Premium Subscriptions cost $20 for two years. That's less than $1 per month! And the money from it goes to pay for this site.  Last month, over 1.8 million different people visited this site! So you can imagine the bandwidth and computer bills.

Subscribers also get access to the WinCustomize browser, a program that directly accesses the underlying database that drives this site making searching and browsing and applying of skins incredibly easy and fast. Plus you get premium suites, unlimited downloads, and other goodies.

If you already have a WinCustomize subscription, go to "subscriber resources" down in the bottom left of this page and you can download it there. Otherwise, you can become a WinCustomize premium subscriber right now:

https://www.wincustomize.com/store/

We're running out of organs to sell! You can make a difference, become a WinCustomize subscriber today!

My rant about uxtheme patching and msstyles

Published on Monday, October 6, 2003 By Brad Wardell In WinCustomize Talk

I'm in a ranting mood today. So I'm going to talk about the whole msstyles, uxtheme, thing on Windows XP.  Now this rant is not aimed at people who choose to make msstyles. I have a very high opinion of anyone who takes time to share with the world anything they create regardless of whether it's for Litestep, msstyles, Hoverdesk, or of course our stuff.

Windows XP comes with its own "visual style engine". That's how you get the blue, silver, and green "styles". But that's all there are. That's because the interface to change them, uxtheme.dll will only use Microsoft digitally signed msstyles (the file that contains the "visual style").  So if you want more, you've got two choices: 1) You can make your own format and apply them (which is what WindowBlinds does) or 2) You can try to crack the security out so that you can use unsigned msstyles.

This is a bit of a sore point for me as a software developer because certain..companies have made it out that they are actually skinning Windows when in fact all they've done is crack the security built into uxtheme.dll.  Hey, if you want to mess with your system DLLs then it's your system, go for it. But what really rips me is how companies try to make it out like patching uxtheme.dll is somehow a safe and easy thing. It is if you're reasonably technical. But those who advocate that don't tend to show up when a new Windows XP service pack shows up and the system won't boot or their title bars are all missing or whatever.  The same company doing this stuff is planning on adding support to change the "boot screen".  I somehow doubt they'll make it clear that to change the boot screen you have to patch the actual Windows kernel (which is why we don't mess with that).  Similarly, those patching uxtheme are stuck having to replace their shellstyles.dll. There are whole websites now that allow people to essentially distribute copyrighted parts of the Windows OS without a) any regard to the piracy issues and without recognizing that when you replace the actual code binaries, bad things may happen in the future. 

That said, I have nothing against people patching uxtheme.dll to apply their own hacked msstyles (there's no such thing as a pure .msstyles file -- they are actually a .DLL renamed with graphics resources inside which means, amongst other things, it's a dead end -- come Longhorn, .msstyles go bye bye).  I just wish its proponents (as well as companies that make a profit off of cracking Microsoft's digital signing security) would be up front about what they do instead of passing what they're doing A) as "their" work and Stop making it out like patching out system DLL security is somehow a "native" way of getting more visual styles. To me native doesn't include the words "patching" and "system files" in the same sentence.

And patching uxtheme certainly doesn't add features. It just means you can, basically, replace the bitmaps of the Windows XP blue, silver, green, msstyle.  This is probably why when Microsoft wants to add more visual styles for a promotion like with the Xbox or Age of Mythology it's WindowBlinds they use as well as what they recommend to OEMs. WindowBlinds doesn't hack the system. What really galls me is the idea that someone would charge the unwary for the patch. It would be like charging money for a program that changes wallpaper because users didn't know where the wallpaper changing dialog was.  I probably wouldn't have such a hard time with the charging of such patching if there was some value-add.

So that's my two cents on that subject. Incidentally, *I* do have my uxtheme patched because I use both WindowBlinds visual styles and msstyles. I certainly didn't pay to do it, I did it myself with a hex editor. But I've been digging into OS internals for over a decade and I don't freak out if my system doesn't boot up. I know how to get back to a command line and mess around with system restore if need be.  But that's the thing, I know what I'm getting myself into. I suspect most normal people with lives who are interested in customizing their PCs just want to download a program that will work well. Not one that may or may not work on the next service pack.

The only other sore point about msstyles is their relentless advocates. People who would, if they could, wreck skinning for the long term because they hate the idea of someone making money on customizing.  Hey, if you want to use msstyles, go for it. It's your PC. But don't go on some web forum and tell people it's somehow better than WindowBlinds because, sorry, that's ridiculous. Besides being relativley primitive in features, msstyles are slower, use more RAM, are larger to download, don't fully skin existing programs, and have only a fraction of the # of visual styles that are available for WindowBlinds. Oh and did I mention they're doomed after XP?

That isn't to say WindowBlinds is perfect. But it is to Photoshop what msstyles are to MS Paint. MS Paint is not a bad start but don't try to argue that it's better than Photoshop. Oh, and in this analogy, Photoshop uses less RAM than MS Paint.

These days the more vocal msstyles zealots will try to say "Well, all the WindowBlinds skins are bloated and ugly.." which means, of course, that they didn't really bother to look. If you scan the net for msstyles, you'll find that they are typically just like Windows XP except now a different hue. Maybe they're purplish.  Of course, you can do this with WindowBlinds without having to find a new visual style since WindowBlinds can change the color of a skin on the fly. That doesn't mean there aren't great msstyles floating around on the net -- there are (of course, SkinStudio can convert them to WindowBlinds since WindowBlinds is a superset of features but I digress). 

But the thing is, WindowBlinds has been around for 5 or so years now, its community has moved way beyond the initial hacker demographic that the msstyles user base is at (and likely to stay at since, like I said, it does require you to crack system DLLs to use which ain't for the average user).  So the styles and tastes are all over the place now. But yea, it too for the first couple of years mainly fixated on those minimalist "Look, it's like KDE!" skins.

Stardock? Where'd that name come from?

Published on Friday, October 3, 2003 By Brad Wardell In Blogging
A user asks:
> > However one minor thing missing I think. How did you come up with the
> > name Stardock exactly?

That's actually a funny story...

So it's 1991 which is when I founded Stardock Systems (DBA, Not incorporated at this point). I got ahold of a whole sale PC parts catalog which, back then, was a pretty big deal.

I called up the place to start ordering parts for a PC and the guy on the phone says "What company is this for?" Being a stupid 20 year old, I panic'd thinking "Oh man, I'm not supposed to be using this catalog, I'm going to get into trouble I better think of something fast!"

Well, I was re-reading Raymond E. Feist's Magician series and I looked down at the book and saw the word "Stardock". I blurted into the phone, "Uh, er the company name is...Stardock....Stardock....Systems! Yes. That's our company. Stardock Systems."

And the rest is history.

10 years of Stardock

Published on Thursday, October 2, 2003 By Brad Wardell In OS Customization

Introduction

October 2003 marks the 10 year anniversary from when Stardock was first incorporated. It's really hard to believe that it's been that long. Age creeps silently upon us and as I've looked at recent photos, I can tell that I'm no longer the "kid" I was when this all began.  I founded Stardock while I was attending Western Michigan University. It was supposed to be a temporary thing. I'd run out of money to pay for school and was already working 3 other jobs and started a 4th (Stardock) to make ends meet.  It's been a long journey since then. So if you're not bored already, sit back and I'll reminisce with you on the history of our odd little company...

1993

Incorporating was my mom's idea. She's the one that took care of it all paper-work wise. She was concerned about potential lawsuits and being incorporated would (in theory but not so much in practice) provide some legal protection. The other benefit is that it gave a better impression to IBM.

IBM? Well yea, you see, in 1993 I was working on an OS/2 game. The first "major" commercial OS/2 game called Galactic Civilizations. I was doing it from my dorm (and later apartment) at WMU. I started doing it with GNU CPP since it was free -- I couldn't afford any real tools. But a group at IBM was pissed off at Microsoft over the "betrayal" of Windows 3.0 and they were determined to make OS/2 compete head to head with Windows. That meant OS/2 needed games and since mine was the only significant one in development, they helped me out. Not with money mind you but they sent software, compilers, documentation, etc.

But when IBM management started getting more serious, they looked for my "D&B" listing (Dun & Bradstreet"). There was none. And having the company be a DBA "Doing Business As" which is what I'd been working as wasn't going to cut it. So Stardock Systems became Stardock Systems, Inc.

My friends Andy Arvanitis and Chris Dailey helped me out on programming issues on Galactic Civilizations. My knowledge of OS/2 programming let alone C programming was pitiful. I had 2 books: "Teach Yourself C in 21 days" and "OS/2 2.0 Presentation Manager Programming". If it weren't in those two books it wasn't in the game.  So what does that mean? Well in GalCiv, every ship, star, planet, etc. was actually a window of style SS_ICON.  My books didn't cover how to do graphics programming but they did show how to create a window and put a picture on it.  So GalCiv probably has the record for the program with the most windows in it -- several THOUSAND (let me put it this way, a typical program may have 4 windows in it total). For artwork in the game itself, such as the aliens, my friend Bill Zalenski provided that.

1994

In 1994 I got my first hard business lesson -- contracts are only as powerful as the legal force behind you. Galactic Civilizations was released for OS/2. It got great reviews. It allegedly sold very well. I say allegedly because Stardock never got paid for a single retail copy of it. The "publisher", it turned out, was essentially a 1 guy operation who didn't know what he was doing and simply didn't pay any royalties even though we (And I'm using the "royal" we at this point) were entitled to 50% of the gross revenue.

So Stardock almost died before it really got started.  "Why didn't you just sue the publisher?" No money. You can always tell someone who has never dealt with the legal system -- they're the ones who threaten to sue people or who think the courts are a magical place of speedy justice. The publisher was in Utah. I was in Michigan. It would have cost a fortune and 1) I had no money since I hadn't been paid any royalties and 2) Odds are he had spent the money already.

But I wasn't out yet. I made an expansion pack called "Shipyards". It sold for $15 and we sold roughly a thousand of them. With that $15,000 I paid my friends who had helped me out. When I was done, I still had around $3000 left. 

Hindsight often makes it clear which path was the way to go.  But in 1994 having gone through quite a bit of pain it was very tempting to just pocket the $3000, have a good story to tell friends and just go out and get a job. My saner friends decided to do just that and so from 1994 on I was on my own other than my brand new wife who has always been incredibly supportive.

I took what little money we had and worked with some shareware authors and created OS/2 Essentials...

1995

OS/2 Essentials was basically a suite of OS/2 shareware utilities that were the full versions of the shareware. It sold for something like $39.95 and because of the fame from Galactic Civilizations, I was able to get it into retail.

It didn't sell great by today's terms but that $3000 investment multiplied by several times. Moreover, it showed that we weren't a one trick pony. It attracted the attention of the person I consider even today to be the best OS/2 software developer of all time - Kurt Westerfeld. He was working on something called "The Workplace Toolset/2".  He saw how popular GalCiv was and that OS/2 Essentials was at retail.  We combined our talents together, rechristened his  program as "Object Desktop" and rounded out features together to make it a more mainstream program.

Meanwhile, IBM was putting together something called the IBM Family FunPak. This was basically a bundle of OS/2 games. A friend of mine at IBM, Mike McNutt, let me in on how much they were paying to license OS/2 games. IBM was interested in Galactic Civilizations. But because of the royalty issue, I told them that game wasn't really available. But I told them of a "new" game we were working on called "Star Emperor". Star Emperor was basically GalCiv with a simplified rule set. I just had to rewrite the AI over a few days and make a few other changes. The whole thing was done in a week or so and IBM paid handsomely to license it. So now we had a bunch of money we could use to market our stuff.

Later in '95, because of non-payment on royalties, we got the rights to GalCiv back and late in 1995 released Galactic Civilizations II.

In 1995 Stardock had its first 5 full time employees.  These employees were manning the phones, running tech support, and working on the next game which would be called "Entrepreneur".

It was the high point of Stardock's OS/2 existence.

1996

Flush with cash but with no business experience we were well prepared to run the company into the ground.  Obviously we didn't know we were doing that at the time.  But we were blinded by our OS/2 zealotry.  We believed IBM's assurances that they were committed to OS/2.  What we didn't know is that Lou Gerstner, CEO of IBM had quietly killed it at the end of 1995 when OS/2 for the PowerPC failed to be released by Fall Comdex '95.

But we were on a roll. In the meantime. I became friends with Dave Pottinger who, like me, believed in OS/2 and had written a fantastic OS/2 game called "Avarice". Take a look at the screenshots on that page and remember -- 1995/1996 time frame.  1024x768 with 32bit graphics, memory compression, object oriented world.  Now, if Dave Pottinger's name sounds familiar, it's because he's now one of the lead developers over at Ensemble on Age of Empires / Age of Mythology. Also like me, he's an OS/2 refugee.

We also released other products such as Trials of Battle, Process Commander, as well as Object Desktop Pro which included a powerful but expensive set of file viewers.

But OS/2 was already dead. We just didn't know it. You see, Microsoft had released Windows NT 4.0 and within months, the core user base of OS/2 was gone.

 

1997

We were starting to get the idea that something had gone wrong by 1997. Sales on all our software had dropped massively. We eventually figured out that it was Windows NT 4.0.  We released more OS/2 programs including the OS/2 version of Links Golf and PMINews.

Watching our revenue drop, I felt like a total fraud when I was featured in Entrepreneur Magazine as one of the "hot young tech executives" that June. When they asked about our next game, I told them "Funny you should ask, our next game is actually called 'Entrepreneur'." The reporter thought that was cool. But it wouldn't be the last we hard from them about the name "Entrepreneur".

 

 

1998 (year of pain)

This is when things came to their low point. Ever done a net worth graph in Quicken or Quickbooks? This is when it went to less than zero. I am pleased to say that we never missed a payroll nor did we ever not pay a developer a royalty. And we did it all on time.  But we were laying off employees. Which was really painful because like many naive, dumb start-ups, I had hired a lot of personal friends of mine to join the company. You can imagine how well this went over in having to lay your friends off.

But the man of the hour was a young developer/artists named Mike Duffy. Today, Mike works on Jimmy Neutron. But in 1998, he happened to be at Stardock. Why was he the man of the hour? Because for some crazy reason, as lead developer of Entrepreneur he decided to make a gaming library called Pear that happened to work on OS/2 and Windows.  This meant that when Entrepreneur was done, it would run on Windows as well.

This also meant that Stardock could have a game at retail that ran on Windows and OS/2 at the same time. Entrepreneur was loosely based on the business tactics of a certain very aggressive and large software company. The object of the game was to become a monopoly in the market you were in by crushing your competitors through a combination of distribution, technological superiority, and a lot of marketing.  Even "FUD" units were in the game (Fear, Uncertainty and Doubt).

The game did pretty well selling something like 75,000 copies worldwide (though in fairness, 40,000 of them were sold at less than $10 apiece). But it was enough to bide us time with what developers we had left to focus on bringing Object Desktop to Windows.

In 1998, we had begun working with some new friends we had met via the Internet.  Three in particular stood out: Andy Satori, Neil Banfield, and Brian Harper.  Together, along with internal developers, Object Desktop was being reborn on Windows. 3 key parts of Object Desktop were in their hands: ControlCenter, WindowBlinds, and IconPackager.

 

But what saved us was customer loyalty.  We decided that since we were going to be developing desktop enhancements on Windows that we would have to be constantly releasing new updates to keep up with changes to the OS.  So Alexander Antoniades, who had founded Game Developer Magazine and was our VP of Marketing, came up with the idea of selling software as a service via a subscription.  This would become our .NET initiative. And our customers purchased Object Desktop subscriptions sight unseen. They trusted us from our OS/2 days to "make good" and it was with their support that we were able to finish it.

But there was a wrinkle. Remember Entrepreneur Magazine? They filed a lawsuit against us over our use of the name "Entrepreneur".  I was appalled by the whole thing but they had a lot of cash ready to spend on making a lawsuit against us as painful as possible. We eventually settled and our sequels have used other names. But the entire experience taught me a great deal about intellectual property law and just how tenuous intellectual property rights really are. It also put a big damper on our game side that would last for years.

1999

1999 was the turning point for Stardock but it almost didn't happen. The Dot-Com explosion had come up and we were quickly eclipsed in terms of "Buzz" by a slew of start-ups who had millions of dollars in venture capital.  In May 1999 an Internet start-up called Neoplanet invited me down to Arizona. They were interested in hiring me and the WindowBlinds team to become part of Neoplanet. They offered lots of stock options which they assured me would be worth millions one day.

But as I stood there in their beautiful building, I just couldn't get over the fact that there didn't seem to be a business model that could generate any significant amount of money. While I was there, I got a T-shirt which celebrated their 1 millionth download.  Not paying customers. Just downloads.  It was a close call.  Stardock wasn't recovered from the OS/2 market by a long stretch. It was tempting to be part of a wealthy organization with lots of fun smart people. But in the end Stardock remained.

In December, The Object Desktop Network (ObjectDesktop.net) was officially launched.

 

2000

Things were really looking up by 2000. Object Desktop was a hit. We had just finished the Starcraft add-on "Starcraft Retribution" and one of the Object Desktop components, WindowBlinds, had really taken off.  Which was amazing because WindowBlinds on Windows 95, 98 and ME barely worked back then.

Despite the problems, WindowBlinds was incredibly popular. It helped launch a program called WindowFX as well. WindowFX was the first program that added truly alpha blended shadows under windows this was long before MacOS X hit the streets.

We also came out with DesktopX. DesktopX allowed users to put real objects on the Windows desktop. Yea, we've never managed to get the marketing message cleaned up so that people recognize just how cool DesktopX is. Basically when it boils down to is that you can build your own desktop out of objects.

So if you had your own ideas on how the computer should look and feel, you could create them with DesktopX. It introduced the concept of "zoomers" (think of icons that grew when you put your mouse over them -- again, before MacOS X came out).

 

2001

In 2001 the Dot-Com era came down with a crash. People today try to blame Clinton or Bush for the recession. Think again. A couple trillion (that's with a T) dollars in investments disappeared with those dot-coms.  And with that investment and capital went millions of jobs and the economy with it.

None of this had much affected Stardock though. That's because we had been left out. We've never received any venture capital. And our customers were end users mainly or established corporations. But there was a side effect: The skin sites were going down.

Skin sites? Our Object Desktop programs allow you to download user-created "themes" for them. Skins, icons, wallpapers, etc. created by users were uploaded to websites that hosted them. Hence the name "Skin sites". The problem with these sites is that they relied on ad revenue from banner ads to fund them. A skin site is very expensive to run since they are, effectively, little more than huge download repositories.  As the skin sites went down, so did our business because our users couldn't download skins for our software, they didn't have as much an incentive to buy our software.

So we launched WinCustomize.com, a new skin site. We included not just skins for our stuff but skin sections for other programs including our competitors. Our view was a rising tide lifts all boats.

The big unknown was the release of Windows XP. Windows XP included its own "skinning" system that while very limited was "free" (in the sense that its cost was factored into your purchase of Windows XP). We weren't sure how this would affect us. Microsoft implemented a security system to ensure that third parties didn't make their own themes -- only Microsoft digitally signed themes could be used.  But like many security systems, it was cracked and techies were making their own "visual styles" for Windows XP.

We weren't sure how Windows XP was going to affect WindowBlinds...

2002

By 2002, it had become clear that Windows XP was helping WindowBlinds. Sales skyrocketed as users exposed to the basic skinning in Windows XP wanted something more. Because XP was designed for desktop customization, our software worked better than ever sales grew across the board.

We concluded that we were now fully armed and operational. It was time to go back and try to do a Galactic Civilizations for Windows. We wanted to do it right so we put together a budget of around $600,000 (which was a lot for us) to create it.

We were also finally getting mainstream attention with companies like Microsoft, Nintendo, nVidia, and dozens of others were licensing our software for their own use. Movie and TV studios were beginning to use our software to put together those "Fake" computer interfaces we always groan about when you see them on TV.

In business terms, the company had reached that positive feedback loop.

 

2003

The positive feedback looped allowed us to grow in terms of new hires.  At the low-point in 1998, our company was down to 3 full time employees.  By 2003, we had grown to nearly 30 people working on various projects around the world.

Galactic Civilizations came out and received editor's choice awards from 2 of the 3 magazines and the average review rating of the 50 or so magazine reviews was between 4 and 5 stars.

Microsoft licensed our software to create an Xbox visual style, an Age of Mythology visual style and visual styles for some of their other games. Warner Bros. did the same thing to create a visual style for Terminator 3.

Skinning, as a market, had grown big enough that there are now companies making a good business creating skins for third parties such as Pixtudio and The Skins Factory (amongst others).

In late 2002 we had begun to rework the entire Object Desktop line to put together Object Desktop 2004 for a late 2003 release. The goal to bring a new level of polish and quality to the Object Desktop components. The first release for this was WindowBlinds 4 and has been followed up with Stardock Central, a program that lets users get updates, visit forums, check docks, chat, and more from a single UI. We've been also struggling to re-do ObjectBar, a program that was meant to be a kind of GUI erector set but has always had trouble finding the right balance between power and ease of use. We're hoping to get ObjectBar 2.0 out this year.  Another big release was WinStyles Theme Manager which finally has a UI that should be pretty straight forward to users. It's already been licensed by other companies for applying themes. And the second generation of DesktopX is ready to go too.

 What we've wanted to do as we came to our 10 year anniversary was to focus on the basics and then prepare for expansion in 2004...

What's next?

There's all sorts of cool stuff in the lab. We have two new games in development right now. One is called The Political Machine, a strategy game where you run for President as well as a future sequel for Galactic Civilizations which won't be out any time soon.

We also are working on something we call an Information Environment.  Where Object Desktop is about customizing the Windows environment to suit your needs, our Information Environment, called ThinkDesk, is designed to let users make use of their "stuff" in a more productive manner. It won't be out for a bit either and we rely on a lot of technology in Longhorn so ThinkDesk will almost certainly require at least Windows XP to function.

We, like other companies, are recognizing the importance of blogging. What's a blog? Well there are lots of definitions but here's mine: Blogging is about regular people being able to share their views about things with the world. I personally like the term "Indie Editiorials" since in many ways, that's what they are. So we're putting a lot of effort into JoeUser.com. A lot of pretty fantastic IT technology is being created along the way that we hope to roll into our other websites to provide more goodies for our WinCustomize, Object Desktop, and Drengin.net users.

 

The ride so far

It's been a crazy journey. This whole thing was just an accident in many respects. When I was nominated for Ernst & Young Michigan Entrepreneur of the Year, I met a lot of other "entrepreneurs". Each has its unique story.  Ours, though, I truly believe is one of the more unique stories. I mean, really, what is Stardock ultimately? It's a bunch of guys who hang out creating really cool stuff. Heck, we make PC video games and then turn around and make desktop customization software. Talk about totally unrelated. It's no wonder we've never gotten venture capital.  A friend of mine commented that Stardock is really a really profitable hobby.

Who knows what the next 10 years will bring.  The first 10 years brought triumph and near bankruptcy and then back to big growth again. If we're around 10 years from now, and I suspect we will be, who knows what adventures we'll have gone on between now and then.  Whether for good or ill, it's always exciting and all in fun, it's been a fun ride.


Brad Wardell is the founder of Stardock Corporation. You can email him at bwardell at stardock.com.

 

Mixing and Matching your icons and your skins

Published on Wednesday, October 1, 2003 By Brad Wardell In WinCustomize News

So you've found the ultimate skin...but unfortunately the ultimate icon package you just got doesn't work with it.

The new version of SkinStudio on Object Desktop can RECOLOR your icons enmasse.  I used it today to turn icons that were blue to orange (to fit my Halloween theme).

Check out this blog: http://adam.joeuser.com/index.asp?AID=309

Written by Adam himself (lead developer of SkinStudio).

WinCustomize Transition

Published on Wednesday, October 1, 2003 By Brad Wardell In WinCustomize News

Right now, WinCustomize is in the process of making a journey from Atlanta to California.  While on the surface the site continues to run, under the covers an immensely complicated set of DNS juggling is being done to keep the site up and running at all.

As a result, you will notice for the next several days certain things missing (i.e. broken link to a skin or an image, etc.).  WinCustomize subscribers and Object Desktop users are currently able to access a premium server we have up and going so thing should work fine if you have a WC premium subscripotion or Object Desktop account (since they're the ones who pay the bills in the first place).  But for everyone else, hold tight. When it's all done WinCustomize will have an immense amount of bandwidth available to it and be on whole rack of new servers Stardock purchased for the site this last week.

October Desktops

Published on Wednesday, October 1, 2003 By Brad Wardell In WinCustomize Talk

Using:
DesktopX (www.desktopx.net) for the pumpkins, meters, calendar, ghosts, and the spiffier icon size/shadow.

IconPackager package of icons from Pixtudio (www.iconzone.com)

WindowBlinds "Trick or Treat" from Pixtudio. I modified this myself to get more useful colors.

CursorXP "Halloween Cursors" so that my cursor is a candy corn. It's pretty cool. I also modified it in CursorXP to be a bit larger than default.

The war against piracy can't be solved by a mechanism

Published on Wednesday, October 1, 2003 By Brad Wardell In PC Gaming

I recently wrote about this topic here. But I wanted to write a more succinct version of it since some people thought I was advocating something akin to Internet Product Activation to thwart piracy.

Let me first Bottom line this: CD based copy protection does more harm than good.

Let me then add: There is no magic bullet that will stop piracy. Game developers need to quit trying to solve piracy via some sort of mechanism and instead design a policy that discourages piracy. Game developers/publishers need to approach piracy in a more realistic way. As a result, there are two basic groups of pirates.

Group A: The kiddies who warez everything. CD Copy protection means nothing to them. They have the game before it even hits the stores.

Group B: Potential buyers who are really more interested in convenience. The price of the game isn't as big a deal to them as convenience.

It's group B that our industry needs to focus more on rather than alienating and inconveniencing our customers by trying to thwart group A. Sure, it ticks me off that people steal stuff I've worked for years making. But we have to be realistic about this, it doesn't do anyone any good to inconvenience customers. In fact, anedotal evidence seems to imply that the more we inconvenience customers, the more we turn them into group B.

Let me explain:
Joe Gamer buys a game that requires the CD to be in the drive. But his 3 year old takes the CD and loses it. Joe Gamer ends up going onto Google or whatever and pretty soon finds not just a way to play that game without a CD but now finds out how to get the "latest games" not just for free but more convenient than ever through the world of peer networks and warez. As a result, as future games come out, Joe Gamer must now balance "doing the right thing" (which typically means driving up to the store, paying money to be inconvenienced by copy protection) and loading up a program and just getting the game, for free, quickly and painlessly.

That's why I think CD based copy protections are a bad idea. I think they create pirates and aren't terribly effective anyway. They're supposed to keep the honest "honest" but I propose a better way.

NOT Internet activation. Instead, game developers adopt a policy that has been very successful in the non-game software market -- after release updates.

PC games often come out buggy, get one patch, and then are largely abandoned. It's really hard to feel sympathy for game developers who treat their customers that way. Instead of doing that, release frequent updates to the game for users. For free. Have them go through a secure network so that only registered purchasing users can get the update but make it as convenient as you can.

By doing this, you create a bigger incentive to be a customer than to be a pirate. It becomes increasingly inconvenient to have the latest/greatest version of the game via the warez route than the legitimate route.

This is what we've been doing with Galactic Civilizations since it's release. You can buy it at the store or directly at galciv.com and either way be able to download the full game electronically along with regular free updates. It has no copy protection on the CD at all. You can install it on your laptop and main PC. We "fight" piracy by releasing regular, meaningful updates that are much easier to get legitimately than through warez channels. We've found a lot of people who initially pirated GalCiv end up buying it as a result. And sales of the game have been quite good. Sell-in at retail world wide is in the six digit range so it's not a matter of "small scale" solutions here.

So how do game developers do this? Just set aside a relatively small amount of the development budget to implement user suggested features. One or two developers, part time, for 8 to 12 month after release can make a big difference. Is GalCiv pirated? Sure. But it's not nearly as easily available via warez channels (we do monitor this stuff) as other games of similar retail sales levels.

There's no magic bullet to stop piracy. Game companies need to realize that. Instead, the goal should be to reduce piracy as much as possible and rather than relying on some mechanism, they should focus on a *policy* that focuses on making it more tempting to be a customer than to be a pirate.

Imagine if D-day were covered by CNN

Published on Tuesday, September 30, 2003 By Brad Wardell In History

Imagine if World War II were covered like Iraq is being covered.

Most people today seem to think that after D-Day the Americans just stormed into Germany and the war was over.  Far from it. Instead, for the first couple of months the Americans and British got stuck in "Hedgerow" country in northern France. A stalemate was largely the result as it took considerable time for the Americans to break out.

But imagine if CNN were covering that. You'd have interviews with nominal Axis allies. No doubt the Vichy French would have weighed in on the "unilateralism of the Americans, British, and Canadians". Words like Quagmire, Stalemate, mounting losses would have no doubt been sprinkled in for good measure.

By December 1944, 6 months later, the Western allies were making good progress. Of course, that's when the battle of the bulge occurred. I don't even want to contemplate how CNN and its ilk would have covered that.

 

Bias in the media? Note what is reported on

Published on Tuesday, September 30, 2003 By Brad Wardell In Politics

Those who say there isn't a liberal bias in the media should take a closer look at what the media chooses to report on. It doesn't even take long to discover that the issues that get reported tend to be ones dear to liberal causes.

Let me give you a good example:

Today the news covered how any millions of people are not covered by medical insurance.  It was reported repeatedly on NPR, CNN, ABC News, and CBS evening news (didn't see NBC but I bet it was reported there).

Is that really big news though? If so, consider this: When was the last time the news reported on how many abortions were performed in a given quarter?  Can you recall the last time you heard of the # of crimes foiled by armed citizens with gun permits? How about the last national comparison of how religious based private schools fair to public funded schools?  Or for that matter, the amount of money spent by religious based charities versus "secular" based charities on public works?

The statistics are out there. Waiting to be reported. While I am personally pro-choice, I would be there are many millions of Americans who are quite concerned about the # of abortions performed each quarter. I don't suppose you'll hear NPR report those numbers even as they repeated no less than 4 times today while I was listening the uninsured statistics.

And somehow I don't expect to see Dan Rather do a report on the amount of crimes stopped thanks to an armed citizenry even though the statistics are out there (and I'm sure the NRA would be pleased to share those stats with journalists). Yet somehow CBS never has a problem reporting on the "millions" of homeless (though strangely these reports are most often done when a Republican is President).

So next time you listen to the news, take note of what statistics they choose to report on. I suspect you'll find that the statistics almost always are ones that strengthen the liberal side of a given debate while simultaneously urging governmental action.