This message was from GWSTEVE@AOL.COM to ALL,
originally in conference comp.os.ge
and was forwarded to you by ANNE PAGE.
@SUBJECT:Re: NDO printing problems (was Re: Goewrite to Geo
Message-ID: 
Newsgroups: comp.os.geos
Organization: AOL http://www.aol.com
There have been a few reports about printing troubles with
New Deal Office posted to these boards. The common thread
so far seems to be "I have a file that will print in Ensemble 2.01,
but it won't print in New Deal Office."
The system software is different between Ensemble 2.01 (based
on Geos 2.01) and New Deal Office (based on Geos 2.1). As the
system software was upgraded, changes were introduced that could
affect performance and could affect how the software interacts
with your hardware. Printing might be affected positively or negatively
depending on your particular hardware and configuration.
Before we conclude that there's a "problem" in New Deal Office, let's
try to determine if we're really talking about oranges, apples, or
bananas.
Check to see if you changed the LPT port setting from 7 to BIOS in
Ensemble. If so, or if not, make the change in New Deal Office. If that
doesn't help, try changing to the DOS setting in New Deal Office's
Preferences, Computer. It's possible that the new system software
might even use a different optimal setting than whatever you used
to use in Ensemble.
If you're running from Windows 95, check all the settings there
for each version of Geos.
"Print after last page is spooled" is often recommended. I find that
I get better results from all versions of Geos if I choose to NOT
"Spool MS DOS print jobs." And a change in those settings might
mean that a different choice for the LPT port setting in Geos
might be optimal. Unfortunately, it's mostly trial and error to
find the best setting.
Re the settings in Preferences, Geos... I believe it's optimal to
keep Page Size at 2048.. but raise Swap File Size to 8 or 10mb.
While not normally recommended, it is possible to raise handles
to as many as 3700 by editing the GEOS.INI file. Don't go higher
than that, and do return to 3500 if you notice any new performance
problems.
Optmize your conventional memory. Load your drivers and TSRs
high if you can. Don't use expanded memory unless you need it
for certain DOS apps.
If you're using Windows 95, conventional memory optimization is
still an issue, and one that is often overlooked. MS DOS 7 provides
some new things you can do to maximize your conventional
memory for DOS applications. BUFFERSHIGH and FILESHIGH,
for example. You can now put your SET statements in the config.sys
file instead of the autoexec.bat. If you don't need memory managers
or CD drivers or TSRs at the DOS prompt, you can remove them from
your startup files and configure the ones you need specifically for each
DOS application. On some systems, you can add the line
"LocalLoadHigh=1" to the [386Enh] section of the system.ini file
to gain up to 9k or so of conventional memory.
Steve
 * SLMR 2.1a * One fact can RUIN a good argument.
--- QScan/PCB v1.16b / 01-0075
---------------