60 doing strange things to windows

wildweasel · Post by **wildweasel** » Thu Jan 08, 2004 7:54 pm

Bio Hazard wrote:hmm... i think so, but the process dosent stop. (or is that what "stays in memory" means?)

Yes. A process has to be in memory to keep going.

Post by **Bio Hazard** » Thu Jan 08, 2004 7:55 pm

but cant something be in memory but not running?

Ultraviolet · Post by **Ultraviolet** » Thu Jan 08, 2004 10:41 pm

Processes do get orphaned, and they are running but they aren't tied to anything -- they aren't giving data to anyone or processing anything -- and therefore serve no purpose, but that's a different thing.

Everything that is in memory is something that is not running.

Only individual instructions are run, therefore if something is waiting in memory then it isn't running yet. Heh.

Biff · Post by **Biff** » Thu Jan 08, 2004 11:00 pm

A "TSR", meaning "terminate and stay resident" program, is in memory but not continuing to execute code which takes computer resources. A typical example is the computer FAX programs of yesteryear. With such running, an incoming call on the appropriate telephone number would be intercepted by your modem, and answered by a FAX program. If you did not start the FAX program, the modem wouldn't be able to answer the call.

Zdoom should not be resident in memory after playing and then quitting. That's a system problem I think.

Post by **Bio Hazard** » Thu Jan 08, 2004 11:19 pm

but its there AND executing something (its sucking up 100% of the cpu)

Post by **Bio Hazard** » Tue Feb 03, 2004 11:12 pm

ah, fixed in 61

*BUG CLOSED*

Post by **randi** » Tue Feb 03, 2004 11:35 pm

Bio Hazard wrote:ah, fixed in 61

Really? I'd love to know what the difference was.

Post by **Bio Hazard** » Tue Feb 03, 2004 11:37 pm

i dunno, probably something i did to my video driver