[fa.info-mac] INFO-MAC Digest V3 #6

info-mac@uw-beaver (06/08/85)

From: Moderator John Mark Agosta <INFO-MAC-REQUEST@SUMEX-AIM.ARPA>


INFO-MAC Digest          Saturday, 8 Jun 1985       Volume 3 : Issue 6

Today's Topics:
                              ScrnEdit.hqx
                          A new MacxBin script
                  New Finder, MacWrite, System bugs...
                             Overheating...
                            (copy) ROM RUMor
                          Apple Hard Drive news
                      (A point about bboard style)
                        Where does Macsbug live?
                        Blit emulation on the Mac
                       Appletalk Cable components?
                         How to run objective C?


----------------------------------------------------------------------

Date: Fri 31 May 85 19:08:09-PDT
From: DBECK@SRI-KL.ARPA
Subject: ScrnEdit.hqx

Hello, John.  I have a useful application downloaded from Compuserve 
called ScrnEdit.  It permits one to specify Menus, Windows, Dialogs, 
Alerts and Icons in an on screen environment.  The result of these 
activities is the ability to construct an RMaker compatible file you
may combine with your CODE's to create an application.  file is about
110K in the .hqx form and too big to mail.  I believe

[ This is another friendly but incomplete resedit type program.
  Find it in SCRNEDIT.HQX -jma ]

   ...Doug Beck dbeck@sri-kl

------------------------------

Date: Sat, 1 Jun 85 22:29:05 pdt
From: ix924%sdcc6@SDCSVAX.ARPA (Chris Borton)
Subject: A new MacxBin script

         This is a new edition of my macxbin shellscript that automati-
     cally xbin's all new files in net.sources.mac since it was last
     invoked.  You need to modify two variables in it to customize for
     your use:

        DLDIR is the directory that you want all the xbin'ned results
               to be put.
        SOURCES is the path to your net.sources.mac.

     It uses the file '.lastls' in your download directory to determine
     what has been done before, so you'll want to create this thefirst
     time with a

             ls [path to your] net.sources.mac > .lastls

      while in your download directory.

      Happy Maccing!
                        Chris Borton, UC San Diego Undergraduate CS

                        {ucbvax,decvax,akgua,dcdwest}!sdcsvax!sdcc6!ix924


[ Find this shell script in <INFO-MAC>MACXBIN.SH -jma ]

------------------------------

Date: Fri, 31 May 1985 14:23:25 EDT
From: AXLER%Upenn-1100%upenn.csnet@csnet-relay.arpa
Subject: New Finder, MacWrite, System bugs...

     There are several minor problems with the new MacWrite 4.5, some
of which existed in previous versions as well:
  1) Neither the ruler nor the menu-driven format commands can be
applied to pictures.  If nothing else, centering ought to work, so
that one doesn't have to relocate the picture box if one changes the
margins.
  2) If the user expands the margins, then saves the current document,
closes it and opens a new one, the new document is given the expanded
margins, whether they're wanted or not.  (This might not happen if the
margin change isn't made on the very first ruler, but I haven't
checked to confirm it.)

     The new system/finder seem to work fairly well, except for one
odd phenom- enon:  every so often, if I boot off the internal drive
and insert a disk into the external drive at the wrong moment, the
machine decides that the second drive effectively doesn't exist.
Nothing I can do, including popping the prob- lem disk w/a paper clip
and re-inserting it, will get the Mac to accept it and read its
directory.  The only solution to this seems to be a shutdown/restart, 
which really isn't very desirable.  Any notion as to what's happening?

Dave Axler (Axler@UPenn-1100.csnet

------------------------------

Date: Tue, 4 Jun 85 11:46 pst
From: "pugh jon%e.mfenet"@LLL-MFE.ARPA
Subject: Overheating...


I had a problem with my Mac and I was wondering about others.  I was
getting strange "Mr Yuck" responses with a hex code from my Mac
whenever I tried booting.  I finally just shut the machine off and let
it cool down.  It worked fine after it was no longer warm to the
touch.  I now have a fan that blows at the back and there has been no
repeat of this problem.  Anyone else experience this?

I was also wondering which is the better way to deal with my
situation.  I am connecting to a large computer center by modem where
I start a job and then disconnect.  After an hour or so I reconnect to
see how it is going.  I was wondering if powering down and then back
up was harmful to my Mac.  Would I be better off just turning down the
screen and leaving it on?  Even in light of my overheating problems
(although they seem to have gone away, it is only spring and the high
last year was 113)?  Any advice?

Jon Pugh pugh%e@lll-mfe.arpa

------------------------------

Date: 04 June 85 21:47 EDT
From: QP2%CORNELLA.BITNET@Berkeley
Subject: (copy) ROM RUMor

Originally sent from: QP2@CORNELLA Originally sent to:
INFO_MAC@CORNELLA

A recent posting quoted Martin Haeberli of Apple as stating some
policy or other about ROM upgrades.  I just spoke with Martin last
week and raised this issue specifically.  Martin says that he does not
know what the policy will be and that therefore any attribution of
statements about the policy to him are false.  I also spoke with other
Apple people (at the MacAdemia conference here at Cornell).  I begin
to suspect that there is no policy in place at this time.  It may be
premature to gripe about a non-existant policy.  Perhaps letters with
concrete suggestions might still have some influence.  (I'm sending
one, anyway.)
 -- Paul Velleman

------------------------------

Date: Thu, 6 Jun 85 09:13:21 edt
From: LARRAGA <larry%udel-cc-vax3.delaware@UDEL-LOUIE.ARPA>
Subject: Apple Hard Drive news


At the Cornell MacAdemia conference Apple's Chris Espinoza indicated
that the Mac Hard Drive would be out in September, be an external
drive that connects to the disk drive port, and will be self-bootable.
This kind of blows out the Hyperdrive connection.  He also mentioned
that this would be the basis for the new developer's system (vs. Lisa
Pascal Workshop).  Has anyone heard any more concerning this?

