Simtel MSDOS 1992 June/SIMTEL_0692.cdr/msdos/ventura/qa_3.arc/QA-3.TXT

Text File | 1988-05-02 | 51KB | 1,222 lines

@CHAPTER = Chapter 2: Hardware

@MENU = Monitors and Graphics boards

@QUESTION = Which <$IGraphics boards>graphics boards does Ventura
Publisher support?

@VERPATCH = 1.0, 1.1(unpatched), 1.1(patch 1 & 2)

@ANSWER = Version 1.0: IBM Color Graphics <169>CGA<170> (640x200),
IBM Enhanced Graphics <169>EGA<170> (640x350), or Hercules Monochrome
(720x350) boards, Xerox 6060 Computer High Resolution Card (640x400).
It will also support graphics on the Xerox Monochrome full-page display.
Additional for Version 1.1(unpatched): IBM PS/2 <169>VGA<170> (640x480),
IBM 3270 monochrome (640x350). Additional for Version 1.1(patch 1
&2): IBM PS/2 Model 30 only, MCGA (640x480).

@QUESTION = Which Full P<$IFull Page Displays>age Displays does Ventura
support?

@VERPATCH = All

@ANSWER = Ventura will support the Xerox full page display, the MDS
Genius, the Wyse WY-700 and the Hercules monochrome graphics card
with appropriate full page monitor. Other oversize monitors are also
being marketed for use with Ventura, but those come with their own
drivers which are supported by the monitor manufacturer, not by Xerox.

@QUESTION = I am trying to get a Sigm<$ISigma Designs Color 400>a
Designs Color 400 graphics board to work with Ventura.  It works with
Gem and when I modify the GEMSETUP.TXT file on Diskette #3 to appear
exactly as it does on the GEMSETUP.TXT file provided with GEM, it
does not work.  Why not?

@VERPATCH = All

@ANSWER = GEMSETUP.TXT is a file that is read by Ventura during installation.  Changing
this file does not guarantee that the device driver for the device
is compatible with Ventura.  Ventura Software is currently working
with a number of manufacturers of graphics boards, screen displays
and printers who all want to be compatible with Ventura Publisher.  It
might be appropriate to have the user check with the manufacturer
to find out the status of his device if it is not on the current list
of Ventura supported products.

@QUESTION = Which monitor selection is used for the Compaq Por<$ICompaq
Computer>table?

@VERPATCH = All

@ANSWER = Select A the IBM Color Card.

@QUESTION = Does <$IMonitors - 19 inch>Ventura support any 19 inch
monitors?

@VERPATCH = All

@ANSWER = Ventura has been working with three vendors supplying them
with the information they need to write their own drivers to make
them compatible with Ventura.  They are Conographic, DBM and Sigma
Graphics. Support of these drivers is through the monitor vendors.

@QUESTION = <$IAMDEC 1280 Monitor>I am using an AMDEC 1280 monitor.  When
I move the mouse across the screen it leaves a "trail" or smear on
the screen.  Can you tell me what is causing this?

@VERPATCH = All

@ANSWER = We have been told, by a customer who called AMDEC, that
AMDEC claims that this is a characteristic of the monitor.

@QUESTION = I purchased a new enhanced graphics card for my PC <$IMicrosoft
Bus mouse - not working>and now my Microsoft Bus mouse is not working.  Why?

@VERPATCH = All

@ANSWER = You will need to check the mouse controller card and possibly
change the jumper settings or the DOS interrupt levels to correspond
to the type of graphics card and monitor you are now using.  Refer
to you Microsoft mouse user's guide or your dealer for the correct
settings.

@QUESTION = Does the 3270 driver<$I3270 driver> in Ventura include
the APA (all points addressable) capability?

@VERPATCH = 1.1(all)

@ANSWER = Yes.

@QUESTION = What large<$IMonitors - large screen> screen monitors<$ILarge-screen
monitors> does Ventura support and do they have their own cards?

@VERPATCH = 1.0, 1.1(all)

@ANSWER = Ventura provides drivers for the Xerox Full Page Display,
the Wyse 700 and the MDS Genius displays.  Each of these comes with
its own controller card.  Other large screens that may be used with
Ventura include the Viking Moniterm monitor, the Sigma Designs LaserView
monitor and the Taxan Crystal View monitor. Screen drivers for Ventura
Publisher are available from the manufacturers.  Each of these monitors
comes with it's own controller card.

@QUESTION = Ventura shows up in reverse video on my<$IReverse video
- IBM PS/2 Mod30> PS/2 Model 30 with MCGA monitor.

@VERPATCH = 1.1(unpatched), 1.1(patch 1), 1.1(patch 2)

@ANSWER = Customer using unpatched 1.1 (4/10/87) on IBM PS/2 Model
30 gets reverse video--white on black instead of black on white. This
is a known bug in unpatched 1.1, which is supposed to be corrected
by Patch 1 (7/2/87).

@ANSWER2 = However, if Patch 1 is installed for a COLOR screen for
the PS/2 Model 30, and if the 3-1/2" disk set is used, the problem
remains. It turns out that the fix was incorporated improperly on
the 3-1/2" disks set, but was correct on the 5-1/4" disks.

@ANSWER2 = This oversight has been corrected on Patch 2 (2/5/88).

@QUESTION = Lockups<$ILockups - oversize monitor> are experienced
when using an add-on oversize <$IMonitor, oversize - lockups> monitor,
such as the Sigma Designs Laserview.

@VERPATCH = 1.1(all)

@ANSWER = This problem may develop right away, or it may appear only
after adding screen fonts or otherwise altering memory usage.

@ANSWER2 = Make sure that the ONLY screen drivers present are those
for the monitor in use.

@ANSWER2 = When such a monitor is installed, Ventura must first be
installed for some standard monitor choice. (The vendor for the add-on
monitor may specify which to use.) Then, after Ventura is installed,
a second installation program must be run to add the drivers for the
oversize monitor. The monitor installation program may not delete
the first set of drivers. If they are still present, it can cause
problems when Ventura is run.

@ANSWER2 = Check not only CONFIG.SYS but also the \VENTURA directory
for the original drivers. If they are present, delete them and cold
boot.

