Why does WinXP run(times) error ? Why does he say that an illegal operation has been executed ? Why aren`t my proggys working on this bullshit Windows ? Why does WinXP lock acces to memory leaks ? When do memory leaks apear ? Why dop some games(comercial) don`t work on WInXP ? P.S: I `m(And 99% of my friends) working all day on WInME and `98 and nothing like that happens(no Illegal op or runtime crash)

Why does WinXP run(times) error ?
> What have you been doing? More info.

Why does he say that an illegal operation has been executed ?
> See above

Why aren`t my proggys working on this bullshit Windows ?
> See above

Why does WinXP lock acces to memory leaks ? When do memory leaks apear ?
> Memory leaks appear when you''re doing things with memory (alloc/realloc/free/new/delete) in a way you shouldn''t. Restricting access to these is not a flaw in XP, but a pointer that there''s a flaw in your programm. Access to memory is restricted for security reasons. That way only the faulty app. will terminate, not the whole OS

Why dop some games(comercial) don`t work on WInXP ?
> Ask the programmers of that game

There''s very little info in your thread, just ranting. Next time, try to give more explanation of your problem.

P.S: Working with XP, no problems with programming...

Well let`s say this happens : In Win95,98,Me my proggys->Work Flawless... but on WinXP it says : Memory cannot be "written" I mean what`s that ?

P.S: See www.geocities.com/cippyboy_7 and download OpenGl Benchmark... If you have WinXP ->Crash, My system=No Problem...

It defenitly smells like a memory leak.
make shure you don't load more stuff in an array than the array can take.
Try not to use pointers at all, they only cause problems.

[edited by - lc_overlord on December 15, 2002 3:58:57 PM]

I changed the 16 to 32 in the config file and it worked fine up until it attempted test 5, the high polygon terain drawing, with A LOT of polygons...

<- Digital Explosions ->
"Discipline is my sword, faith is my shield
do not dive into uncertainty, and you may live to reap the rewards" - (Unreal Championship)

The info you''re giving is still pretty vague. Maybe post the sourcecode so people can try to figure out the problem.

I agree with ic_overlord, this is most likely a memory leak. My guess would be that you''re doing something with pointers and memory allocation in a way you shouldn''t.
Win 9x isn''t very protective about the system memory, so you might get away with it there. Ever tried running your Benchmark on a Win2k system? Because I guess you''d get the same problems there.

quote:

---

Try not to use pointers at all, they only cause problems.

---

I agree that you have to be carefull when working with pointers. But: avoid them completely? Just how on earth do you want to do that?