Re: Windows 7 + FrameMaker 11 = BOOM!

id nothing that disagrees with that. -Fred Ridder From: david.da...@invensys.com To: framers@lists.frameusers.com Date: Mon, 12 Aug 2013 04:29:32 -0500 Subject: RE: Windows 7 + FrameMaker 11 = BOOM! Fred, one o

RE: Windows 7 + FrameMaker 11 = BOOM!

Craig Ede wrote: Framemaker can take quite a while to do some things, so it's important to know the difference between a crash and a FrameMaker is not responding message. The latter means Wait until I complete this task. The former is accompanied by a crash message and exiting from

RE: Windows 7 + FrameMaker 11 = BOOM!

Cc: Davis, David; framers@lists.frameusers.com Subject: Re: Windows 7 + FrameMaker 11 = BOOM! 4 GB of RAM may be of no use to FrameMaker if it's the only application open, but if you have other applications open and you only have 4 GB, wouldn't those other application be competing for the same 4

Windows 7 + FrameMaker 11 = BOOM!

An HTML attachment was scrubbed... URL:

Windows 7 + FrameMaker 11 = BOOM!

We get crashes on FM10 pretty often when manipulating conditional text dialog boxes. Sometimes they crash "cleanly", but sometimes we don't get a crash message etc, FM just freezes. I left one overnight a while ago and it was still frozen the next morning. (We've tested FM11 and it looks like

Windows 7 + FrameMaker 11 = BOOM!

Craig Ede wrote: > > Framemaker can take quite a while to do some things, so it's important to know > the difference between a crash and a "FrameMaker is not responding" > message. The latter means "Wait until I complete this task." The former is > accompanied by a crash message and exiting from

Windows 7 + FrameMaker 11 = BOOM!

8 To: Fred Ridder Cc: Davis, David; framers at lists.frameusers.com Subject: Re: Windows 7 + FrameMaker 11 = BOOM! 4 GB of RAM may be of no use to FrameMaker if it's the only application open, but if you have other applications open and you only have 4 GB, wouldn't those other application be

Re: Windows 7 + FrameMaker 11 = BOOM!

I'd second the advice that anti-virus software is something to look for as a culprit for these crashes! (I must say that, in corporate network environments, I've had orders of magnitude greater losses in productivity from damned anti-virus software than from ever getting an actual virus :)

RE: Windows 7 + FrameMaker 11 = BOOM!

...@iinet.net.au, framers@lists.frameusers.com framers@lists.frameusers.com Subject: RE: Windows 7 + FrameMaker 11 = BOOM! Message-ID: bay171-w98706b7f8ec1559036865cba...@phx.gbl Content-Type: text/plain; charset=iso-8859-1 But the application is not the only thing using memory. Even if a 32-bit

RE: Windows 7 + FrameMaker 11 = BOOM!

...@lists.frameusers.com] On Behalf Of Ken Poshedly Sent: Thursday, August 08, 2013 11:54 AM To: FrameMaker Users List Subject: Windows 7 + FrameMaker 11 = BOOM! Due to the addition of 2 new contract writers and the replacement of the hard drive in an existing terminal in my department, we're now

RE: Windows 7 + FrameMaker 11 = BOOM!

@lists.frameusers.com Subject: RE: Windows 7 + FrameMaker 11 = BOOM! Fred, one of the most basic functions of an operating system is to be able to manage memory (without crashing!) :) Simply because applications might all want more memory on the go at one time than is physically available, should not mean

RE: Windows 7 + FrameMaker 11 = BOOM!

it is true that one of the most basic functions of an OS is memory management. I said nothing that disagrees with that. -Fred Ridder From: david.da...@invensys.com To: framers@lists.frameusers.com Date: Mon, 12 Aug 2013 04:29:32 -0500 Subject: RE: Windows 7 + FrameMaker 11 = BOOM! Fred, one

RE: Windows 7 + FrameMaker 11 = BOOM!

with the company's IT procurement folks. David -Original Message- From: Rick Quatro [mailto:r...@rickquatro.com] Sent: 13 August 2013 14:58 To: Davis, David; framers@lists.frameusers.com Subject: RE: Windows 7 + FrameMaker 11 = BOOM! You can disagree if you want, but those of us with heavy

RE: Windows 7 + FrameMaker 11 = BOOM!

Framemaker can take quite a while to do some things, so it's important to know the difference between a crash and a FrameMaker is not responding message. The latter means Wait until I complete this task. The former is accompanied by a crash message and exiting from FrameMaker. Very seldom do I see

