#Final Copy II Problem
3 messages in this thread
Well, well, well… It appears that cpublit (!) is the culprit. I went
ahead a renamed the WBStartup directory as you suggested (Neat idea,
that!) and I also commented out all of the "unusual" stuff I start in my
User-Startup (This included QMouse, cpublit, upd and resethandler). FCII
then printed the document just fine. OK, re-boot with everything back to
normal, on to the next step. Since I had noticed some problems I
associated with cpublit before (with TurboText), I shut it down (cpublit
-q) and tried to print… no problems. Startup cpublit again, try to
print, BOOM! Hmmm, methinks cpublit must be stomping on someone elses
memory. Just a guess, maybe cpublit has problems with programs that do
extensive text blitting (such as FCII and TurboText).
Thanks for the help. (Yea!) I never really tried to track this down
before, since I loath resetting my system. Because it is a UUCP site I
run it 24hrs 7 days a week. D*mn, I'm going to hate having my text flash
in JR-Comm again (without cpublit running). *SIGH*
Thanks again for your help!
Bill
Bill,
Get an AGA machine and all your text blitting problems are solved
(unless you use a 256 color screen).
If you have 2.04 (or later), I highly recommend Term. It's quite
excellent.
Ric Fischer
SoftWood Tech Support
Phoenix, Arizona, USA
(602) 431-9151
> Get an AGA machine…
Nah, got *way* too much stuff installed in my A3000, much of which I'd
have to abandon. Memory, SCSI devices… The lack of SCSI on the A4000
(and the lack on a hardware de-interlacer) *really* annoyed me! I've got
four SCSI devices on my A3000, two of them external. The SCSI port on the
back of the A3000 is one of its best features!
> Term….
Tried Term once, didn't really care for it. Besides, I've got JR-Comm set
up just the way I like it. 🙂 And Term should flash just like JR-Comm if
it uses the blitter to move the text. Only happens on 16 (8?) color ANSI
screens anyway, I'll live with it (at least until Terminus is released).
Later,
Bill