#1 startFIPAOS problem on Win ME

[Anonymous]

As a newbie to FIPA-OS I hope neither of the two
questions below show too much of my lack of
knowledge! Here goes anyway:

1) I'm trying to do some multiple platform development
(Notebook running Win ME plus desktop running Win 95)
and am having a problem starting up FIPA-OS on the Win
ME machine.

(a) if I just run startFIPAOS from a msdos prompt, I
get errors when the ACC tries to start as the NS
haven't begun since they have been started with the /m
option (I think?).

(b) I tried changing the START_SWITCH option to /max
instead but this just causes the msdos window I typed
the command in to become unresponsive.

(c) I can work around this by manually clicking on
various windows after I've typed startFIPAOS, but
there's got to be a better way (?). Note that with
this work-around, I'm able to get cross-platform
communications to work fine.

=> Is there something I can change to have FIPA-OS
start up more smoothly on this machine or is it my own
fault for trying to use Win ME?

{One puzzling thing here ... I thought I had managed
to get this to startup fine yesterday with the /max
option, but today, no dice!}

2) I've configured both platforms, using startConfig,
to use "MemoryDatabases" in both acc and default
profiles. With this setting I expected my databases
directory to stay empty but it does not. When I shut
down the platforms on my two machines, there are
subdirectories and files in the databases dir.

=> Is this proper behaviour, and in indicator of my
ignorance (in which case, I apologize for bothering
you with it) or it this anomalous?

Thanks, in advance, for your consideration.

Yours

Paul Rogers (rogers@enme.ucalgary.ca)

P.S. I tried to log in before submitting this but it
wouldn't let me ... is it seeking my mailing list
details (id & password) or is there something else I
should have joined?

[Alan Treadway]

Logged In: YES
user_id=40816

1) a) The "start" /M option should simply minimise the
window - unfortunately we haven't got a WinME test machine,
but I would imagine that you would want to use /MIN rather
than /MAX to duplicate this (this is the case for Win2k at
least)

b) Again, I'm not sure why this would be the case unless
the /MAX option does something different in WinME - check
by typing "start /?" at a command prompt

c) Ditto.

2) The settings for databases in the Configurator are not
the only ones - the AMS and DF override these settings in
their own profiles (ams.profile and df.profile), hence the
creation of persistent DB's for these Agents

The username and password that is being requested are your
SourceForge username/password NOT your mailing list username
(?)/password - unless you're actively participating in an
Open Source project at Source Forge, its unlikely you'll
have one of these (although anyone can sign up)