Why do I sometimes get a blue screen after closing Respax and stays like that for one minute? (Respax slow shut-down)
Index
Overview
Respax runs (at the moment 
) on the newest Micro$oft servers. There is a piece of software that talks between the client printers and the servers. Due to Micro$oft, if clients with older operating systems or different operating systems, uses the printer software a translator program is used. Respax uses this printer software to print, preview reports and exporting reports. Due to Micro$oft, this translating program prevents a user from logging off the server for one minute, after the translating program has been used.
Solution:
1. Close Respax as normal
2. Close the RDP session by clicking on the yellow bar's X - see picture below.
Detailed description
On Server 2003 x64, the system uses the Splwow64.exe process to translate between 32-bit programs and the driver model of the 64-bit operating system. When a 32 bit program is used a process Splwow64.exe is loaded that remains in memory for several minutes. This process remains in memory in order to increase system performance and unloads from memory after a specified time from the end of the last job. By editing the registry, the un-load period can be adjusted to 1 minute minimum. Although this can be good for performance, it causes RDP sessions to hang when short time has passed after the user has done his last print and tries to close the session. There is no work-around on this. (Apart from running Micro$oft Window$ 64 bit operating systems and printers.)