🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.next.misc
Article #36

Re: Dove Fax Troubles

#36
From: Dean Blakeley MD
Date: Wed, 28 Oct 1992 15:22
61 lines
3507 bytes
Yesterday, I wrote:

In article <6419@news.duke.edu> dblakele@hercules.acpub.duke.edu writes:

>Again, I've got a 68040 Cube at home running NS 3.0 (which was painfully
>loaded on two weeks ago).  Connecting me to the world is a DoveFax 24/96
>purchased more than a year ago with a driver dating back to Nov 91.

That driver was version 1.03 which was shipped with the unit at the time
it was purchased.  In the recycler on the floppy was Version 1.00.

>This evening I was in the process of sending a fax to a friend of mine,
>but couldn't seem to be able to get the modem to switch into fax mode
>to send it out.  I was sending an image within Appsoft Draw and had
>created an address listing within the new ~/Library/Addresses area.
>
>Now, with Print Manager dividing things between printers and fax modems,
>the Dove had been set to be in Private mode (like I've done in NS 2.1)
>like I had before, but this time the FM indicator lights didn't come
>on like in the past.

Well, I got on the phone with NeXTconnection and Dove Computer company
this morning and got an answer.   Problem #1 was that the .pkg file
from Dove was corrupted and a symbolic link was not created between

/usr/lib/NextPrinter/Dove_Fax_Modem -> 
/usr/lib/NextPrinter/Class2_Fax_Modem*@

as well as 

/usr/lib/NextPrinter/pdf/Dove_Fax_Modem.pdf -> 
/usr/lib/NextPrinter/pdf/Class2_Fax_Modem.pdf@

Thus, when I tried to select the fax modem in PrintManager.app to be
created and set up as a private printer device, nothing happened with
the modem without the links set up.

This problem was created inadvertantly when I had to rebuild my hard drive
after making a semi-fatal error while installing NS 3.0.  A lot of what
I had customized and forgotten was wiped by mistake while rebuilding from
a NS 2.1 optical and was not recovered when re-installing everything.
Anyway, the problem was quickly fixed with a number efforts at reloading
the DoveFax.pkg and deleting/creating the fax modem in PrintManager.app.

I'm faxing once again, but the folks at Dove Computer are sending me an
updated fax driver (I think Version 2.0 or 2.x or something like that)
tomorrow.  So, anyway, if there are folks out there with a floppy from
Dove dated around May 1992 or June 1992 and are trying to rebuild your
system with NS 3.0, I would suggest getting in contact with Dove Computer
at (919)-763-7918 or at their tech line (919) 343-5610.  Their feeling
that a lot of their other problems are coming from some flakiness in 
PrintManager.app (which doesn't surprise me due to the fun I had in 2.1)
but are more than willing to send out an uncorrupted floppy/.pkg file.

Peace

-- 
| Dean D Blakeley, MD            | Internet:dblakele@acpub.duke.edu           |
| Ambulatory Care Service (11C)  | BITNET:blake007@dukemc.mc.duke.edu         |
| Durham VA Medical Center       | FORUM:blakeley,dean d@durham.va.gov        |
| Durham NC 27705                | NeXTMail accepted  #include <disclaim.h>   |
Technical Details
Message-ID: <6430@news.duke.edu>
Path: arc1-ca.pugleaf.net!sparky!uunet!usc!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!ames!decwrl!concert!duke!news.duke.edu!acpub.duke.edu!dblakele
References: <6419@news.duke.edu>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!usc!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!ames!decwrl!concert!duke!news.duke.edu!acpub.duke.edu!dblakele
From: dblakele@acpub.duke.edu (Dean Blakeley MD)
Newsgroups: comp.sys.next.misc
Subject: Re: Dove Fax Troubles
Message-ID: <6430@news.duke.edu>
Date: 28 Oct 92 15:22:33 GMT
References: <6419@news.duke.edu>
Sender: news@news.duke.edu
Organization: Duke University; Durham, N.C.
Lines: 61
Nntp-Posting-Host: raphael.acpub.duke.edu