Home All Groups Group Topic Archive Search About
Author
20 Nov 2007 6:20 PM
David DB
Hi,

On some machines our VB6 program produces the error "Unknown error 50003".

After searching on the net I found out that this could have something to do
with wrong versions of some components. I have included these in the setup.
but with no luck.

After removing a GIF picture from a form it went further, but now it get
this "This program has executed a illegal instruction and will now close (or
something like this)"

This only occurs on Win98 machines for one client. But they have 250  Win98
machines.....

The development platform is WinXP VB6 SP6

Please help!!

Author
20 Nov 2007 6:32 PM
Bob Butler
"David DB" <er_forts***@hotmail.com> wrote in message
news:%23EBLuJ6KIHA.1208@TK2MSFTNGP05.phx.gbl...
<cut>
> The development platform is WinXP VB6 SP6

the standard rule of thumb is to develop, or at least test and do the setup
packaging, on the lowest OS version you plan to support.  If you are
distributing XP components to Win9x machines you may have numerous
versioning problems.  Your best bet is to get a Win98 system set up to test
& package the app.
Author
20 Nov 2007 6:45 PM
David DB
Hi Bob,

This is not possible for us, and anyway it might be that we dont include the
correct components anyway. And this only happens with this customer.

David

Show quoteHide quote
"Bob Butler" <noway@nospam.ever> wrote in message
news:OoaNcP6KIHA.4808@TK2MSFTNGP05.phx.gbl...
> "David DB" <er_forts***@hotmail.com> wrote in message
> news:%23EBLuJ6KIHA.1208@TK2MSFTNGP05.phx.gbl...
> <cut>
>> The development platform is WinXP VB6 SP6
>
> the standard rule of thumb is to develop, or at least test and do the
> setup packaging, on the lowest OS version you plan to support.  If you are
> distributing XP components to Win9x machines you may have numerous
> versioning problems.  Your best bet is to get a Win98 system set up to
> test & package the app.
>
>
Author
20 Nov 2007 8:43 PM
Steve
On 20 Nov, 18:45, "David DB" <er_forts***@hotmail.com> wrote:

> This is not possible for us,

Then it may be that you have no solution. You don't say why it's not
possible for you, but ultimately you will have problems if you're not
at least packaging on the same OS that the customer is using, as
others have said. Hence either they must upgrade their 250 machines,
or you must obtain one running Win 98.

Now I'm no expert on Microsoft's licensing policy and its implications
here, but depending on why you say it's not possible for you to
package on Win 98, might it be possible to install VB6 - maybe
temporarily in the first instance - on one of your customer's Win 98
machines and package your source code there?


> and anyway it might be that we dont include the
> correct components anyway.

I don't understand this - surely the Packaging and Deployment Wizard
automates this process.


> And this only happens with this customer.

Do you have many customers still running Win 98?  Are they running the
same code as this one? If so, could there be differences in Win 98
patch level, especially the presence or otherwise of OSR2, which was a
major patch for 98 and introduced a lot of new functionality (e.g. USB
support, IIRC) and a number of bug fixes.


Steve Adams
Author
20 Nov 2007 11:48 PM
David DB
Hi Steve,

Our program is quite complex with a load of third-party components and
tools. So making a build environment on Win98 will be too much work. And
this as I said will not solve the problem since it works perfectly in our
Win98 test environment.

We have thousands of customers using Win98 with no problem, and we suspect
that the one customer that is having problems is due to another program
installing some incompatible components. And they are all exactly the same
ghosted Win 98 installation.

Our problem is refered to in several places on the net, but the solutions is
not working for us.

And we dont use the Packaging and Deployment Wizard since this simple thing
is useless to us. We're using the excellent Inno setup program.

It might be that we must have a image of a PC sent to us to further debug.

David

