Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde!uunet!samsung!brutus.cs.uiuc.edu!usc!apple!claris!wombat From: wombat@claris.com (Scott Lindsey) Newsgroups: comp.sys.apple Subject: Re: AWGS 1.1 Keywords: bat, photography, monk, seven Message-ID: Date: 5 Dec 89 23:02:04 GMT References: <8912050042.AA15991@decwrl.dec.com> <1989Dec5.195806.13131@ncsuvx.ncsu.edu> Sender: wombat@claris.com Organization: Claris Corporation, Santa Clara, CA Lines: 54 In-reply-to: rnf@shumv1.uucp's message of 5 Dec 89 19:58:06 GMT Subversive: KGB In article <1989Dec5.195806.13131@ncsuvx.ncsu.edu> rnf@shumv1.uucp (Rick Fincher) writes: > Everything is generally faster, particularly the spread sheet which is several > times faster. Modules load faster. Support for networked imagewriter II's is > included, as well as for AppleTalk in general, it is not multi-launch, though. Specifically, it is single-launch on a AppleShare file server. Originally, marketing wanted me to make it 0-launch, but I was able to convince them otherwise. > I presume the database files are not byte range locked but I haven't had a > chance to see yet. Byte Range Locking allows multiple users to work on the > same database (or other) file simultaneously (Scott- any word on this?). No, byte range locking is not done (does anyone know if this capability is even available through GS/OS?) DB is a memory-based database... it loads the entire database into memory and works with it there. In general, AWGS does not have "good" support for a network environment. This is mainly due to its design (back before System 3.2 and any hint of the IIgs being a network machine). AWGS opens files, reads them, closes them, lets the user modify them... if the user saves, the file is opened, truncated, and rewritten. This means that users have the capability to change files out from under each other on a fileserver. > The > different disk format for the database is puzzling. The database program > seems otherwise unchanged. Did they do this so the DB files would load faster? > Or, to make the files more compatible with FileMaker (a Claris Mac product)? There is some speed gain, but the main reason was an internal data structure change in DB. > Or maybe to conform with Claris' proposed file exchange standard? I assume you mean XTND? XTND has to do with providing a mechanism for reading other file formats, whatever they may be, so there's no particular reason for a file format change for compatibility here. > The new printer drivers help a lot. Personnaly, I find the improved draft > mode performance to be the biggest help here. If you printed in draft mode > before and set the ImageWriter II to NLQ, that was turned off at the beginning > of each page. Graphics mode printing is just too slow for business purposes, > although the speed has improved in the new version. So, being able to print > in NLQ without doing anal calisthenics is a big plus. The funny thing is that the opt/cmd key modification to the ImageWriter driver was done at the last minute as a "hidden feature" because I thought it might appease a few vocal users who wanted to use NLQ or Correspondence modes. Scott Lindsey |"Cold and misty morning. I heard a warning borne in the air Claris Corp. | About an age of power when no one had an hour to spare" ames!claris!wombat| DISCLAIMER: These are not the opinions of Claris, Apple, wombat@claris.com | StyleWare, the author, or anyone else living or Dead.