Re: Screensaver Issues - Kernel32.DLL Error

Well, you probably haven`t read my whole post because I stated there that it
crashes BEFORE it goes into my program since first line of function WinMain
creates LOG.TXT and writes a message there to help me with debugging. I also
checked and my constructors also don`t crash (because that`s what`s executed
even before WinMain).
Of course, the screensaver NEVER crashes if run from command-line (be it
with or without arguments like /a/p/c).

So my main question is, what else is "Display Properties" doing besides
calling the screensaver with command-line arguments like "/p /a /c" ?

What other information do you need besides all of my posts above ? Please be
more specific.
Do you really think I didn`t debug the hell out of my code ? But it doesn`t
even get there. It crashes (or doesn`t do anything) even before WinMain is
executed. So there must be something else that Display properties does.

I tried everything, googled net and newsnet/mailing groups for last 5 days
but noone seems to have had the same problem before(and posted a question on
such mailing lists/groups).

Since you didn`t ask for any specific information I`ll summarize what I
think is important:
PC1:Windows ME (very old installation - almost 4 months old)
PC1:Windows XP (very fresh installation - 1 day old)
PC2:Windows XP (old installation - 3 months old)
Various Detonators from 2 years old to latest (no difference in outcome
though)
Written uder DX 8.1 Debug
DirectX 8.1 (one windows with retail and another with debug dlls);
9.0c (just retail)
Microsoft Visual C++ 6.0
Common Files basis for the screensaver (from DirectX docs)
I have experience with 2 finished budget PC games written from scratch by me
and some 3D constract work, so I`m not just starting out as you probably
think (judging by the sound of your reply).

Please advise.
Vladimir Repcak

"Richard [Microsoft Direct3D MVP]" wrote:

> [Please do not mail me a copy of your followup]
>
> Its kinda hard to say without more information. I mean, basically
> you're saying "hey, on some machines my program crashes in certain
> situations. What should I do?" and about the best we can offer
> without more information is something like "debug your code".
> --
> "The Direct3D Graphics Pipeline"-- code samples, sample chapter, FAQ:
> <http://www.xmission.com/~legalize/book/>
> Pilgrimage: Utah's annual demoparty
> <http://pilgrimage.scene.org>
>
.

Relevant Pages

  • Re: Program crashes when running it outside dev environment
    ... If I try to launch the debug on the ... crashing program, it'll close before the debugger opens. ... If it just fails strangely and sometimes inside system functions it might be overwritten memory or some such problem. ... Put one of those lines immediately before the line that crashes the program. ...
    (comp.lang.c)
  • Re: problem with release DLL.
    ... i tried by commenting certain suspicious statements in my code and found ... assigned variable or memory overflow problem. ... actually crashes, it is a stack problem where there is an array or character ... though it isn't alway the same as debug (optimization sometimes changes the ...
    (microsoft.public.vc.mfc)
  • Re: Automation Error - Qualifying my code
    ... There is a debug ... read", with yet another debug button, which gives the same error and crashes ... Is there a way to write my Immediates window to a log ... Set oWord = Word.Application ...
    (microsoft.public.word.vba.general)
  • Re: CreateInstance returns Server execution failed
    ... crashes. ... create a second instance of my COM module process (can see that from ... It doesn't make sense to me why only the debug version ... Maybe the Release version corrupts the process heap but keeps running to cause undefined results later (like Server execution failed). ...
    (microsoft.public.win32.programmer.ole)
  • Re: problem with release DLL.
    ... I've found that, for me, when these sorts of things happen it's usually an assigned variable or memory overflow problem. ... Many times, if the program actually crashes, it is a stack problem where there is an array or character buffer that gets overflowed. ... You could also try debugging the release version since you can often step through it even though it isn't alway the same as debug. ...
    (microsoft.public.vc.mfc)
Loading