Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!src.honeywell.com!msi.umn.edu!cs.umn.edu!ux.acs!clarson
From: clarson@ux.acs.umn.edu (Chaz Larson)
Newsgroups: comp.sys.mac.misc
Subject: Re: Afterdark 2.0t question
Message-ID: <2743@ux.acs.umn.edu>
Date: 19 Nov 90 18:58:11 GMT
References: <1990Nov15.214311.6536@cunixf.cc.columbia.edu> <1990Nov17.064008.5168@silvlis.com>
Reply-To: clarson@ux.acs.umn.edu (Chaz Larson)
Organization: Iron City, USA
Lines: 36

In article <1990Nov17.064008.5168@silvlis.com> jimb@silvlis.com (Jim Budler) writes:
|In article <1990Nov15.214311.6536@cunixf.cc.columbia.edu> cmm1@cunixa.cc.columbia.edu (Christopher M Mauritz) writes:
|>I just bought Afterdark.  It is version 2.0t.  It works on other machines
|>that I've tried it on, yet not my MacIIcx at work.  The only difference I
|>can think of is that the machine at work uses system 6.0.7 while the 
|>others use 6.0.4.  Is there some sort of incompatibility problem?
|
|It runs fine on my MacIIsi. In fact according to a note on Compuserve
|the bug fixes in 2.0t include 6.07 sound manager compatibility fixes.
|
|So your problem is not likely to be 6.07. 

Check the date on the problem machine.  This was the cause of an odd AD problem
on my system.  Let me explain.

I purchased After Dark 2.0t on October 28, and installed it that day.  A couple
of days later, I was given an evaluation version of QuicKeys2 that would only
run until October 15, 1990.  So, in order to get a look at QuicKeys2 [which, by
the way, I have yet to receive upgrade info for], I set my clock back to October
1, 1990.  When I rebooted the machine, both icons showed up.  QuickKeys Eval
worked just fine; however, whenever After Dark kicked in, all that would be
displayed was the Starry Sky module, which now featured a scrolling message
stating "Randomizer module requires After Dark version 2.0."  This happened
with all modules, not just Randomizer.  When I set the clock ahead to the real
date, After Dark worked just fine.

I'm puzzled by this.  These modules couldn't possibly be checking for After Dark
2.0 using the _date_, could they?

chaz



-- 
Someone please release me from this trance.
clarson@ux.acs.umn.edu                                       AOL:Crowbone