@QUESTION = The customer had installed a MDS Genius Full<$IMonitor
- MDS Genius> Page Display<$IMonitor - losing full page mode> which
worked in full page mode within Ventura.  When Ventura was exited,
it lost the full page mode.<$IMDS Genius - losing full page mode>

@VERPATCH = 1.1(all)

@ANSWER = The user needs VHR MDS as the last line of the VP.BAT file
to retain full page mode after exiting Ventura.

@PAGE END =

@MENU = Mice

@QUESTION = Can Ventura be operated without a <$IMouse Requirement>mouse?

@VERPATCH = All

@ANSWER = It is possible, but not recommended. The software is designed
to take full advantage of mouse mobility (drop down menus and <169>point
and drag<170> graphics and frame manipulation). The software will
function, however, using the cursor keys to move about the screen.

@QUESTION = I am trying to load Ventura with a <$IMouse - Logitech
LogiMouse><$ILogiMouse>LogiMouse but am having difficulties.  Why
doesn't the mouse respond?

@VERPATCH = All

@ANSWER = The LogiMouse can emulate several different mouse devices.  Make
sure that you understand which mouse selection requires a mouse driver
in the autoexec.bat file.  The Logimouse works without a driver in
emulating certain mice and with a driver when emulating others.  It
could be that you have selected a mouse which does not require a driver
(PC Mouse) and have a driver installed on your system.  If you are
sure your selection is correct, try powering the system off immediately
after finishing the VPPREP program and then turning it back on and
bringing up Ventura. The installation which is usually most successful
in Ventura is to install as choice "B" (PC Mouse) and put no mouse
drivers at all in CONFIG.SYS or AUTOEXEC.BAT.

@QUESTION = I installed <$ILogiMouse>Ventura with a LOGIMOUSE using
selection B for PC Mouse (which LOGIMOUSE emulates) and it worked
fine.  Today I installed PC Paintbrush and installed for a LOGIMOUSE
and PC Paintbursh works fine, but now the mouse does not work in Ventura.
<$IMouse - LogiMouse> Why not?

@VERPATCH = All

@ANSWER = LOGIMOUSE is unique in that it can emulate several of the
popular mouse protocols.  This creates a problem when you have installed
one software package in which the LOGIMOUSE emulates one type of mouse
and another software package in which it emulates another.  When installed
as a LOGIMOUSE using the driver which comes with the mouse or using
the LOGIMOUSE selection in PC Paintbrush, the mouse will emulate a
Microsoft serial mouse.  This is why you had problems with Ventura.  The
"Microsoft" mouse driver was still loaded when you brought up Ventura
creating a conflict since Ventura was expecting a "PC Mouse" protocol.  To
correct this problem, either re-install Ventura and select the Microsoft
serial mouse, or re-install PC Paintbrush and select the PC Mouse
or PC Mouse compatible selection (Summa Mouse will work).

@QUESTION = I bought a Summa Mouse, which Ventura says it <$ISumma
Mouse>supports, and it does not work on my system.  Why not?

@VERPATCH = All

@ANSWER = It is our understanding that Summa has introduced a new
model of Mouse, the 420 which utilizes a different driver than the
original Summa Mouse.  Contact the manufacturer and ask them to send
you a driver which will allow you to simulate operation of the original
model.

@QUESTION = Why is my <$IMicrosoft serial mouse - trail>Microsoft
serial mouse leaving a trail of dots across the screen on my MDS Genius
monitor?

@VERPATCH = All

@ANSWER = Check your hardware.  Make sure all jumpers and switches
are set correctly.  Typically this problem is a result of wrong switch
and or jumper settings.

@QUESTION = I have tried several times to get my LogiTech mouse to
<$ILogitech mouse>ork with Ventura.  I have installed as a PC Mouse
and a Microsoft Serial Mouse but it will not respond.

@VERPATCH = All

@ANSWER = One customer reported that he had gotten the following information
from LogiTech on configuring the LogiMouse:

@ANSWER2 = Use CLICK.SRC which comes packaged with your LogiMouse.

@ANSWER2 = Insert a line for Ventura as follows:  "VP 1200 150 5B(tab
arrow) Publisher".

@ANSWER2 = Modify the autoexec.bat file to include the following:

@ANSWER2 = MOUSE 2

@ANSWER2 = MENU

@ANSWER2 = CLICK

@QUESTION = Customer installed Ventura on a Tandy TX with CGA display
and Microsoft<$IMS:Buss Mouse on Tandy TX> Buss Mouse. Correctly selected
"C" for the mouse installation, and had proper mouse drivers installed.
However, the mouse did not respond in Ventura.

@VERPATCH = All

@ANSWER = The Tandy TX is a pseudo-XT clone, with an XT-type buss
but 80286 processor. It turned out that the interrupt had to be changed
from 2 to 3, after which Ventura worked fine and other programs continued
to also work fine with the mouse.

@QUESTION = When moving a PC Mouse<$IPC Mouse - jerky> around on its
pad, the movement<$IMouse - jerky> in Ventura is jerky.

@VERPATCH = All

@ANSWER = Turn the pad 90 degrees and try it. Optical mouse pads often
have two different colors of lines.

@QUESTION = My new Microsoft serial<$IMS:Serial mouse - with IBM PS/2>
mouse, with the special adapter that plugs into a special round "mouse"
port on the back of my PS/2, is not working with Ventura.

@VERPATCH = 1.1(all)

@ANSWER = It has been found in several cases that the mouse wouldn't
work if it was installed the normal way in Ventura (choice "D--Microsoft
Serial Mouse"). Installing it as "C--Buss Mouse" made it work, as
follows:

@ANSWER2 = 1) Install in Ventura as "C--Buss Mouse."

@ANSWER2 = 2) Be sure the proper version of "MOUSE.COM" is invoked
before loading Ventura.

@ANSWER2 = 3) If entering Ventura after using other software, a COLD
boot may be necessary.

@PAGE END =

@MENU = Scanners

@QUESTION = Does Ventura support the Dat<$IDatacopy Scanner>acopy
sca<$IScanners>nner?

@VERPATCH = All

@ANSWER = Ventura supports two image formats, GEM and PC Paintbrush.  If
the scanner can output to one of these formats it does not make any
difference to Ventura which brand it is.

