This isn't really a PowerBasic question, but I do use it all
the time and really appreciate the expertise you guys have and
I was hoping one of you might be able to help me out...
I run a technical support dept and I am at my wits end trying to
solve a problem with our software on a small number of NT 4 PCs
and I was hoping one of your geniuses might be able to help with
this. The program is written in Visual C++... Some parts of the
program is 16-bit and some is 32-bit... At the point where
one 16-bit program ends the following error message appears on
a small number of NT 4 PCs.
X has caused an access violation in file ddd.exe.
The character X looks like two S characters placed over each other
overlapping... One S is slightly above the other S in this displayed
character. I can't find this character anywhere...
The ddd is the name of the 16-bit executable that just completed
itself. On PCs with this problem, any 16-bit executable that
was just called ends with the above message. The program then
continues.
On one customer's PC, the problem occurs after they load MDAC_TYP.EXE
version 2.5 (from another program). Yes, we use MDAC_TYP in our
software (version 2.1), but on the one
PC at our location we can load MDAC_TYP 2.5 with no problems. We
tried having the customer load Service Pack 6.0a...no fix...
Any ideas at all, anyone?
Patrick
------------------
the time and really appreciate the expertise you guys have and
I was hoping one of you might be able to help me out...
I run a technical support dept and I am at my wits end trying to
solve a problem with our software on a small number of NT 4 PCs
and I was hoping one of your geniuses might be able to help with
this. The program is written in Visual C++... Some parts of the
program is 16-bit and some is 32-bit... At the point where
one 16-bit program ends the following error message appears on
a small number of NT 4 PCs.
X has caused an access violation in file ddd.exe.
The character X looks like two S characters placed over each other
overlapping... One S is slightly above the other S in this displayed
character. I can't find this character anywhere...
The ddd is the name of the 16-bit executable that just completed
itself. On PCs with this problem, any 16-bit executable that
was just called ends with the above message. The program then
continues.
On one customer's PC, the problem occurs after they load MDAC_TYP.EXE
version 2.5 (from another program). Yes, we use MDAC_TYP in our
software (version 2.1), but on the one
PC at our location we can load MDAC_TYP 2.5 with no problems. We
tried having the customer load Service Pack 6.0a...no fix...
Any ideas at all, anyone?
Patrick
------------------
Comment