home *** CD-ROM | disk | FTP | other *** search
- Hi Folks,
-
- It took a little longer than I expected (doesn't everything) to
- straighten out E/NS 1.99p6, because there were a couple other severe
- problems to be addressed, but BleedingEdge contains E/NS 1.99p6 now.
- Unfortunately I'm having trouble forcing vorlon.mit.edu to do a
- mirror, so you can expect ftp.ardi.com to be pretty busy until people
- can use vorlon, too.
-
- I'm now going back to work on getting 1.99p6 out for DOS and Linux.
-
- For the benefit of our NEXTSTEP users,
- ftp://ftp.ardi.com/pub/BleedingEdge/NEXTSTEP/README is included below.
-
- --Cliff
- ctm@ardi.com
-
- executor-nextstep-199p6.tar.gz contains a complete Executor/NEXTSTEP
- distribution (Fat: Motorola + Intel). The installation procedure is a
- little non-standard, but it's the first Motorola release we've had in
- a while and we know people have been waiting for this, so we made it
- available as a bleeding edge release as soon as we could.
-
- Shortly after 1.99p6 was first made available for Executor/NEXTSTEP,
- our customers quickly pointed out three fairly major bugs. Here are
- descriptions of the bugs and workarounds:
-
- 1. Summary: ardimods was not included in the original distribution
-
- Symptom: Executor would not start up and "ls /LocalApps/Executor.app"
- would show that there was no directory "ardimods" in
- "Executor.app"
-
- Solution: We repacked the 1.99p6 distribution to include the ardimods
- directory and also made the contents of that directory available
- as the file "ardimods.tar.gz"
-
-
- 2. Summary: Making Executor "Fat" broke our registration code
-
- Symptom: NEXTSTEP/Motorola users could not use the supplied temporary
- serial number and authorization key to register Executor.
-
- Solution: We repacked the 1.99p6 distribution with a modified INSTALL
- shell script which will automatically "thin" the Fat Executor
- binary. The drawback is this means that /LocalApps/Executor.app
- can only be run on machines with the same architectures as the
- machine which Executor is initially installed from.
-
-
- 3. Summary: Unexpected Executor termination can corrupt DirectoryMaps
-
- Symptom: After quitting Executor, Executor refuses to start up again
-
- Solution: We repacked the 1.99p6 distribution to include a modified
- executor-nextstep.readme file with this advice:
-
- If you find Executor refusing to run, try typing this
- at the command line:
-
- sh -c 'for f in /LocalApps/Executor.app/DirectoryMap*; do > $f; done'
-
-
- All three of the above bugs should be fixed in 1.99p7, which we hope
- to have out as soon as we've collected all the "showstopper" bug
- reports from all the 1.99p6 distributions.
-
-