🚀 go-pugleaf

Well if you want to preserve citadel's workings and just make two changes it 
would work just fine under forem...
Since forem takes the modem off hook on all local logins it would be
unecessary for the citadel running under forem to play with it... 
Hmm did I say two changes? anyways..
What forem will do is the following when it runs a door program.
It creates a file containing the users name and time information etc
(I think it would be best to ignore this for now though)
and then from its menu it will run the program just as the desktop would..
A programs entry in the menu looks like this..
Citadel
24
intro.txt
remote.prg
local.prg
exit.txt

The above line "Citadel" would be the menu name given to the user..
intro.txt would be printed while it was loading the program (exit.txt
is the exiting text)
the 24 is the user level that the person needs in order to run the program
the remote.prg would be the program taht would run if its a remote call and
local.prg would be run if it was a console login..
I think that if you let citadel accept a command line shutting off any sort
of line handling from citadel (Ie don't hang up the modem or even touch
the lines... Just check for carrier...) and had it look at the carrier detect 
at the initial run of the program to see if its a local call or not and handle
the text outputting accordingly it would work great..
When I ran Citadel on the st it was when the floor stuff was initially added
and there was nothing like a floor invite at the time...
I had alot of people that liked citadel alot but at the time there were not
enough features in it.. So I went to forem.. I should be able to add citadel
real easy since the way citadel works is very simular to things forem allows..
Citadel will run easily under 512k I do assume..
(I hope you were able to pull out something out of this garbage.. I cvant seem
to type straight this morning..)