[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::windows95

Title:Microsoft Windows 95 ("Chicago")
Notice:Please read topics 1 to 22 before writing anything
Moderator:EEMELI::BACKSTROM
Created:Mon Nov 14 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2958
Total number of notes:19968

2850.0. "Music printing problems with Noteworthy Composer" by MARVIN::SHAND (Mike Shand) Fri Mar 14 1997 07:35

I apologize in advance for this rather long note...

My daughter uses Noteworthy Composer for Music printing. This uses its
own TrueType Font, and has been working fine on my Win 3.1 system, with
a Canon BJ10ex printer.

Recently I bought a new system running WIN95 (OSR2). One of the first
things my daughter installed was NOteworthy, and she *claims* it printed
perfectly. Unfortunately I have no personal evidence of this. She could have
been mistaken and may not have tried printing, but she is adamant that she did.


However, a few days later while messing with partitions I rather cleverly
managed to trash my C: drive (and D: drive for that matter). SO I reinstalled
everthing from scratch, and continued the process of installing all sorts
of stuff. When my daughter came to print from Noteworthy, she discovered that
it prints as if each note were surrounded by a block of whitespace obscuring
the lines underneath.

So... what's the cause of the problem? I have the following information.

1) Reinstalling Noteworthy makes no difference

2) Deleting and reloading the music font makes no difference.

3) The win 3.1 system continues to work printing to the same printer either
directly, or spooling over the network to the WIN95 system. (so its not a
printer configuration / cable / port settings problem)?

4) Canon, on their web site, don't have a specific driver for the BJ10ex. They
say use the microsoft one.

5) I *haven't* yet tried removing and reintalling the printer support, though
in desperation I probably will.

6) I've tried messing with OutlineThreshold in win.ini; not understanding what I
am doing, but noticing that this is often given as a solution to the problem of
large truetype fonts printing as white boxes (which is a bit similar to my
problem). All to no avail.

7) I've contacted noteworthy, but so far no answer.

8) Among the many differences between the configuration before and after the
crash is that I have installed support for an HP laserjet 4L (printing to FILE).
I can't see how that would be relevant, but I mention it just in case. This
was using the microsoft drivers off the CD, so they shouldn't have overwritten
some dll ot other with a different version.

9) Hmmm - again it should be irrelevant, but I tried to install KEAterm and it
completly trashed my display setup (would only boot in safe mode). I had to
reinstall the Matrox drivers etc. I've since given up on Keaterm and am using
VTstar instead. 

10) Oh, in case it isn't obvious, I'd had no other problems (yet) printing
anything else from any other application (mostly only word so far).


Any suggestions? I'm at a loss to know how to approach debugging this.

	Mike
T.RTitleUserPersonal
Name
DateLines
2850.1Its the Matrox Mystique driverMARVIN::SHANDMike ShandMon Mar 17 1997 06:4987
Thanks to Phil Allwood on the Noteworthy forum

> NoteWorthy Composer Forum
> 
> [ Home | Forums | Contents | Search | New Message | Reply | Next |
> Previous | Up ]
> 
> ----------------------------------------------------------------------
> 
> Re: Printing Problem
> 
> From: Philip Allwood (philip@allwood.demon.co.uk
> Date: 16 Mar 1997
> Time: 07:27:18
> 
> Details
> 
> I had similar problems when I bought a new PC. The fault lies in the
> graphics drivers supplied with some video cards. In my case this is a
> Matrox Mystique. The problem was only brought to light on the
> Microsoft Knowledge Base on 18 February. The fix with the Matrox card
> is to turn off the use of the PowerGDI Acceleration in the display
> control panel MGA settings. No need to reboot for the correction to
> work. It affected any program which prints text (the notes in
> Noteworthy) over graphics (the staves).
> 
> I hope this helps
> 
> Phil
> 
> ----------------------------------------------------------------------
> 
>   NoteWorthy Composer forum is sponsored by NoteWorthy ArtWare, Inc.


and from the Microft Knowledge Base


                      Text Printed with White Background with
                      Matrox Video Drivers

                      Article ID: Q163771 
                      Creation Date: 18-FEB-1997
                      Revision Date: 18-FEB-1997 

                      The information in this article applies to: 
                          Microsoft Windows 95 

                      SYMPTOMS 

                      Text positioned over shading or other objects may be 	
		      printed with a white background
                      when you are using the Windows 95 Matrox Millenium or 	
		      Mystique video driver version
                      3.22. 

                      RESOLUTION 

                      The Windows 95 Matrox (MGA) Millenium and Mystique drivers
			      enable a feature called
                      "PowerGDI" by default. This feature replaces some 	
		      functions of Windows GDI and may
                      cause printed output to look different from when it is 	
		      previewed. Most notably, text
                      positioned over shading or other objects is printed with a
			      white background. To disable
                      this feature, follow these steps: 
                        1.In Control Panel, double-click Display. 
                        2.On the MGA Settings tab, click Advanced. 
                        3.Click the Performance tab. 
                        4.Click the Use PowerGDI Acceleration check box to clear
				it. 
                        5.Click OK until you return to Control Panel. Note that 
			you do not need to restart
                          the computer for this change to take effect. 

                      MORE INFORMATION 

                      This problem can occur when you are printing to most 	
		      non-PostScript printers, such as
                      Hewlett-Packard LaserJets, DeskJets, and compatibles, and 
		      most dot-matrix and
                      inkjet printers. 

                      This problem also occurs with the Beta version 3.30 video 
		      driver available on the
                      Matrox Graphics Web site.