Im currently working at home under Ashell/Windows and wondering if the GDI //IMAGE command looks at the Windows Ashell permcache or cache directory for the image? as im uploading theses all upfront at users login, If so then its must be me being a fool somewhere.
Im getting the following GDI error and pretty sure the image is in my Q:\Madics\miame\cache folder.
//IMAGE,FORMETAL.PNG,1,1,1658,2244,IMGF_STRETCH
7 16:26:05 <PRINT:4cc9> IMAGE Library Error #0 (No error (0) (FORMETAL.PNG))

(And I guess it work the same under ATE and it looks at the ATE cache folder.)

Thanks
Steve

Well I thought it was working in the office under ATE/Linux yesterday and this confirms that side of things:


Does Ashell/Windows do something similar?

This really is just to keep most my code consistent between platforms and having it working when developing at home

The best way to see what it's really doing is to activate the FOPENS trace. If I do this from a local Windows context and try reference a non-existent file coffee2.jpg in an //IMAGE directive, I see this.



Line 77, which says "try(-1)" appears only if the environment variable ASWCACHE exists (in my case, I set it to C:\TEMP). That's one difference between local A-Shell/Windows and ATE (which will instead look in the %ATECACHE% and %ATEPERMCACHE% directories.)

Line 78, which says "try(4)" is looking in the ASHLPD: ersatz directory.

If it's an ICO or PNG file, it will also look in the %MIAME%\icons\ subdirectory (both ATE and A-Shell/Windows).

Thanks Jack, as I’m using PNG files I could place them All in %MIAME%\icons but maybe best I set ASWCACHE to a %MIAME%\cache folder, thanks for the tips!

Under Ashell/Windows transferring the files to c:\temp\madics and setting ASWCACHE worked a treat. Thanks! GDI Printing is happy again.