Skip to main content

[Migrated content. Thread originally posted on 13 May 2005]

When i am using this library

CALL "WIN$PRINTER" USING WINPRINT-SET-SETTINGS
UTIMP-WINDOW-DEVICE GIVING IDX
WINPRINT-DATA
CALL "WIN$PRINTER" USING WINPRINT-GET-SETTINGS
UTSETIMP-SETUP GIVING IDX

my problem is under windows xp and windows 98 if a configure under window xp the printer it will not work under 98 and the opposite.

[Migrated content. Thread originally posted on 13 May 2005]

When i am using this library

CALL "WIN$PRINTER" USING WINPRINT-SET-SETTINGS
UTIMP-WINDOW-DEVICE GIVING IDX
WINPRINT-DATA
CALL "WIN$PRINTER" USING WINPRINT-GET-SETTINGS
UTSETIMP-SETUP GIVING IDX

my problem is under windows xp and windows 98 if a configure under window xp the printer it will not work under 98 and the opposite.
This is expected behavior. What this opcode returns to you is a Windows internal datastructure known as DEVMODE. DEVMODE has one part that is static across all implementations, but it also contains a driver specific part. Although I cannot tell for sure, it is quite evident that there are different drivers for Win98 and WinXP. Thus, this opcode is not a good option in a mixed environment.
This behavior is a result of Microsoft Windows and its drivers, not ACUCOBOL-GT.