.exe compiled on vista doesn't run on xp??

[nik]

Hi,

I've compiled my application on my vista machine, and it won't run at
all on my xp machine. In the windows error report I get Exception
code; 0xe0434f4d. I searched for that exception, but didn't see
anything related to my problem. I can run a different .exe that I made
on the vista machine on the xp machine, so I am wondering what is
different/wrong with this one.

The xp machine does have vb6 installed on it, could that be an issue?
What reasons and solutions for this problem?

Thanks in advance,
Nik

[Brian Gideon]

On Aug 24, 7:51*pm, nik <nikb...@gmail. comwrote:

Hi,

I've compiled my application on my vista machine, and it won't run at
all on my xp machine. In the windows error report I get Exception
code; 0xe0434f4d. I searched for that exception, but didn't see
anything related to my problem. I can run a different .exe that I made
on the vista machine on the xp machine, so I am wondering what is
different/wrong with this one.

The xp machine does have vb6 installed on it, could that be an issue?
What reasons and solutions for this problem?

Thanks in advance,
Nik

So we know that at least one executable compiled on the Vista machine
works on XP right? That tells me that the .NET Framework is
*probably* installed correctly on the XP machine. Is the problem
executable using any unmanaged code? That might be part of the
problem. Can you be more specific about the error you're getting?
What makes you think 0xe0434f4d is an error code? It looks like it
coulde be a memory address as well.

[Family Tree Mike]

It could be almost anything at this point, except for the vb6 being on the
machine. You should debug on the machine, or at least some machine with XP
on it. Never assume that builds done on XP will run on Vista, or vise
versa. Debugging on the machine should show you where the app is crashing.

"nik" <ni*****@gmail. comwrote in message
news:d6******** *************** ***********@w39 g2000prb.google groups.com...

Hi,

I've compiled my application on my vista machine, and it won't run at
all on my xp machine. In the windows error report I get Exception
code; 0xe0434f4d. I searched for that exception, but didn't see
anything related to my problem. I can run a different .exe that I made
on the vista machine on the xp machine, so I am wondering what is
different/wrong with this one.

The xp machine does have vb6 installed on it, could that be an issue?
What reasons and solutions for this problem?

Thanks in advance,
Nik

[Bill McCarthy]

Hi Nik,

Ensure they have the same version of the framework on their machine. Also
you should get VPC (free from Microsoft) and run XP in it to test your apps
before deployment.


"nik" <ni*****@gmail. comwrote in message
news:d6******** *************** ***********@w39 g2000prb.google groups.com...

Hi,

I've compiled my application on my vista machine, and it won't run at
all on my xp machine. In the windows error report I get Exception
code; 0xe0434f4d. I searched for that exception, but didn't see
anything related to my problem. I can run a different .exe that I made
on the vista machine on the xp machine, so I am wondering what is
different/wrong with this one.

The xp machine does have vb6 installed on it, could that be an issue?
What reasons and solutions for this problem?

Thanks in advance,
Nik

[Michael D. Ober]

"Bill McCarthy" <Bi**@localhost .comwrote in message
news:72******** *************** ***********@mic rosoft.com...

Hi Nik,

Ensure they have the same version of the framework on their machine. Also
you should get VPC (free from Microsoft) and run XP in it to test your
apps before deployment.

Install the VPC (Virtual PC) on your Vista system and install an XP Virtual
machine in it.

Mike.

>
"nik" <ni*****@gmail. comwrote in message
news:d6******** *************** ***********@w39 g2000prb.google groups.com...

>Hi,

I've compiled my application on my vista machine, and it won't run at
all on my xp machine. In the windows error report I get Exception
code; 0xe0434f4d. I searched for that exception, but didn't see
anything related to my problem. I can run a different .exe that I made
on the vista machine on the xp machine, so I am wondering what is
different/wrong with this one.

The xp machine does have vb6 installed on it, could that be an issue?
What reasons and solutions for this problem?

