Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?

Comment Only part of the problem. (Score 2) 165

There are two real issues here.

The first is that malicious programs could open up, grab screen buffers, and get access to stuff that had been on the screen to use for their nefarious purposes.

This is bad, and unless we get decent support to isolate the frame buffers (and other graphic memory) between apps at either the driver or hardware layer, it's not going away anytime soon. Dont want this? Power cycle (all the way off - not just hiberante) between application launches would do it.

The second is sloppy programming on the part of non-malicious applications. That's what is being talked about in the application. Diablo apparently asked for a frame buffer, and then presented it, as is, to the user without putting what it wanted in place, trusting for it to be in a particular state. Which it wasn't.

You want a black screen to show to the user, then write zeros into your buffer before you show it to the user. Decent compilers/languages will tell you if you've tried to read from unitialized variables, and you should never trust that anything you've asked for dynamically is in a safe state, unless you've explicitly requested that it's cleared before being handed to you. Why should a resource from the graphics card be treated any differently?

NVidia is right about one thing here - most of the time, nearly all of the time, the thing you do with that buffer you're given is to write your stuff into it, completely overwriting it, and it would slow things down if they had to guarantee that it was cleared before handing it out to you. If your program doesn't care enough to do so itself, that's not really their fault.

It would be nice if, on program exit, all GPU resources used by that app were flushed, but again, that would involve the OS needing to be told of all the GPU resource allocations and deallocations so it could clean up properly, and that too would probably slow things down. Not a lot, but enough to be annoying when your game stutters.

Comment Home built auto answer modem (Score 4, Interesting) 251

Only having a 300 baud acoustic modem and a Tandy Color computer 2, I still wanted to run my own home written BBS. Wound up running the phone line through the cassette relay control on the Coco2.

All night long, Click, see if someone hit return at least one, click - hang up. Click - pick up, watch for return. Click - hang up.

Must have driven Thunder Bay Tel completely nuts trying to find out why someone would keep picking up and hanging up every 5 seconds or so for weeks on end. This was back in 1984. The BBS lasted about 2 years and did have a fair number of people connect in to it.

Comment Rockets... (Score 1) 216

Wouldn't it be easier to mount, say, 4 model rockets on wires under it? Electronic ignition and off you go. If you want them to make holes in things, well, put a nail sticking out of the nose. Pick your engine size based on your required damage.

Woosh. The first flying Gyrojet...

Comment Re:When they get rude (Score 1) 217

Had this happen to me - I have an idea for the next app - I'll tell it to you, you build it, and you can have 1/2 the cash. My response? Consider: Someone approaches Steven King. Tells them they have a brilliant idea for a book - all he has to do is write it, and he can keep 1/2 of money. I'm betting Mr. King has a very full well (or 2, or 3) of the bodies of people like that.

If, on the other hand, someone approaches me, with desing notes, screen sketches etc of what they want built, I can give them an estimate as to how much it will cost them to get me to build it.

Somehow, realizing that they are going to have to pay to get their idea built seems to frighten most of them off.

Slashdot Top Deals

The confusion of a staff member is measured by the length of his memos. -- New York Times, Jan. 20, 1981