RE: Frame Crash - Internal Error: 6004, 6016882, 7541026, 0

[Dov Isaacs <isaacs@xxxxxxxxx>]

And I will add very specifically that you should NEVER,
repeat NEVER do an UPGRADE from any version of Windows to
either Windows 2000 or Windows XP. You must do a "clean
install" which implies that you backup your data, delete the
existing partitions containing the operating system and
application programs, and then do a installation of the
operating system and applications on a newly formatted
partition.

Contrary to what Microsoft may lead you to believe, their
"upgrader" from other versions of Windows to Windows 2000
or Windows XP just does not adequately handle issues such
as ATM, fonts, drivers, Acrobat, registries, and other such
minor conveniences. (The upgrader from Windows 2000 to XP
may be the only exception since XP is basically 2000 under
the hood with a bunch of UI changes.)

        - Dov


At 2/14/2002 09:34 AM, Thomas Neuburger wrote:
>Hi Karl,
>
>I'll second Art's comment and lay the blame on the OS. The key to your post is "Win98". You can't run Win98 for extended periods without rebooting, especially if you are doing lots of work. And the lower your available disk space, the more frequent the problems.
>
>Software solutions:
>
>o  Upgrade to Win2k, as suggested below. It's NT-based and more bullet-proof.
>
>o  Delete files from disk. You want the highest possible ratio of free disk space to used disk space. (I don't know why the ratio matters if the disk is large, but in my experience it does.)
>
>o  Don't run high mem programs when running Frame (I know that's not always possible, but try.) Running Frame, Eudora, and Netscape together. for example, for long periods will eventually crash the OS.
>
>o  Close the programs named above and reopen them periodically. This "tends" to free resources.
>
>o  Reboot frequently.
>
>(Did I mention upgrading from Win98? That's the real solution.)
>
>
>Good luck,
>
>Tom Neuburger

*

>Art Campbell wrote:
>
>>I'd put money on a FM and/or MS memory leak eventually drawing down your
>>pool
>>of available RAM... coupled with using a less-than-robust operating
>>system.
>>
>>Try to bump your RAM as high as possible, and put your (enlarged) swap
>>file on
>>a drive other than the FM executable. And maybe migrate to Windows 2K or
>>XP Pro
>>if you're feeling adventurous.
>>
>>
>>Art Campbell
>>Manager of Communications
>>Sandburst Corporation
>>600 Federal Street
>>Andover, MA 01810
>>978 689-1673

*

>>-----Original Message-----
>>From: kkuessel@cymer.com [mailto:kkuessel@cymer.com]
>>Sent: Thursday, February 14, 2002 11:18 AM
>>To: Framers List
>>Subject: Frame Crash - Internal Error: 6004, 6016882, 7541026, 0
>>
>>
>>Fellow Frame Users,
>>
>>For several years, I have endured numerous Frame crashes when working in
>>my books.  The crash usually occurs after I have opened and closed
>>numerous files or after doing a Generate update.  Usually, the crash
>>occurs when I save or close the book.
>>
>>The message Frame: Internal Error: 6004, 6016882, 7541026, 0
>>
>>System Information
>>FrameMaker 6.0.0 for Intel
>>Build: 6.0p405
>>Window System: MS Windows
>>Operating System: Windows 98 (major.minor.build: 4.10.2222  A )
>>
>>Our IT group doesn't have a clue.
>>Several years ago, I contacted Adobe. They assigned a case number - I
>>never heard back from them.
>>
>>Any ideas?
>>
>>Karl Kuessel


** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **