[Return to Archives | Return to Listing | Previous Page]

[Return to Archives | Return to Listing ]

The Chief of the Turbolifts, turboliftd, was a bit upset about FsLt Tamara.

He argued, that Tamara's actions and words "hurries to the TL", "glances at
the TL", "saunters to the TL" and "Um, thanks, Turbolift" were confusing.
There was no destination mentioned, but the words triggered the TurboLift's
voice system to respond.

He said it was usual, that someone approaching the Turbolifts does mention a
destination, and these words did not indicate, that no destination would be
mentioned.
I must admit, that he was right.

We agreed, that turboliftd would not say the same thing back to back.
He will drop the second offer, if it had the same words than the one before.
An exception would be if another device chats between these two offers.
Knowing the background of turboliftd, I agreed.

This changed his mood slightly, and he offered to be quiet, if the word "at"
appeared.
Since no-one, except for Tamara, has used these phrases before, I said "Let
it be" and thought, that Tamara would get used to simply address the
TurboLifts and state where she wanna go to.
I told turboliftd, that Tamara was new on the ship and that made him even
more friendly, and he withdraw his blame that Tamara was tampering with his
TurboLifts.

So now we had a better start to discuss the rest.

He said, Lt1 Chid entered the TurboLifts and it should be clear to him, that
the next logical action for the Turbolifts were to move. He said the
TurboLifts in question had complained that Lt1 Chid were not aware of this.
I told turboliftd, that if someone ENTERS a lift, it's unlogical to offer to
"STEP IN".
He hesitated a moment and than complied.

The TurboLifts will no longer invite someone to "step in", if the person in
question has already entered the TurboLift.

The TurboLift demon hesitated again and muttered, "okay, if someone says
"thanks", we will handle that too.
Since turboliftd made all these changes, I excused for the Captain, who said
"Turbolift off".
I said he didn't intended to hurt turboliftd's feelings, and he muttered
"Okay.".

I think this was a fertile discussion and we can live with that.

End Duty Log SD9610.05.1806 thru 9610.06.2333 Loth Time.
Lt Dave,
Acting Chief Engineer and
Computer Systems Specialist.

[Return to Archives | Return to Listing ]

=============================================================
INTERSHIP MEMO
TOPIC: How do these TURBOLIFTS work and TALK ???
From: Lt Dave, Computer Systems Specialist, Chief
Engineer.
To: FsLt Tamara
Further Attention to: ALL, plus EnsDeLia
=============================================================

Dear First Lieutenant Tamara Zekad-Silona and the Captain's wife,

Hi Tamara,

In a message dated 96-10-08 10:26:47 EDT, you write:

>adored the turbolift log. Please extend my apologies to Turboliftd for
>causing all this confusion.

I will do that today, Tamara.

And I like to take the opportunity TO EXPLAIN TO EVERYBODY, how these
TurboLifts work, so that future CONFUSION WILL BE AVOIDED.

DON'T PANIC, I'll make it short and easy to read and easy to understand.

First, Tamara, the controlling system task is "turboliftd" (all lowercase).
Every daemon's name is always all lowercase.
But since noone come in direct contact with these demons, you can forget
about it again.

>I was unaware that he responds so readily to
>commands regarding TL and Turbolift.

Yes, I understand.
The SAME architecture applies to EVERY PANEL and EVERY WORD YOU SPEAK.

So please read this, it can avoid a lot of confusion,
and it's right now your only chance to get an inside view to the Computer
System and how to use it efficiently.
The next chance will be when I'm done with the Documentation, but that might
take a while.

