If the image was really destroyed, it shouldn't be there anymore. But for a "secure" way you could do a flip after the GCCollect and see if it helps.
But you must have quite a strange graphics card ... Because 640x480 as TImage means 1024x1024 which normally won't work on such old cards at all (GeForce 3 or 4 at minimum when I remember correctly) and thats what is needed to have an image of that size (as 640 becomes 1024 and 480 becomes 512 -> max(1024,512) = 1024).
To test if it is a VRAM thing you could load it as pixmap and draw the pixmap ... if it works then then it most likely might be VRAM thing.
If not, then perhaps the system just is too low on memory or has a too small paging file. (because out of memory often comes up if the paging file can't be made larger either because manually fixed to that size or because the users have their C partition full of trash)
But you must have quite a strange graphics card ... Because 640x480 as TImage means 1024x1024 which normally won't work on such old cards at all (GeForce 3 or 4 at minimum when I remember correctly) and thats what is needed to have an image of that size (as 640 becomes 1024 and 480 becomes 512 -> max(1024,512) = 1024).
To test if it is a VRAM thing you could load it as pixmap and draw the pixmap ... if it works then then it most likely might be VRAM thing.
If not, then perhaps the system just is too low on memory or has a too small paging file. (because out of memory often comes up if the paging file can't be made larger either because manually fixed to that size or because the users have their C partition full of trash)