@QUESTION = Does <$IScanners>Ventura support any other scanners beside
the <$IMicrotek scanner>Microtek and <$IDest scanner>Dest scanners?

@VERPATCH = All

@ANSWER = Ventura does not care which scanner created the image.  What
matters is the file format.  Any scanner which creates, or can convert
to GEM Paint (Digital Research), PC Paintbrush or PC Paintbrush +
(Z-Soft) format can be used with Ventura Publisher.  the list of such
scanners will grow as more products come on the market.

@QUESTION = Is the Xerox <$IXerox full page display/Microtek scanner>full
page display compatible with the <$IMicrotek scanner/Xerox full page
display>Microtek scanner and GEM software?

@VERPATCH = All

@ANSWER = Yes and No.  There are no screen drivers written to drive
the full page display.  When installing the Microtek software use
the CGA option which will utilize the upper third of the full page
screen.  The resolution will not be the same quality as Ventura but
you will be able to drive the scanner.

@PAGE END =

@MENU = Compatibility and Miscellaneous

@QUESTION = Can a RAM Disk or ex<$IExtended Memory>panded memory allow
me to manipulate larger documents than with a 640K machine?

@VERPATCH = All; related improvement in 1.1(all)

@ANSWER = No.  Ventura currently addresses 640K of memory.  Additional
memory will not enable you to access larger documents at this time.
However, Version 1.1 does allow use of a RAM disk to speed up handling
of large text files (Reference Guide p. 2-8).

@QUESTION = Does clock spe<$IClock Speed>ed determine whether a computer
is compatible with Ventura?

@VERPATCH = All

@ANSWER = Clock speed determines how fast a processor will execute
instructions.  It has no direct bearing on compatibility with Ventura.  Obviously,
the faster the computer executes instructions the faster Ventura will
run.

@QUESTION = Does Ventura work on a ne<$INetworks>twork?

@VERPATCH = All

@ANSWER = No.  Ventura is not currently network compatible and is
not licensed to run in that environment.  It is possible to utilize
Ventura on a PC that is tied to a network, but the software and all
related files must reside on the PC's own local hard disk. Printing
from Ventura over some networks is successful, provided the presence
of the network software in RAM does not use up too much memory or
otherwise interfere with Ventura.

@QUESTION = I am having trouble configuring a printer using Ventura
on a 6<$IXerox 6085>085 workstation.  Can you help?

@VERPATCH = All

@ANSWER = Ventura is not currently supported on the 6085 workstation.

@QUESTION = Can Ventura run on an <$IIBM 3270 PC>IBM 3270 PC?

@VERPATCH = 1.0 limitation--fixed in 1.1(all)

@ANSWER = Not in Version 1.0.  The 3270 PC is supported in Version
1.1.

@QUESTION = I have a 256K <$IMemory RAM vs Disk>AT&T 6300 with a 20MG
hard card.  Can't I use some of the memory from the hard card to configure
a enough memory to run Ventura.

@VERPATCH = All

@ANSWER = There is a difference between processor memory and disk
storage memory.  Ventura requires 512K of processor memory.  Ventura's
speed is a direct result of loading the application directly into
processor memory.  Using disk storage, even if it were possible, would
produce unsatisfactory results due to the difference in response time
of the disk itself as opposed to the almost instantaneous response
of Random Access Memory used by the processor.

@QUESTION = What are the <$IEquipment Requirements>equipment requirements
for Ventura Publisher?

@VERPATCH = 1.0, 1.1(all)

@ANSWER = Xerox Ventura Publisher requires an IBM PC XT, AT or compatible
with hard disk, 512K RAM (640K strongly recommended for Version 1.1),
graphics board and display, mouse, and compatible printer.  It also
supports the Xerox full page display for PC's.

@QUESTION = Are the <$IIBM compatibles>IBM <169>compatibles<170> absolutely
compatible with Ventura Publisher?

@VERPATCH = 1.0, 1.1(all)

@ANSWER = Compatiblity with any <169>clone<170> cannot be guaranteed.
However, Ventura Publisher Version 1.0 has been tested and verified
to work on a wide variety of equipment, such as the Compaq Deskpro,
Compaq Deskpro 286, Compaq Portable, HP Vectra, Xerox 6065, and the
AT&T 6300. In addition, Ventura Version 1.1(all) will run on the IBM
PS/2 and the IBM 3270.

@QUESTION = Do I need to <$IStandard drivers>purchase printer drivers,
fonts, or other software?

@VERPATCH = All

@ANSWER = No.  Ventura Publisher comes complete with drivers and basic
fonts for all printers and graphics displays listed.

@QUESTION = What are the resolutions of the different <$IPrinter resolution>printers,
both for text and for graphics?

@VERPATCH = All

@ANSWER = All laser printers are supported at full 300 dots per inch
resolution for both text and graphics, except for the HP Laserjet,
which is 300 dpi for text, but only 75 dpi for graphics.  With the
Xerox 4045 Laser, the size of the graphic which can be printed is
dependent upon the amount of memory resident in the 4045 and also
upon the level of the electronics firmware. (Firmware 2.1.1 will allow
up to 512K of memory in the 4045, while firmware 3.1.1 will allow
up to 1.5Mb of printer memory to be installed.)  Epson dot matrix
resolution is 120x140 dots per inch.  Xerox 4020 ink jet color resolution
is 120 dots per inch.

@QUESTION = Whenever the "Pause" key on an enhanced keyboard<$ILockup
- enhanced keyboard> is<$IEnhanced keyboard - lockup> struck, Ventura
appears to lock up. The mouse will not move and the keyboard is inoperative.

@VERPATCH = 1.1(all)

@ANSWER = Striking either "Delete" key will unlock the screen.

@PAGE END =





@CENTER = (This page intentionally left blank.)

@CHAPTER = Chapter 3: Printers

@MENU = AST Turbo Laser

@QUESTION = Is the<$IAST Turbo Laser> AST Turbo Laser compatible with
Ventura?

@VERPATCH = 1.0 limitation--fixed in 1.1(all)