Show quoteHide quote
"Steve" <st***@hatchwarren.plus.com> wrote in message
news:0037e1ba-84b3-4141-b5c4-f8d7d05356c0@i29g2000prf.googlegroups.com...
> On 20 Nov, 18:45, "David DB" <er_forts***@hotmail.com> wrote:
>
>> This is not possible for us,
>
> Then it may be that you have no solution. You don't say why it's not
> possible for you, but ultimately you will have problems if you're not
> at least packaging on the same OS that the customer is using, as
> others have said. Hence either they must upgrade their 250 machines,
> or you must obtain one running Win 98.
>
> Now I'm no expert on Microsoft's licensing policy and its implications
> here, but depending on why you say it's not possible for you to
> package on Win 98, might it be possible to install VB6 - maybe
> temporarily in the first instance - on one of your customer's Win 98
> machines and package your source code there?
>
>
>> and anyway it might be that we dont include the
>> correct components anyway.
>
> I don't understand this - surely the Packaging and Deployment Wizard
> automates this process.
>
>
>> And this only happens with this customer.
>
> Do you have many customers still running Win 98?  Are they running the
> same code as this one? If so, could there be differences in Win 98
> patch level, especially the presence or otherwise of OSR2, which was a
> major patch for 98 and introduced a lot of new functionality (e.g. USB
> support, IIRC) and a number of bug fixes.
>
>
> Steve Adams
>
Author
20 Nov 2007 6:44 PM
MikeD
Show quote Hide quote
"David DB" <er_forts***@hotmail.com> wrote in message
news:%23EBLuJ6KIHA.1208@TK2MSFTNGP05.phx.gbl...
> Hi,
>
> On some machines our VB6 program produces the error "Unknown error 50003".
>
> After searching on the net I found out that this could have something to
> do with wrong versions of some components. I have included these in the
> setup. but with no luck.
>
> After removing a GIF picture from a form it went further, but now it get
> this "This program has executed a illegal instruction and will now close
> (or something like this)"
>
> This only occurs on Win98 machines for one client. But they have 250
> Win98 machines.....
>
> The development platform is WinXP VB6 SP6


Did you also package your app under WinXP?  If so, you might have included
XP-only components that are hosing Win98. If at all possible, you should
package your app under the lowest OS version you need to support. Some
people say you should also compile under the lowest OS version you need to
support, but personally, I think it's more the packaging than the compiling.

List the components you're distributing and we might be able to determine
the problematic one and provide more help.

--
Mike
Microsoft MVP Visual Basic
Author
20 Nov 2007 8:53 PM
Kevin Provance
I'm not sure about the second error, but as far as the 50003 error, this is
what happens when you attempt to use an image with igher colour resolution
than the OS will support.  I had this problem numerous times on Win 98 and I
ended up having to redo my images in 256 colors, versus the some million it
originally was.

Why?  Who knows, but that was what I did to fix it.

- Kev

Show quoteHide quote
"David DB" <er_forts***@hotmail.com> wrote in message
news:%23EBLuJ6KIHA.1208@TK2MSFTNGP05.phx.gbl...
| Hi,
|
| On some machines our VB6 program produces the error "Unknown error 50003".
|
| After searching on the net I found out that this could have something to
do
| with wrong versions of some components. I have included these in the
setup.
| but with no luck.
|
| After removing a GIF picture from a form it went further, but now it get
| this "This program has executed a illegal instruction and will now close
(or
| something like this)"
|
| This only occurs on Win98 machines for one client. But they have 250
Win98
| machines.....
|
| The development platform is WinXP VB6 SP6
|
| Please help!!
|
|
Author
20 Nov 2007 11:51 PM
David DB
Hi Kev,

Yes we found out by removing one graphics element that it worked, but then
the whole program crashed later on. And it might have something to do with
the first problem.

Still suspect a component version error.

David

Show quoteHide quote
"Kevin Provance" <ca***@tpasoft.com> wrote in message
news:%233k1cd7KIHA.1208@TK2MSFTNGP05.phx.gbl...
> I'm not sure about the second error, but as far as the 50003 error, this
> is
> what happens when you attempt to use an image with igher colour resolution
> than the OS will support.  I had this problem numerous times on Win 98 and
> I
> ended up having to redo my images in 256 colors, versus the some million
> it
> originally was.
>
> Why?  Who knows, but that was what I did to fix it.
>
> - Kev
>
> "David DB" <er_forts***@hotmail.com> wrote in message
> news:%23EBLuJ6KIHA.1208@TK2MSFTNGP05.phx.gbl...
> | Hi,
> |
> | On some machines our VB6 program produces the error "Unknown error
> 50003".
> |
> | After searching on the net I found out that this could have something to
> do
> | with wrong versions of some components. I have included these in the
> setup.
> | but with no luck.
> |
> | After removing a GIF picture from a form it went further, but now it get
> | this "This program has executed a illegal instruction and will now close
> (or
> | something like this)"
> |
> | This only occurs on Win98 machines for one client. But they have 250
> Win98
> | machines.....
> |
> | The development platform is WinXP VB6 SP6
> |
> | Please help!!
> |
> |
>
>