Larry Larraga (larraga@udel-louie.ARPA)

------------------------------

Date: Thu 6 Jun 85 17:02:04-PDT
From: John Mark Agosta <INFO-MAC-REQUEST@SUMEX-AIM.ARPA>
Subject: : A point about bboard style

Larry-

A small point of style: Please use a descriptive subject, instead of
Re: "INFO-MAC Digest Vn #x".  THe subject you choose will appear in
the "today's list of topics" at the top of the digest.  If you don't
do this I have to edit in a subject , by hand.  Also If it's a
question (which yours is not) it helps if its followed by a question
mark. -jma

By the way, the product announcement I have heard about the hard disk 
is consistent with your account.

------------------------------

Date: Thu, 6 Jun 85 15:12:23 edt
From: Ephraim Vishniac <vishniac%wang-inst.csnet@csnet-relay.arpa>
Subject: Where does Macsbug live?


I've run into an unusual problem with Macsbug, and I hope someone out
there in netland can shed some light on it.

In a "normal" Mac (thin or fat), Macsbug, Maxbug, and their relatives
live at or near the top of physical memory, away from the heap, stack,
screen, and other interesting data structures.  Because Apple warns
that Macsbug and company *do not* work in a Lisa (use Lisabug
instead), I imagined that Macsbug's use of memory reflected the
expected limits of a Mac (i.e., never more than 512K).

The problem:  when I use Maxbug in my obese Mac (1.5 megabytes), the
code seems to be located just under the 512K boundary (as is normal),
but something related to Maxbug goes in the extended memory area.  The
symptom: when my 1-meg ramdisk is about half-full, the Mac falls into
a very confused Maxbug.  The screen is not cleared properly, and
Maxbug does not respond to commands (except with "HUH?").  When I run
without Maxbug, I can fill the ramdisk completely without any problem.

Does anyone know how Maxbug decides to place its data?  Is there any
way that other code can detect that Macsbug is running, and avoid the
contested memory area?

Ephraim Vishniac
  [apollo, bbncca, cadmus, decvax, harvard, linus,
masscomp]!wanginst!vishniac
  vishniac%Wang-Inst@Csnet-Relay

------------------------------

Subject: Blit emulation on the Mac
Date: 05 Jun 85 20:36:13 PDT (Wed)
From: tamir%ucbkim@Berkeley

Has anybody developed a Blit emulation program for the Mac ?  Many
people are using the Mac as a terminal connected to a UNIX system so a
Blit emulation seems like the obvious step up from various simple
terminal emulators.

For those who are not familiar with the Blit:
   The Blit is a programmable bitmap graphics terminal that
   was designed specifically to run with UNIX.
   With appropriate software on the host UNIX machine, the
   Blit provides an asynchronous multiwindow environment.
   This environment is similar to the multiwindow environment
   on a UNIX workstation (such as the SUN).
   For more info on the Blit see the Oct. 84 issue of BSTJ.

                                     Yuval Tamir ARPANET/CSNET:
tamir@Berkeley
         UUCP: ucbvax!tamir

------------------------------

Date: 4 Jun 1985 18:59-EDT
From: Kevin.Dowling@CMU-RI-ROVER.ARPA
Subject: Appletalk Cable components?

What is the commercial (non-apple) equivalent of the Appletalk cable?
Is there a Belden or Alpha Wire equivalent for this?

Connectors are undoubtedly more difficult to get ahold of but it may
be cheaper to buy cable from 3-rd parties and buy connector kits from
Apple if they're not second sourced.

                                        nivek

Aka :  Kevin Dowling Bell:  (412) 578-8830 Arpa:  nivek@cmu-ri-rover
Mail:  Robotics Institute
                                        Schenley Park
                                        Pgh, PA 15213

------------------------------

Date: 07 Jun 85 15:52 +0100
From: Michel_E_Debar_DECUS%QZCOM.MAILNET@MIT-MULTICS.ARPA
Reply-to: Info-Mac_Mailing_list%QZCOM.MAILNET@MIT-MULTICS.ARPA
Subject: How to run objective C?

Can someone give me pointers as to how I can get Objective C, or C++ 
to run on Vax/VMS, Vax/Unix, MacIntosh.

thanks, Michel

------------------------------

End of INFO-MAC Digest
**********************