Re: Windows 7 + FrameMaker 11 = BOOM!

We operate from network server drive, and have experienced the very same problems while using Win 7 FM 11. It isn't really a problem with FM, it's a server problem involving latency on the server. If you look at the resulting files after a crash you may see son with stable, apparently random

Windows 7 + FrameMaker 11 = BOOM!

at lists.frameusers.com Subject: RE: Windows 7 + FrameMaker 11 = BOOM! Fred, one of the most basic functions of an operating system is to be able to manage memory (without crashing!) :) Simply because applications might all want more memory on the go at one time than is physically available, should

Windows 7 + FrameMaker 11 = BOOM!

Of course it is true that one of the most basic functions of an OS is memory management. I said nothing that disagrees with that. -Fred Ridder > From: David.Davis at invensys.com > To: framers at lists.frameusers.com > Date: Mon, 12 Aug 2013 04:29:32 -0500 > Subject: RE: Windows 7

Windows 7 + FrameMaker 11 = BOOM!

to cut ice with the company's IT procurement folks. David -Original Message- From: Rick Quatro [mailto:r...@rickquatro.com] Sent: 13 August 2013 14:58 To: Davis, David; framers at lists.frameusers.com Subject: RE: Windows 7 + FrameMaker 11 = BOOM! You can disagree if you want, but t

Windows 7 + FrameMaker 11 = BOOM!

Framemaker can take quite a while to do some things, so it's important to know the difference between a crash and a "FrameMaker is not responding" message. The latter means "Wait until I complete this task." The former is accompanied by a crash message and exiting from FrameMaker. Very seldom do I

Windows 7 + FrameMaker 11 = BOOM!

We operate from network server drive, and have experienced the very same problems while using Win 7 FM 11. It isn't really a problem with FM, it's a server problem involving latency on the server. If you look at the resulting files after a crash you may see son with stable, apparently random

Windows 7 + FrameMaker 11 = BOOM!

I'd second the advice that anti-virus software is something to look for as a culprit for these crashes! (I must say that, in corporate network environments, I've had orders of magnitude greater losses in productivity from damned anti-virus software than from ever getting an actual virus :)

Windows 7 + FrameMaker 11 = BOOM!

To: Helen Borrie , "framers at lists.frameusers.com" Subject: RE: Windows 7 + FrameMaker 11 = BOOM! Message-ID: Content-Type: text/plain; charset="iso-8859-1" But the application is not the only thing using memory. Even if a 32-bit application can only address 4 GB,

Windows 7 + FrameMaker 11 = BOOM!

ameusers.com [mailto:framers-boun...@lists.frameusers.com] On Behalf Of Ken Poshedly Sent: Thursday, August 08, 2013 11:54 AM To: FrameMaker Users List Subject: Windows 7 + FrameMaker 11 = BOOM! Due to the addition of 2 new contract writers and the replacement of the hard drive in an existing te

Re: Windows 7 + FrameMaker 11 = BOOM!

e never saw a crash. But that was FMv5.5.CraigWin7, 8GBFrom: framers-boun...@lists.frameusers.com[mailto:framers-boun...@lists.frameusers.com] On Behalf Of John PosadaSent: Friday, August 09, 2013 3:40 PMTo: Ken PoshedlyCc: FrameUsers ListSubject: Re: Windows 7 + FrameMaker 11 = BOOM!Ive been on FM11 and W

Re: Windows 7 + FrameMaker 11 = BOOM!

I think it's fair to say that FrameMaker never crashes _for you_. However, given my (somewhat different) experience with the stability of FrameMaker 11, I'm sensitive about having our concerns dismissed. :-) Stability of FrameMaker seems to vary greatly depending on the source files being

Windows 7 + FrameMaker 11 = BOOM!

gt; >> >> On the SUN workstations we never saw a crash. But that was FMv5.5. >> >> >> >> Craig >> >> Win7, 8GB >> >> >> >> From: framers-bounces at lists.frameusers.com >> [mailto:framers-bounces at lists.frameuse

Windows 7 + FrameMaker 11 = BOOM!

I think it's fair to say that FrameMaker never crashes _for you_. However, given my (somewhat different) experience with the stability of FrameMaker 11, I'm sensitive about having our concerns dismissed. :-) Stability of FrameMaker seems to vary greatly depending on the source files being

Re: Windows 7 + FrameMaker 11 = BOOM!

