Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Run old games in DOSBox in the browser

naclbox.com

Post reply on HN
Print view View original

1–10 of 44 posts

Re: Run old games in DOSBox in the browser

#2

Post by buster »

If this isn't clear to someone:

This needs Chrome and the Native Client.

From the page:

  Please Note:

  You must have Native Client enabled in Chrome 12 or 13 for   this game to work in your browser.

  To enable Native Client, do the following:


  Go to "about:flags" in your address bar (without quotes)
  Click "Enable" next to Native Client
  Go to "about:plugins" in your address bar (again, without quotes)
  Occasionally you will find that you have to click "Enable  NaCl" here too
  Restart Chrome
  Have fun!

Re: Run old games in DOSBox in the browser

#5

Post by kleiba »

buster wrote: post #2

If this isn't clear to someone: This needs Chrome and the Native Client. From the page: Please Note: You must have Native Client enabled in Chrome 12 or 13 for this game to work in your browser. To enable Native Client, do the following: Go to "about:flags" in your address bar (without quotes) Click "Enable" next to Native Client Go to "about:plugins" in your address bar (again, without quotes) Occasionally you will…

...thus it would be nice to change the headline from "..in the browser" to "..in Chrome".

Re: Run old games in DOSBox in the browser

#6

Post by ck2 »

Native client is a horribly bad idea on so many levels. Wiz-bang demos aren't enough to distract from the danger.

Now trojans have one huge, lovely target. Just change browser settings and boom, easy attack. This in combination with hiding everything from users (status bar, url bar, etc.) is super dangerous. It's activex all over again.

Do it in webgl or otherwise, leave native code execution outside the browser.

Re: Run old games in DOSBox in the browser

#8

Post by jbri »

ck2 wrote: post #6

Native client is a horribly bad idea on so many levels. Wiz-bang demos aren't enough to distract from the danger. Now trojans have one huge, lovely target. Just change browser settings and boom, easy attack. This in combination with hiding everything from users (status bar, url bar, etc.) is super dangerous. It's activex all over again. Do it in webgl or otherwise, leave native code execution outside the browser.

In what way is NaCl worse than webgl?
Post reply on HN