Thanks in advance,
Nik

[nik]

On Aug 24, 7:10 pm, Brian Gideon <briangid...@ya hoo.comwrote:

On Aug 24, 7:51 pm, nik <nikb...@gmail. comwrote:

Hi,

I've compiled my application on my vista machine, and it won't run at
all on my xp machine. In the windows error report I get Exception
code; 0xe0434f4d. I searched for that exception, but didn't see
anything related to my problem. I can run a different .exe that I made
on the vista machine on the xp machine, so I am wondering what is
different/wrong with this one.

The xp machine does have vb6 installed on it, could that be an issue?
What reasons and solutions for this problem?

Thanks in advance,
Nik

So we know that at least one executable compiled on the Vista machine
works on XP right? That tells me that the .NET Framework is
*probably* installed correctly on the XP machine. Is the problem
executable using any unmanaged code? That might be part of the
problem. Can you be more specific about the error you're getting?
What makes you think 0xe0434f4d is an error code? It looks like it
coulde be a memory address as well.

I don't think I am using unmanaged code, but how do I check for sure?
Is there a compiler setting that would flag unmanaged code?

[Mr. Arnold]

"nik" <ni*****@gmail. comwrote in message
news:c1******** *************** ***********@p10 g2000prf.google groups.com...

On Aug 24, 7:10 pm, Brian Gideon <briangid...@ya hoo.comwrote:

>On Aug 24, 7:51 pm, nik <nikb...@gmail. comwrote:

Hi,

I've compiled my application on my vista machine, and it won't run at
all on my xp machine. In the windows error report I get Exception
code; 0xe0434f4d. I searched for that exception, but didn't see
anything related to my problem. I can run a different .exe that I made
on the vista machine on the xp machine, so I am wondering what is
different/wrong with this one.

The xp machine does have vb6 installed on it, could that be an issue?
What reasons and solutions for this problem?

Thanks in advance,
Nik

So we know that at least one executable compiled on the Vista machine
works on XP right? That tells me that the .NET Framework is
*probably* installed correctly on the XP machine. Is the problem
executable using any unmanaged code? That might be part of the
problem. Can you be more specific about the error you're getting?
What makes you think 0xe0434f4d is an error code? It looks like it
coulde be a memory address as well.

I don't think I am using unmanaged code, but how do I check for sure?
Is there a compiler setting that would flag unmanaged code?

Any language that doesn't use the .Net Framework, in particular, the CLI and
CLR is unmanaged code. VB6 is unmanaged code. An example of that would be a
VB.Net solution making a call to COM DLL written in VB6. The COM DLL didn't
originate itself by being complied using a .NET compiler.

[nik]

On Aug 25, 1:42 pm, "Mr. Arnold" <MR. Arn...@Arnold.c omwrote:

"nik" <nikb...@gmail. comwrote in message

news:c1******** *************** ***********@p10 g2000prf.google groups.com...

On Aug 24, 7:10 pm, Brian Gideon <briangid...@ya hoo.comwrote:

On Aug 24, 7:51 pm, nik <nikb...@gmail. comwrote:

Hi,

I've compiled my application on my vista machine, and it won't run at
all on my xp machine. In the windows error report I get Exception
code; 0xe0434f4d. I searched for that exception, but didn't see
anything related to my problem. I can run a different .exe that I made
on the vista machine on the xp machine, so I am wondering what is
different/wrong with this one.

The xp machine does have vb6 installed on it, could that be an issue?
What reasons and solutions for this problem?

Thanks in advance,
Nik

So we know that at least one executable compiled on the Vista machine
works on XP right? That tells me that the .NET Framework is
*probably* installed correctly on the XP machine. Is the problem
executable using any unmanaged code? That might be part of the
problem. Can you be more specific about the error you're getting?
What makes you think 0xe0434f4d is an error code? It looks like it
coulde be a memory address as well.

I don't think I am using unmanaged code, but how do I check for sure?
Is there a compiler setting that would flag unmanaged code?

