Kernel386 forbidden..(Aaaarrrhhhggg)
Ok guys, i''m not sure this is pure GL but here it goes:
All of asudden i get "Kernel386 forbidden.." error and the whole system goes down. I can run my engine perfectly but when i close it down and try to run some other program the error occurs...
Have i forgotten to release something? Memoryleak?
I thought GL didn''t care about freeing mem or not.
______________________________Only dead fish go with the main-stream.
January 19, 2001 03:16 PM
yes, it is time for the linux user to laugh at the unstable microsoft platform. Ha!
Interesting problem!
In theory it shouldn''t make any difference about freeing OpenGL mem but a badly written driver and bugs in windows itself may cause leaks. One of my ATI cards has this problem! Besides it''s bad programming practice to not free all the resources your allocating. In every program I write I put in the code to free the resource immediatly after writing the code to allocate it. That way I don''t forget it later.
As for what''s causeing your problem? I dont'' know, the only thing I can think of trying is to see if you can run your engine then run another program before you close it? If you can then you''ll know that you have something going wrong durring shutdown. If you can''t then you know somehtings going wrong much earlier!
to the laughing linux user I say this. I use linux and it does crash! I''ve had linux crash for all of the following reasons...
bad device drivers (not a windows specialty)
conflicting daemons
bad programs (they must be the bad programmers migrating to linux)
and programs trying to do conflicting things at the same time.
So go ahead and enjoy your delusions.
In theory it shouldn''t make any difference about freeing OpenGL mem but a badly written driver and bugs in windows itself may cause leaks. One of my ATI cards has this problem! Besides it''s bad programming practice to not free all the resources your allocating. In every program I write I put in the code to free the resource immediatly after writing the code to allocate it. That way I don''t forget it later.
As for what''s causeing your problem? I dont'' know, the only thing I can think of trying is to see if you can run your engine then run another program before you close it? If you can then you''ll know that you have something going wrong durring shutdown. If you can''t then you know somehtings going wrong much earlier!
to the laughing linux user I say this. I use linux and it does crash! I''ve had linux crash for all of the following reasons...
bad device drivers (not a windows specialty)
conflicting daemons
bad programs (they must be the bad programmers migrating to linux)
and programs trying to do conflicting things at the same time.
So go ahead and enjoy your delusions.
------------------------------Piggies, I need more piggies![pig][pig][pig][pig][pig][pig]------------------------------Do not invoke the wrath of the Irken elite. [flaming]
Ok. Prob fixed. I traced the error down to a bad declaration in a header file...MY code was correct.. I''m still amazed the engine ran with that error present...Seems there was some bad memory management involved...(For a moment there i was about to blame Win32..)
______________________________Only dead fish go with the main-stream.
January 19, 2001 10:56 PM
Sorry, avianRR, I was just joking. I know linux crashes. i just saw the Kernel386 part and thought it was an operating system thing, not a driver thing. But who knows, it doesn''t really matter anyway. Don''t want to start another linux v.s. windows thread again!
January 20, 2001 12:59 PM
I find it hard to believe that any competant programmer would say anything but Linux is a godsend!
January 22, 2001 10:30 PM
it is a godsend, i just didn''t want to start a flame war by bashing windows needlessly. And in MY opinion, linux > windows.
I don''t think anyone particularly likes microsoft. But linux isn''t the easiest OS to use is it.
"To err is human, to really mess up requires a computer"
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement