Re: Compile Differences, WinXP-Pro and Win2K
- From: Sinna <news4sinna_NOSPAM@xxxxxxxxxx>
- Date: Thu, 19 Oct 2006 08:26:49 +0200
Signet wrote:
I have an application that I'm trying to release tomorrow, and just found out that with the latest release, if the app is compiled to exe on WinXP Pro, it will not run properly on my work Win2K machine. It starts fine, and most everything works, but where a bunch of graphics should be loaded, they apparently are not. Likewise, if I compile on Win2K, the same thing happens on my WinXP Pro machine.Always build the application on the lowest OS you want to support. Only in that way you'll be able to circumvent some nice features of newer OSes that aren't supported by the older ones.
I'm running VB6 SP6 on both machines, and yes, there could be some runtime differences. But the EXE itself is different, a byte here, a byte there, but a total of around 1,000 differences in a 1 MB file.
I guess I could include both EXEs in my app, and use one for each OS, but I'd really like to figure out what the problem might be. This happened once during this app's development, when I tried to compile to Native code, so I switched back to P-Code, and the problem disappeared. Until now, on the eve of the app's release.
Any ideas? I really could use some! ;-)
I've once searched for an incompatibility between Win2K and XP. Finally I found out that the default interface for COM+ on XP is Version 1.5 while the default one on 2K is Version 1.0.
Perhaps you're now facing the same: are you using GDI+?
Sinna
.
- References:
- Compile Differences, WinXP-Pro and Win2K
- From: Signet
- Compile Differences, WinXP-Pro and Win2K
- Prev by Date: FIND LDAP PATH of COMPUTER OBJECT
- Next by Date: Re: Turn off autochange in VB6
- Previous by thread: Re: Compile Differences, WinXP-Pro and Win2K
- Next by thread: FIND LDAP PATH of COMPUTER OBJECT
- Index(es):
Relevant Pages
|
