I used Firefox.

It's been up solidly for days, and now I get two blue screens in a row :/

Bah, just tried and it looks like they all get JARs screwed up.

Stupid browsers. :@

They don't. A jar is a zip archive.

:(

It's an executable zip file.

A browser's default behaviour should be treating it as an executable, because people that know/care they are zip files (the minority) will know how to override that behaviour, whilst people that don't will get all confused.

kos was off to watch rugby, he may not notice for a while

* The browser should choose what to do based on what the server says the file is.

Well, if there's different content types to specify that, then yeah.

(And, if it hasn't explicitly been set by the uploader, the default behaviour should again be to determine if its an executable JAR and act accordingly.)

my browser (IE8) did detect it and act accordingly - maybe spinningplates has buggered about with some settings or installed some software that hijacked the .jar extension?

IRQL_NOT_LESS_OR_EQUAL :@

Have you tried reseating the RAM?

That has a mime type?

google says that means vista has a hardware issue :(

I'm now getting a stop code on boot, : 0x0000007E.

 

As far as I can tell froma quick google that's something to do with a kernal mode driver? :|

I can't be bothered figured out what you're saying there; I'm hungry and have stuff to do.

The JAR provided was an executable one. Unless someone explicitly said "don't treat this as an executable" (which wasn't done because there's no functionality to do that on Beehive's attachment page) then it should have been detected as an executable and passed down the chain to the browser which should have said "this is an executable jar, run or save?"

And what it definitely shouldn't have done is tacked on a .zip extension, because it already has a valid extension, (and because it isn't a pure zip).

And now I'm going to go eat and not let myself get distracted so I can get stuff finished. :@

Usually indicates hardware error, often memory.

 

There is a registry setting you can change to make Windows display the driver filename in the BSOD to help narrow down where the problem is.

 

If I remember correctly you had problems with the RAM when you installed Windows didn't you? My money would be on it being at fault.

:-|

 

Les Buggers, as they say in france.

Back up on 2GB of RAM for now. Let's see what happens.

I have worked out how to make that dynamic map thing work - it likes light - if you put down a torch a whole area clears - seems to stay visable if you take the torch with you too