pngquaint error when building html5 on 7.0.1

[cammerayguy]

I have an html5 project previously released with 7.0.

I have upgraded to 7.0.1 but now find the project does not build.

After Captivate starts converting the videos I get a pop-up that says:

"C\Program Files\Adobe\Adobe Captivate 7 (32 Bit)\utils\opt\win\pngquant.exe"

X Windows cannot access the specified device, path or file. You may not have the appropriate permissions to access the item

Captivate locks up and I have to kill the process.

After reading some other posts in this forum I did move the files closer to root.

The build location is

C:\Adrian\Allergan\aModules\WAP\C\html5

and the Project title is

WAPF_22

Even with that cryptic naming I get the error.

Other info - Running WinXP (though scheduled for an upgrade soon!)

Any help appreciated - as I'd like to see if/how much the html5 experience has been improved.

[Guest]

We have now got the exact same issue

To work around it we have to publish to a local folder then copy across to the server manually

[cammerayguy]

Some guidance from Adobe on this new problem would be great!

The consus is that 7.0.1 has introduced new restrictions on the html5 build environment... which is bad news if you have deployed projects that you now can't republish.

Mr Clisse suggests that a network build .location causes the issue.

But in the example I quoted my build location is on my C: drive.

Our projects however use a lot of library items that are loaded from a shared resource area on a network drive.

As an experiment I went through about 70 library items, changing their location manually to a local copy on my C: drive.

I may have forgotten something ... because I still get exactly the same error message.

[Sankaram]

Hi Cammerayguy,

    It looks like the issue is specific to WinXP. We are investigating at our end. Meanwhile can you try the following and update us?

a) If you have Windows 7 machine, do you encounter the issue in Win7?

b) On WinXP, Can you Switch OFF "Retain Slide Quality Settings"  and set the slider to "High"  (settings can be found at Edit: Preferences: Project: SWF Size and Quality) and try to publish to HTML5?

Also Can you share the sample project you encounter the issue? upload the cptx file to workspaces.acrobat.com and share the link with me at sankaram at adobe dot com.

Thanks,

Sankaram.

[Guest]

Hi Sankaram,

All our desktops are Windows 8, and we have the issue.

cammerayguy I don't think its network related, its more length of file path related.

We have a project on our server, and we publish to a sub folder on that server.

The full path to the publish location is approx 70 chars

If I publish it locally to C:\Publish, its then works, but I think its because the folder length is much shorter

[cammerayguy]

I set the preferences to switch OFF "Retain Slide Quality Settings"  and set the slider to "High"  as suggested.

The html5 build now publishes successfully.

It is 500k larger than it was before - probably because the audio is now set to a higher quality.

I've uploaded the project for you.

I will check the previously released (unmodified)  project on Win 7 for you tonight.

[dt4pt]

I find that cammerayguy's Slide Quality Settings solution works for me. I'm running the 64bit version on Windows Vista.

[joyhhoffman]

Hi have the same issue. I get the error...

c:\prolgram files\adobe\adobe captivate 7 x64\utils\opt\win\pngquant.exe

The filename or extention is too long

So, I changed the file name to 6 characters and published it to c:\cappub.

Still get the error... any thoughts?

I'm running the patched version of Captivate 7 on a 64 bit Window 7 machine.

Joy

[cammerayguy]

Sankaram,

I have copied the project to my home office PC running 64bit Win 7.

Without making the changes you suggested I get an error during the build.

The Win 7 error is "The filename or extension is too long."

I don't have any networked drives on this PC - so the problem is not network related.

[Sankaram]

Hi Cammerayguy,

     I have got the file. We could see the issue at our end.You are right,This has nothing to do with networkdrive. The issue is with path being long for optimising HTML5 published content.Timebeing I suggest you should use smaller paths as suggested by Mr Clisse. Following fields helps reducing the path.

a) "ProjectTitle" in published dialog should be minimum in length. (You can rename once the publish is done)

b) "Folder Location" (Publish to root like C/D Drive)

This is more prominent in WinXP as it can hold less number of characters.

Thanks,

Sankaram.