@ANSWER = There are now three versions of the Turbo Laser in the field.
(1) The original Turbo Laser, which has its own adapter card with
imaging memory on it, is compatible with Ventura Version 1.1 but not
directly with 1.0.  Drivers were available from AST to support the
Turbo Laser in Version 1.0. (2) Turbo Laser EL: emulates HP LaserJet
Plus. Install in Ventura as HP LaserJet Plus (not Turbo Laser). (3)
Turbo Laser PS: PostScript only. Install in Ventura as PostScript
(not Turbo Laser).

@QUESTION = I have a document that printed in 10 minutes with Version
1.0 that now takes 16 minutes in Version 1.1.  Why?

@VERPATCH = 1.0, 1.1(all)

@ANSWER = Ventura is managing the fonts differently in Version 1.1
and that could account for the difference in speed.<$IAST Turbo -
slow printing> Another factor is the choice of printer port. The Turbo
Laser card takes over a printer port, and the speed of printing varies
with the port chosen; if a different port is chosen when installing
1.1 than had been used in 1.0, the print speed could be altered. According
to AST, COM2: gives the fastest printing.

@QUESTION = Why is my AST<$IAST TurboLaser - slow printing> TurboLaser
<$IAST TurboLaser - port choice>taking 1.5 hours to print 11 lines
on a page?

@VERPATCH = 1.1(all)

@ANSWER = Even AST does not know why but the best print speed is obtained
by installing to COM2: as our documentation indicates.  This particular
customer indicated the system used to respond faster.  When his CONFIG.SYS
file was evaluated we found that installation of a new software package
had modified (deleted) his files and buffers statement.  Revising
the CONFIG.SYS file allowed &BOOK-P1.CHP (page 1) to print out in
its standard time of about 3 minutes.

@QUESTION = AST Turbo laser<$IAST Turbo - blank pages or garbage>
would not print using standard Ventura set up.  Muliple Blank Pages
or Pages with garbage in one corner.

@VERPATCH = 1.1(all)

@ANSWER = Big news in the AST Arena.

@ANSWER2 = 1) This customer had down level AST<$IAST Turbo - software
level> software Version 1.02.  AST committed to send them the update
to current level 1.21G.

@ANSWER2 = 2) AST no longer sells the <$IAST Turbo - versions>version
of the AST TURBO LASER directly supported by Ventura Publisher.  Two
version and an upgrade kit are now available to the public.  This
was done to reduce the cost of the initial system.

@ANSWER2 = Version 1 - AST Turbo<$IAST Turbo EL - HP emulation> Laser
EL - Comes with 512k memory and Two Software printer<$IHP emulation
- AST Turbo EL> emulation drivers. ASTJEL.LNG = HP Laser Jet Plus
emulation and ASTDEL.LNG = Diablo 630 daisywheel emulation.

@ANSWER2 = EL Language<$IAST Turbo - upgrade kit> Upgrade Kit - $995.00
1.5 MB upgrades the printer to 2 Meg and supplies the ASTLASER.LNG
driver for Ventura.  Also, supplies an extended character set driver
for Diablo emulation as well as EPSON, and the HPGL plotter language.

@ANSWER2 = Version 2 - AST Turbo Laser<$IAST Turbo PS - PostScript>
PS - Postscript only printer.  Will have to be driven by our PostScript<$IPostScript
- AST Turbo PS> driver, not the AST driver.

@PAGE END =

@MENU = Cordata

@QUESTION = Which Cordata printer is Ventura compatible with?

@ANSWER = The LP300X.

@QUESTION = I am getting a garbled<$ICordata - garbled line at top>
line at the top of each page whenever I print to my Cordata printer,
which is installed with two monitors--EGA and LaserView.

@VERPATCH = 1.1(all)

@ANSWER = The hardware configuration for this system included a 2-monitor
setup, creating an interrupt level conflict which caused the garbled
line.<R>
<R>
The system configuration was as follows: IBM AT with EGA card, Sigma
Designs LaserView monitor<$SSigma Designs LaserView;LaserView> and
card, PC mouse and the<$ICordata - with LaserView> Cordata <$ILaserView
- with Cordata>printer.

@ANSWER2 = 7The conflict came from the location each device driver
occupied in memory. Memory locations are referred to as "pages".<$IMemory
pages - Cordata> Corda7ta allows<$ICordata - memory pages> for installation
to either the "C" page (default) or the "D" page (optional). The <$ILaserView
- memory pages>LaserView is normally installed to the "D" page, but
Sigma Designs can provide the user a driver which will position the
LaserView on the "A" page. The user also retained his EGA card, which
only addresses the "C" page.

@ANSWER2 = To resolve the conflict, he changed the addresses of the
Cordata and the LaserView. He moved the Cordata to "D" and the LaserView
to "A", leaving the EGA on the "C" page. Theoretically this should
have worked.

@ANSWER2 = Unfortunately, it appears that the LaserView "A" driver
was originally a "D" driver that was modified and all calls were not
changed to look at the "A" page.  Whenever the screen cycled to refresh
it apparently issued a call to the "D" page which caused a conflict
with the Cordata printer.

@ANSWER2 = The problem was solved by removing the EGA card and allowing
the LaserView to occupy its default "D" page address and the Cordata
to occupy its default "C" address and there were no further conflicts.

@QUESTION = I am attempting to print a Ventura document, but my Cordata<$ICordata
- prints blank sheets only> prints only blank pages. One blank sheet
is ejected for each page of the actual document. Ventura behaves onscreen
as if it has printed successfully.

@VERPATCH = 1.1(all)

@ANSWER = First, make sure it is the supported<$ICordata - supported
version> version of the Cordata--the LP300X. (If there is no "X" it
is not supported by Ventura.)

@ANSWER2 = Also make sure it is installed<$ICordata - installation>
correctly. In particular, CONFIG.SYS contains "DEVICE=LLD.SYS"; the
AUTOEXEC.BAT file contains the command "RIM" and does not contain
a string that reads "LPX (something)."

@ANSWER2 = In this case, it was the supported version and it was installed
correctly. The problem was caused by failure of the Cordata adapter
board to initialize<$ICordata - initialization problem> properly at
boot-up. The Cordata seems prone to this problem on an erratic basis
(the one I have installed here does the same thing). The customer
was told how to "persuade" it to initialize and it then printed properly.

@ANSWER2 = Here is what to watch for and what to do if you run into
this problem:

@ANSWER2 = <MU>DURING BOOT-UP:<D>

@ANSWER2 = You will see the following lines on the screen:

@NUMBER =

@STEP = LLD: Cordata LP 300X Low level Driver--Version 1.31 Copyright
(etc.)

@NUMBER =

@STEP = LLD: Initializing the Laser Printer Mechanism...

@ANSWER2 = The "initializing" message should stay on the screen for
several seconds if it is initializing properly, even on a 386 computer.
Then it will be followed by:

@NUMBER =

@STEP = LLD: Installed successfully.

@ANSWER2 = Then the boot-up process will quickly be completed, producing
the system prompt.

@NUMBER =

@STEP = <MU>If the "initializing" message appears only momentarily
and then is immediately followed by the "installed successfully" message,
the initialization has actually failed, contrary to the message.<D>

@ANSWER2 = <MU>HOW TO PERSUADE IT TO INITIALIZE:<D>

@NUMBER =

@STEP = 1) Shut down both the PC and the Cordata.

@NUMBER =

@STEP = 2) Cold boot the PC with the Cordata still turned off.

@NUMBER =

@STEP = 3) Wait until just before the "LLD" messages are about to
come up-- then flip on the Cordata switch. (You may have to boot up
a few times to get the timing right.)

@ANSWER2 = This procedure causes the Cordata board to find the printer
powered up (thereby avoiding a "printer does not acknowledge" abort),
but not ready for initialization because it has to re-heat for a few
seconds. This forces the board to wait on the printer, and in the
process generally seems to force proper communication to be established.

@ANSWER2 = Note that this is not a Ventura problem as such, since
it has to do with the Cordata initialization which takes place before
boot-up is even completed.

@PAGE END =

@MENU = Epson Dot Matrix Printer

@QUESTION = I used <$IPrint to file - Epson>print to filename to create
a print file to be transferred to another system.  The file was created
using the Epson Width table to be printed out on an IBM Pro Printer.  The
document is two pages long, but only half of the first page prints.  I
used the instructions in the manual on copying to the LPT1 port, what
is wrong?

@VERPATCH = All

@ANSWER = When copying print files to either an Epson or Epson compatible
or to the Hewlett Packard LaserJet, use the /b option since these
are binary files and may contain a Ctrl Z in the text (which could
be interpreted by the printer as an end of file marker).  The /b option
will prevent this from happening.

@QUESTION = <$IPrinter - Epson JX 80>I am a Xerox software dealer
and I am using an Epson JX 80 with a number of computers in my shop.  The
Epson emulates FX 80 mode which is compatible with Ventura.  On a
Leading Edge machine running MS-DOS, the software and the printer
work fine.  However, I have a PC-XT and an AT running PC-DOS and the
Epson is inserting extra line feeds when driven by either of these
machines.  What is causing this?

@VERPATCH = All

@ANSWER = This is probably being caused by the different BIOS in the
two operating systems.  Try changing the dip switch settings (check
Epson operating manual for settings) on the Epson when cabled to the
PC-DOS machines.

@QUESTION = How do I install<$IPrinter - 34 LQ> 34 LQ, <$IPrinter
- P12>P12 and <$IPrinter - P12>P32 printers.

@VERPATCH = All

@ANSWER = Install for the Epson MX 80 for all three printers.  You
will have to set your 34 LQ in the alternate mode for it to function
properly.  On the P32 you will want to reset the fourth switch on
switch bank 2 to the off position.

@QUESTION = When printing from Ventura<$IEpson - extra line feed>
to my dot matrix printer, there is an extra<$IDot matrix - extra line
feed> line feed at the top of some pages. Sometimes successive <$IExtra
line feed - Epson>pages gradually walk downward off the sheet. Why?

@VERPATCH = 1.1(unpatched, patch 1) bug--fixed in 1.1(patch 2)

@ANSWER = Customers using dot matrix printers have noticed that they
get an extra line feed at the top of some pages. This happens on Epson
and Epson-emulating printers. The extra line feed occurs, specifically,
at the top of the first page of any chapter. Second and succeeding
pages of the chapter are positioned properly.

@ANSWER2 = If the customer has a multichapter publication consisting
of a series of single-page chapters, the spurious line feed occurs
on each page printed. In this situation, the successive pages of the
publication gradually walk downward until they no longer stay on the
sheet.

@ANSWER2 = This is a software bug which is present in Version 1.1
unpatched (4/10/87) and Patch 1 (7/2/87). It is corrected in Patch
2 (2/5/88).

@QUESTION = Can fonts<$IFonts - adding, for Epson> be added to Ventura
for use with my dot matrix<$IEpson - adding fonts> printer?<$IDot
matrix - adding fonts>

@VERPATCH = 1.1(all)

@ANSWER = There is no indication of a method for doing this in the
Ventura Reference Guide. There is now a way that it can be done using
Bitstream Fontware. The steps are basically as follows:

@ANSWER2 = 1) Install Fontware for Epson.

@ANSWER2 = 2) Generate the desired fonts and a width table for them
using Fontware.

@ANSWER2 = 3) Use "Add/Remove Fonts" to merge the new width table
into a copy of the standard Ventura Epson width table. The status
of the added fonts should be "Download," even though Epson fonts are
not downloaded in the sense of a laser printer.

@ANSWER2 = 4) In "Paragraph/Typographic Controls" set "Tracking" as
necessary to get the character spacing to look right. (In the example
tested--Bitstream Charter font--tracking was set to "0.100 looser"
to obtain proper character spacing.)

@PAGE END =

@MENU = Interpress

@QUESTION = When will <$IInterpress>Interpress be available?

@VERPATCH = 1.1(all)

@ANSWER = Interpress is available in Version 1.1.

@QUESTION = Is there some way to get<$IInterpress - 9700> Ventura
Interpress documents to a 9 track tape and from there into the 9700<$IXerox
9700 - Interpress> for printing?

@VERPATCH = 1.1(all)

@ANSWER = At the current time the 9700 standalone with tape input
does not support Interpress formatted documents.  Xerox is working
on an Interpress Interpreter for the 9700 standalone. The minimum
configuration for an Interpress 9700 requires a 8000 server with the
FPS (Formatting Print Service) software connected to the 9700 in an
Ethernet invironment.  The File transfer may be done by a PC connected
to Ethernet with XNS-PC software and a 3-COM PWA or from 360k disk
to a Xerox 6085 w/DOS option package.

