stiber@cs.ucla.edu (Michael D Stiber) (12/08/89)
I would like to use WindChooser for the "Shrinker" WDEF, which seems
quite handy with Multifinder. There's only one problem -- an
incompatibility with DiskLock. For the uninitiated, Disklock unmounts
the hard disks after a certain amount of idle time, requiring a
password to remount them. The problem is that, after Disklock
unmounts the disks, some event must take place that requires the WDEF
to do something (most likely having something to do with blanking the
screen -- my guess).
My speculation is that WindChooser installs a patch which reroutes
calls to WDEF #0 to the WDEF selected within it. Here lies the
problem. After the disks are unmounted, calls to the WDEF apparently
require accessing the WindChooser file. Since the hard disk is
unmounted, this means we get a "Please insert disk FOO" dialog box,
defeating the purpose of the screen blanking. I tried to unset the
purgeable and set the locked bits in the WDEF, but this didn't solve
the problem.
So, my question is this: is there any good way to install the
"Shrinker" WDEF into the system, so it will work just like the default
one does, without interfering with DiskLock? I already tried just
replacing the WDEF #0 in the system, but this didn't change the window
appearances. Therefore, I have reasoned that the critical WDEFs
aren't in the System. So, what's the technique? I thought that's
where all of that stuff was kept?
Thanks in advance to all you Mac gurus out there.
--
Michael Stiber
stiber@cs.ucla.edu UCLA Computer Science Dept.
...{ucbvax,ihpn4}!ucla-cs!stiber Machine Perception Laboratory
3564 Boelter Hall,Los Angeles, CA 900246600pete@hub.UUCP (12/08/89)
From article <STIBER.89Dec7220457@maui.cs.ucla.edu>, by stiber@cs.ucla.edu (Michael D Stiber): > My speculation is that WindChooser installs a patch which reroutes > calls to WDEF #0 to the WDEF selected within it. Here lies the > problem. After the disks are unmounted, calls to the WDEF apparently > require accessing the WindChooser file. Since the hard disk is > unmounted, this means we get a "Please insert disk FOO" dialog box, > defeating the purpose of the screen blanking. I didn't write the INIT part of WindChooser, just the cdev. But I have the source to the INIT, which was written by Jorg ("jbx") Brown, of hierDA fame. I will take a look at the code and see what's happening. However, I seriously doubt that a look at the disk is required. More later... > So, my question is this: is there any good way to install the > "Shrinker" WDEF into the system, so it will work just like the default > one does, without interfering with DiskLock? There's a thread in comp.sys.mac.programmer about how to do this. > I already tried just > replacing the WDEF #0 in the system, but this didn't change the window > appearances. Therefore, I have reasoned that the critical WDEFs > aren't in the System. They're in the ROMs. Lots of resources are nowadays. A good thing, too, or you wouldn't be able to make a usable System floppy... ------------------------------------------------------------------------------- Pete Gontier | InterNet: 6600pete@ucsbuxa.ucsb.edu, BitNet: 6600pete@ucsbuxa Editor, Macker | Online Macintosh Programming Journal; mail for subscription Hire this kid | Mac, DOS, C, Pascal, asm, excellent communication skills
d83_sven_a@tekno.chalmers.se (SVEN AXELSSON) (12/09/89)
In article <STIBER.89Dec7220457@maui.cs.ucla.edu>, stiber@cs.ucla.edu (Michael D Stiber) writes: > I would like to use WindChooser for the "Shrinker" WDEF, which seems > quite handy with Multifinder. There's only one problem -- an > incompatibility with DiskLock. [stuff deleted] > So, my question is this: is there any good way to install the > "Shrinker" WDEF into the system, so it will work just like the default > one does, without interfering with DiskLock? I already tried just > replacing the WDEF #0 in the system, but this didn't change the window > appearances. Therefore, I have reasoned that the critical WDEFs > aren't in the System. So, what's the technique? I thought that's > where all of that stuff was kept? > > Thanks in advance to all you Mac gurus out there. > -- > Michael Stiber > stiber@cs.ucla.edu UCLA Computer Science Dept. > ...{ucbvax,ihpn4}!ucla-cs!stiber Machine Perception Laboratory > 3564 Boelter Hall,Los Angeles, CA 90024 The WDEF 0 resource is actually in ROM (on all machines with 128K or 256K ROMs), so you must tell the system to use the new resource in the system file instead of the one in ROM. Do this by editing the ROv# resource corresponding to your Rom-version (or change it in all of them if you don't know the version). You should insert a new entry here with type=WDEF and id=0. This will make the system work the way you want. +-------------------------+--------------------------------+------------------+ | Sven Axelsson | d83_sven_a@tekno.chalmers.se | DISCLAIMER: | | dep:t of Linguistics | (^^ best ^^) | | | univ. of Gothenburg | dlv_sa@hum.gu.se | This is not | | SWEDEN | usdsa@seguc21.bitnet | a disclaimer. | +-------------------------+--------------------------------+------------------+