In a message dated 4/11/01 4:44:42 AM Eastern Daylight Time, [log in to unmask]
writes:
<< Anyway - here is a question, has anyone got any opinions on HyperResearch
as
a package - we're all running on iMacs here and so our choices of software
are restricted. Although we do have n4, we are interested in looking at
other options, so Hyper has arisen as a possibility. What are the specs?
Would iMacs be able to cope? >>
HyperRESEARCH 2.03 should work just fine on an iMac, if you're running Mac OS
9 (or Mac OS X in classic mode). We're working on a Carbonized version for
Mac OS X. We recommend 64MB+ of RAM (as with most applications, the more the
better).
I'd like to invite you to try HyperRESEARCH out for yourself as that's really
the best way to decide whether a given QDA software package is right for you.
(In fact, if you can borrow a Windows machine, I suggest you try some of the
packages available for Windows as well, such as Atlas TI -- once you find the
right package, you can determine if it's worth the extra expense to either
switch to Windows or get a Windows emulator for your iMac....)
As a Mac afficionado, and as HyperRESEARCH's documentation/tech support
specialist, I highly recommend HyperRESEARCH, but I'm obviously biased. :-)
Anyhow, for a free trial version go to http://www.researchware.com/demos.html
and download the "Macintosh PowerPC Demo Version." This is a fully
functioning version of HyperRESEARCH 2.03 -- except that the "save" and
"print" commands are disabled.
You can see some tutorials online at
http://www.researchware.com/tutor/tutorials
If you're feeling adventurous, you can sign up as a betatester for our latest
version, HyperRESEARCH 2.5b2. The online application form for betatesting
status is at http://www.researchware.com/BetaTestForm.html
Being a betatester will give you a sneak preview of the latest version, which
sports numerous improvements over the currently shipping version (2.03) --
including improved performance, and fixes for the known bugs in version 2.03
(problems with printing, problems with displaying the Codes in Context
feature, etc.). Just be aware that becoming a betatester has its privileges
(helping us make the program better, ensuring that your suggestions for added
features for future releases will be considered, getting a free version of
the software if you submit regular betatest reports, etc.) -- but also its
duties (submitting those reports, especially if you encounter any problems!)
and hazards (it *is* a betatest version, not deemed ready for commercial
release because of known and unknown problems -- please help us discover
those unknown problems and test our fixes for the known problems!).
whew! :-)
Best regards,
Ann Dupuis
ResearchWare, Inc.
http://www.researchware.com
[log in to unmask]
[log in to unmask]
|