Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!think.com!hsdndev!husc3.harvard.edu!husc9.harvard.edu!khoo From: kik@wjh12.harvard.edu (Ken Kreshtool) Newsgroups: comp.sys.mac.hardware Subject: DeskWriter driver 2.1 versus System 7 Summary: Use VM + 32-bit mode, or no VM + 24-bit Message-ID: <1991May29.233145.1215@husc3.harvard.edu> Date: 30 May 91 03:31:44 GMT Organization: Harvard University Science Center Lines: 29 Nntp-Posting-Host: husc9.harvard.edu Originator: khoo@husc9.harvard.eduLines: 29 As has been posted, the DeskWriter, using driver 2.1, does not like to print under System 7 with virtual memory turned on. This seems to be a bug in System 7, but HP is trying to do a work around. In the meantime, we're supposed to live either with VM or printing, but not both. Well, I need printing even more than I need VM, so I sighed and turned off VM. But I just downloaded Nobu Toge's Flash-It 2.2b1, a screen capture init/cdev. He notes in his docs that he also had trouble with virtual memory on, but only in _24-bit mode_. (I haven't tried Flash-It yet, but I read the docs.) So I thought, hmmmmmmmm, maybe the DW has the same problem. Maybe all of us with printing problems in VM were also in 24-bit mode at the time? After all, don't really _need_ 32-bit, and so many apps can't handle it yet that I (and maybe others?) have left it off. I have switched VM back on, and have put my machine (IIsi) into 32-bit mode. And printing is working! No "datacomm buffer overrun" messages from the DW, at least not yet! 'Course, gotta turn 32-bit off for some apps, but still.... Anybody else having the same kind of experience? Ken Kreshtool kik@wjh12.harvard.edu (my real e-mail address; this post is from a friend's account on a different machine, so please don't just "r" back) -- --- Ah Love! Could You and I with Fate conspire, To Grasp this sorry scheme * of things (Lawrence Oon-Chye Khoo) Entire, * Would we not khoo@husc9.harvard.edu Shatter it