Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

help:Printing problems with win32s

0 views
Skip to first unread message

dc...@arcland.com

unread,
Jan 22, 1995, 7:00:04 AM1/22/95
to

>Does anyone have any suggestions? I can live without print preview,
>but I really need to get the print functionality working under win32s.
>Has anyone else had these sort of problems?

You bet - Win32s is no Windows NT, that's for sure. I've found that
a few problems have been circumvented by overriding and re-writing
some portions of MFC 2.0 code, but that there are many, many other
problems which are printer-driver / Win32s interactions. Basically
if the call to CreateDC fails, there's probably a problem with
how the printer driver is dealing with its DEVMODE data.

Try everything with many printer drivers to see if it's your app
or not... Usually, it can be tracked to the printer driver for
Windows 3.1 making some assumptions that are invalid under Win32s.

Of the five or so that I use regularly for testing, the HP LaserJet
IIIP driver for Windows 3.1 works BEST. Hope this helps.


David Cole
Senior Software Engineer
Arcland Inc.
dc...@arcland.com


Michael R. Gile

unread,
Jan 22, 1995, 12:19:59 PM1/22/95
to
In article <3fthc4$f...@merengue.worldcom.com>, <dc...@arcland.com> wrote:
>
>>Does anyone have any suggestions? I can live without print preview,
>>but I really need to get the print functionality working under win32s.
>>Has anyone else had these sort of problems?
>
>You bet - Win32s is no Windows NT, that's for sure. I've found that
>a few problems have been circumvented by overriding and re-writing
>some portions of MFC 2.0 code, but that there are many, many other
>problems which are printer-driver / Win32s interactions. Basically
>if the call to CreateDC fails, there's probably a problem with
>how the printer driver is dealing with its DEVMODE data.

now you tell us!
I have been fighting with this thing for a while, and yesterday
found that the problem was the print driver.

>Try everything with many printer drivers to see if it's your app
>or not... Usually, it can be tracked to the printer driver for
>Windows 3.1 making some assumptions that are invalid under Win32s.
>
>Of the five or so that I use regularly for testing, the HP LaserJet
>IIIP driver for Windows 3.1 works BEST. Hope this helps.
>

ok, just for reference, the HP DeskJet 500 series drivers are the worst.
The ones that come with windows don't fail as mentioned above, but they
have other bugs. Version 4.x and 5.0 don't work with mfc. Don't bother
trying them.

thanks for your note. Even though I discovered the driver problem on
my own, it is nice to know that I am not the only person who is having problems
with this. (misery loves company principle)

--
Michael Gile | Graduate Assistant
gi...@rpi.edu | Computer & Systems Engineering
"Don't Blame Me, I voted for Perot!"| Rensselaer Polytechnic Institute

0 new messages