Hi Ken, I have used FM11 unstructured on Win7 with files on the network since FM11 was released. I have no problems. Maybe your files are too big with the embedded ages? On Thursday, August 8, 2013, Ken Poshedly wrote: Due to the addition of 2 new contract writers and the replacement of the

a different experience RE: Windows 7 + FrameMaker 11 = BOOM!

...@lists.frameusers.com] On Behalf Of Ken Poshedly Sent: Thursday, August 08, 2013 10:54 AM To: FrameMaker Users List Subject: Windows 7 + FrameMaker 11 = BOOM! Due to the addition of 2 new contract writers and the replacement of the hard drive in an existing terminal in my department, we're now

RE: Windows 7 + FrameMaker 11 = BOOM!

Hi Ken, One option that you have is to put your files in a SVN repository. If you do this, then checked out files will be local to the person's computer and there's no issue with network latency etc. You can certainly do the check out to an external hard drive to if that's needed. Once the user

RE: Windows 7 + FrameMaker 11 = BOOM!

...@lists.frameusers.com [mailto:framers-boun...@lists.frameusers.com] On Behalf Of John Posada Sent: Friday, August 09, 2013 3:40 PM To: Ken Poshedly Cc: FrameUsers List Subject: Re: Windows 7 + FrameMaker 11 = BOOM! Ive been on FM11 and Win7 since maybe Feb and have not crashed once

Re: Windows 7 + FrameMaker 11 = BOOM!

, August 09, 2013 3:40 PM To: Ken Poshedly Cc: FrameUsers List Subject: Re: Windows 7 + FrameMaker 11 = BOOM! Ive been on FM11 and Win7 since maybe Feb and have not crashed once. ___ You are currently subscribed to framers as art.campb

Windows 7 + FrameMaker 11 = BOOM!

At 01:32 a.m. 10/08/2013, Rick Quatro wrote: > >Otherwise, make sure the writers have plenty of RAM. In my opinion, 8 GB is >the minimum. This may help with the performance problems. > More than 4 GB of RAM is of absolutely no use for running a 32-bit application, whether it be on a 32-bit or

Windows 7 + FrameMaker 11 = BOOM!

ramers-bounces at lists.frameusers.com] On Behalf Of John Posada > Sent: Friday, August 09, 2013 3:40 PM > To: Ken Poshedly > Cc: FrameUsers List > Subject: Re: Windows 7 + FrameMaker 11 = BOOM! > > > > Ive been on FM11 and Win7 since maybe Feb and have not crashed once.

RE: Windows 7 + FrameMaker 11 = BOOM!

contention for memory resources even if it can only access 1/2 or 1/3 of the total memory available to the OS. -Fred Ridder Date: Sat, 10 Aug 2013 06:23:55 +1200 To: framers@lists.frameusers.com From: hele...@iinet.net.au Subject: RE: Windows 7 + FrameMaker 11 = BOOM! At 01:32 a.m. 10/08

Re: Windows 7 + FrameMaker 11 = BOOM!

Ive been on FM11 and Win7 since maybe Feb and have not crashed once. On Aug 9, 2013 12:50 AM, Ken Poshedly poshe...@bellsouth.net wrote: Due to the addition of 2 new contract writers and the replacement of the hard drive in an existing terminal in my department, we're now stuck with Windows 7

RE: Windows 7 + FrameMaker 11 = BOOM!

Poshedly Sent: Thursday, August 08, 2013 8:54 AM To: FrameMaker Users List Subject: Windows 7 + FrameMaker 11 = BOOM! Due to the addition of 2 new contract writers and the replacement of the hard drive in an existing terminal in my department, we're now stuck with Windows 7 and FrameMaker 11 on those

Windows 7 + FrameMaker 11 = BOOM!

+ FrameMaker 11 = BOOM! Due to the addition of 2 new contract writers and the replacement of the hard drive in an existing terminal in my department, we're now stuck with Windows 7 and FrameMaker 11 on those three platforms for the past month or so. And it's been nothing but problems ever since

Windows 7 + FrameMaker 11 = BOOM!

t lists.frameusers.com > [mailto:framers-bounces at lists.frameusers.com] On Behalf Of Ken Poshedly > Sent: August-08-13 11:54 AM > To: FrameMaker Users List > Subject: Windows 7 + FrameMaker 11 = BOOM! > > > > Due to the addition of 2 new contract writers and the replacem

Windows 7 + FrameMaker 11 = BOOM!

nd that you need to >> implement some sort of source control to check out/in files from your server >> to your local drive. >> >> >> >> From: framers-bounces at lists.frameusers.com >> [mailto:framers-bounces at lists.frameusers.com] On Behalf Of Ken Poshedly

