Re: [Framers] Windows XP versus Windows Explorer (Ding!)

2016-11-16 Thread Ken Poshedly
As stated in the original, I'm still with Windows XP. And I will definitely check into the "thumbs.db" things. Thanks very much. -- Ken in Atlanta On Wednesday, November 16, 2016 3:27 PM, Tino H. Haida wrote: ... Yes, this is weird. Win 7 locks folders when you

Re: [Framers] Windows XP versus Windows Explorer (Ding!)

2016-11-16 Thread Tino H. Haida
... Yes, this is weird. Win 7 locks folders when you work with them in certain applications (Acrobat, FrameMaker), but also with the normal Win Explorer. The Explorer puts an invisible "thumbs.db" file into folders that have been opened and keeps them locked. See

Re: [Framers] Windows XP versus Windows Explorer (Ding!)

2016-11-16 Thread Lise Bible
I'm on Win 7 64 bit, but if I'm trying to rename a folder and get that message I will try changing the view in Windows Explorer first (before resorting to a reboot). I like list or detail view as a default, but when I change it to icons and try again, it often lets me rename the folder. Worth a

Re: [Framers] Windows XP versus Windows Explorer (Ding!)

2016-11-16 Thread Martinek, Carla
For the record, it happens from time to time on Win 7 64bit as well. -Carla -Original Message- From: Framers [mailto:framers-bounces+cmartinek=zebra@lists.frameusers.com] On Behalf Of Ken Poshedly Sent: Wednesday, November 16, 2016 1:27 PM To: Framers List

[Framers] Windows XP versus Windows Explorer (Ding!)

2016-11-16 Thread Ken Poshedly
Here's an annoyance where two "things" on my computer simply can't get along and I wonder if anyone here has any suggestions on how to stop this from happening. While my two coworkers use Windows 7, my own office platform is still chugging along nicely with Windows XP. This is because in the

Re: [Framers] crash saving to XML - resolved, sort of

2016-11-16 Thread Robert Lauriston
Is it possible you exceeded the Windows maximum path length? https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx#maxpath > On Wed, Nov 16, 2016 at 9:50 AM, Fred Wersan wrote: > >> Last week I asked about a crash when I try to save to XML (Frame 2015,

Re: [Framers] crash saving to XML - resolved, sort of

2016-11-16 Thread Fred Wersan
Well, all the files saved to XML fine in September. Other books work and they all use more or less the same naming conventions and file structure, so it is hard to think that all of a sudden that's the problem. That's why it is hard to point a finger at one particular source for the problem.

Re: [Framers] crash saving to XML - resolved, sort of

2016-11-16 Thread Bernard Aschwanden (Publishing Smarter)
I've been using the most current patches of most/all of the software without that issue, but... Maybe some of the path names (do you link to other files, import images by reference, conref things) may be a part of the cause? Odd issue, quirky workaround, but glad you got your content back!

Re: [Framers] crash saving to XML - resolved, sort of

2016-11-16 Thread Fred Ridder
In past years, I've seen problems when any directories (folders) in the path contain one or more spaces. As a result I have *always* used either camelCase or underscores as separators in multi-word folder names just to avoid the whole issue. Windows itself doesn't care, but some applications,

Re: [Framers] crash saving to XML - resolved, sort of

2016-11-16 Thread Peter Gold
Just a guess based on having been bitten by odd bugs over the years with various applications on various platforms: P,erhaps the shorter pathname involved in saving to Desktop eliminates either particular characters, or avoids problems caused by longer pathnames, or a combination of both.

[Framers] crash saving to XML - resolved, sort of

2016-11-16 Thread Fred Wersan
Last week I asked about a crash when I try to save to XML (Frame 2015, structured). After trying everything I could think of, I called Adobe support. After about an hour or so, the resolution was that if I copied the problem files to my desktop, I could save them to XML without crashing. This