Axiant Requirements?

[WITKOPP@IDT.COM]

Keep in mind the typical PC can't cache more than
64 megs, so as soon as you install more than that,
you slow down because PC's generally load memory
from the top down. i.e. the uncached portion. It's easy
enough to get a motherboard that caches > 128 megs, but
they aren't in your typical HP, or whatever, PC.

> I am a long time powerhouse developer (14+ years) who has just completed a
> sizeable system port from a hp3000/image/powerhouse application to nt/sql
> server/axiant.
> I would gladly participate in any online discussion and can also be reached
> at nextwaveinc@msn.com for any offline questions.
> I found that as a developer, "more is certainly better" in terms of RAM, and
> ultimately my workstation had 80 meg of memory (as a win 95 client).  Other
> client server tools were in use (sql database manager...) and this made my
> development work rather cleanly.
> Some other developers on the project had as few as 32 meg(not recommended),
> and generally 64 meg.  As far as deployment goes, if you are running thin
> client (highly recommended) the client footprint is rather small.  Most of
> our clents had 32 meg, and run fine, although 64 would be ideal.
> I could go on and on, but I don't want to bore anyone.  If you have any
> other specific questions, I would be more than happy to participate!
> -----Original Message-----
> From: Deskin, Bob <Bob.Deskin@Cognos.COM>
> To: 'powerh-l@lists.swau.edu' <powerh-l@lists.swau.edu>; 'Stewart, Mark'
> <MStewart@VICTORIA.COM>
> Date: Thursday, July 16, 1998 10:19 AM
> Subject: RE: Axiant Requirements?
> 
> 
> >Regarding RAM, it depends what you want to do. 40 Meg is a good starting
> >point. If you want to have lots of forms on the go at once, then more is
> >better. And RAM is cheap these days. The idea is to keep as much in
> >memory as possible for performance.
> >
> >The disk space is for Axiant and SQL Anywhere. You'll also need space
> >for you're application. Keep in mind this is a graphical development
> >environment. As a comparison, when I installed VB 5, it took about 130
> >Meg.
> >
> >Axiant runs on Win 95 and NT. We have not tested formally on Win 98 as
> >yet, but we haven't found any problems in informal testing.
> >
> >The latest release is 2.02. Version 2.03 is going into Field Test. It
> >provides terminal deployment as well as GUI.
> >
> >The extensions added to QDESIGN for PowerHouse Web will go into Axiant
> >2.04. It will be out later this year.
> >
> >Bob Deskin
> >Senior Product Advisor  bob.deskin@cognos.com
> >Cognos Inc.             (613) 738-1338 ext 4205 FAX: (613) 228-3149
> >3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9 CANADA
> >
> >
> >> ----------
> >> From: Stewart, Mark[SMTP:MStewart@VICTORIA.COM]
> >> Sent: Thursday, July 16, 1998 9:58 AM
> >> To: 'powerh-l@lists.swau.edu'
> >> Subject: Axiant Requirements?
> >>
> >>
> >> Does anyone know the minimum requirements for running Axiant on a PC
> >> in the
> >> Windows 95 environment?  I heard at the conference - 'more RAM the
> >> better'.
> >> Would 40 meg of RAM do the trick?  I also heard that it needs 100 meg
> >> of
> >> free disk space.  Can full development take place on a stand alone PC
> >> running 95/98.  How does Axiant work with Windows 98?  I'd appreciate
> >> any
> >> further information.  What is the very latest release available for
> >> Windows
> >> 95?  How far away is Cognos away from adding the Web enhancements to
> >> Axiant,
> >> roughly?  Thanks in advance.
> >>
> >> Mark Stewart
> >> PowerHouse 4GL Consultant
> >> Columbus, Ohio
> >> U.S.A.
> >> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> >> = = =
> >> Subscribe: "subscribe powerh-l" in message body to
> >> majordomo@lists.swau.edu
> >> Unsubscribe: "unsubscribe powerh-l" in message to
> >> majordomo@lists.swau.edu
> >> powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
> >> This list is closed, thus to post to the list, you must be a
> >> subscriber.
> >>
> >= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> >Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
> >Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
> >powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
> >This list is closed, thus to post to the list, you must be a subscriber.
> 
> 
> 
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
> Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
> powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
> This list is closed, thus to post to the list, you must be a subscriber.
> 
> 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.