Re: Screensaver Issues - Kernel32.DLL Error
- From: "Wessam Bahnassi" <wbahnassi@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 21 Jun 2005 20:54:28 +0300
How about you start a new vanilla screen saver project, then keep growing it
slowly towards your current one, until you face the crash itself... At least
then you'll know what's wrong...
Slow'n'easy,
Wessam Bahnassi
Microsoft DirectX MVP,
Lead Programmer
In|Framez
"Vladimir Repcak" <VladimirRepcak@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:F9C3BFC6-2409-489D-BF69-C5D55CEB678E@xxxxxxxxxxxxxxxx
> 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>
>>
.
- Follow-Ups:
- Re: Screensaver Issues - Kernel32.DLL Error
- From: Vladimir Repcak
- Re: Screensaver Issues - Kernel32.DLL Error
- References:
- Screensaver Issues - Kernel32.DLL Error
- From: Vladimir Repcak
- Re: Screensaver Issues - Kernel32.DLL Error
- From: Wessam Bahnassi
- Re: Screensaver Issues - Kernel32.DLL Error
- From: Vladimir Repcak
- Re: Screensaver Issues - Kernel32.DLL Error
- From: Richard [Microsoft Direct3D MVP]
- Re: Screensaver Issues - Kernel32.DLL Error
- From: Vladimir Repcak
- Screensaver Issues - Kernel32.DLL Error
- Prev by Date: Re: Screensaver Issues - Kernel32.DLL Error
- Next by Date: Re: Checking for D3DX
- Previous by thread: Re: Screensaver Issues - Kernel32.DLL Error
- Next by thread: Re: Screensaver Issues - Kernel32.DLL Error
- Index(es):
Relevant Pages
|
