When is Version1.0 expected to be available and what will change?
We hope to release Version1.0 in a few months. The primary changes will
be bug fixes. The internal interfaces will not change beyond necessary
changes for bug fixes.
What platforms is PREDATOR supported on?
Version 0.95 (pre-release of Version 1.0) runs on PCs with
WindowsNT4.0 and higher. It also runs on Sparc workstations running Solaris2.5.1
or higher.
Is there a binaries-only release?
The current pre-release is in source-code form only. Version1.0 will have
a binaries version as well.
Is PREDATOR supported under x86 Solaris or Linux?
Unfortunately, PREDATOR has not been tested under either environments, and so Predator is not supported on x86 Solaris or Linux. However, we recently found out that there is now a version of SHORE that supports the Linux environment. You can reach the SHORE homepage at http://www.cs.wisc.edu/shore. Since PREDATOR is written with a rather generic C/C++ code base, we believe that PREDATOR will also run under Linux provided you are using the Linux-compatible version of SHORE. Note, however, that because we never tested PREDATOR using the Linux or the new Linux-compatible SHORE, it is highly possible you will encounter problems that we are unfamiliar with and cannot reproduce; consequently, when such problems occur, we may not be able to assist you.
Does a JDBC driver manager already exist?
Yes, we have an internal version of a JDBC driver which we hope to release
with Version1.0.
Does an ODBC driver manager already exist?
Yes, we have an internal version of a ODBC driver which we hope to release
with Version1.0.
I had some difficulties when trying to download the postscript file for "design and implementation document". When I run GhostView to see it, I got many error messages.
First, our old (and wrong answer):
This may be because it is in Postscript 3.0. MS Word automatically generates PS 3.0, while GhostView usually can only handle 2.0. We suggest that you try printing it directly, or instead use the html version of the document. We know of no simple solution.
Now, the right answer from Dan Riley:
Since this is apparently a FAQ, I thought you might like to know the real
story. First, word generates PS level 2, not 3--the PS-Adobe-3.0 indicates
the version of the postscript document structuring conventions the document
follows, not the postscript version. The reason the document fails in
ghostview is because Microsoft violates the document structuring conventions
they claim to follow; printers don't look at the document structuring
conventions (they just look like comments to printers), but ghostview needs
them so it can jump to arbitrary pages. If you apply the enclosed patch
(which just moves one comment by one line) it will work fine in ghostview.
I have no clue why Microsoft haven't fixed their postscript generation.
Here's the diff:
*** designdoc.ps~ Mon Jul 20 14:54:39 1998
--- designdoc.ps Mon Jul 20 14:55:41 1998
***************
*** 52,59 ****
<setpagedevice
%%EndFeature
} stopped cleartomark
- %%EndSetup
NTPSOct95 begin
%%Page: 1 1
NTPSOct95 /PageSV save put
13.238 780.059 translate 72 600 div dup neg scale
--- 52,59 ----
<setpagedevice
%%EndFeature
} stopped cleartomark
NTPSOct95 begin
+ %%EndSetup
%%Page: 1 1
NTPSOct95 /PageSV save put
13.238 780.059 translate 72 600 div dup neg scale
--
Dan Riley dsr@mail.lns.cornell.edu
Wilson Lab, Cornell University
Mail user support: predator-support@cs.cornell.edu
.... Back to PREDATOR Home Page