Welcome, Guest. Please login or register.

Author Topic: OS4 rollout schedule  (Read 35640 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Dietmar

  • Full Member
  • ***
  • Join Date: Nov 2002
  • Posts: 220
    • Show all replies
    • http://devplex.awardspace.biz
Re: OS4 rollout schedule
« on: June 17, 2003, 11:51:03 PM »
> If you want a port of, say, Heretic II, you don't send a free Amiga to Activision. You obtain a licence. What's so strange about this concept?

What is strange with this concept is that normally, mainboard manufacturers don't have to purchase permission for running an OS. The user purchases the OS and a mainboard and that's the end of it.  It's a  fair situation, with mutual benefits: both have their development costs, the OS manufaturer sells the OS software, and the mainboard manufacturer sells mainboards, everybody wins. Not exactly rocket science, is it ?

A license requirement on top of the OS price looks like a thinly veiled attempt to milk money out of the hardware manufacturer.
 

Offline Dietmar

  • Full Member
  • ***
  • Join Date: Nov 2002
  • Posts: 220
    • Show all replies
    • http://devplex.awardspace.biz
Re: OS4 rollout schedule
« Reply #1 on: June 18, 2003, 12:37:04 PM »
1. Ben claims that the license scheme is to protect customers from fraudulent mainboard manufactures. Ignoring for a second the inherent below-the-belt quality of this justification, what makes a group of developers the court and judge of the market? Next thing that might happen is that developer x is unsatisfied with the ethics of Hyperion and blocks his software to run on the A1. I don't think we should enter the road of judging competitor's ethics.

2. It was claimed that the scheme is used to protect IP by complicating piracy with a hardware device. That's a perfectly valid approach but it is just unreasonable to charge the mainboard manufacturer for a service that primiarily benefits Hyperion. Many of us are developers, none of us requests special chips on mainboards. If we feel the need to protect our software, we use cheaper methods that work reasonably well. In the case of A1 and Pegasos mainboards, the unique MAC address of the built-in ethernet controller would be a good hook for an unlocking procedure.

3. Some claim that Hyperion has to cover high development costs, in a small market, and that justifies milking money from the mainboard manufacturer, on top of charging customers for supplying the OS. Considering that the mainboard manufacturer has had considerably higher development costs, I don't see the moral justification for the software side charging the hardware side. One side gets an OS, the other side gets a platform, costs and benefits are evenly split, and the money comes from the customers alone.
 

Offline Dietmar

  • Full Member
  • ***
  • Join Date: Nov 2002
  • Posts: 220
    • Show all replies
    • http://devplex.awardspace.biz
Re: OS4 rollout schedule
« Reply #2 on: June 18, 2003, 02:05:20 PM »
Quote

HyperionMP wrote:
That about sums it up, yes.


Ben, you have lost me now. Taking this statement alone, it appears that Hyperion will give the OS to the mainboard distributors for a bundled sale, and take royalties for sold units? That would be a perfectly normal scheme. Until now, I was under the impression that Hyperion plans a certified-hardware licensing scheme (on top of selling the OS and taking royalties).

But that begs the questions: why? Bundling normally is used as an alternative distribution path, not as sole distribution path. If you don't sell the OS as standalone product, won't you be shooting yourself into your feet? Everybody already using a Pegasos and everybody deciding to skip the bundle offer (when purchasing the mainboard) would be a customer lost forever.