@PAGE END =

@MENU = JLaser

@QUESTION = What is <$IJLaser>JLaser and what does it do?

@VERPATCH = All

@ANSWER = The JLaser board is a large memory board and laser printer
driver which plugs into the PC expansion slots.  It works with most
<$ICanon-based printers>Canon-based printers, including most versions
of the HP Laserjet.  It dramatically increases printing speed by bypassing
the slow serial or parrallel printer connections, and by allowing
information to be transferred directly from the hard disk to the printer
memory (which with JLaser, is installed in the PC) at DMA rates.  Ventura
provides a very fast, proprietary software RIP that rasterizes the
pages as fast as many dedicated hardware RIPs.

@QUESTION = Can I print a document on a JLaser<$IJLaser Board> and
a PostScript device?<$IPostScript Device>

@VERPATCH = All

@ANSWER = It is possible to output a document, created in Ventura,
to more than one type of printer.  Make sure, however, that the appropriate
width table is used to achieve the desired result.  Using a Jlaser
width table to print to a Xerox 4045, for example, could cause certain
alignment problems and affect the way graphics are displayed.

@QUESTION = I have a <$IJLaser board with LaserJet>JLaser board with
a Hewlett Packard <$ILaserJet with JLaser>LaserJet.  Can I purchase
additional Hewlett Packard fonts for my printer and use them with
the JLaser?

@VERPATCH = 1.0 limitation--fixed in 1.1(all)

@ANSWER = Version 1.0: No. Version 1.1(all): Yes. Appendix K of the
Ventura Reference Guide describes procedures<$IHP softfonts - AST,
Cordata, JLaser> to convert HP softfonts for use with the JLaser,
Cordata, and AST TurboLaser.<$IAdditional fonts - JLaser>

@QUESTION = Can I <$IJLaser print to file>use the print to file feature
in conjunction with the JLaser board?<$IPrint to file - JLaser>

@VERPATCH = All

@ANSWER = No.

@QUESTION = Can I <$IAdditional fonts - JLaser>obtain <$IJLaser -
additional fonts>additional fonts for the JLaser board?

@VERPATCH = 1.0 limitation--improved in 1.1(all)

@ANSWER = Version 1.0: No. Version 1.1(all): Yes. Appendix K of the
Ventura Reference Guide describes procedures<$IHP softfonts - AST,
Cordata, JLaser> to convert HP softfonts for use with the JLaser,
Cordata, and AST TurboLaser.

@QUESTION = I am getting garbage when printing to my JLaser <$IJLaser
- printing garbage>driven H. P. Laserjet.  There are bars across the
page and letters are incomplete.

@VERPATCH = All

@ANSWER = Check for the interrupt setting in your config.sys file.  It
could be that the interrupts for the JLaser board and your enhanced
graphics adaptor are in conflict.  The enhanced graphics board typically
has an interrupt setting of 10, if the JLaser is also set at 10 this
could be your problem.  You can also check the memory paging settings
on the JLaser board itself.  These are physical settings, changed
by shunts on the JLaser card.  Changing the position of the shunts
could also solve your problem.  If in doubt, call Tall Tree Systems
for further technical assistance.

@QUESTION = I am printing to a <$IJLaser board>JLaser board.  After
printing one page, the system appears to lock up and will not print
any more.

@VERPATCH = All

@ANSWER = This occasionally happens with the JLaser board, the processor
will beep and you will see lines across the screen because JLaser
is trying to send a message back to the screen.  To resume printing,
you will have to respond to the message JLaser is sending.  Without
seeing the message it is difficult to know which response to give
but one of the following letters should work: R D I

@QUESTION = Customer with JLASER<$IJLaser - manual legal feed> wanting
to do 8 1/2 x 14" Landscape "Manual"<$IManual legal feed - JLaser>
Feed.

@VERPATCH = All

@ANSWER = JLASER will according to Tall Tree function in a Manual
Feed mode. However, Ventura will not currently drive the JLaser in
Manual mode. No workaround currently exists.  14" Portrait and Landscape
is functional with JLaser if a 14" papertray is present.

@QUESTION = My Jlaser is able to print 8 1/2 x 11 letter size in both
portrait and landscape but cannot print legal 14" lengths.<$IJLaser
- won't print legal>

@VERPATCH = All

@ANSWER = Customers' CONFIG.SYS included  DEVICE = JDRIVE.BIN 720K.  This
statement effectively removed about 25% of the JRAM PWA memory for
a Ram disk she was not using.   Removing this statement cured the
problem and the JLaser was able to print legal as well as letter size.

@QUESTION = Why has my JLaser suddenly started<$IJLaser - slow printing>
taking 8 minutes to print 4 lines of text?

@VERPATCH = 1.1(all)

@ANSWER = "Suddenly" turns out to mean "after I added 187 fonts to
the Ventura subdirectory". Everytime you see on the screen "Loading
Fonts", VP is taking every (*.B30) font and spooling it into a temporary
file.  With this many fonts in the directory on a slow access ridged
drive it was taking forever.

@ANSWER2 = Two pieces of corrective action:<R>
<R>
1) Increase Buffers to 25 or 30.<R>
<R>
2) Set up separate directory to hold fonts that are not actually needed
on a particular document and set up batch files to copy needed fonts
into (and later delete from) the Ventura Directory.

@QUESTION = JLaser<$IJLaser - only prints 1 page> will only<$IJLaser
- lockup after 1 page> print 1 page from Ventura--then it locks up
or the screen<$IJLaser - screen scrambles> scrambles.

@VERPATCH = All

@ANSWER = This problem is due to a bug in the JLaser software, according
to Tall Tree Systems. It is supposed to be fixed by a new software
release due out at the end of January 1988.

@ANSWER2 = <B>WORKAROUND:<D> Before going into Ventura, access drive
A: in some manner. For example, put a disk in drive A: and do a DIR
on it. Then you should be able to load Ventura and print successfully
using the JLaser.

