By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
429,083 Members | 1,957 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 429,083 IT Pros & Developers. It's quick & easy.

Any ideas on this?

P: n/a
Hey guys

I have a app that runs fine on my deve machine, in debug oe or straight from
my installer.

Stick it on another machine, similar spec and when i close a child form it
closes the whole app....essentially crashing but no crash message. It's as
tho i closed it.

On another machine it crashes on closing the second form that pops up.

This form is a directx scene.

So why on my dev machine does this never happen? But happens 100% of the
time on other machines, what difference could their be?
Sep 19 '06 #1
Share this Question
Share on Google+
7 Replies


P: n/a
Video card?

--
HTH,

Kevin Spencer
Microsoft MVP
Digital Carpenter

A man, a plan, a canal,
a palindrome that has gone to s**t.

"Daniel" <Da*****@vestryonline.comwrote in message
news:ul*************@TK2MSFTNGP05.phx.gbl...
Hey guys

I have a app that runs fine on my deve machine, in debug oe or straight
from my installer.

Stick it on another machine, similar spec and when i close a child form it
closes the whole app....essentially crashing but no crash message. It's as
tho i closed it.

On another machine it crashes on closing the second form that pops up.

This form is a directx scene.

So why on my dev machine does this never happen? But happens 100% of the
time on other machines, what difference could their be?

Sep 20 '06 #2

P: n/a
Kevin,

Why not the sound card?

:-)

You are right with your answer but in my idea is this not resolvable by a
newsgroup than just guessing.

Cor

"Kevin Spencer" <uc*@ftc.govschreef in bericht
news:ut*************@TK2MSFTNGP05.phx.gbl...
Video card?

--
HTH,

Kevin Spencer
Microsoft MVP
Digital Carpenter

A man, a plan, a canal,
a palindrome that has gone to s**t.

"Daniel" <Da*****@vestryonline.comwrote in message
news:ul*************@TK2MSFTNGP05.phx.gbl...
>Hey guys

I have a app that runs fine on my deve machine, in debug oe or straight
from my installer.

Stick it on another machine, similar spec and when i close a child form
it closes the whole app....essentially crashing but no crash message.
It's as tho i closed it.

On another machine it crashes on closing the second form that pops up.

This form is a directx scene.

So why on my dev machine does this never happen? But happens 100% of the
time on other machines, what difference could their be?


Sep 20 '06 #3

P: n/a
Hi Daniel;
I have had similar problems in the past. The main issue is that the
applications is compiled differently when you compile it in the debug
mode and on release mode. To prevent these kind of problems is to write
saver codes i.e. uses more checkes (Try ..catch), use config files
where possible to reference outside files and always test both the
version compiles in Debug mode and release mode before moving to
production machine.
Hope this is helpful.
Shivam

Daniel wrote:
Hey guys

I have a app that runs fine on my deve machine, in debug oe or straight from
my installer.

Stick it on another machine, similar spec and when i close a child form it
closes the whole app....essentially crashing but no crash message. It's as
tho i closed it.

On another machine it crashes on closing the second form that pops up.

This form is a directx scene.

So why on my dev machine does this never happen? But happens 100% of the
time on other machines, what difference could their be?
Sep 20 '06 #4

P: n/a
Hey guys

Thanks for the replies. I know its like guessing Kev but i want opinions and
educated guesses, hoping someone might point me to something. Shiviams
answer is th ekind of thing i was expecting, thanks for the advice.

D

"Shivam" <sh***********@gmail.comwrote in message
news:11**********************@k70g2000cwa.googlegr oups.com...
Hi Daniel;
I have had similar problems in the past. The main issue is that the
applications is compiled differently when you compile it in the debug
mode and on release mode. To prevent these kind of problems is to write
saver codes i.e. uses more checkes (Try ..catch), use config files
where possible to reference outside files and always test both the
version compiles in Debug mode and release mode before moving to
production machine.
Hope this is helpful.
Shivam

Daniel wrote:
>Hey guys

I have a app that runs fine on my deve machine, in debug oe or straight
from
my installer.

Stick it on another machine, similar spec and when i close a child form
it
closes the whole app....essentially crashing but no crash message. It's
as
tho i closed it.

On another machine it crashes on closing the second form that pops up.

This form is a directx scene.

So why on my dev machine does this never happen? But happens 100% of the
time on other machines, what difference could their be?

Sep 20 '06 #5

P: n/a
Well, it was an educated guess, based upon the very limited amount of
information provided, and my own experience with DirectX. DirectX sits
directly on top of the Hardware Abstraction Layer of the OS, and is designed
to work directly with the video card, which does most of the actual drawing
work. Most video cards these days have support for storing and drawing 3D
objects, to some extent or another. DirectX therefore has quite a number of
methods for getting video card support information from the video card, as
not all video cards support all of the same types of operations, and vary in
terms of video memory, etc.

If one builds a DirectX application that draws on one machine, and does not
include enough querying to the video card to find out what it supports,
one's code may attempt to use some function that is not supported by a video
card on a different machine. This would result in the kind of behavior
described by the OP.

