Problem with converting eps file to vector format from GSView under Windows (x64)

Where do legs

If you suddenly (I don’t know why) had the idea “if I don’t need to redo my old scientific article from TeX in Microsoft Word” or if you have to quickly sculpt a presentation of your outstanding diploma / thesis in PowerPoint, then You will be horrified to see the quality of excellent vector eps graphics after inserting them into documents created by you in Microsoft office applications. The reason for this is the use of a raster preview image of your vector eps-picture instead of correctly converting it to a similar format with which Windows is capable of working. This is emf (enhanced windows metafile). Files of this format are inserted in such a way that it is pleasant to see: increase by how many times you want - you will not see the “steps” and the text on such graphs can be edited.

How to convert

For the magical transformation of EPS files that are not particularly familiar to Microsoft in native emf files, they usually use the relatively free (if you don’t want any additional gadgets from it) pstoedit program. This program easily converts PostScript files into other formats, including the necessary emf. Problems running it from the command line usually do not exist. But not everyone likes this way of working (well, they got used to the mouse, which does not happen). Such people can be happy. In the “standard” viewer of PostScript files called GSView there is a special sub-item in the Edit menu, this sub-item is “Convert to vector format ...” and it does nothing but launches the pstoedit I mentioned, of course installed. Users of the 32-bit version of Windows can finish reading here, since there shouldn't be any problems with the working bundle GhostScript-GSView and the installed pstoedit.

And if you have 64-bit Windows

Then you probably put GhostScript 64-bit. And in this case, when you run "Conversion to vector format ..." you can not avoid a critical error. The solution is to use the command line by running pstoedit directly. But if the craving for the mouse is insurmountable, then you can read the error report when converting and see an unexpected thing for yourself:
pstoedit: version 3.60 / DLL interface 108 (built: Aug 27 2011 - release build - MS VC++ 1600 - 64-bit) : Copyright (C) 1993 - 2011 Wolfgang Glunz
running-win command line: C:\Program Files\gs\gs9.05\bin\ gswin32c.exe -q -dDELAYBIND -dWRITESYSTEMDICT -dNODISPLAY -dNOEPS D:/_temp/psin2
Interpreter failure: -1
Instead of the 64-bit version of GhostScript you installed ( gswin64c.exe ), pstoedit launched from GSView tries to call its 32-bit counterpart ( gswin32c.exe ).
I quickly failed to figure out who is to blame in this case and therefore I propose a solution that amazes with its originality. In the folder with gswin64c.exe, create a copy of this file and name it gswin32c.exe .
')
Probably there is a more kosher solution, but so far I have been completely satisfied with this option. Everything worked and the mouse again nicely warms the hand.