>>>>I am using the wonderful tool by Marat Chariev, Frx2Any.
>>>>I had occasion to rebuild an exe which uses it and now that app throws an exception:
>>>>Error #125 in program ANYPRINTER.INIT on line #0
>>>> Printer is not ready.
>>>>
>>>>Frx2Any.app and the companion iSEDQuickPDF.DLL are in the root of the application.
>>>>the application is run via Task Scheduler.
>>>>it starts up in the sub folder with the path fully qualified to the root.
>>>>
>>>>nothing of substance has changed in the app from the previous version to this new one other than insuring a date not be null.
>>>>
>>>>any clues?
>>>
>>>Is there any printer installed, and if, is the default one online, connected ,etc?
>>
>>Thanks Lutz,
>>
>>If this were an isolated application i would be looking to issues with the printer. However there is a (shall we say) Flag Ship application which uses the same instance of Frx2Any and sharing the same folders and files and this application has no issues generating PDF output. The only real difference, other than the size and scope, is that the Flag Ship is run from a shortcut on the desktop.
>
>What does the shortcut that runs the "Flag Ship" actually do?
>
>I've seen cases where a shortcut actually runs a CMD or batch file which, prior to actually starting the app, maps drive letter(s) and sets default folders on those drive(s) and may set session environment variables. Or, even if the shortcut just calls the EXE, it may have a "Start in" folder set. The app or FRX2Any may not work properly without those presets, maybe tied in with security.
>
>As a general rule, anything you run as a scheduled task should contain no references to mapped drive letters. Those should all be converted to UNC paths.

S:\pro50\sbtw9.exe -CS:\pro50\config.fpw