• Announcements

Archived

This topic is now archived and is closed to further replies.

Serious issues in NeHe base code!

Recommended Posts

I upgraded to Windows 2000 recently which is 32bit and runs in protected mode. Well after a week or so I started just rashing uinstanting when a program would do something. After a couple calls to Microsoft I learned that in NT when the software tries to gain access to the hardware it says "i dont think so" and kicks your ass out. There are 2 things I have found that cause this. One is starting a download with mutliple mirrors with DAP while running Media Player. The other is the fullscreen code used in every GL tutorial on this site. What happens is it tries to change the screen settings but the attempt gets half assed so windows returns an error and as soon as you try to create the message box it crashes. The tech said that 9x wasnt supposed to allow hardware control either but it was more tolerent than NT. The exact stop error is 0x0000001E. This really needs fixed. Hunter-Killer

Share on other sites
Read the disclaimer, what you call "half assed" has helped thousands of budding developers.

If you want to point out a bug, point it out. Don't go on some tirad against someone busting their hump to help us out.

As for your comments on Win2k. A large number of us DO use Win2k for our development, and I have yet to see anyone make comments such as yours. I have used the pascal equivalents of NeHe's code many times and never once caused access violations using his resolution or context code.

Care to explain a little with more patience and show us the bad segment instead of ranting?

Jason

Edited by - DeschutesCore on March 22, 2001 8:26:05 AM

thanks.

Share on other sites
You could enter the BIOS setup when your computer starts. Try to set some slower settings for the memory.

Share on other sites
There should be an Athlon AGP patch available on AMD''s site. You can find it at MS''s site, too, but it''s buried a little.

Jason

Share on other sites
Hey guys, I appreciate you jumping to my defense, but Hunter-Killer has a valid point. I am aware of problems on NT and 2000. In the most recent code lesson 32 the problem should be fixed (the settings are stored so they can be safely recalled). I''ve had alot of problems with fullscreen code over the last year. What works on one OS does not always work on another. Sometimes changing your driver fixes the problems, other times it does not.

I did run both NT 4.0 and 2000 at one point in time, and the most severe problem I had was the start bar getting messed up in NT 4.0. So I''m not able to recreate the problem. So to anyone able to fix the fullscreen code, I am publicly offering \$25 and a FREE CD.

How''s that for incentive? It has to be compatible across all platforms, and I would prefer it doesn''t use DirectX or an external library. Sorry the offer isn''t great, I''m low on money at the moment

Share on other sites
Just wanted to post another quick comment. I dont mind gentle ribbing, I don''t mind people pointing out flaws, it''s the ONLY way things will get better around here. Just keep in mind that all my stuff is free, and I don''t get anything out of running this site, or by replying to all the emails I receive. If I was charging you to view the tutorials then yeah, you could attack me if something was wrong, but as is, I''m just trying to give you a stepping stone to get started. Along the way I hope you''ll develop your own styles, your own routines, and listen to what some of the absolutely brilliant people in this forum have to say in regards to making things even better.

One thing that someone brought up is the amount of code on the site. You have to keep in mind that a bug in the base code means I have to rewrite all 32 tutorials. I''d rather point out the mistake, and include the fix in a future tutorial. The work is just too much, especially when the fix is minor.

The next tut should have some nice modifications... minor but things that will help. Such as libraries automatically included, defining TRUE/FALSE, etc... so the odd compiler doesn''t choke, etc.

Thanks again for all the feedback! Play nice

Share on other sites
Hunter-Killer said that "it tries to change the screen settings but the attempt gets half assed so windows returns an error" not that OpenGL or NeHe's tutorials are "half-assed" - why do you deliberately mis-represent him?

If there are known issues with nt/win2k then surely he can suggest that some more experienced person than himself try to fix them, without being flayed alive? I know myself that it's frustrating to experience unexpected problems when you are learning - I think some more tolerance is in order .

Paulcoz.

Edited by - paulcoz on March 28, 2001 1:27:11 AM

Share on other sites
hunter killer ( or anyone ) what cards does this happen on?

http://members.xoom.com/myBollux

• Partner Spotlight

• Forum Statistics

• Total Topics
627674
• Total Posts
2978558

• 11
• 11
• 10
• 12
• 22