Re: FM4 (Win) and GPFs

Subject: Re: FM4 (Win) and GPFs
From: Sbbrown <sbbrown -at- NANDO -dot- NET>
Date: Mon, 1 May 1995 10:21:37 -0400

I am currently using FM4 for Windows and have problems with graphics
and GPFs. I have done all of the things FM suggests for importing
my graphics, and I am stillhaving problems. I get a GPF, sometimes,
when I pass over a graphic in teh file, and sometimes I don't. When
I do GPF, the strange thing is that I can cancel out of it and the
app doesn't quit. The graphic is corrupt and I have to replace it, but
my file is ok otherwise.

Ever seen thisone before?

Any help is much appreciated!!

Sandy Brown
sbbrown -at- nando -dot- net

On Sun, 23 Apr 1995, Grant Hogarth wrote:

> Charles Webster <cwebster -at- IX -dot- NETCOM -dot- COM> posts:

> >Third:
> >What are people's experiences wrt the stability of FrameMaker 4.0 for
> Windows?
> I have been using FM3/4 for Win since before it first shipped.
> (Yes, I used to work there <g>)
> The things that I have noticed that will increase the number/frequency of
> GPFs are:
> Number of fonts loaded, number of printers loaded, number and type of TSRs
> loaded, and the settings in your EMM386.exe line. Also the *order* in which
> things are loaded may make a difference.

> Suggestions:
> - Keep fonts to a minimum. Use FontMaster, FontSpec, or some
> other font manager to load just the fonts you need at the time.
> - Load only the printers you need (especially if you have printers that
> require different drivers.)
> - Load only those TSRs that you need. Network stuff should be loaded
> early... not sure why, just seems to work better for me. YMMMV
> - In config.sys set the line cointaining EMM386. to use NOEMS
> (unless you *have* to have it) and do not use the RAM statement.
> Further, try the following:
> 1) disable EMM386 (and networks), 2) reboot, 3) At the DOS prompt,
> type: "debug" (no quotes)and press return, then type "d c800" (zeroes).
> If the display shows 00(zeros) or FFs, do nothing. If it shows *ANY*
> other characters, note the lines that they occur in, (at left of screen).
> repeat this for cc00, d000, d800, dc00, e000, e800, ec00, f000, f800, &
> fc00.
> When you are done, type "q" to quit DEBUG.
> Take the line numbers you have noted and add them to the EMM386 line
> in config.sys. It will look similar to the following:
> Device=c:\dos\emm386.exe NOEMS x=c800-c8ff, x=dcbb-dfff
> Also, if you have run memmaker, it may show i=b000-b700...this is the
> monochrome video space...excluding it as well may reduce your
> problem rate.
> Once you have done this, re-enable anything you disabled, and you
> should be fine!
> NOTE: If you make any changes, and you *have* run
> memmaker before, you must run it again, as the settings may be invalid.
> This procedure excludes any conflict areas between any I/O cards
> and hardware device drivers (such as SCSI cards) and EMM386.
> - In System.inin, set EMMExclude=mmmm-nnnn (to match the setting
> in config.sys), NoEmmDriver=ON, and PageBuffers= at least 32

> Hope this helps.

> Grant Hogarth
> Tech Services Group Manager,
> Onyx Graphics Corp.

> Backup not found: (A)bort, (R)etry, (G)et a beer?

Previous by Author: History of DTP
Next by Author: mass storage
Previous by Thread: Re: off topic... what's the meaning of this expression?
Next by Thread: Re: FM4 (Win) and GPFs

What this post helpful? Share it with friends and colleagues:

Sponsored Ads