@QUESTION = JLaser prints black pages<$IJLaser - black pages> instead
of the correct printout.

@VERPATCH = All

@ANSWER = Several things can cause this to happen:

@NUMBER = 1.

@STEP = CONFIG.SYS--must not contain a "JRAM" or "GEMPRINT.SYS" driver.

@NUMBER = 2.

@STEP = JLaser board could have a problem. Check this by running JLaser
diagnostics, according to the manual provided to the customer. If
the board is okay, it should print a page which is blank except for
a large "X".

@NUMBER = 3.

@STEP = The Ventura installation could be bad. If this is suspected,
try to determine WHY it is bad, if possible, before recommending reinstallation.
For example, check disk space, determine if there have been any known
hard disk problems on that PC, and the like.

@QUESTION = A customer<$IJLaser - graphics won't print> was unsuccessful
trying to print graphics through his<$IJLaser card - on Compaq 386>
JLaser. It was installed on a Compaq 386.<$ICompaq 386 - with JLaser>

@VERPATCH = All

@ANSWER = The Compaq 386 cannot use the JLaser card we know and love--it
must use the JLaser "standalone" card with NO MEMORY ON THE CARD.
The JLaser must then make use of the computer's expanded memory. This
was confirmed a representative at Tall Tree Systems. This apparently
holds true for all 386 computers.

@ANSWER2 = It is not clear as yet how much memory is needed on the
computer before the JLaser is fully usable.

@PAGE END =

@MENU = LaserJet and LaserJet Plus

@QUESTION = I have created a width<$ILaserJet+ - width table> table
in Version 1.0 and some of my fonts are not printing correctly.

@VERPATCH = 1.0 bugs & limitations--improved in 1.1(all)

@ANSWER = The font conversion utilities in Version 1.0 were faulty
for the HP LaserJet Plus and Xerox 4045. However, a temporary interim
version called 1.01 was released which used the same procedures given
in the 1.0 manual. If this is what you are using, make sure that you
have included Ventura's original Times 10 point normal and Helvetica
10 point normal in your .LST file.  Also be sure that you have grouped
your fonts by family in assending point size and in the correct weight
order (please see reference manual).

@ANSWER2 = Assuming that all procedures have been followed correctly,
the problem could be in the number of fonts you have in the width
table.  In Version 1.0 Ventura<$ILaserJet+ width table limits> supported
50 fonts in the LaserJet Plus device driver (28 of which were reserved
for Ventura's resident fonts leaving the user only 22 fonts to be
added) the 51st font in the .LST file will not print correctly.  Version
1.1 eliminates any practical limitation other than disk space and
memory.<$ILaserJet - new fonts don't print correctly>

@QUESTION = I purchased Version 1.1 and I am unable to get my LaserJet
to print correctly.  I am using the F cartridge as specified in the
manual.  What is the problem?

@VERPATCH = 1.1(unpatched) bug--fixed in 1.1(patch 1)

@ANSWER = There is a problem in the device driver in the preliminary
release of 1.1 which can cause this type of problem.  This problem
has been fixed by Patch 1 (7/2/87).<$ILaserJet - font cartridge not
printing correctly>

@QUESTION = I have a serial LaserJet Series II and it will not print
unless I first press the escape key.

@VERPATCH = All

@ANSWER = As it turns out this customer had a clock program resident
in memory which was causing this unusual situation.  Remember, it
is highly recommended that all memory resident programs be deactivated
prior to running Ventura.<$ILaserJet - must press escape to print>


@QUESTION = I purchased a new font<$IFont conversion> for my Hewlett
Packard LaserJet Plus<$IHewlett Packard Laserjet> and used the utilities
provided by Ventura to convert it to Ventura compatible format.  However,
when I display or print using the new font the sizing is not correct.  What
caused this?

@VERPATCH = 1.0 bug--fixed in 1.1(all)

@ANSWER = The utility that converts Hewlett Packard fonts to Ventura
format in Version 1.0 was inoperative.  This utility has been modified
to correct this problem and is available in Version 1.1.

@QUESTION = I have a <$IJLaser board with LaserJet>JLaser board with
a Hewlett Packard <$ILaserJet with JLaser>LaserJet.  Can I purchase
additional Hewlett Packard fonts for my printer and use them with
the JLaser?

@VERPATCH = 1.0 limitation--fixed in 1.1(all)

@ANSWER = Version 1.0: No. Version 1.1(all): Yes. Appendix K of the
Ventura Reference Guide describes procedures to convert HP softfonts
for use with the JLaser, Cordata, and AST TurboLaser.

@QUESTION = Can I use fonts <$IFonts - LaserJet>other than Hewlett
Packard fonts on my LaserJet Plus or LaserJet II?

@VERPATCH = All

@ANSWER = If these fonts are guarranteed by the manufacturer to be
compatible with downloadable fonts for the LaserJet you can follow
the font conversion process for Hewlett Packard fonts detailed in
the Reference Manual.  Please note that these fonts are provided for
the printer only (Ventura provides screen and printer fonts for the
typefaces which are included in the standard package) and there will
be no corresponding screen fonts for Ventura to load.  Ventura will
try to match, as closely as it can, the font size on the screen, but
the screen characters will not be identical to the printed output.

@QUESTION = How many of the print cartridges for the Hewlett <$ILaserJet
font cartridges>Packard LaserJet does Ventura support?

@VERPATCH = All

@ANSWER = The only print cartridge supported for the LaserJet is the
"F" cartridge.

@QUESTION = I <$ILaserJet - large graphics>tried to print a large
graphic on my LaserJet Plus (or LaserJet II)and it came out on two
pages with the center of the graphic on one page and the two outside
quarters on the second page.  Why did it print this way?

@VERPATCH = All

@ANSWER = Typically this type of problem is caused by insufficient
memory in the printer.  A Laser printer constructs the entire graphic
in its memory before outputing it to the paper.  Large graphics are
memory "hogs" utilizing large amounts of memory.  The LaserJet Plus
contains about .5 MB of memory which may not be enough for large graphics.  Try
reducing the size of the graphic, or increasing the memory in your
printer. (The current printer in this series, the HP LaserJet II,
comes with 512K built in. An expansion board can be added containing
1Mb, 2Mb, or 4Mb; the most common choice is 2Mb, giving a total of
2.5Mb of printer memory.)

