SynapseDirect

Well, 214 final is now out .. so time to look at what is up for 215 betas!

Considering I had forgotten about this great version checker/downloader, Let's plan for Client 215 final to be in less than 2 months.

After automated upgrade of the client, I got this message when trying to create local PDF, one other client does not have this problem:

An error has occurred.  If this occurred with an upgrade, please revert to the older version for the meantime, and report the error message as documented below.

make object! [
    code: 300
    type: 'script
    id: 'no-value
    arg1: 'gswin32-path
    arg2: none
    arg3: none
    near: [gswin32-path { -q -dSAFER -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sOutputFile=} to-local-file pdffilename " -f "]
    where: 'rejoin
]

Hmmm.  Graham will have to look into that.

The obvious workaround is copying your working synapse.exe to the PC which was upgraded. 

The latest versions of Synapse try to discover the path to gswin32 in the registry instead of asking the user to setup the ghostscript path which was too tasking for a lot of people.

Are you using 64 bit software instead??

Qilin

Do you have something like this  in your registry

HKEY_LOCAL_MACHINE\SOFTWARE\GPL Ghostscript\8.63

and if so what is the value of the key GS_DLL ?

Does Synapse say that your installation passes when it does the verification on startup?

Graham:

Are you using 64 bit software instead??

I am using 32 bit gswin32 under vista 64, it was working after the most recent upgrade of the client

Do you have something like this  in your registry

HKEY_LOCAL_MACHINE\SOFTWARE\GPL Ghostscript\8.63

No such item.

So, presumably your verification of installation is complaining that ghostscript is not installed.

What is the registry setting for ghostscript in vista 64?

hmm, I don't see anything for ghostscript in the registry.  So that's why the new client couldn't find it.

I tried to reinstall and the installation ended prematurally without adding into the registry.  It was previous working because I have a dual boot system, with two OS pointing to the same program files folder, ghostscript was installed in windows XP as well.  I will try to add the registry manually and see if it will fix the problem.

I'm going to release a version that drops back to the previous method of using the system path if it can't find it in the registry.

Tried manually adding the same from XP to the registry of vista 64, still not working.  R215B1 works fine, thanks Graham :-)

Good to know that it now works.

But didn't the verification screen warn you that it couldn't find gswin32c.exe ??

The verification windows doesn't seem to be accurate with 64 bit OS, ghostscript and gsview were both working but none were found by the client. I remembered it's the same with 64 bit XP before I switched to vista.

One minor problem, after PDF was created, the URL is using 127.0.0.1:8002 adddress and internet explorer could not open the page, the port need to be changed to 8001?