Any language that doesn't use the .Net Framework, in particular, the CLI and
CLR is unmanaged code. VB6 is unmanaged code. An example of that would be a
VB.Net solution making a call to COM DLL written in VB6. The COM DLL didn't
originate itself by being complied using a .NET compiler.

If I understand this correctly, if all of the References under the
solutions properties page are of type .NET and pointing into the .NET
framework, then everything is composed of .NET parts and is therefore
managed code. ie. the solution doesn't reference any unmanaged dll, so
there is no unmanaged code involved.

[Michel Posseth [MCP]]

The xp machine does have vb6 installed on it, could that be an issue?

No not if you installed first VB6 and then VS.Net

Well actually 0xe0434f4d. is a basic exception

What reasons and solutions for this problem?

As you do not provide anny detailed info about your application it is hard
guessing what exactly is the problem
but a wild guess from my side is that you use a managed reference that is
not availlable on the target system
maybe you installed a certain SDK on the development system ?

for instance if you use anything from the windows live id classes this will
work on Vista but not on a XP machine without windows Live installed
it will bomb with a 0xe0434f4d exception
regards

Michel Posseth

"nik" <ni*****@gmail. comschreef in bericht
news:d6******** *************** ***********@w39 g2000prb.google groups.com...

Hi,

I've compiled my application on my vista machine, and it won't run at
all on my xp machine. In the windows error report I get Exception
code; 0xe0434f4d. I searched for that exception, but didn't see
anything related to my problem. I can run a different .exe that I made
on the vista machine on the xp machine, so I am wondering what is
different/wrong with this one.

The xp machine does have vb6 installed on it, could that be an issue?
What reasons and solutions for this problem?

Thanks in advance,
Nik

[Michel Posseth [MCP]]

"nik" <ni*****@gmail. comschreef in bericht
news:4e******** *************** ***********@r35 g2000prm.google groups.com...

On Aug 25, 1:42 pm, "Mr. Arnold" <MR. Arn...@Arnold.c omwrote:

>"nik" <nikb...@gmail. comwrote in message

news:c1******* *************** ************@p1 0g2000prf.googl egroups.com...

On Aug 24, 7:10 pm, Brian Gideon <briangid...@ya hoo.comwrote:
On Aug 24, 7:51 pm, nik <nikb...@gmail. comwrote:

Hi,

I've compiled my application on my vista machine, and it won't run
at
all on my xp machine. In the windows error report I get Exception
code; 0xe0434f4d. I searched for that exception, but didn't see
anything related to my problem. I can run a different .exe that I
made
on the vista machine on the xp machine, so I am wondering what is
different/wrong with this one.

The xp machine does have vb6 installed on it, could that be an
issue?
What reasons and solutions for this problem?

Thanks in advance,
Nik

>So we know that at least one executable compiled on the Vista machine
works on XP right? That tells me that the .NET Framework is
*probably* installed correctly on the XP machine. Is the problem
executable using any unmanaged code? That might be part of the
problem. Can you be more specific about the error you're getting?
What makes you think 0xe0434f4d is an error code? It looks like it
coulde be a memory address as well.

I don't think I am using unmanaged code, but how do I check for sure?
Is there a compiler setting that would flag unmanaged code?

Any language that doesn't use the .Net Framework, in particular, the CLI
and
CLR is unmanaged code. VB6 is unmanaged code. An example of that would be
a
VB.Net solution making a call to COM DLL written in VB6. The COM DLL
didn't
originate itself by being complied using a .NET compiler.

If I understand this correctly, if all of the References under the
solutions properties page are of type .NET and pointing into the .NET
framework, then everything is composed of .NET parts and is therefore
managed code. ie. the solution doesn't reference any unmanaged dll, so
there is no unmanaged code involved.

Just to confirm,, Yes you understand this correctly
But as you wil read in my below post the described error is actually a basic
framework error

;-)

Regards

Michel