home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: alt.galactic-guide
- Path: sparky!uunet!ftpbox!news.acns.nwu.edu!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!eff!news.oc.com!mercury.unt.edu!vaxb.acs.unt.edu!il67
- From: il67@vaxb.acs.unt.edu
- Subject: Re: Getting AmiGuide to work.
- Message-ID: <1993Jan27.155004.1@vaxb.acs.unt.edu>
- Lines: 30
- Sender: usenet@mercury.unt.edu (UNT USENet Adminstrator)
- Organization: University of North Texas
- Date: Wed, 27 Jan 1993 21:50:04 GMT
-
- In reply to your problem with AmiGuide (sorry it took me a while to reply),
- it should be creating a temporary file in RAM called Index1, and not
- "Index 1". I'm not real sure what could be causeing this. I do know the
- reason for the all too many disk swaps, which could only be corrected if
- you put AmiGuide on a stripped down workbench disk..
-
- Actually, I have done some more work on it, and plan to release a new
- version pretty soon. (2.0) AmiGuide (as criticized) is currently very
- slow. The next version (AFTER 2.0) will almost definately be written in
- C. I have looked into using the AmigaGuide standard for storing the files,
- (3.0) but I was not certain as to what and how the AmigaGuide standard
- handled such big databases. It would defeat the point of using the Amiga
- Guide standard if it couldn't properly X-reference articles. And I know
- Hyper takes up a lot of memory (I assume because of the size of the file)
- but I'll look into it. If any Amiga programmers are out there, and think
- they can beat me to a C version of an Amiga Guide reader - go for it. I
- have no idea when it will be complete (I am also co-writing a BBS, so a
- lot of my time is being eaten up.)
-
- Good luck, (expect a new version of AmiGuide up within 7 days or so,)
- James Palmer
-
-
-
-
-
-
-
-
-
-