ZDoom

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

i dunno, probably something i did to my video driver

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.

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

ah, fixed in 61

*BUG CLOSED*

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

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

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.

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.

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

but cant something be in memory but not running?

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.

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

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

by **randi** » Thu Jan 08, 2004 4:42 pm

Bio Hazard wrote:with a little bit of research i managed to figure out that the process "zdoom" (that is zdoom im assuming) does not end upon quitting the program

In other words, its the same as this?

by **Bio Hazard** » Tue Jan 06, 2004 9:16 pm

those are the options i changed between the last time it locked and when it started working

i thinkl its just fullscreen that does anything

by **randi** » Tue Jan 06, 2004 8:09 pm

Vsync is never used in windowed mode.

by **Bio Hazard** » Tue Jan 06, 2004 7:40 pm

with a little bit of research i managed to figure out that the process "zdoom" (that is zdoom im assuming) does not end upon quitting the program, and ending it manually dosent kill it either...

also

this bug dosent happen when i run zdoom in a window with capped fps and vsync

by **Ultraviolet** » Fri Jan 02, 2004 11:06 pm

It didn't do anything because the heatsink is not in proper contact with the chips on each module. Also, the thermal sensor should be on the chip, not the card. ALSO, heat sinks won't do much good for long if your case's airflow isn't any good, because there will nothing to carry away the heat and it'll just travel back into the chip the heatsink is sitting on.

by **Bio Hazard** » Fri Jan 02, 2004 10:08 pm

it actually didnt do anything... it remains the same as before

maybe its not attached properly... ill mess with it later...[reallytinytext]or ill go buy some real ones[/reallytinytext]

ZDoom

60 doing strange things to windows

Post a reply

Expand view Topic review: 60 doing strange things to windows