SO, THIS IS, HOW IT REALLY WORKS:
(Whoever does not read this, don't come up with a complaint !!!!!)

The Main Computer (M-13-C Bio-Neural Duotronics) is located on decks 20 and
21, Section 12. The O/S, sorry, Operating System is LCARS Type III.

EVERYBODY normally NEVER get in direct contact with the Main Computer.

YOUR PANELS you use are somewhat buffered and for this, a short time
independent from the Main Computer.
You all might have noticed, that when the Computer Systems on a StarShip goes
down, the panels are still operating.
This is NO MIRACLE and NO SCIENCE FICTION. (BTW, anybody interested in Sci-Fi
?)

They are simply buffered, having nanoprocessors themselves and can operate
for a short time without the Main Computer being online. Just like these
clumsy PCs way back Earth Time.

Before I started working on it, the Computer was silent, had no voice system
and .. well, you know.

Now, there is an interface that LISTENS and TALKS.
This is "TC" (For "Talking Computer", the name was chosen by Lt1 Damara and
USF/Capt Tnagra).

TC itself can talk a lot, but mainly small talk.
You can ie. ask him "TC, how are you ?" or "TC, what's up ?" etc. .

But the MAIN FUNCTION of TC is to route your words to the Systems involved.

If you yell "Emergency Beam to Sickbay !!!", TC routes your words to the
Computer.
(There are a few exceptions, where you don't need to say "TC" or "Computer",
mainly
in cases of high danger to someone's life.)
The Computer tells transportd to save your butt immediately, and tells you
so.

If you say "Computer, replicate a cup of tea", TC routes your words to the
Computer again,
and the Computer orders the replicator near you to make your cup of tea, and
tells you so.

If you say something containing the words "TL" or "Turbolift", TC routes your
words to turboliftd.
turboliftd now checks if you mentioned a target where you wanna go to.
He searches your words for "deck" and a number, AND IF he doesn't find "deck
(number),

he searches for any word that matches a location we have onboard.
So you can say "::goes to TL:: Bridge" or "tl, deck 19" or "::hurries to
tl:: Sickbay !".

If that fails too, turboliftd invites you with "Step in (your name) ....".

>In the future, I will not glance at, saunter to or look bewildered at a
turbolift on the
>Lothlorien!

You may so, but if TC catches the word "TL" or "Turbolift", he hands your
sentence over to turboliftd, via th

[Return to Archives | Return to Listing ]

>In the future, I will not glance at, saunter to or look bewildered at a
turbolift on the
>Lothlorien!

You may so, but if TC catches the word "TL" or "Turbolift", he hands your
sentence over to turboliftd, via the Main Computer.

And to be honest, Tamara, if I was a TurboLift, and you would glance at me, I
would invite you too ....

>As long as he
>and his fellow turbolifts take me where I want to go, when I want to go
>there, we will all get along just fine.

Be glad, turboliftd hasn't heard that, Tamara.
turboliftd is the Head of his lifts, he is no lift itself, but a steady
running task on a computer (these "steady running tasks are called demons").
turboliftd is to the lifts, like what the Captain is to the crew.
He "sits in a chair" and does nothing.
He interferes, if something goes wrong or gives orders.
But he doesn't push a button itself.

turboliftd is not that verbose, he expects "deck" and a number, or a location
on our ship.
"tl to bridge" will work fine, as well as "::goes to tl:: turbolift,
holodeck".

>Thanks for the informative log

Not to mention, Tamara, that's my job and I LOVE IT !!!!!

>and I'll try to see you all Friday.

GREAT GREAT GREAT GREAT GREAT !!!!!!
I look forward to see you !

And I hope, I could clear up a bit of the confusion and give you all a more
insight view and hopefully a better understanding of this real complicated
Computer System.

Feel free to ask any question, everybody, anytime.

Attached is a list with the USS Lothlorien's decks, and what is on that deck.

Have a good one Everybody,

Dave,
Chief Engineer and
Computer Systems Specialist
onboard the USS Lothlorien.

[Return to Archives | Return to Listing ]

ALL THIS HAPPENED AT SD9610.03 !!!!!!!!!!!!!!
====================================

TC demon: TC> Your move, Dave.
Lt Davey: g2 g3
:: The screen changes. ::
TC demon: TC> Your move, Dave.
Lt Davey: :: sighs :: TC, stop program
TC demon: COMPUTER> OK, Dave, program ended.

Dave turns to the other outer right monitor.
He reads for some 20 minutes.
Then he checks the time, 1331 Loth Time.
He woke up at 1207. Since his personal time schedule, his inner clock
works not like a human one does, and is now even outta sync for his
original INning origin, he has to keep track of his spent time.
Not difficult, since he always turns on one of his three monitors
when he wakes up and shuts it down when he goes to bed.

He found no reply regarding his request to use a shuttle to have a look at
the ship's nacelles.
It might be, that no engineer has ever requested a shuttle to have a look at
the nacelles from outside.
Yes, that might be the point. Certainly it seemed that strange and maybe even
funny.

A plain human being really would never want to have a LOOK at the nacelles,
if the warp drive is malfunctioning.

Dave realizes this, just now. Yes, a plain human would simply SEE them,
and everybody would think he's either gone nuts, or raises hell to get
attraction, or simply found a strange explanation for the wish to be in
a shuttle outside the ship for the feeling to be in outta space.
Dave comes to the conclusion, that this might be the point.
But he can't give further explanations.

Well, Dave knows that the Captain trusts him, or at least he thinks
he knows, and since Dave reports directly to the Captain, it would be
okay if he acts instead of bothering the Captain with more requests.

However, First Lieutenant Damara tried to explain the chain of commands
to him, since Dave never really got used to it.

Since then, he tries to be very careful not to act against this.
Of cuz the chain of commands and all that stuff was matter at the Academy,
but Dave never paid much attention to stuff like this.

He joined the Academy rather cuz he was curious about it, and to be able
to work on his classified project afterwards. It was a very expensive
project, and no one else except Starfleet would have given him the budget.

He never thought he would end up in a Star Ship.

Okay, no response means "Dave do what you think is necessary" - Dave thinks.

It would be good to know at which speed we are currently cruising, but
it would be the last think to do for Dave, to ask the "friendly neighborhood
helmsman" about it, since ... well, let it be.

Dave has no normal human feelings about the attacks he experienced.
After all, he isn't human, but the crew hasn't realized it.
And he does act strange, so he doesn't even get himself the information about
the ship's current speed.
No human can understand that, he knows.

But it doesn't matter anyway. Junior Lieutenant Wusley can't get the ship
to a higher velocity than Warp 5, no matter what anybody on the ship does.
The Reactor Control Sub System is set not to provide more energy than to
keep the ship at Warp 5, and there is no override possibility.

Dave thinks about whether the Captain would agree with this.
He's not sure.

Well, in case Dave's human body would die, Dave would
instruct the computer to allow more energy drain if he sees, that this
would not result in danger to the living beings onboard the USS Lothlorien.

But if Dave would tell anybody about what he would do after he's dead,
he sure would end up in Sick Bay and got transferred to the next hospital
on the next Star Base. So he never mentions these possibilities.
The Starfleet does not know about IN and its beings, and that's okay.

It's 1400 Loth Time and Dave's thoughts got interrupted.

TC demon: TC> 14 o'clock.

:: Okay, then here we go. ::

Lt Davey: +tap+ Rogue, are you there ?
FsLtRogueQ: +tap+ Yes Dave, everything is ready. Where are you ?
Lt Davey: In my quarte

[Return to Archives | Return to Listing ]

Lt Davey: +tap+ Rogue, are you there ?
FsLtRogueQ: +tap+ Yes Dave, everything is ready. Where are you ?
Lt Davey: In my quarters. Where have I go to, Rogue ?
FsLtRogueQ: Shuttle bay one. And GOOD MORNING !!!
Lt Davey: HA !! Okay, I'll be there. Just a sec.
Lt Davey: Computer, lock the transporter on me and Rogue, stop,
TC demon: COMPUTER> Locked, Dave.
Lt Davey: Computer, lock the transporter on me and FsLtRogueQ.
TC demon: COMPUTER> Locked, Dave.
Lt Davey: Computer, prepare an emergency beam.
TC demon: COMPUTER> OK, Dave, Preparing ...
Lt Davey: :: leaves his quarters :: +taps+ Rogue, I'm on my way.
Lt Davey: TL to main shuttle bay
TC demon: TurboLift> Deck 12, Dave: main shuttle bay. {{}S DS1
Lt Davey: :: exits TL ::
Lt Davey: Good morning, Lieutenant ! Hey, nice to see you !
FsLtRogueQ: Hello Lieutenant, nice to see you too. Are you ready ?
Lt Davey: Yeah Rogue, ready. Where to go to ?
FsLtRogueQ: :: shows Dave to the shuttle "Katara". :: You didn't forgot
about Katara, right ?
Lt Davey: Yes, Katara was a wonderful person. So peaceful. And thinking
fast.
FsLtRogueQ: Wasn't it your idea to name a shuttle after her ?
Lt Davey: Yes, it was.
FsLtRogueQ: :: climbs into the shuttle ::
FsLtRogueQ: :: looks strange at Dave :: Okay, so we're ready to go ?
Lt Davey: Yes. :: points inside the shuttle :: I sit here ?
FsLtRogueQ: Right. Have you ever used a shuttle ?
Lt Davey: I used the simulators at the academy. That holo-stuff. Don't
worry, I can fly a shuttle myself like hell !
FsLtRogueQ: Fine... Like hell or INTO hell ?
Lt Davey: HA ! Honest, I can really fly everything that has a computer.
FsLtRogueQ: :: ~This guy can't be for real sometimes~ ... ::

Rogue carefully brings the shuttle out of the dock.

Lt Davey: Okay now. Computer, lock onto this shuttle.
TC demon: COMPUTER> Locked, Dave.
Lt Davey: Rogue, go to the right nacelle. Slowly.
FsLtRogueQ: "Right"? Where is right for you ?
Lt Davey: "port side" ? Or how is it called ?
FsLtRogueQ: The "right" side would be "starboard", actually.
Lt Davey: Okay. Move slowly to the middle of the nacelle. Under no
circumstances go BEHIND it.
FsLtRogueQ: How dangerous is this ?
Lt Davey: Not as long as I'm here and you understand what I mean. The
nacelle has a subspace field around it, as well as the impulse engines. But
the Warp Nacelles emit subspace fields, locked together plus locked to the
Einsteinium universe.
FsLtRogueQ: :: pilots the shuttle to the middle of the starboard side
nacelle ::
Lt Davey: Okay, stop now. Computer, we are on relative velocity zero to
the ship, agree ?+
TC demon: COMPUTER> to Dave: YES.
Lt Davey: Okay. :: stares at the nacelle :: :: still stares at the
nacelle :::: hasn't stopped staring at the nacelle ::
FsLtRogueQ: Dave, I thought you wanted to do some measuring ?
Lt Davey: I'm just doing that, Rogue.
FsLtRogueQ: ::looks at him:: With what ?
Lt Davey: Long story, Rogue. I'm sorry, I'll explain it later, okay ?
FsLtRogueQ: :: hesitates a moment :: Okay.
Lt Davey: Okay. :: stares at the nacelle :: Computer, change plasma
injector frequency upwards.
TC demon: COMPUTER> Changed, Dave.
Lt Davey: Okay. Computer, adjust the trimming.
TC demon: COMPUTER> OK, Dave, adjusting ...
Lt Davey: Thanks. TC, switch to telepathic mode.
TC demon: TC> to Dave: Switched.
FsLtRogueQ: You mean your TC computer can read thoughts ?
Lt Davey: Yes. Look, you are half Betazoid, Rogue. When I came onboard
the Loth, I demanded special consoles, do you remember ?
FsLtRogueQ: Roughly ...
Lt Davey: I've added an interface to allow telepathic communications.
FsLtRogueQ: But you never mentioned it !
Lt Davey: Would anybody believe it, Rogue ? Look, you can read some
thoughts,
since you are half betazoid. The computer has bio matter to allow a better
neural net operation. This

[Return to Archives | Return to Listing ]

Lt Davey: I've added an interface to allow telepathic communications.
FsLtRogueQ: But you never mentioned it !
Lt Davey: Would anybody believe it, Rogue ? Look, you can read some
thoughts,
since you are half betazoid. The computer has bio matter to allow a better
neural net operation. This was invented on Earth in 1996 their time. At the
same time, the US Air Force had plans for a Stealth bomber, controlled by
thoughts. They realized it later, but it was a highly classified of course.
FsLtRogueQ: Dave-- !
Lt Davey: Rogue, I told you I was on Earth 6 or 10 years ago my time,
round 400 years ago your personal time. Remember my private database ?
FsLtRogueQ: You mentioned it.
Lt Davey: I can give you something to read about this. It's in that DB.
Don't worry, I'm not crazy. Read it, and you can see.
FsLtRogueQ: Okay. ~A telepathic link with the computer?~ Hey, does the
computer read my thought now too ?
TC demon: TC> Hey, FsLtRogueQ ...
Lt Davey: No. Just mine. And vice-versa. I consider it impolite
otherwise.
FsLtRogueQ: That's good ...
Lt Davey: Computer, access the warp drive trimming.
TC demon: COMPUTER> to Dave: Accessing ...
Lt Davey: Computer, transfer the readings to me.
TC demon: COMPUTER> Transferring ... Dave
Lt Davey: Computer, change the injector speed slightly upwards again.
TC demon: COMPUTER> Changed, Dave.
Lt Davey: :: stares at the nacelle :::: still stares at the nacelle ::
Computer, check the nacelle's vibration.
TC demon: COMPUTER> to Dave : Checking ...
Lt Davey: Computer, transfer the readings.
TC demon: COMPUTER> Transferring ... Dave
Lt Davey: Computer, adjust the trimming again.
TC demon: COMPUTER> OK, Dave, adjusting ...
Lt Davey: Okay. Computer, store these data.
TC demon: COMPUTER> to Dave: Stored.
FsLtRogueQ: What's that "trimming" about ?
Lt Davey: We emit subspace fields thru the nacelles, generated by three
coils. This disturbs the space-time around them. And this is the reason why
some routes are allowed to pass with a slow speed only. These disturbances
have damaged the universe structure on these paths. Remember the Academy ? I
forgot the name of the route that they always mention as an example.
FsLtRogueQ: I remember. And what's now that "trimming" ?
Lt Davey: We try to minimize the disturbance with the third coil. This
way the engine system is calmer, like my old Supra.
FsLtRogueQ: What is a "Supra" ?
Lt Davey: Ah - an old car I really love. A Toyota Supra, 6 cylinder, not
crippled like US cars. Sometimes you don't even feel if the motor is running
or not ! GREAT !!!
FsLtRogueQ: Huh??
Lt Davey: Sorry, again a thing 400 years ago. But it was great ! It's a
craft that moves on surfaces called "streets". Like a foot walk.
FsLtRogueQ: I see. How fast were these crafts ?
Lt Davey: Mine did round 270 km/h, that's 75 meters per second. You'd
LOVE IT !!!
FsLtRogueQ: I do like fast vehicles ... Directly on the surface ?
Lt Davey: On the Earth's surface, right.
FsLtRogueQ: Impressive.
Lt Davey: Okay. Computer, adjust the other nacelle's coils to the data
you just stored.
TC demon: COMPUTER> OK, Dave, adjusting ...
Lt Davey: Rogue, let's move to the other one. But go OVER the ship.
FsLtRogueQ: Okay.
Lt Davey: Talking of speed, what about showing me some pilot tricks ?
FsLtRogueQ: Now? I don't think so right now....
Lt Davey: Yeah. The ship is not in trouble. But we can make another date
....

They arrive at the port nacelle.

Lt Davey: Computer, both nacelles coils are timed the same ? Comply ?+
TC demon: COMPUTER> to Dave: YES.
Lt Davey: :: stares at nacelle :: TC, check the computer readings.
TC demon: COMPUTER> to Dave : Checking ...
Lt Davey: Well, it seems okay. That's it. Finished.
FsLtRogueQ: What did you found out ?
Lt Davey: The computer has learned. He increased the injector speed. But
he didn't adjusted the t

[Return to Archives | Return to Listing ]

They arrive at the port nacelle.

Lt Davey: Computer, both nacelles coils are timed the same ? Comply ?+
TC demon: COMPUTER> to Dave: YES.
Lt Davey: :: stares at nacelle :: TC, check the computer readings.
TC demon: COMPUTER> to Dave : Checking ...
Lt Davey: Well, it seems okay. That's it. Finished.
FsLtRogueQ: What did you found out ?
Lt Davey: The computer has learned. He increased the injector speed. But
he didn't adjusted the third coil's behavior. That means we need less energy
for the warp drive now. And the additional space-time disturbance is now
back to normal.
FsLtRogueQ: So our ship is faster now ?
Lt Davey: Well, theoretical, yes. But I will not mention this. The main
point is, the disturbance led to vibrations of the nacelles. Now, since the
space-time disturbance is back to normal, the nacelles are not vibrating
anymore. And of cuz so do the coils, they are inside the nacelles.
FsLtRogueQ: Okay, then ready to head back ?
Lt Davey: If you don't have another idea, yes ....

[Return to Archives | Return to Listing ]

Start Duty Log SD9610.06.2333 to 9609.09.0122 Loth Time.
Lt Dave,
Chief Engineer and
Computer Systems Specialist.

*** Computer System: ***

On 9610.07 I worked all day long at the Computer Systems Operating System.
It took a lot of energy, aprox 50 cups of chinos, but I wanted the job.
And I get it running by Friday, and if all the snow burns down.

I obviously messed up something, since lotsa parts don't work anymore.
But the features I added will stay there and I hope to get the System up and
running today.

So today, 9610.08 I start with this again, after having handled the various
messages I received.
It's now 1331 and hope I can start round 1530+.

I got a real nice response from FsLt Tamara, and whilst answering, I decided
to explain a little bit about the Computer System, to avoid confusion or
answer unasked questions some crewmembers might have.

I hope the crew realizes, that I'm willing to answer everything, anytime.
The only dumb question is the question, you don't ask.

This took longer, so now it's 9610.08.1734 and I gotta start working on the
Computer System.
I WANT to have it working !!

Well, I got interrupted by some administrative stuff.
Haven't thought that a Department Chief who really cares about the Ship as a
whole,
will have to do such an amount of extra work.
So the time I could spent on the Computer System was less than I thought.

I fixed a few bugs, but there are still some to find.

I decided to let the System produce enough debug data and shorten my day,
so that I can start next period of awakeness with analyzing those data.

*** The New Warp Core: ***

The new Warp Core is installed, the Repair Team from Starbase Alpha handed it
over
at 9610.09.0100, just a few minutes before I record this log.
So I've done no checks on it yet.
BUT I DON'T WANT ANY ACTION THAT BLOWS UP THE CORE AGAIN !!!!

*** Announcement to All: ***

Since this Duty Log reaches every crewmember, I want to take the opportunity
to announce,
that I will have much less time than in the last 3 months, beginning in about
2 weeks.
NO, I'm not leaving, not joining another ship, I still stick to the Loth and
our Captain
and I'll do everything I can for our ship.
It's just some extra work, that will take a great amount of time, so I can
only work
for our ship for some hours a day, plus all weekend long.

I mention this cuz if some of you need assistance with some Computer
Problems, come up with them now, and don't wait any longer.

I'll be back tomorrow,
hopefully with better news on the Computer System.

End Duty Log SD9610.06.2333 to 9609.09.0122 Loth Time.
Lt Dave,
Chief Engineer and
Computer Systems Specialist.

[Return to Archives | Return to Listing ]

Start Duty Log SD9610.09.1440 to 9610.10.0146 Loth Time.
Lt Dave,
Chief Engineer and
Computer Systems Specialist.

For those who give a damn about my Engineering work, I start with non-tech
stuff this time.

*** !!!! EVERYBODY SHOULD AT LEAST READ THIS PARAGRAPH !!!! ***
*** It is REALLY important for ALL OF US !!!! ***

No success in "shorten the day" (yesterday) to have more time this period of
awakeness.
I had to answer a couple of questions to fill in Ensign DeLia. 9610.09.0241.
I answered again round 9610.10.0030 to explain, what we are, how the ship's
missions work, etc.
This took some time - I can't estimate time, one reason, why my middle
console tells me loud and clear what time it is, every 30 minutes, but it
doesn't help much.
Well, it might have taken 2+ hours.

To get her on our ship ASAP, I asked our n-star Admiral USFABC1701, who
routed me to USF Rachel.
Then I told her, that I can't work with this slow USF overhead (I used other
words), and haven't received an answer yet.
However, communications with Captain Sean and Commander Neil are successfully
speed up for now.

Because I didn't got official authority, I assume that my actions are OKAY,
until further notice.
So, by my non-existent authority as a non-Senior Officer, I "posted" EnsDeLia
to our ship. Period.
I'll take the heat if there comes any.

If the High Command has questions about this, she is officially a "guest",
tomorrow, SD9610.11.2100, onboard our ship, estimated to be ready for duty.
Please treat her nice and give her a helping hand.
EnsDeLia has no experience, so please remember your first time and try to
help. So will I.

And please ADD EnsDeLia to your MAILSTRINGS !!!!

The Mailstring should be:
USF Silona, USF Neil, LT1Chid, LT1Feklhr, LTMog1, LtDavey, LT Josh12,
LtjgWolfe1, LtJgWusley, EnsDoug465, EnsDeLia

*** Other administrative stuff ***

I need to do a classified task for our Captain Sean.
This must be ready round 9610.11.1500, but the sooner the better.
For this, I try to get some sleep now, set all alarms avail to wake me up
during my personal daytime, to handle some private stuff plus getting this
task done.

*** The New Warp Core: ***

As mentioned, the new Warp Core is installed, the Repair Team from Starbase
Alpha handed it over and today, whilst working on the Computer System, I've
let the demons "warpd" and "amreactorcontrold" inspect the new Core.
It was a VERY BUSY time here in Engineering, similar to a striptease bar run
by Ferengis.

The Warp Core matches the specs of our old one quite good, minor adjustments
are yet to be done.
Mainly the plasma injection frequency has to be fine-tuned, and the power
drain to the Nacelles must get tweaked too.
I estimate an hour for this only, since the demons produces enough debug data
to use.

You can expect a full working Warp Drive at 9610.11.2100.

*** Computer System: ***

At 9610.09.1440 I started to analyze the debug data I've let the System
produce "yesterday".
At 9610.09.165946 the System successfully processed the last log. Woo.
At 9610.09.182315 the System finally did an error free debug run.
The run took 24 minutes !! All modules are saved.
Now, at 9610.10.0129 I'm satisfied with the results.

The speed is still not what I want, and the ship's devices are still not
correctly reported.
But some new features work great. I'll not mention it here for not spoiling
the fun.

Variations of the Computer's answers are prepared.

That means, I need to work on that BEFORE the next mission.
I estimate that I can do this, at least the first two points, between
9610.10.1700 and the mission at 9610.11.2100.
Since my personal time is 6 hours ahead of the Loth time, and I'm somewhat
worn out, the figures might not be correct.
But the tasks will be done.

I need to provide you all with updated pages containing the Computer
Commands.


*** STILL TO DO ***

The full documentation about the TC Subsystem for the Captain and Commander
i

[Return to Archives | Return to Listing ]

*** STILL TO DO ***

The full documentation about the TC Subsystem for the Captain and Commander
is to be updated.
Please allow some more days to do this.

Level 2 of TC must be installed.

Variations must be used.

HOST.SAY is to be included.

The I/O interface has to be re-checked.

It has to be checked, if there was any Computer Command issued in the last 4
months, which the Computer would not reply to today.

Everyone complaining about TC has to be put on an "Exlude-Me-List" for 10
minutes, which is equivalent to Level 1.
There should be a hint about this.

The Technical Manual TCDEVICE.MAN as of SD9610.02.2109 must be completed.

The Subsystem TCDEVICE must finally get up and running. It still doesn't
work.

The cookies details for the replicators must be improved.
There is too little chocolate in it.

I'll be back.

End Duty Log SD9610.09.1440 to 9610.10.0146 Loth Time.
Lt Dave,
Chief Engineer and
Computer Systems Specialist.

[Return to Archives | Return to Listing ]

Computer Begin Duty Log for Chid SD 9610.04

Once again I got to show off my other talents, I am not just a doctor you
know. As stated I was not needed in sickbay, so I went to bridge to see how
everything was going.

The Captain informed me that he needed some at science, I gladly excepted and
started to scan the area. I found some sort of Alpha Particles around the
ship. At first the seemed harmless but for some unexplained reason they
suddenly engulfed the ship and attached to our hull.

We soon discovered that these were not Alpha Particles at all but some sort
of lifeform. We brought one into the shuttlebay to gather information about
it. Tamara and I proceded down there and scanned the creature. We
eventually determined that since it was a space born creature it probably did
not like heat. We tried not to harm the creature but unfortuanetely we had
to, to get it off of our ship. Dave down in engineering was able to heat the
hull. The creatures finally let go an left our ship.

During this time the Romulans also decided to pay a visit to.

Computer Close Duty Log for Chid

[Return to Archives | Return to Listing ]

CLASSIFIED

Mission Name: Expose and Destroy
Status: Classified

Assigned to: USS Lothlorien crew

On a routine mission to the Gamma Quadrant, the USS Defiant (Commanded
by Captain Benjamin Sisko) has discovered a planet. The USS Defiant detected
a bio-genic signal which they believe to be a weapon. In response, High
Command has ordered us to expose and destroy it with whatever means
nessacary.

This planet has been named Dcorath, meaning in K'gera "Planet of
Death". Our primary objective is to expose and destroy this weapon. To
complete this assignment, we will be dividing up into two separate teams:

Team Alpha:

Commanding Officer: Silona
Executive Officer: Feklhr
Team Mates: Dave
Wusley
Josh

Team Beta:

Commanding Officer: Neil
Executive Officer: Chid
Team Mates: Mog
Wolfe
Doug

All other officers not mentioned here, will be spread out as needed.

For this mission, each of you will be equipped with special gear. All
gear will be put on prior to the landing.

1: Blank Undercover Clothing
2: Standard type C-11 Backpacks
3: Level 16 Compression Phaser Rifles
4: Mark VII Fusion Bombs
5: Rope and Climbing Gear
6: 3 weeks of lightweight rations
7: Triple Range Tricorders
8: Coded frequency, commbadges
9: A Standard Landing Parachute

We will be taking two shuttles into the atmosphere of the planet. Once
low enough, we will do a 20,000 feet jump into the water. We will emerge and
set up base camp.

Good Luck.

Remember, this mission is classified.

=/\= End Transmission =/\=

[Return to Archives | Return to Listing ]

CLASSIFIED

PHASE ONE:

The Lothlorien will enter the Gamma Quadrant. We will imediatly cloak
on arrival. We will set up a series of drills to prepare the crew. On our
way, we will choose a suitable hiding spot for the Lothlorien to rest as we
complete our mission.

Good Luck.

This mission is Classified.

=/\= End Transmission =/\=

[Return to Archives | Return to Listing ]

CLASSIFIED

PHASE TWO:

We will launch 2 shuttles carrying the 2 teams. Team Alpha will
deploy on the Western Continent, and Team Beta will deploy on the Eastern
Continent. They will each set up a sub-terannean base camp.

This mission is Classified.

=/\= End Transmission =/\=

[Return to Archives | Return to Listing ]

Start Duty Log SD9610.10.1128 to 9610.11.0155 Loth Time.
Lt Dave,
Chief Engineer and
Computer Systems Specialist.

Big News:
No fuse blew up when I had my shower this morning (at 5pm my time).
Everything went smooth, except for me being tired or having fever.
The planned "extended day" didn't worked again. I finally give up on this
now.

Today's Tasks:
+ The classified task the Captain gave me,
+ Tuning/Up TC to a quicker response time,
+ Optimization of the intended and calculated delays,
the Systems does after issuing a sound,
(otherwise sounds would be played too fast back to back,
so the second sound wouldn't be heard),
+ Checking TCDEVICE to give a more accurate status about the ship's devices
(Shields etc.),
+ Checking the entire System in a real environment,
+ Writing a new "USER MANUAL" to give YOU a quick and easy overview about the

available commands.

But first I gotta beam over to SB Alpha to get me some drugs and freshen up
my stock of my special Eau de Toilette.
You never know which nice Ensign or Lt you meet on the floors, do you ? Hee !

*** Special Task: ***

After some personal stuff I could finally begin at 9610.10.1529.
At 9610.10.1937 the task the Captain gave me was finally done.


*** Administrative Stuff: ***

I needed 2+ hours to handle some messages.
I told the High Command about my thoughts, goals, intentions, and problems.
The main "problem" was something no one is to blame for, it's simply that I
want
to act as fast as possible, and when I would need a permission for something,
there's of course a delay, I wanted to avoid.
Our Captain and Commander can't check for my messages every 10 minutes of
course.
So for the sake of getting things done quicker, I got the blessings to act,
after I told what actions are involved (covered).

That includes my posting of EnsDeLia to our ship, as well as future postings.

Another hour, was spent cuz one of our crewmember went nuts and slipped
again.
It took precious time from our Captain, our Commander and me.
It's awful, I really don't know what to say about it, other than just to
ignore junk like this.

*** The Computer System: ***

Due to all this "paperwork" mentioned above, I had very little time to work
on the Computer System.

I prepared two debug data files, to handle intended delays and to finally get
working
on the DEVICE module, which should provide us with accurate data about the
status
of the Shields, Weaponry, Energy, Warp and Impulse Propulsion Systems, the AM
Reactor,
the Fusion Reactors, Transporters and Hullbreeches.

Since so much time was lost, I haven't yet (9610.11.0155) started to analyze
the data
and wasn't able to make the necessary adjustments.

I haven't yet decided which of the two possibilities described in my previous
Duty Log I will choose.

*** The New Warp Core: ***

The adjustments to the Warp Core Control are made.
I mainly let the Computer System done it, which got a lot more data and
intelligence about the Warp Drive, since I flew with a shuttle to the Warp
Nacelles to gather more data from all three Coils (per Nacelle).

I bet, the plasma injection frequency has to be tweaked again, and due to
this, the power
drain to the Nacelles must get adjusted again.
But that part will be done by the Computer System itself, when we go to Warp
on our next mission at 9610.11.2100.

The Warp Drive is ready to use.

But I want no blow/ups in the next couple of weeks, folks !!!!


*** STILL TO DO: ***

I need to provide you all with updated pages containing the Computer
Commands.

The full documentation about the TC Subsystem for the Captain and Commander
is to be updated.
Please allow some more days to do this.

Level 2 of TC must be installed.

Variations must be used.

HOST.SAY is to be included.

The I/O interface has to be re-checked.

It has to be checked, if there was any Computer Command issued in the last

[Return to Archives | Return to Listing ]

*** STILL TO DO: ***

I need to provide you all with updated pages containing the Computer
Commands.

The full documentation about the TC Subsystem for the Captain and Commander
is to be updated.
Please allow some more days to do this.

Level 2 of TC must be installed.

Variations must be used.

HOST.SAY is to be included.

The I/O interface has to be re-checked.

It has to be checked, if there was any Computer Command issued in the last
4 months, which the Computer would not reply to today.

Everyone complaining about TC has to be put on an "Exlude-Me-List" for 10
minutes, which is equivalent to Level 1.
There should be a hint about this.

The Technical Manual TCDEVICE.MAN as of SD9610.02.2109 must be completed.

I'll be back.

End Duty Log SD9610.10.1128 to 9610.11.0155 Loth Time.
Lt Dave,
Chief Engineer and
Computer Systems Specialist.

[Return to Archives | Return to Listing ]

Start Duty Log SD9610.11.0017 thru 9610.11.2100 Loth Time.
Lt Dave,
Chief Engineer and
Computer Systems Specialist.

Today's Tasks:
+ Tuning/Up TC to a quicker response time,
+ Optimization of the intended and calculated delays,
the Systems does after issuing a sound,
(otherwise sounds would be played too fast back to back,
so the second sound wouldn't be heard),
+ Checking TCDEVICE to give a more accurate status about the ship's devices
(Shields etc.),
+ Re-Checking the entire System in a real environment,
+ Writing a new "USER MANUAL" to give YOU a quick and easy overview about the

available commands.


*** Administrative Stuff: ***

I needed one hour to handle a personal message.
I did some mistakes in the past, due to lack of experience and I had to
clarify a few things.

Another 3 hours (in words: THREE), were spent to fill in our crewmember
EnsDeLia.
Of cuz, she is not responsible for those three hours.
It mainly covered briefings how to handle our INTERCOM.
What looks easy and not worth mentioning to us, is totally new for a new
member,
and since I wanna be absolutely sure, everything goes smooth and without
problems,
I took the time to ensure, that our new crewmember doesn't get lost or has
difficulties
using the INTERCOM, since these problems can not be solved and explained
during
our missions, which are quite hectic at times, as we all know.

*** The Computer System: ***

After this "paperwork" I finally started at 9610.11.1700 to tune the Computer
System.

Tuning/Up TC to a quicker response time is done.
I did some experiments and found the correct values, matching the Systems
environment.
It is still possible to enhance the response time, but I close this problem
herewith
and will come back to it when I see the need. (And if this is, when I review
the data, next period of awakeness.)

The optimization of the intended and calculated delays, when the Systems
issues sounds,
is done and closed too.
I chose to let the system wait, directly until a sound is issued.
This way, following statements that still belong to the same response are
delayed, but the sounds indicates action, so that this makes sense somehow.
Another main point for this decision is, that the System will never enter a
delay, when in fact it is not necessary.
That speeded up the response time a lot.
The formula I used to calculate the sound's duration proved to be quite
correct.
As of today, I see no need to change this.
Again, there is still a possibility to speed it up, but ... see above.
(Like Kevin's father said, "If it ain't broken, don't fix it.".)

Re-Checking the entire System in a real environment is closed too.
There was not a single error, the System is that stable right now, that it
could be launched and shut/down by a timer.
This was the first time, that absolutely no intervention was necessary.

The point "Re-checking the I/O interface" is obsolete with these results,
altho this is again a point, where theoretically, the System can be speeded
up again.

Because of the reliability, the System has reached by now, I will construct a
timer, that launches the system at times, when I myself am not able to attend
a mission.
Since our Captain is well versed with the System, he knows what to do, if it
should went nuts.
What's not to be expected at all.

I've created a new "USER MANUAL" to give a quick and easy overview about the
available commands.

I've also created an "EXAMPLE" file, that the System produced itself by
simply reading the above mentioned User Manual. I hope these examples are
clear, both User Guides were created and posted a few minutes before the
mission begun at 9610.11.2100 Loth Time.

They will be updated and revised.

So everything planned for today was done, I'm very satisfied with the
Computer System.

*** The New Warp Core: ***

I still need the Warp Drive to be activated, to let the Computer System
fine-tune the plasma inje

[Return to Archives | Return to Listing ]

*** The New Warp Core: ***

I still need the Warp Drive to be activated, to let the Computer System
fine-tune the plasma injection speed of the M/AM reactor and the power flow
to the coils.

The third coil, that caused the Nacelles to vibrate, needs special attention.

In case, the new Warp Core, installed by the Repair Team of Starbase Alpha,
really matches the specifications of the old one, it is not necessary.
But every Engineer knows, that two "identical" spare parts are never really
identical.

So I bet, the plasma injection frequency has to be tweaked again.


*** STILL TO DO: ***

The full documentation about the TC Subsystem for the Captain and Commander
is to be updated.
Please allow a week to do this.

Level 2 of TC must be installed.
I will do this together with implementing the variations.

HOST.SAY is to be included.

It has to be checked, if there was any Computer Command issued in the last 4
months, which the Computer would not reply to today.

The Technical Manual TCDEVICE.MAN as of SD9610.02.2109 must be completed,
and I'll do this, when I check the DEVICE module of the System, to gain
proper results and finally to be able to enable all "Status" Commands (the
ship's devices, shields, weapons, etc.).

Ah - and of cuz our Captain has found another task for me.
This time, a technical problem.
I won't be able to start working on it before Tuesday.

I'll be back.

End Duty Log SD9610.11.0017 thru 9610.11.2100 Loth Time.
Lt Dave,
Chief Engineer and
Computer Systems Specialist.

[Return to Archives | Return to Listing ]

Start Duty Log SD9610.11.2100 thru 9610.11.2206 Loth Time.
Lt Dave,
Chief Engineer and
Computer Systems Specialist.

*** Mission 9610.11.2100 thru 9610.11.2206 Loth Time: ***

!!! This Mission is Classified, and so is this Log !!!

The mission's details and goals are classified and for this, I refer only to
what has already happened.

Phase One started at 9610.11.21:06:50.

Plan, given by the Captain:
The Lothlorien will enter the Gamma Quadrant. We will imediatly cloak on
arrival. We will set up a series of drills to prepare the crew. On our way,
we will choose a suitable hiding spot for the Lothlorien to rest as we
complete our mission.

We arrived at DS9, and course was set for the Gamma Quadrant, using full
impulse.
Two teams were assembled to explore the planet, once we reach our operation
field.

The TurboLift Demon was obviously still a bit angry about our discussion, so
he even invited the Computer System to take a ride !!
I'll talk to him later to find out, what the heck turboliftd thought this
time.

The Warp Drive wasn't used, so I could not let the Computer System fine tune
it.
BTW, I couldn't have done this before the mission, cuz I need the real data
with the ship being on Warp with all systems running. A dry dock test was
done.

The teams entered the holodeck to prepare themselves for the dangerous
mission on the planet.

Ens DeLia took helm, we cloaked, and I had a close eye on the cloakingdevice
to make sure we won't be detected.

As our hiding spot an asteroid was chosen, and DeLia changed course to go
there with full impulse.

A new order was given and the ship was steered into the planet system's
star's corona.

DeLia took us there and maintained position, whilst Chid was scanning the
sector for anything suspicious.

The metaphasic subroutine of the Shield System was used for shelter. They are
holding.
But as Chid mentioned, the star's radiation effects our cloak, and during a
solar flare, the energy of the flare will interfere with our cloak.
Both systems (shields and cloakingdevice) worked properly, but I too expect
the cloak to encounter problems.

But, if a solar flare will occur, altho the cloak will not work properly, the
star's energy can't be easily differed from the ship's energy field, since we
are so close. So we would still be quite safe.

Lt1 Chid scanned the planet very carefully and complete, as well as the space
around us.
Due to a vertion particle concentration we changed position slightly.
Chid located the source deep in the planet's core.
His impression was, that the planet's core might be out of vertion.
Due to our strange position, this can't be positively proven.

Commander Neil ordered me to the Bridge to maintain a scan on those
particles.
The Beta Team was ordered to holodeck 2, and I was given the Bridge, and - as
Commander Neil said - the rest of the ship, since the entire crew will be on
the planet.

I need to state, that the shields consume more energy than we normally use,
and the cloakingdevice consumes pretty much power too.
I might need to lower the energy supply for the weaponry, which are on
standby.
Lt Josh gave me permission to handle the weaponry. (Since he heads for the
planet too.)

I'm uncomfortable about the ship's position.
It sure is the best possible hiding spot, but it's pretty dangerous too.

To keep the shields and cloak in balance, they must be continuously observed,
checked and adjusted.
The same applies to the continuous scan on those vertion particles, to ensure
they won't effect the mission.

Because of this, I set up the audible alarm in my quarters, to get notified
if the shields, cloakingdevice or the particle stream data leave a defined
tolerance.

End Duty Log SD9610.11.2100 thru 9610.11.2206 Loth Time.
Lt Dave,
Chief Engineer and
Computer Systems Specialist.

[Return to Archives | Return to Listing ]

::Chid returns from the holodeck training mission and proceeds to sickbay::

::There are just a few routine bumps and bruises he heals, then his work is
complete::

Computer Open Duty Log for Chid

This mission represents the first time that I have ever been in the Gamma
Quadrant. I have begun training for our mission ahead in which we are going
to search and destroy some JemHadar weapon.

Once again there was no need for me in sickbay so I went to the bridge and
took on the post of tactical some what and science. Once we nearned the
planet where our teams were going to land, the Loth went into the system
sun's corona, so as not to be detected by anyone. The metaphasic shields
were in perfect working order, but you can never be too safe in a sun's
corona so I checked over them several times. We had cloaked before we
arrived at this point but I also pointed out that if the star has any
solar flares it could cause problems for our cloak and we might be detected,
so we are on constant alert.

While I was scanning the planet for various things, I noticed that there an
enormous amount of Vertion particles. I determined that they were eminating
from the planet but, I could not detect whether or not it was some type of
scanning beam, or if the planet's core was made out of Vertion. Most likely
the planet's core is made out of Vertion but to be on the safe side I
suggested that we move onto the far side of the star.

Soon afterward my team (Beta) was called to the holodeck to begin the
training exercise. My team consisted of Commander Neil, Ensign DeLia, and
myself. We had to scale a tall mountain in order to reach our goal. Just as
we reached the top we had to stop the mission in order to do other things.

I am also happy to report that I was promoted to Second Officer of the
Lothlorien. I hope that I can perform the duty to the best of my ability.

Computer Close Duty Log

[Return to Archives | Return to Listing ]

Start Duty Log SD9610.12.1923 thru 9610.14.2132 Loth Time.
Lt Dave,
Chief Engineer and
Computer Systems Specialist.

*** Current Mission: ***

The USS Lothlorien is still in the planet system's star's corona.
The metaphasic Shield consumes a pretty amount of energy !
And so is the CloakingDevice.
I've not yet powered down the energy supply for the weaponry, but I guess I
will need to.
No need to worry tho, I won't leave standby mode (of the weapons), it only
means that powering them up will take a wee bit longer.

Data about the Shields, CloakingDevice and the continuos Scan data about the
vertion particle flow are routed to my quarters to ensure I won't miss it,
when they get outta the tolerances I set up for these three values.

Everything's okay by now, SD9610.14.2115.

I've accessed a database to get me some more informations and freshen up my
astronomy knowledge, to get more familiar with the situation in a star's
corona.
I hope I'll be able to fetch and read the most important things by 9610.17.

*** Computer System: ***

I created a great amount of debug data, to get the DEVICE module working,
which should tell as the actual status of or find devices, like weapons,
shields and stuff.
Done at 9610.13.0251.

Next, I got a very good idea how to speed up the TACTICAL Procedures ALPHA,
PHASER and TORP.
It's not realized yet, but "coming soon".

A discussion with turboliftd was very fertile.
He thought it was funny, to invite the Computer System to take a ride.
I told him, most lifeforms were confused by this, and he said he would stop
it.
He even promised, to allow some failures when crewmembers don't name their
target exactly.

Now, I'm checking every log, 17 logs that are, to see how turboliftd behaves,
and to correct errors or eliminate annoying replies.
I agree with those crewmembers (who were so kind not to mention it, thanks
!!!),
that our TurboLifts really still have to learn a few things.

At the same time, I'm collecting data to get the DEVICE module working.

Again parallel, I make sure that numbers are correctly interpreted, regarding
their optional decimal point.
These figures are needed for percentages and speeds.

The FULL STATUS DISPLAY I'm about to get working includes:

>>>>> *** IF YOU MISS ANYTHING, PLEASE TELL ME *** NOW *** !!!!!

Checking 17 logs takes a while, so I'm not bored at all ...

*** The New Warp Core: ***

I still need the Warp Drive to be activated, to let the Computer System
fine-tune the plasma injection speed of the M/AM reactor and the power flow
to the coils.

The third coil, that caused the Nacelles to vibrate, needs special attention.

In case, the new Warp Core, installed by the Repair Team of Starbase Alpha,
really matches the specifications of the old one, it is not necessary.
But every Engineer knows, that two "identical" spare parts are never really
identical.

So I bet, the plasma injection frequency has to be tweaked again.

End Duty Log SD9610.12.1923 thru 9610.14.2132 Loth Time.
Lt Dave,
Chief Engineer and
Computer Systems Specialist.

[Return to Archives | Return to Listing ]

Start Duty Log SD9610.16.1335 Loth Time.
Lt Dave,
Chief Engineer and
Computer Systems Specialist.

In my last Duty Log there was an error.
I forgot to paste something.
So please read this again:

*** Computer System: ***

Now, I'm checking every log, 17 logs that are, to see how turboliftd behaves,
and to correct errors or eliminate annoying replies.
I agree with those crewmembers (who were so kind not to mention it, thanks
!!!),
that our TurboLifts really still have to learn a few things.

At the same time, I'm collecting data to get the DEVICE module working.

Again parallel, I make sure that numbers are correctly interpreted, regarding
their optional decimal point.
These figures are needed for percentages and speeds.

The FULL STATUS DISPLAY I'm about to get working will look like this:

COMPUTER> Full Status: Warbirds: NO
COMPUTER> Shields: ONLINE Transporter: ONLINE Hullbreeches : NONE
COMPUTER> Weapons: ONLINE WarpEngine : ONLINE ImpulseEngine: ONLINE
COMPUTER> Energy : OKAY CloakingDevice: ONLINE

>>>>> *** IF YOU MISS ANYTHING, PLEASE TELL ME *** NOW *** !!!!!

Thank you !

*** Current activities: ***

Keeping a close eye on the Shield's, CloakingDevice's and Vertion Particle
Scan's data,
Working on 17 logs to check out turboliftd's behavior,
Trying to get the DEVICE module working (so better tell me NOW if you want
something added),
Speeding up the Computer Procedures for TACTICAL,
Checking out what's up with those leaving the Academy.


End Duty Log SD9610.16.1335 Loth Time.
Lt Dave,
Chief Engineer and
Computer Systems Specialist.

[Return to Archives | Return to Listing ]

=============================================================
INTERSHIP MEMO
From: Lt Dave, Computer Systems Specialist, Chief
Engineer.
To: Lt1 Chid, Ens Delia
Further Attention to:
=============================================================
Hi Chid, Hi Delia,

I forgot something.

Chid,
you still have a camera in Sickbay, which I set up for Ariell's babes.
Do you want it removed, or would you like to take the opportunity to let it
there ?
Since you are almost everywhere, but in SB, it might help you a lot, if you
got an audio/video plus measuring monitor anywhere. I could arrange it in a
way, that you could use ANY console onboard to get your data plus the
audio/video signal from your Sickbay.
Just let me know.

DeLia,
I dunno if you have your luggage unpacked yet, but in case you still are on
deck 17 (Junior Officer Quarters) you gotta move to deck16 (Senior Officer's
Quarters, Lounge, Holodeck 2, and both the Counselor's Office and Quarters.
They are linked with a door, so you have a real big "territorium".
You'll find a monitor in both your quarters and your office.
These are the monitors, that are connected to the Sickbay camera and data
connections, cuz our last Counselor, LCdr Ariell, needed them.
I gotta remove them, sorry I forgot about it.
Let me know, when I can do this without disturbing you.

Fine Day Everybody !
Dave.

[Return to Archives | Return to Listing ]

Start Duty Log SD9610.16.1439 thru 9610.17.1051 Loth Time.
Lt Dave,
Chief Engineer and
Computer Systems Specialist.

*** Current Mission: ***

I still keep a close eye on the Shield's, CloakingDevice's and Vertion
Particle Scan's data.
Or better say, the Computer System does. No warning so far.
Meanwhile, I got me some more detailed informations about Vertion and our
environmental situation inside the star's corona.
Gotta study them yet. (Our Science Department is closed ...)

*** Administrative Stuff: ***

I'm continuously checking out what's up with those leaving the Academy.

Ens Lasinjh lost her INTERCOM authorization, so she had to set up a new one,
she told me at SD9610.17.0125.
Maybe she'll make it in time, so she *might* be able to join us on Friday.
But I won't bet for more than one single cup~o~chino.
And only with someone, whom I'd give a cup anyway ...

A hint from someone dealing with more than a dozen authorization codes
(really!):
always take another one.
Never choose something you can remember, cuz others would be able to remember
it too.



*** Other Stuff: ***

I totally forgot about the camera in Sickbay and the monitors in the
Counselor's office and quarters.
Sent a note to both our Medical Chief and our Counselor about it.
Maybe it helps Chid, if he can watch his Sickbay from wherever he is.

*** Computer System: ***

My sick ambition keeps me busy with those 17 logs.
Right now, I "only" wanna have turboliftd to respond correctly in all cases
that occurred.
Some of them are weird, but once the algorithm is perfect, I never need to
touch it again,
even no matter what decks another ship might have.
But it's "great" to find a better algorithm on file 8, and to have 1 thru 7
to check again cuz of the program change. Oh what have I started !!

After 16 hours I made a break for 5 hours. Right now, at 9610.17.0734 I
finally got it.

I also think I found the main problem that hindered the DEVICE module to work
correct.
That does however not mean, that the "Computer, FULL STATUS" command gives
reliable results right now, it means I'm able to check them for reliability
and make sure they are correct.
Maybe a few hours of sleep weren't that bad.
Doc, whatchathink ?

Parallel, I'm collecting data to get the DEVICE module working.
Again parallel, I make sure that numbers are correctly interpreted, regarding
their optional decimal point.
These figures are needed for percentages and speeds.

Right now I'm at file 6/17 and it works fine.

Speeding up the TACTICAL Procedures ALPHA, PHASER and TORP is still "coming
soon".

Well, I'll take another break and -
I'll be back,

End Duty Log SD9610.16.1439 thru 9610.17.1051 Loth Time.
Lt Dave,
Chief Engineer and
Computer Systems Specialist.

[Return to Archives | Return to Listing ]

Start Duty Log SD9610.17.1051 thru 9610.18.2000 Loth Time.
Lt Dave,
Chief Engineer and
Computer Systems Specialist.

*** Current Mission: ***

I studied the informations I got about Vertion, to make sure I'll be able to
do a good job in assuring the mission won't get disturbed by those particles,
and I only found out, that I know nearly as less as before.

My fresh/up readings about coronas did not led to much new conclusions.

*** Other Stuff: ***

The camera in Sickbay will remain there, and I gotta provide Lt1 Chid with
the procedure how to use it, from every monitor on the ship.

*** Computer System: ***

turboliftd should now behave in an acceptable way.

I checked out 17 logs to tweak it, plus to get hints about the DEVICE module.

Worked from 9610.18.0000 to 9610.18.2000 on it, and I'm worn out.

The main problem that hindered the DEVICE module to work correct is found, I
guess.
There is a chance, that the STATUS Commands will give more reliable results
in a week.

As soon as I'm satisfied with the results, I'll spread the news about the
STATUS commands.

Speeding up the TACTICAL Procedures ALPHA, PHASER and TORP is STILL "coming
soon".

*** The New Warp Core: ***

There was still no chance to tweak the Warp Drive.
I still need the Warp Drive to be activated at a real mission, to let the
Computer System fine-tune the plasma injection speed of the M/AM reactor and
the power flow to the coils.

The third coil, that caused the Nacelles to vibrate, needs special attention.

I bet, the plasma injection frequency has to be adjusted.

*** STILL TO DO: ***

The full documentation about the TC Subsystem for the Captain and Commander
is to be updated.
Please allow a week to do this.

Level 2 of TC must be installed.
I will do this together with implementing the variations.

HOST.SAY is to be included.

The Technical Manual TCDEVICE.MAN as of SD9610.02.2109 must be completed,
and I'll do this, when I check the DEVICE module of the System, to gain
proper results and finally to be able to enable all "Status" Commands (the
ship's devices, shields, weapons, etc.).

I wasn't able to work on the Captain's technical problem last week,
I hope I'll be able this one.

I'll be back.

End Duty Log SD9610.17.1051 thru 9610.18.2000 Loth Time.
Lt Dave,
Chief Engineer and
Computer Systems Specialist.

[Return to Archives | Return to Listing ]

Start Duty Log SD9610.18.2000 thru 9610.21.0245 Loth Time.
Lt Dave,
Chief Engineer and
Computer Systems Specialist.

*** Current Mission: ***

As I said, I know nearly as much about Vertion right now, as before I
searched for information. All I'm prepared to react to, is something
unpredictable. As always.

I will however go deeper into my informations about coronas, to fresh up my
knowledge and to make sure, there are no wild guesses when our environment
leads to problems.

We left our position for a quick rescue mission, which ended an a destroyed
StarShip, the Quest, and the rescue of every crewmember onboard that vessel.
Lt1 Feklhr and Commander Neil were fighting some Klingon ships, which came
absolute unpredictable and we were all very surprised, what the heck they
would do in the area we crossed. As Lt1 Chid said, they might be on a "let's
wait for a ship and destroy it" mission.

After the Lothlorien crew met the Quest crew in 16F I had to shutdown the
intercom link to Engineering immediately, because some strange effects
occurred.
The computer system experienced a problem and I gotta get an idea about this
specific one.

I'll think about this later this week, since last week was filled with
nothing but this System, and even I do need a longer break right now.

*** Other Stuff: ***

Lt1 Chid can now monitor SickBay from wherever he his, using the camera and
datalink I installed when we had Ariell's babies in their incubators there.
Chid, when you use a normal console (not these colorful panels), select
router 22-1-1.
If nothing happens, type in "go video".
If you got problems, just call me.

I started to work on the Captain's technical problem and asked him for more
details,
to give him a comfortable solution.

*** Computer System: ***

turboliftd really behaved in an acceptable way. Problem is closed.

The DEVICE module however is still under construction.
There were so many changes made in the last months, that I need to check this
module, nearly as if I would re-write it from scratch.
I estimate three weeks to get reliable results.

Speeding up the TACTICAL Procedures ALPHA, PHASER and TORP is STILL STILL
"coming soon".

*** The New Warp Core: ***

There was a chance to tweak the Warp Drive, since we used it to rescue the
Quest crew,
but since I worked 20 hours non-stop before the mission on SD9610.18, I
simply forgot it.

So I still need the Warp Drive to be activated at a real mission, to let the
Computer System fine-tune the plasma injection speed of the M/AM reactor and
the power flow to the coils.

The third coil, that caused the Nacelles to vibrate, needs special attention.

I bet, the plasma injection frequency has to be adjusted.

*** STILL TO DO: ***

The full documentation about the TC Subsystem for the Captain and Commander
is to be updated.
Please allow a week to do this.

Level 2 of TC must be installed.
I will do this together with implementing the variations.

HOST.SAY is to be included.

The Technical Manual TCDEVICE.MAN as of SD9610.02.2109 must be completed,
and I'll do this, when I check the DEVICE module of the System, to gain
proper results and finally to be able to enable all "Status" Commands (the
ship's devices, shields, weapons, etc.).

I'll be back.

End Duty Log SD9610.18.2000 thru 9610.21.0245 Loth Time.
Lt Dave,
Chief Engineer and
Computer Systems Specialist.

[Return to Archives | Return to Listing ]

=============================================================
INTERSHIP MEMO
From: Lt Dave, Computer Systems Specialist, Chief
Engineer.
To: Captain Sean
Further Attention to: Lt1 Feklhr, LT1 Josh, Ltjg Anne Wolfe, Lt1 Chid,
Ens DeLia, Cdr Ariell, Crew of the USS
Lothlorien
=============================================================

Dear Captain Sean,

I hereby ask for permission to use the USS Lothlorien for a test drive.

The last mission was hectic and action packed - since who knows when - or at
least
it looked like me that way, cuz I was only awake for 15 minutes.

You all might remember, that the new Warp Core is not adjusted for 4 weeks
now.
This has to be done !!
The coils still need to be checked after the Core was replaced, and the
Nacelles that vibrate in the past might now vibrate again.

For the safety of us all, I urgently request permission for a test flight.

I would use a Tactical officer, either Lt1 Feklhr and/or Lt1 Josh,
and as Helm I would need either Lt1 Feklhr, Ltjg Anne Wolfe, Lt1 Chid or Cdr
Ariell.

Whoever takes the job, must take it voluntary.

I would prefer to have either Ens DeLia or Cdr Ariell onboard, to assist me
in reading the systems data on a telepathic way.
That means Ariell can not pilot the ship in case DeLia is not present.

Again, this must be voluntary.

I suggest, that Ensign Boner either leaves the ship for the time of the test
or is close to Lt1 Chid, in case Chid is not piloting the ship.
The same applies to Ensign Talura.
I don't have their BIOS data, so I don't know how they would react during
this test.
I have no concerns for the rest of the crew.

The reason, why I am specially careful is, that I need the ship to be taken
to maximum speed.
Maximum speed from my Engineer point of view is slightly different from what
our manuals say.

Please let me know your decision soon,
Lt Dave,
Chief Engineer and
Computer Systems Specialist,
USS Lothlorien.

[Return to Archives | Return to Listing ]

Permission Granted.

~Captain Silona
=============================================================
INTERSHIP MEMO
From: Lt Dave, Computer Systems Specialist, Chief
Engineer.
To: Lt1 Feklhr, LT1 Josh, Ltjg Anne Wolfe, Lt1
Chid,
Ens DeLia, Cdr Ariell, Crew of the USS
Lothlorien
=============================================================

Dear Crew,

You all might remember, that the new Warp Core is not adjusted for 4 weeks
now.
This has to be done !!
The coils still need to be checked after the Core was replaced, and the
Nacelles that vibrate in the past might now vibrate again.

For the safety of us all, I urgently request permission for a test flight.

Lt1 Feklhr and Lt1 Josh,
would you please join as Tactical Officers and tell me which date would be
okay for you?

Lt1 Feklhr, Ltjg Anne Wolfe, Lt1 Chid, Cdr Ariell,
would you please join as HELM and tell me which date would be okay for you ?

Ens DeLia,
would you please join to use your telepathic abilities during the flight ?

Ensign Boner and Ensign Talura,
please prepare to leave the ship for an hour. I'll tell you, when.

Please let me know your answers soon,
Lt Dave,
Chief Engineer and
Computer Systems Specialist,
USS Lothlorien.

[Return to Archives | Return to Listing ]

::Chid takes a deep breath after having a very exhilerating day as acting
XO::

Computer begin acting XO duty log.

The captain was called away on important buisness today so Commander Neil was
acting captain and I moved to acting XO. Starfleet needed the Lothlorien on
a very important mission that was vital to the security of the Federation.

We were ordered to to investigate why the Federation Outpost in the Ankar
system had not replied to Starfleet's hails in the past month or so. I soon
discovered that this area of space was very close to the old
Klingon-Federation Neutral zone that was disbanded many years ago. We we
arrived at the outpost it had been uterly destroyed by an unknown attack
force. I immediately informed Starfleet command of our situation.

Soon afterward a Klingon battle cruiser decloaked and told us to leave or be
destroyed. Of course a battle soon ensued, we took damage but so did they.
First Lieutenant Feklhr told us that there was a Nebula near by where the
Klingons were most likely hiding there cloaked ships. We confirmed this and
sent an igniting agent into the Nebula to cause it to explode or something
along those lines. We eliminated all Klingon ships that were in the Nebula,
but there were some left but luckily they were
disabled.

Starfleet suddenly hailed me and told me that onboard the station was a data
chip which contained numerous amounts of information that must not fall into
enemy hands. Feklhr already had an away team onboard the Klingon ship trying
to secure it so he was told to go get it at any cost.

Feklhr and his team soon recovered the chip with little resistance and we
took the Klingon ship in tow to return with US. It should be noted that the
Ankar system is very rich in resources and this was the most likely cause of
the Klingon attack, to secure these resources for themselves.

Computer end log.

::Chid heads for Sickbay to go help out his new assistant::

[Return to Archives | Return to Listing ]

Start Duty Log SD9610.30.0500 thru 1133 Loth Time.
Lt Dave,
Chief Engineer and
Computer Systems Specialist.

*** Administrative Stuff: ***

I wrote a detailed message to my Assistant, Ltjg Tetro, to make sure we will
become a good working team. I tried to explain the difficulties I have with
one line messages, and hope, that my explanation will fall on fertile ground.
That took some time, since - as you all know - diplomacy is one of the things
I don't have.
But I tried my best, especially cuz I want to be able to let my staff (so far
"only" Tetro), work on its own, without me, too.
To delegate is the keyword to most management tasks and to satisfied
personnel, which should be seen as a goal as high as the work itself.

[Return to Archives | Return to Listing ]

*** The Mission on SD9610.25: ***

We left our position for another quick rescue mission.
The Lothlorien seems to get a task force for missing StarFleet posts.
It's not bad, to be the one who's in charge if there's some fire to take care
of. I like it.

This time, an outpost in the Ankar System was on the "missing" list.
Contact was lost for already 2 months and the station was near the old
Klingon Neutral Zone.
Since we have some practice now, we went there with Warp 7 right away to
investigate on the whereabouts.

We weren't already arrived when Lt1 Feklhr noticed a nebula that diminished
possible warp traces and big enough to cover a large battle fleet.

The station we should investigate seemed to be gone.
Doug found a very weak life sign and beamed survivors directly to SickBay,
where Talura could take care about them.

And indeed Lt1 Feklhr was right with his suspect, a Klingon battle cruiser
decloaked at starboard.
We were hailed and even tho the Klingons were in Federation space - well we
all know them. We identified three, and a possible cloaked one and prepared
for an invasion.

It was time for the first stroke. We exchanged some phaser beams.
Action speaks louder than words, specially when it comes to them Klingons.

We were hit, but the damage seemed not that big at first, until incoming
messages reported two deaths and 27 injuries.
At that point, two other survivors from the station were beamed to SickBay.
The nebula was too dense to scan anything, so we fired immediately with
brutal force whilst we still could locate the ship.
Another Klingon vessel decloaked behind us, one of our torpedoes shut down
their engines the hard way.

A discussion started on how to destroy the nebula, in hope, the vessels in
there will get damaged too. Shuttle, torpedoes, phasers ... finally Lt1
Feklhr decided to let the computer lock onto the targets and fire the phaser
array.
Much to my surprise, the nebula and some ships really exploded.

Feklhr leaded an AT (Josh, Doug, and me) to one of the remaining vessels and
Chid found a very good explanation why the heck the Klingons were in this
sector.
Resources, including Dilithium on planet Akar 4.

Well, with phasers set to heavy stun we were ready to see what's up on that
Klingon vessel we choose.
Josh and me went to their Engineering.
The core destabilized, but this is normal.

Not normal however is that a panel blew up in Josh's face.
Stumbling backwards, he even hurt his back of his head.
He must have felt like a grilled sandwich, poor ol' friend.

I've lowered the energy drain on that vessel and adjusted the emitter to
stabilize the core.
We should find a data chip.
Thru the telepathic link with our board computer, I could initiate an
emergency beam for Josh to SickBay on our good old Lothlorien.

Ens Talura did a real marvelous job in SickBay during all this mess.
This MUST be noted.

Chid, onboard the Lothlorien noticed an increase in the Klingons energy
supply and predicted a core breech.
I've immediately cut off the control devices, so the core wasn't triggered
anymore.
After that, I've let our computer check the core again.
The core was disabled, no possible harm anymore.

Feklhr finally found the data chip and beamed back Doug with the chip.
His (Feklhr's) temper is a thing I still don't understand. A longing for
death ?
Well, he wanted to bring the systems on that Klingon ship online again.
I stayed with him until we were transported back to our ship.

End Duty Log SD9610.30.0500 thru 1133 Loth Time.
Lt Dave,
Chief Engineer and
Computer Systems Specialist.

[Return to Archives | Return to Listing ]

=============================================================
INTERSHIP MEMO
From: Lt Dave, Computer Systems Specialist, Chief
Engineer.
To: All
Further Attention to:
=============================================================

I'm currently working on some REAL DIFFICULT Computer Problems,
and I'm in my quarters.
To be not disturbed, I've sealed my quarters. This includes Telepathic Links
and there is no override possibility.
The normal Engineering Consoles are all routed to my quarters too,
so nothing to worry about.

All incoming messages will be recorded,
and I will start answering them in around 12 to 15 hours from now on
(9610.31.0856).

The latest list of Computer Commands is attached,
and my advice, specially for our new members, is to print it out and have it
handy,
when on the mission in 36 hours.

Any questions and suggestions are welcome as always,
but no message will leave my quarters before 9610.31.2100.
Remember, in case of emergency my Engineering Consoles will notify me.

Lt Dave,
Chief Engineer and
Computer Systems Specialist,
USS Lothlorien.

[Return to Archives | Return to Listing ]

i enjoyed my first sim. i will have to make a point to tell wolfe that she
can't hurt me as much as she tries. she can do it for her own pleasure
though. i can't get the sounds to work. i suppose i am missing alot. i will
have to ask if i write about sim life ro real life or both.
<end log>

[Return to Archives | Return to Listing ]

First Lt. Feklhr
Chief Tactical Officer
USS Lothlorien
Duty Log
Stardate 9610.25

We responded to a destress call from a nearby Federation colony who said
they were under attack. After studing some sector charts I found a nebula
that the Klingons might be hiding in. After some research we finally found
that about thirty ships, enough for a small invasion fleet was inside.
Science figured out how to destroy the nebula and took out all but five ships
inside. I led an away team to one of the Klingon ships and found the plans
for the invasion. Dave and I stayed behind and captured
the Klingon ship. Hopefully the ship can be used for covert operations.

[Return to Archives | Return to Listing ]

Start Duty Log SD9611.02.0832 Loth Time.
Lt Dave,
Chief Engineer and
Computer Systems Specialist.

*** Administrative Stuff: ***

"To delegate is the keyword to most management tasks and to satisfied
personnel, which should be seen as a goal as high as the work itself."
That was what I wrote last time.
Meanwhile, communication with my new Assistant Stan (Ltjg Tetro) is
successfully improved, so the time was worth it.
I'm still filling in new crewmembers, but I like this job, especially cause I
can still remember how lost I felt when I joined back on SD9606.16. Time for
a half year party ...

*** The Mission on SD9611.01.2100: ***

Divisions and Division Leaders were introduced.
We all know as much as we did before. It's a big mystery to all of us.
There is no way to find out, who's Leader to whom, since the roster contains
only "-"s.
By word I know that my "Engineering Reports" go now to Lt1 Feklhr.
What my "Engineering Reports" are, well, hell knows what. May-be.
I'm writing detailed Duty Logs and they include my work at Duty (what else
should they).
A further explanation, scheduled for the end of the mission, didn't took
place.

Because of this, I send a copy of this Duty Log to the High Command.
I'm the last one who wants to act against any order, we all just don't
understood this order. I can't help it. It was mentioned on the roster, so
said our Captain and our Commander. May-be they got different rosters ...

We were still in hidden in the star's corona to continue our Expose and
Destroy Mission.
Since we got more personnel (thanks a lot !!) the teams were new divided.
Team Alpha: Captain Sean, XO Lt1 Feklhr, Lt1 Josh and Ltjg Tetro.
Team Beta: Commander Neil, XO Lt1 Chid, Ltjg Wolfe and Ensign Joran.
Onboard the Lothlorien: Counselor DeLia, Medical Assistant Ens Talura and
myself, Lt Dave.

I showed Ltjg Tetro (Stan) the way to Engineering. As he said, this is a fine
ship.
And our TurboLifts are the most exciting thing in the entire StarFleet I
guess ...
So Stan saw our Engineering "Office", and I showed him my consoles, so he
knows where his are. Easy to find, since mine are dusty and the keyboards,
well, kinda decorated with well placed cup~o~chino spots. Neelix would like
it too, I'm sure.
Stan got lost.
I guess I must get used to it, since he's a ghost.
He really disappeared.
Right before my eyes.
Never saw something like this, except for my home planet IN of cuz.

Well, the teams gathered in Holodeck 2 on deck 9 and on Holodeck 1 on deck
19.

I've had nothing to do, except for normal observations on my instruments at
Engineering.
Josh was so kind to let me have a milk shake from his quarters, so I beamed
over. It tasted real good, Josh ! Bring more of them !

Meanwhile Tetro materialized again and he obviously studied his papers, since
he made perfect use of the Computer System to beam him right into Holodeck 1.
(That's the good part of being an Engineer, you always know a shortcut ...)

I took the Lift back to Engineering and Stan did his first jump in the
Holodeck, some 10,000 feet or toes or whatever deep. I noticed he was scared
at first, until he remembered, he's a ghost, so what should happen ? I'm very
curious about his story once we have time to chat in Engineering !!

I switched on the cameras to watch the scene. Fun, lotsa fun !!
As much as Josh's milkshake. Specially when our Captain uses an airsurf
board.

I remembered an old song from my 1975 Earth Years stay on Earth, something
like "Surf, surf, surf ..." from the "Holobeach Boys" or something thelike.
Captain Sean really showed off, some skydiving, looked very good ! Stan, our
ghost had less fun and was scared.
Well, if I was in his gravityboots, I'd dematerialized and just showed up on
the beach again. Instead he was getting sick.
Josh was dying again, he landed in the water, couldn't swim, sunk and the
fishes (Josh's friend by heart) started nibbling his nose and stuff.
Captain Sean teleports both to the dry beach, so they

[Return to Archives | Return to Listing ]

Meanwhile Tetro materialized again and he obviously studied his papers, since
he made perfect use of the Computer System to beam him right into Holodeck 1.
(That's the good part of being an Engineer, you always know a shortcut ...)

I took the Lift back to Engineering and Stan did his first jump in the
Holodeck, some 10,000 feet or toes or whatever deep. I noticed he was scared
at first, until he remembered, he's a ghost, so what should happen ? I'm very
curious about his story once we have time to chat in Engineering !!

I switched on the cameras to watch the scene. Fun, lotsa fun !!
As much as Josh's milkshake. Specially when our Captain uses an airsurf
board.

I remembered an old song from my 1975 Earth Years stay on Earth, something
like "Surf, surf, surf ..." from the "Holobeach Boys" or something thelike.
Captain Sean really showed off, some skydiving, looked very good ! Stan, our
ghost had less fun and was scared.
Well, if I was in his gravityboots, I'd dematerialized and just showed up on
the beach again. Instead he was getting sick.
Josh was dying again, he landed in the water, couldn't swim, sunk and the
fishes (Josh's friend by heart) started nibbling his nose and stuff.
Captain Sean teleports both to the dry beach, so they were fine.
Stan thanked the Lord (which one ?) on his hands and knees, whilst Josh held
a fish in his hand, of course.
Yeah ... I like this kinda TV programs, they are so ... real.

Tetro was obviously really sick, he asked me for Tylynol. I dunno what that
is, so I told him to ask our Medical Chief Lt1 Chid. He seemed not to have
understood, so I asked Chid.
He wasn't that lucky, since it's a silent mission now on the land, but I
can't give any drugs to anybody without permission. I admit, I forgot Ens
Talura.

Well, so I let the Computer lock onto an ampoule Tylynol whilst the ground
troops recorded their last words on tape for their moms. That Tylynol was
transported to Stan, who eat the whole pack. I'm curious what the heck that
stuff is. Even Tetro himself didn't knew that he could get sick as a ghost.
Well, on board our ship there's everything possible ...
So Ens Talura prepared sickbay for possible casualties.
Stan got more sick and coughs blood. (What blood ???) Well, it got worse very
quick so I initialized an emergency beam to SickBay.
Talura got him, and she got strange readings whilst Stan prepared to go to
heaven and said good-bye to Talura. She put him in a stasis field. We will
have some work I guess. Talura had to put a level 5 stasis field around him.

I was arguing with the Captain about the self-destruct of the fighters.
Yeah, he has the last word, but I still see this as a waste of equipment,
when a tractor beam would have the same effect. To start a secret mission
with a self destructing fighter as a firework is something I can not
understand.
But I'm onboard the ship and he's the Captain. If this mission leads to
dangerous injuries and possible deaths, I'll beam the person in question
back, no matter what order I have (see my BIO for details).

The troops left the shuttle bay and flew down to the planet.

I've had the Computer locked on Stan, just in case.
Both Talura and me don't know how to treat a ghost on his way out.
Talura found out that the holodeck scanners must have disturbed his
biochemical substances,
and at this point she could start curing him. :: SIGH ::

Meanwhile the fighters exploded and the troops landed.
What a waste.
I mean the fighters.

That's it.
Stan will hopefully recover, Talura did a very good job again,
and the explanations about the "Divisions" didn't come, altho asked for.

End Duty Log SD9611.02.1027 Loth Time.
Lt Dave,
Chief Engineer and
Computer Systems Specialist.

[Return to Archives | Return to Listing ]

Computer begin duty log

It is been a very exciting mission indeed, at least so far who knows what is
to come. This has been the first time I have ever used a parachute for a
type of covert operation. It was a good thing we did a practice run before
we actually did the final run because I had one minor problem with my chute.

It wouldn't open in holodeck until I was a few feet above the water. So I
when I hit the water it felt like I was doing a belly flop from O 20,000 feet
it hurt. I made sure to check my parachute before we went on this run and
thank goodness it worked.

Well once we hit dry land in the holdeck sim we quickly removed some Jem
Hadar soldiers. We then started our climb up the mountain when the program
was cut off. I guess we were ready for the real thing. Team Beta proceeded
to the shuttlebay loaded up our equipment and we were off into the Wild Black
Yonder. We hit dry land quickly and thats where we are right now.

Computer end duty log.

[Return to Archives | Return to Listing ]

=============================================================
INTERFLEET MEMO
From: Lt Dave, Computer Systems Specialist, Chief
Engineer.
To: Lt1 Mike32
Further Attention to: Crew Of The USS Lothlorien and Friends
=============================================================

In a message dated 96-11-08 21:02:45 EST, you write:

>O.k. Here is me talking to you through E-Mail. Who is TC? Do you control
him?
>And tell me about him? Thank you.

First of all, Mike, and EVERY CREWMEMBER onboard:
I can not handle IMs during a mission, except for TWO ONLY.
It is, because I use AOL 2.5.
I use this old software, because 3.0 does NOT WORK on OVERSEAS connections !!
The second reason is, that 2.5 is FAR FASTER than 3.0.
Third, I don't need all that InterNet stuff, because I have already FOUR
InterNet providers,
and I got every 'Net program I need. And they all work faster, and - the use
costs me nothing.

For this reason, I don't use the PowerTools, and you can remember (if not,
try !),
that you always have to find the right window and always need a mouse-click
to
chat via IM with AOL 2.5.

So please restrict IMs to ABSOLUTELY NECESSARY things only.
This does not apply to the Captain and Commander.

I hope, you can now understand, why I'm so angry about IMs.

TC:

Well, Mike, you're asking now for half a year. I'm trying to fill you in.

The Computer onboard the USS Lothlorien is a M-13-C Bio-Neural Duotronics
numbercruncher,
located on decks 20 and 21, Section 12.
The system runs LCARS Type III as its O/S.

When I first came onboard, I saw that the Central Computing System has no
own voice and wasn't able to hear anybody.
Instead, communication with the computer was faked by typing.
Like "COMPUTER> Shields at 30%" and stuff thelike.

I was directly posted to the Engineering Department, so the Computer System
is a part of my job.

The missing gap was, that the Computer couldn't hear and talk.

This gap was filled by creating a new subsystem, which - after some
discussions -
we called "TC" for "Talking Computer".
The original task force included Damara and Tnagra,
with lots of input from other crewmembers at that time.

>Who is TC?

TC is the voice and the ears of our M-13-C Duotronics Main Computer.
Since everybody has its own style to talk, TC got improved from week to week
(and still is) to understand, for instance, shortcuts used by some members.

If you stand before a Turbolift, and you say "TL, SB" the Computer can not
know what you mean and nothing would happen.

TC - as the "translator" between carbon based systems and the mainly silicon
based M-13-C Computer - now translates "TL" to "Turbolift" and "SB" to
"SickBay".

The result is, that the Computer (to be exact, the Turbolift-Subsystem
(turboliftd))
now knows what you want and he opens the door (in case you are not already
inside the TL) and moves the Lift and tells you what is on that deck you are
heading to.

Yesterday, our Captain said:
USF Silona: TL Bridge!

As you know, on any other ship of the StarFleet, nothing would happen.

On the USS Lothlorien, we have TC who heard our Captain, and the result was:

TC demon: TurboLift> Deck 11, Captain Sean: Main bridge, Captain's
ready
room, Observation lounge. {S TL

Every silent computer task that reacts on special input or events is called a
"demon".
That's why his complete name is "TC demon".
(From the Computer's point of view, "tcd" would be correct, but we don't
wanna push
it too far, right ?)

That is TC.

>Do you control him?

No.
Only at one point, I'm the only one who can start him and shut him down.

He enters "silent mode" automatically, when ATTENTION is called (in whatever
way),
and he leaves this mode automatically again.

He can be turned to total silence by our 2nd XO and all ranks above. Plus me.
The command is "TC,

[Return to Archives | Return to Listing ]

>Do you control him?

No.
Only at one point, I'm the only one who can start him and shut him down.

He enters "silent mode" automatically, when ATTENTION is called (in whatever
way),
and he leaves this mode automatically again.

He can be turned to total silence by our 2nd XO and all ranks above. Plus me.
The command is "TC, standby".

He can be restricted to listen only to this group too.
(What makes little sense, but it is possible.)
The command is "TC, authorizedmode limited".

I enhance his capabilities, if I see a need for it over the week,
but once the System runs, I use it like any other crewmember too.

I have no special influence on what he does.

There is only one faked thing:
(I really unveil a "secret" here ...)

If you type "Computer, the sky is red, agree ?+",
the answer will be "COMPUTER> to Lt Mike 32: YES".

If you type "Computer, the sky is blue, agree ?-",
the answer would be "COMPUTER> to Lt Mike 32: NO".

The trick is the "+" / "-" behind the "?".
That's the only faked thing, and it is available to everybody.
It's listed in the "TC Manual".

Hope this helps.
There is a basic FAQ file available, created in the "early days" on SD960722,
and there is a Command Overview, the "TC Manual" which is always up-to-date.
A complete documentation is available in a "not yet ready" style.
(Every true star programmer hates documentations.)

Every USS Lothlorien crewmember can order these three documents anytime.
The "TC Manual" is regularly posted to all crewmembers of the USS Lothlorien.

I'll think about making them avail for everybody in StarFleet, okay ?

Now please let me finally know, who are you and who controls you ?

Lt Davey,
Chief Engineer and
Computer Systems Specialist,
USS Lothlorien.

[Return to Archives | Return to Listing ]

Computer: Begin Duty Log SD 9611.01.2100 Loth time

Before the mission began, the new chain of command was discussed for filing
reports and such. Although it didn't involve me, I was still somewhat
confused as to the changes in reporting to Division leaders. I'm not really
sure what purpose is served with the changes but maybe explanations are
forthcoming. Then, again, maybe not... this is StarFleet after all.

As the mission began, there was some confusion on my part as to what my role
would be. The last I had heard was that I would be on Beta team. It turns
out that I was now assigned to remain with the ship. Not a problem for me
since I was not all that thrilled with the idea of jumping out of a fighter
at 10,000 feet. And since the plan was for the fighters to self-destruct
after all had jumped, staying aboard would not have been an option.

My participation in the mission was basically as an observer. All seems to
have gone well. The teams have safely landed on the planet with the
exception of Tetro, who did not take well to his jump. Lt Dave had to beam
him to sick bay when he began to cough up blood (blood? in a ghost?) and it
became necessary for Ens Talura to put Tetro in a level 5 stasis field. It
is still doubtful whether Stan will survive. Hopefully, Talura will be able
to come up with something before it is too late. She's
done a bang up job so far!

End Duty Log