Comments on: Adobe Captivate and corporate networks with storage restrictions

By: Tim

Tim — Thu, 24 Mar 2011 23:12:50 +0000

Thanks a lot. This has proved very helpful for me!

By: Simon

Simon — Wed, 14 Apr 2010 15:59:40 +0000

Great post, this solved the problem for me at work. Thanks.

By: Michael

Michael — Mon, 29 Mar 2010 07:20:36 +0000

@ Jim – Happy to have helped ;o)

/Michael

By: Jim Leichliter

Jim Leichliter — Fri, 26 Mar 2010 16:46:49 +0000

If Cp cannot find the My Documents folder, it will also crash. In my case, If I had to VPN into work, I’d log onto my PC first before initiating VPN. This would cause my login to be faster, but my mapped drives didn’t exist. Consequently, Cp would display the splash screen and then bomb because the My Documents folder wasn’t mapped yet. Once I mapped the drives, it was fine. I’m glad you pointed this out. Now I won’t have this problem anymore.

Thanks,

Jim Leichliter

By: Dave Howard

Dave Howard — Fri, 26 Mar 2010 05:42:53 +0000

Mike,

First of all; great post and thanks for sharing on Twitter.

Second; my company uses Team Foundation Server and I have to publish all of my stuff to our support website using Visual Studio and TFS. It’s a big change and a little time consuming. The upside is we have the security thing wired and we can always bring up a previous build if something goes kablooey. It was difficult for me to get used to the “local” file being the expendable one.

I am going to take your advice and point the default publish path to an empty folder with no restrictions.

By: Tweets that mention Adobe Captivate and corporate networks with storage restrictions | CP Guru - Adobe Captivate E-learning Blog -- Topsy.com

Fri, 26 Mar 2010 05:22:34 +0000

[...] This post was mentioned on Twitter by rickzanotti, Lieve Weymeis and Michael Lund, Edward Martino, PhD. Edward Martino, PhD said: RT @cpguru_com: New post – Adobe #Captivate and corporate networks with storage restrictions http://bit.ly/9KsQUl #adobeCaptivate [...]

By: Michael

Michael — Thu, 25 Mar 2010 22:24:51 +0000

Yeah they really did it this time. The 100MB isn’t even the worst part – they also implemented SharePoint. However, not all files are supported apparantly so now we have all our storyboards and text documents (office files, PDF, etc) in SharePoint and all our sourcefiles (Cp, Flash, PSD, images etc. ) on a regular network file server. The brilliant part is that when we create a SCORM package we might want to have a PDF linked in the course. Now with this Sharepoint stuff we can no longer store this in our “final files” folder on the network drive because it has to be in SharePoint since it’s a PDF. Basically it’s splitting all our files up in two separate locations. I’m sure this will create many enjoyable moments for us in the future ;o)

By: wheat

wheat — Thu, 25 Mar 2010 20:55:51 +0000

Nice sleuthing, Mike. 100MB is an insane local file restriction. Good luck with that battle. But at least you can use Captivate again.