Windows 7 + FrameMaker 11 = BOOM!

users.com] On Behalf Of Ken Poshedly Sent: Thursday, August 08, 2013 11:54 AM To: FrameMaker Users List Subject: Windows 7 + FrameMaker 11 = BOOM! Due to the addition of 2 new contract writers and the replacement of the hard drive in an existing terminal in my department, we're now stuck with Wind

Windows 7 + FrameMaker 11 = BOOM!

On Fri, 9 Aug 2013 09:32:32 -0400, "Rick Quatro" wrote: >I would be tempted to do an informal "downgrade" and have all of the writers >use FrameMaker 8. I am running FrameMaker 8 with Windows 7 with no problems. >In my opinion, FrameMaker 8 is still the "gold" version of FrameMaker as far >as

Windows 7 + FrameMaker 11 = BOOM!

-Original Message- From: framers-boun...@lists.frameusers.com [mailto:framers-bounces at lists.frameusers.com] On Behalf Of Helen Borrie Sent: Friday, August 09, 2013 2:24 PM To: 'FrameMaker Users List' Subject: RE: Windows 7 + FrameMaker 11 = BOOM! At 01:32 a.m. 10/08/2013, Rick Quatro wrote

Windows 7 + FrameMaker 11 = BOOM!

contention for memory resources even if it can only access 1/2 or 1/3 of the total memory available to the OS. -Fred Ridder > Date: Sat, 10 Aug 2013 06:23:55 +1200 > To: framers at lists.frameusers.com > From: helebor at iinet.net.au > Subject: RE: Windows 7 + FrameMaker 11 = BOOM

Windows 7 + FrameMaker 11 = BOOM!

Ive been on FM11 and Win7 since maybe Feb and have not crashed once. On Aug 9, 2013 12:50 AM, "Ken Poshedly" wrote: > Due to the addition of 2 new contract writers and the replacement of the > hard drive in an existing terminal in my department, we're now stuck with > Windows 7 and FrameMaker 11

Windows 7 + FrameMaker 11 = BOOM!

ists.frameusers.com] On Behalf Of Ken Poshedly Sent: Thursday, August 08, 2013 8:54 AM To: FrameMaker Users List Subject: Windows 7 + FrameMaker 11 = BOOM! Due to the addition of 2 new contract writers and the replacement of the hard drive in an existing terminal in my department, we're now stuck wit

Windows 7 + FrameMaker 11 = BOOM!

Hi Ken, I have used FM11 unstructured on Win7 with files on the network since FM11 was released. I have no problems. Maybe your files are too big with the embedded ages? On Thursday, August 8, 2013, Ken Poshedly wrote: > Due to the addition of 2 new contract writers and the replacement of the >

a different experience RE: Windows 7 + FrameMaker 11 = BOOM!

at lists.frameusers.com] On Behalf Of Ken Poshedly Sent: Thursday, August 08, 2013 10:54 AM To: FrameMaker Users List Subject: Windows 7 + FrameMaker 11 = BOOM! Due to the addition of 2 new contract writers and the replacement of the hard drive in an existing terminal in my department, we're now

Windows 7 + FrameMaker 11 = BOOM!

Hi Ken, One option that you have is to put your files in a SVN repository. If you do this, then checked out files will be local to the person's computer and there's no issue with network latency etc. You can certainly do the check out to an external hard drive to if that's needed. Once the user

Windows 7 + FrameMaker 11 = BOOM!

...@lists.frameusers.com [mailto:framers-bounces at lists.frameusers.com] On Behalf Of John Posada Sent: Friday, August 09, 2013 3:40 PM To: Ken Poshedly Cc: FrameUsers List Subject: Re: Windows 7 + FrameMaker 11 = BOOM! Ive been on FM11 and Win7 since maybe Feb and have not crashed once. -- next part

Windows 7 + FrameMaker 11 = BOOM!

Due to the addition of 2 new contract writers and the replacement of the hard drive in an existing terminal in my department, we're now stuck with Windows 7 and FrameMaker 11 on those three platforms for the past month or so. And it's been nothing but problems ever since, with unpredictable

Windows 7 + FrameMaker 11 = BOOM!

Due to the addition of 2 new contract writers and the replacement of the hard drive in an existing terminal in my department, we're now stuck with Windows 7 and FrameMaker 11 on those three platforms for the past month or so. And it's been nothing but problems ever since, with unpredictable