Angus Hewlett wrote: > > From: Angus Hewlett <angus@...> > > At 16:06 02/12/99 +0100, you wrote: > >From: "Frank W.Kooistra" <pipeline@...> > > > >Angus Hewlett wrote: > > >> and the stupid, totally over-the-top GUI, which hogs RAM even when you > >> don't want it - i.e. GUI is loaded even when Pulsar is running in system > >> tray mode - and uses insane amounts of CPU cycles for its glows, > >> alpha-blends, shadows, etc. > > > >Hmm bit overreacting : but i can imagine if your system is just too > >small. > > Sure, my system is too small for Pulsar, that's obvious. Only thing is, the > system in question is a 333MHz p2, 160M ram, Asus mobo, decent graphics > card. Which _should_not_ be too small to control a DSP accelerator board :-) > > Also, it's well within the recommended minimum spec. > > >I do not get what you mean with system tray mode ( I guess when you just > >see the connection diagram) > > >there is a mode which is quit useful , when you do not need interactive > >access : this is the mode which is started in winstart.pro : In this > >mode you can use the card as a multi I/o card with out the overload of > >gui. winstart.pro is configurable so routing to emagic is possible .. > > Yes, but if you use devices in winstart.pro - which is what I mean by > system tray mode - their graphics are still loaded in to mem even though > you can't see them! Look at Windows System Monitor, compare mem. usage > between winstart.pro in the task tray and open in the full program - almost > identical memory use. OK I simple route un winstart pro ( adat to asio and so on ) Minimum system ram -- I advice 256MB ( my god Ram not a HDU) as a minimum.. regards frank