The OP was somewhat unclear about what he was doing, but did mention the
term "scene," which is a DirectX term for a 3D "scene". Since he indicated
that the app works fine on one machine, but breaks on others, because
DirectX relies quite heavily on the video card's capabilities, and since the
OP didn't mention anything about the video cards on these other machines, I
concluded that it was most likely that the OP was not aware of the intimate
dependency of DirectX on hardware. Therefore, I somewhat tentatively
suggested that he look at the video card differences between the machines.

--
HTH,

Kevin Spencer
Microsoft MVP
Software Composer

A watched clock never boils.

"Cor Ligthert [MVP]" <no************@planet.nlwrote in message
news:%2****************@TK2MSFTNGP02.phx.gbl...
Kevin,

Why not the sound card?

:-)

You are right with your answer but in my idea is this not resolvable by a
newsgroup than just guessing.

Cor

"Kevin Spencer" <uc*@ftc.govschreef in bericht
news:ut*************@TK2MSFTNGP05.phx.gbl...
>Video card?

--
HTH,

Kevin Spencer
Microsoft MVP
Digital Carpenter

A man, a plan, a canal,
a palindrome that has gone to s**t.

"Daniel" <Da*****@vestryonline.comwrote in message
news:ul*************@TK2MSFTNGP05.phx.gbl...
>>Hey guys

I have a app that runs fine on my deve machine, in debug oe or straight
from my installer.

Stick it on another machine, similar spec and when i close a child form
it closes the whole app....essentially crashing but no crash message.
It's as tho i closed it.

On another machine it crashes on closing the second form that pops up.

This form is a directx scene.

So why on my dev machine does this never happen? But happens 100% of the
time on other machines, what difference could their be?



Sep 20 '06 #6

P: n/a
Hello Daniel,

Did u try to run release version

Does other machines have the same Win+SP, DirectX, SDK versions?

DHey guys
D>
DI have a app that runs fine on my deve machine, in debug oe or
Dstraight from my installer.
D>
DStick it on another machine, similar spec and when i close a child
Dform it closes the whole app....essentially crashing but no crash
Dmessage. It's as tho i closed it.
D>
DOn another machine it crashes on closing the second form that pops
Dup.
D>
DThis form is a directx scene.
D>
DSo why on my dev machine does this never happen? But happens 100% of
Dthe time on other machines, what difference could their be?
D>
---
WBR,
Michael Nemtsev :: blog: http://spaces.live.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche
Sep 20 '06 #7

P: n/a
Kevin,

I know, Herfried has given often the same answer in the newsgroup
language.vb.

However, thanks for your deep explanation, which reminds me again better to
it.

But it still is a gues in my opinion. While than in my idea it can be the
soundcard as well, for which is too DirectX support.

Cor

"Kevin Spencer" <uc*@ftc.govschreef in bericht
news:On**************@TK2MSFTNGP03.phx.gbl...
Well, it was an educated guess, based upon the very limited amount of
information provided, and my own experience with DirectX. DirectX sits
directly on top of the Hardware Abstraction Layer of the OS, and is
designed to work directly with the video card, which does most of the
actual drawing work. Most video cards these days have support for storing
and drawing 3D objects, to some extent or another. DirectX therefore has
quite a number of methods for getting video card support information from
the video card, as not all video cards support all of the same types of
operations, and vary in terms of video memory, etc.

If one builds a DirectX application that draws on one machine, and does
not include enough querying to the video card to find out what it
supports, one's code may attempt to use some function that is not
supported by a video card on a different machine. This would result in the
kind of behavior described by the OP.

The OP was somewhat unclear about what he was doing, but did mention the
term "scene," which is a DirectX term for a 3D "scene". Since he indicated
that the app works fine on one machine, but breaks on others, because
DirectX relies quite heavily on the video card's capabilities, and since
the OP didn't mention anything about the video cards on these other
machines, I concluded that it was most likely that the OP was not aware of
the intimate dependency of DirectX on hardware. Therefore, I somewhat
tentatively suggested that he look at the video card differences between
the machines.

--
HTH,

Kevin Spencer
Microsoft MVP
Software Composer

A watched clock never boils.

"Cor Ligthert [MVP]" <no************@planet.nlwrote in message
news:%2****************@TK2MSFTNGP02.phx.gbl...
>Kevin,

Why not the sound card?

:-)

You are right with your answer but in my idea is this not resolvable by a
newsgroup than just guessing.

Cor

"Kevin Spencer" <uc*@ftc.govschreef in bericht
news:ut*************@TK2MSFTNGP05.phx.gbl...
>>Video card?

--
HTH,

Kevin Spencer
Microsoft MVP
Digital Carpenter

A man, a plan, a canal,
a palindrome that has gone to s**t.

"Daniel" <Da*****@vestryonline.comwrote in message
news:ul*************@TK2MSFTNGP05.phx.gbl...
Hey guys

I have a app that runs fine on my deve machine, in debug oe or straight
from my installer.

Stick it on another machine, similar spec and when i close a child form
it closes the whole app....essentially crashing but no crash message.
It's as tho i closed it.

On another machine it crashes on closing the second form that pops up.

This form is a directx scene.

So why on my dev machine does this never happen? But happens 100% of
the time on other machines, what difference could their be?



Sep 20 '06 #8

This discussion thread is closed

Replies have been disabled for this discussion.