I've written a VB 5 program which runs OK on all machines but one (about 5 in all) on to which it has been loaded. The "rogue" machine has the identical Windows 95 (version 2), and the same TT fonts as another on which it runs successfully.
The program code sets the font to TT Arial 8.25, but on the rogue machine it appears on screen as largerr. And the program does not respond correctly to code which assumes the font is 8.25.
The rogue machine appears to run all the other software loaded on it without problem, and therefore I am not strongly inclined to suspect corruption of the OS.
Have now built in code to check the actual font size after it has been set to 8.25 and to downsize it if necessary. But it is not easy to get access to the rogue machine so will not be able to test it for a while. (Anyway after many unsuccesful attempts to think of a cause, I'm not very hopeful ).
Chip problem? I wouldn't have thought so because setting a font is one of the simplest things a chip can be involved in and therefore I wouldn't have thought it could have got it wrong.
Has anyone else encountered this or a similar problem and if so, were they able to find a solution?
Does anyone have any ideas please?
Thanks
RexA
The program code sets the font to TT Arial 8.25, but on the rogue machine it appears on screen as largerr. And the program does not respond correctly to code which assumes the font is 8.25.
The rogue machine appears to run all the other software loaded on it without problem, and therefore I am not strongly inclined to suspect corruption of the OS.
Have now built in code to check the actual font size after it has been set to 8.25 and to downsize it if necessary. But it is not easy to get access to the rogue machine so will not be able to test it for a while. (Anyway after many unsuccesful attempts to think of a cause, I'm not very hopeful ).
Chip problem? I wouldn't have thought so because setting a font is one of the simplest things a chip can be involved in and therefore I wouldn't have thought it could have got it wrong.
Has anyone else encountered this or a similar problem and if so, were they able to find a solution?
Does anyone have any ideas please?
Thanks
RexA