@QUESTION = The manual addresses<$ILaserJet - resident fonts>making
fonts <$IFonts - LaserJet, resident>resident in the LaserJet (page
F- 14) and mentions a font ID<$IFont ID number - LaserJet> number
to identify to the printer which font is to be used. Where does this
ID number come from?

@VERPATCH = 1.1(all)

@ANSWER = The utility Hewlett Packard supplies with the LaserJet prompts
the user for a font ID at the time the font is actually downloaded
to the printer. This is the ID number that must be used in Ventura.

@QUESTION = Can LaserJet Plus fonts<$ILaserJet fonts - directory>
reside in a directory other than the <$IFonts - LaserJet, directory>Ventura
directory?

@VERPATCH = 1.1(unpatched, patch 1), 1.1(patch 2)

@ANSWER = Not with Ventura Version 1.1 unpatched (4/10/87) and Patch
1 (7/2/87): Ventura will only look in the Ventura directory for LaserJet
fonts. However, Patch 2 (2/5/88) enables LaserJet Plus fonts to be
stored in any subdirectory.

@QUESTION = I have tried to print<$IBroadsheet> a broadsheet page
in strips to my LaserJet<$ILaserJet - broadsheet> and it only prints
the top third of the page.

@VERPATCH = 1.1(all)

@ANSWER = Strip printing is only effective when printing to PostScript
typesetters, such as the Linotronic 100 and 300. It will not work
with laser printers.

@QUESTION = I am using a HP supplied utility to download fonts to
my LaserJet II and the printer acknowledges correctly. Ventura uses
these fonts fine if set to "download" but will not use those that
are pre-downloaded ("resident"). Why?

@VERPATCH = 1.1(all)

@ANSWER = Four things are necessary to use HP resident fonts:

@NUMBER = 1.

@STEP = The utility or batch file used must make the fonts permanent
(as long as power is supplied to the printer) or the Ventura initial
Escape "E" will erase them.

@NUMBER = 2.

@STEP = The utility of batch file used to download must either invoke
or otherwise attach a two digit number to identify the font in the
printer.

@NUMBER = 3.

@STEP = Per the instructions of appendix F page 14, the HPLJPLUS.CNF
file must be modified to indicate both the font ID number (assigned
by the utility or batch file) and the font filename which must be
identical to the one used to create the WIDth table.<R>


@NUMBER = 4.

@STEP = The width table must be set to RESIDENT for those fonts previously
downloaded.

@ANSWER2 = The customer in question had skipped step 3 and had modified
his file names, which confused step 4.

@QUESTION = Why won't graphics<$IGraphics not printing - LaserJet
II> print from inside Ventura to my HP <$ILaserJet II - graphics not
printing>LaserJet II?

@VERPATCH = All

@ANSWER = Chkdsk showed 550k available but investigation of the customers
CONFIG.SYS file indicated a very large number of device drivers including
Fast Disk Access managers etc.  Asking the customer to rename config.sys
to config.old and creating a new config.sys with only Files, buffers
and mouse.sys statements cured the problem.  Chkdsk showed only a
27k improvement to 577k free which indicates that some of the specialized
drivers are fragmenting memory. It was recommended that the customer
replace only the ones needed and replace them one at a time.

@QUESTION = Text in the<$ILaserJet - landscape: left text missing>
leftmost column of a landscape printout on a HP LaserJet Plus/II is
missing. The whole column of text may be missing, or only certain
paragraphs. Everything looks fine onscreen.

@VERPATCH = 1.1(unpatched) limitation--improved in 1.1(patch 1)

@ANSWER = Check the margins and "In from left" settings on the text
in the leftmost column. If the first character in any line of text
is supposed to begin in the non-printing area near the edge, the entire
line of text will be lost. If the left margin is set within the unprintable
zone, and if all the text in the first column starts at the margin,
the whole column will be lost. If some lines or paragraphs are indented
past the non-printing zone, they will print.

@ANSWER2 = This problem is most often encountered with unpatched 1.1,
since the non- printing zone at left and right is about 0.5 inch in
landscape with that software.

@QUESTION = After loading an image file on a page, all fonts on that
page print as Courier<$ILaserJet - defaulting to Courier> using HP
LaserJet II. When the image is removed, the text prints fine.

@VERPATCH = 1.1(all)

@ANSWER = CONFIG.SYS file contained no "Buffers" or "Files" statements,
which are essential for font downloading when a graphic is present.

@QUESTION = Using Ventura graphics, if several different shapes are
made with the same fill<$ILaserJet - graphic fill varies> pattern
(#3 for example), they don't all print out with the same pattern on
the HP LaserJet II.

@VERPATCH = All

@ANSWER = To conserve printer memory, Ventura uses the printer's built-in
shading capability wherever possible, instead of building a bit pattern
itself and sending it to the printer. Printer internal patterns are
available only for rectangular shapes; for rounded shapes, Ventura
has to build a pattern.

@ANSWER2 = The problem is that Ventura doesn't build patterns that
perfectly match the printer patterns. As a result, rectangular graphics
get one pattern, and rounded graphics get another--even though the
same pattern was selected by the user.

@QUESTION = During printing of a large publication, the customer's
Quadram<$IQuadram QuadLaser - timeout problem> QuadLaser (HP <$ILaserJet
emulation problem - QuadLaser>LaserJet emulator) stops printing at
some point. On smaller print jobs it goes through okay.

@VERPATCH = All

@ANSWER = There is a timeout problem on the QuadLaser that can cause
this effect when printing out a large publication. According to Rene
Hursh of Quadram, their engineers are working on their HPLJ+ emulation
to correct this problem.

@QUESTION = Is there a way to print Dingbat<$IDingbats - on HP LaserJet>
<$IFonts, Dingbat - LaserJet>symbols on the HP<$ILaserJet - Dingbat
fonts> LaserJet Plus/II?

@VERPATCH = 1.1(all)

@ANSWER = Yes. Dingbat soft fonts can be obtained for the HP LaserJet
Plus from Weaver Graphics. To install them for use by Ventura, basically
copy all of the *.SFP fonts and width tables to \VENTURA directory
and merge the new width tables with the current width table.