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

[Return to Archives | Return to Listing ]

:: After Ariell showed Dave where the first monitor in her office should
be set up, she walks with him into her quarters to show where she wants
the second monitor to be. Both rooms are really big and comfortable. ::

I think that I want it to go here.

:: She points to the top of the dresser ::

I can see this area from all parts of the room. Yes I think this will do
nicely.

Okay then.

:: Dave heads back towards the office ::

I will put the one in your office in first then I will come over here to do
the other one.

:: Dave walks into the office. The adjoining door closes ::

(Smooth. These doors know how to behave. HA! When I was on the Heart-Of-Gold,
with ol' Buddy Zaphod, the doors behaved real strange. But it was lotsa fun,
that's for sure. And Marvin ... :: laughs :: ... oh yeah ...)

:: Dave walks to the table Ariell has set up for the monitor. ::

(Yes, that's solid enough.)

:: Grabs the monitor outta the container. Well, kinda "grab". ::

:: Gets it on the table. ::

(Well, non-techies don't like cables, they should see ** my ** quarters,
well, better not. Any dome here ?)

:: Dave knees down to search for a connection box on the floor.
There is one, under Ariell's office table, but it is not in use. ::

(Okay then, before she stumbles over a wire or maybe thinks this could be
done in more "comfortable" way, I'll use a wireless connection.
Would never use it in my quarters tho.)

:: Dave removes the back cover from the monitor. ::

(Yo, Buddy. Don't ever assume someone would like the way you handle stuff
in your quarters.)

:: Dave leaves Ariell's office and heads to the TL. ::

Hi Turbolift, let's have a ride to 31.

Turbolift> Deck 31, Engineering Support, Ltj Dave.

(I still haven't changed TC to forget about that "LTj". Last period of
awakeness was a again a typical one. No direct visible successes,
and who looks behind the scene ? - No-one!)

:: TL stops at deck 31, Dave gets out and searches for two wireless
data links. He found them, heads back to the TL. ::

Lift, back to 16.

Turbolift> Deck 16, Senior officer's quarters, Lounge, Holodeck, Counselor's
Office,
Turbolift> Ltj Dave.

(Yo ! Hope you call me Dave when I got the time today and find that bug
I couldn't find yesterday, well, last period.)

:: Dave leaves the TL on deck 16, goes to Ariell's office. ::

Hi door, Dave again. Would like to have you open!

:: Door opens without the slightest noise. ::

:: Dave changes some switches on one of these data links, then he inserts
it inside the monitor. Closes the rear cover. ::

(And now ? What the heck is the name of the nearest router ? I will need to
create
aliases for every router as soon as I'm finished here. No-one can keep track
of these names. Except for ...)

+taps+ TC, on deck 16 there is a new data link. Ah - wait a sec.

:: Dave leads the cable from the monitor to the rear end of the table the
monitor stands on, under the plate towards Ariell's desk, pushes
the monitor table a bit away from her desk, removes the cover of the
connection fillet, inserts the power cable to an unused jack.
Pushes the cover back into her desk and moves the monitor table back,
directly to her main desk. ::

:: Dave holds his forehand directly before the screen and switches it on.
The monitor got power. ::

+taps+ TC, there is a new data link on deck 16. Locate the nearest router,
give this router the alias name 16-COUNSELOR-OFFICE, and connect
the new data link to this router.

TC> Connecting ... LTj Dave.

+taps+ Thanks, TC !

TC> Okie-Doki, Ltj Dave.

(He got the same problem the lift has. Gotta work on TC today !!!)

:: Dave walks around the two desks, that now look like one big desk, with
a kinda "extension" at the rear end, sits down in Ariell's chair. ::

(Wow. I need a promotion to get a chair like this.)

+taps+ TC, connect the new data link that you just connected to the r

[Return to Archives | Return to Listing ]

+taps+ Thanks, TC !

TC> Okie-Doki, Ltj Dave.

(He got the same problem the lift has. Gotta work on TC today !!!)

:: Dave walks around the two desks, that now look like one big desk, with
a kinda "extension" at the rear end, sits down in Ariell's chair. ::

(Wow. I need a promotion to get a chair like this.)

+taps+ TC, connect the new data link that you just connected to the router
16-COUNSELOR-OFFICE to router 22-1-1.

TC> Connecting ... Ltj Dave.

:: Dave watches the screen. It flickers a few times then he sees two
babies in their incubators. ::

(YEP!)

TC, this will be a steady connection. Interrupt this one only if you
really need the resources. In this case shut down the connection without
asking anybody.

TC> Acknowledged, Ltj Dave.

(This name thing will be one of the first things I change when I'm back down
under.)

+taps+ Ariell, I'm ready here, shall I install the other one in your
quarters now or later ? For me, it doesn't matter.

[Return to Archives | Return to Listing ]

"Not much to say... might a well though. Computer, Begin Log."

~^~BEEP~^~

Tonight was frustrating to say the least. There wasn't much on the side of
duty, but we got a new captain, X.O., etc. As I said, there wasn'r much duty
so there isn't much log.

"Computer, End Log"

~^~BEEP~^~

[Return to Archives | Return to Listing ]

Duty Log SD 9609,10,1252 Lothlorien Time.
LTj Dave,
Engineering,
Computer Systems.

Another Day In Paradise !

May my cup-o-chino program for the replicator live long and prosper !

Still no message from the Captain, whether his panels are working or ruined.
I don't like it when someone tries things on his own that really are
dangerous.
On the other hand, Captain Ryan seems to be familiar with computing stuff.

I'm very glad about this fact.
He will see things like our TC Project from another point of view than ...
YO.
I should find and fix the bug during the next period of awakeness.
After that, the synchronization process has to be re-programmed.
I guess Captain Ryan will allow TC to reply when someone talks
to the computer and them turbolifts.

On the other hand, Captain Ryan will detect any fault I make. <BG>

Okay, first task as everyday: answered all incoming messages.
I dunno how long I worked on it, but 4 hours might be close.
Well, and I like this, it shows that this ship is really awake all the time.
When we finally got the rest of crew, that Captain Ryan will bring with him,
I hope we'll get closer to somewhat like a family. It's a good feeling here.

But maybe, I simply went loco already.
(Although I didn't stayed too long in Acapulco, in fact I never was there.)

Well, I spent 6 hours reviewing some technical stuff, some of them I
forwarded
to Science and some to Tactical.

Meanwhile, meaning parallel, I continued to tweak the meanwhile famous
subsystem,
that now has a real good performance.

Finally I could start working on TC, trying to find the bug.

Got a note from our Captain, the CMOS security feature works okay on his
machines.
I wish others would take more care about their stuff too...

It's awful, after 5 hours I could locate the routine that obviously is buggy,
but that animal itself ... haven't found it yet.
But on the other hand I still continue to speed up Darkstar, the machine that
crashed
so horrible the other day.

TC's status messages about single devices (shields, engines, transporter
etc.)
have to be carefully reviewed before they can be enabled.
When the sync problem will be solved, I think we could let TC answer
as the computer and the lifts, until Damara and me
have checked the reliability of the different status messages.
Always assuming I find and fix the bug, and the sync process works.

I take a break. SD9609,10,2239 Loth Time.

Okay, I spent the last two hours talking to a friend of mine, a Counselor.
I wanted to check out about my crazy time schedule.
I'll change some things, but I'll keep working as long and as hard as I
always did.

Darkstar, the subsystem, that causes that much trouble, will stay how I
configured it in this period.

I transferred a connection application to Darkstar, that will allow us to
gather more
information, since it runs automatically while I can work on other tasks.
This took nearly 2 hours, but it will save a lot of time in the future.

But now, I'll call it quits.

End Duty Log SD 9609,11,0646 Lothlorien Time.
LTj Dave,
Engineering,
Computer Systems.

[Return to Archives | Return to Listing ]

Dave is in Ariell's Office and is finishing work on the monitor that shows
her babies in the Sick Bay's incubators. He's just talking to TC.

TC> Connecting ... Ltj Dave.

:: Dave watches the screen. It flickers a few times then he sees two
babies in their incubators. ::

(YEP!)

TC, this will be a steady connection. Interrupt this one only if you
really need the resources. In this case shut down the connection without
asking anybody.

TC> Acknowledged, Ltj Dave.

(This name thing will be one of the first things I change when I'm back down
under.)

+taps+ Ariell, I'm ready here, shall I install the other one in your
quarters now or later ? For me, it doesn't matter.

Go ahead, Dave, I've left my quarters.

(She seems to be in a lift, at least it sounds like that.)

+taps+ Okay, Ariell.

:: Dave thinks about the heavy monitor, that still is inside the container
near
the Office door. Comfortable to have a door between quarters and duty
room.
More or less, he made his quarters to his duty room ... by installing and
routing
his engineering consoles to his room. ::

(Okay. I need to start.)

:: He stands in front of Ariell's door between her office and her quarters.
::

Door, get open. And STAY open.

:: Door opens without any noise and really stays open. ::

(Fine. Now transport the monitor ...)

:: No way, he grabs the monitor outta the container, and carries it over to
Ariell's quarters, puts it on her dresser. Well more or less, "let it
fall"
would describe it better. ::

(Wow. But these old time monitors have some features, these modern panels
don't have.
Good to have some in stock in the supply.)

:: He walks back to the container and takes the data link card. ::

(Okay. Now lets get rid of the cover...)

:: Dave removes the rear cover of the monitor. He sets some switches on the
data link
and inserts it into the monitor. He luckily finds a power outlet near the
monitor. ::

TC, I'm in Ariell's office.

TC> Good for you ! How's it going ?

What's up ??!!?? TC?

TC> Sorry, does not comply: "What's up TC".

TC, are you there ?

TC> Sorry, does not comply: "TC are you there"

(Hell, what's up with him ?)

TC, did you got yourself a camera and watched some old time movies about
robots that
behave like carbon copies ?? Any weird Enterprise stuff ?? Anything with a
figure called
"Data" ?

TC> Sorry, does not comply: "TC did you ...

TC, stop this nonsense. Locate a new data link on deck 16.

TC> Got it, LTj Dave.

(When will I find the time ...)

Good, connect the new data link to the router 16-COUNS-OFFICE.

TC> There is no such router.

TC, what was the last alias name you gave to a router ?

TC> 16-COUNSELOR-OFFICE.

Okay, connect the new data link to router 16-COUNSELOR-OFFICE.

TC> Connecting ...

Thanx !

TC> Okie-dokie, Ltj Dave.

(Yo !)

:: Dave switches on the monitor. It flickers, than the screen goes blank. ::

(Yo !)

TC, connect the router 22-1-1 via router 16-COUNSELOR-OFFICE to the new data
link.

TC> Connecting ...

:: Two tiny babes appear on the screen. ::

TC, Thank you !

TC> Okie-dokie, Ltj Dave.

(Yo !)

:: Dave walks back to Ariell's office. ::

Hey door, close yourself.

:: The door closes without the slightest noise. ::

(Yo !)

:: Dave grabs the empty container and leaves Ariell's office, walks out to
the floor. ::

Hi door, get closed !

:: The office door to the floor closes without the slightest noise. ::

(Yo !)

:: Dave walks to the next TurboLift. ::

Hi TL, deck 36.

Turbolift> Deck 36: Main engineering.

(Yo !)

+taps+ Ariell, your monitors are ready and working.

Thank you, Dave.

+taps+ Okie-dokie. Ah, sorry, I mean not to mention.

Okay, Dave.

[Return to Archives | Return to Listing ]

Duty Log SD 9609,12, 1014 Loth Time.
LTj Dave,
Engineering,
Computer Systems.

Gotta continue work on TC.

Ah - before I forget, the two monitors for Ariell are set up and working.
And I sent a few jet pictures to Anne.

Starting on TC at 1500 Loth Time.
Ready for a test drive at 1757 Loth Time.

TC enters the scene.
And works.

On Darkstar, the performance is real poor, due to the sloooow system itself.
But a real test can't be done unless at a real mission, there is no such high
traffic anywhere
else.

The new sync routine is great, I'm just not sure if he catches one line to
late.
Was right. He was too late. That's fixed.
But there are still times he gets really outta sync.

I've a slight idea about it, but I'm too tired again.
I'll have a break. SD9609,12,2130 Loth Time.

End Duty Log SD 9609,12, 2214 Loth Time.
LTj Dave,
Engineering,
Computer Systems.

[Return to Archives | Return to Listing ]

-------------------------

Computer, begin duty log, 9609.6.
Voice Authorization Code: Alpha-Theta 82

This was a big day for me today, larger than most. There was drastic
changes in the chain of command, for the better. We were ordered to the
shuttle bay where our Captain and Commander transfered their authorization
codes to Captain Sean Astro Ryan, our new captain. Our former Captain and
Commander made their final farewells to the crew and the went into the
shuttle. The shuttle doors closed and bay door opened, and they left.

After the change of command, Captain Ryan ordered everyone to 16 Forward
where we got to know eachother. I sat by my self in a corner. I watched a
little "friendly" game of chess between LT1Chid and LT1 Feklhr.

Computer, delete the last line and change it to "A minor disagreement between
LT1Chid and LT1Feklhr".

A very stressful day for me.

Computer, End Duty Log.

--------------End Duty Log--------------

[Return to Archives | Return to Listing ]

Duty Log
SD: 9609.7
LT Josh
Assistant Chief Tactical Officer

^v^v^v^vBeep^v^v^v^v^

I've just got done upgrading the Lothlorien's shielding frequencies.
This will allow the ship to change shielding frequencies in a time of an
emergency to have more suscess in shielding agains phaser fires, torpedo
hits, etc.

I put a program which will aproximate the energy that will discharge on
the shield and in return, adjust the shield frequency accordingly. This is
best worked away from any source of Gamma radiation due to some unkown things
that will cause the program to get a less accurate reading on the energy
discharged on the shields.

End and Secury Duty Log.

[Return to Archives | Return to Listing ]

First Lieutenant Damara Seven
Chief Engineer
USS Lothlorien

DUTY LOG STARDATE 9609.13

::On board the Shuttle, Damara decides to take the opportunity to record her
log as they approach the planet::

Computer, open duty log for LT1 Damara.

C > Acknowledged.

The Lothlorien has been called to Crysalon 4 in order to investigate the
disappearance of two geologists. They were on the planet studying a mineral
new to the Federation. When we arrived at the planet, we discovered that an
energy field which surrounded it prevented anyone from transporting to the
surface. The field apparently originated from the planet itself. Since the
electrical readings were stable and constant, I thought that the field might
be artificial rather than natural. However, Lt. Josh had
a theory that an unstable wormhole may have sucked part of a star into
intself.

Lt1Mog suggested sending a class 8 probe, with boosted sensor input, to
compensate for the electrical interference in order to confirm the exact
nature of the energy field. Lt1Feklhr and I concurred with the suggestion.
Once Mog had made the necessary modifications, the Commander ordered the
probe to be launched. We immediately started getting data back from the
probe. Mog was also able to pinpoint that the shield was eminating from a
power genorator on the planet, somewhere in the south-polar region.
Phasers could not penetrate the shield but a shuttle could pass through
safely and hopefully an away team could deactivate the shield.

An away team was assembled consisting of myself, Cmdr. Neil, Feklhr, Rogue
and Josh. Mog transferred the details about the generator and coordinates for
the science outpost to the shuttle. While we were preparing to leave, Mog
reported that our probe had been destroyed by an energy blast from the
science outpost on the planet. The shuttle is currently on its way to the
planet.

Computer, close duty log.

C > Duty log closed.

[Return to Archives | Return to Listing ]

::Ariell is in her quarters after visiting the twins::

Computer begin Duty log authorization Thomas 3
>Begin when ready

SD 9609.13

I was not needed on the Bridge today so I stayed in my quarters to
recouperate from the birth of my twins.

To my knowledge the ship was summoned to some planet in the Chryslon system.
Some of our crew was assembled on an away team for a shuttle ride to one of
the planets.

Lieutenant Commander Ahrele has decided to transfer to the USS Columbia. Her
shuttle leaves in two days. There are many changes happening on the USS
Lothlorien. I have no idea what other such changes shall transpire before I
make my own decision about my future here.

Computer close log and secure authorization Thomas 3
>File closed and secured

[Return to Archives | Return to Listing ]

Duty Logs SD 9609,13,1003 thru SD 9609,16,1735 Lothlorien Time.
LTj Dave,
Engineering,
Computer Systems.

At 1800 Loth Time TC seems to work reliable. The sync process works nearly
all the time.
Nearly.

SD 9609,13,2015 Loth Time.
Now the sync process works. No errors, all "invisible" recovered.
That's the way I like.

Just Darkstar is still too slow, I try to speed him up as far as possible.
A few bucks would help ...

Hey, wasn't there a mission scheduled for today ?
Gotta hurry ....

Duty Log SD 9609,14, 1718 Lothlorien Time.
Lt Dave,
Engineering,
Computer Systems.

Yesterday was a great day for me and TC.
I was promoted to LT, and TC was switched off and on by our Captain, who
started to use him.
I couldn't follow what really happened on the mission, due to a steady
communication,
but TC did a fine log I will review right now.

And I'll extend his set of commands and replies to our Captain's style of
asking.

TC is an intelligent system, which grows after every mission.

Gotta work.
Done. SD 9609,14,2050 Loth Time.

I improved the response set of both TC and the COMPUTER and now ... I "only"
need to
do a documentation. The most hated task of every real programmer.

Maybe I let TC do the documentation himself, by starting him and typing
everything he
replies to.
Maybe a nap will get me closer to a quick way.

SD 9609,16,1733 Loth Time
I worked the last days on the documentation about TC,
and since this is a thing every starprogammer hates, I couldn't update any
logs,
but needed to concentrate on this work only.

I hope it will be ready today.

End Duty Log SD 9609,16,1735 Loth Time,
Lt Dave
Engineering,
Computer Systems.

[Return to Archives | Return to Listing ]

Duty Log SD 9609,16,1800 Loth Time.
Lt Dave,
Engineering,
Computer Systems.

Everything on board works fine. Regarding the hard- and software.

The loss of Damara as my Chief in Engineering is very hard to take.
Somehow I always am somehow both working on Engineering and Science stuff,
but since I love the challenge to solve very critical situations the ship and
crew might
run into during a mission, I'm still in Engineering.
This is a Duty Log, but my feelings about her loss effect my work, so it has
its place here.

The loss of Ahrele and Ariell is hard to take too.
Again, the rats are abandoning ship.

Two issues for today.
The TC Documentation and the Wormhole we encountered on the last mission.

I start with the documentation. SD 9609,16,2034.

Meanwhile I've sent a pre-release of the TC Documentation
to Damara, Captn Sean and Commander Neil.
After that I took a nap and woke up right now, 24 hours later.

There is something wrong.

I will continue my work after getting the news as usual.

End Duty Log SD 9609,17,1713 Loth Time.
Lt Dave,
Enginnering,
Computer Systems.

[Return to Archives | Return to Listing ]

LT1 Chid Chief Medical Officer
Duty Log SD 9609.13

::Sits down in his office::

Computer Begin Duty Log.

Today was great day for the medical staff, no one had any medical problems,
and there were no wounded at all. Since I was not needed in Sickbay at the
time I proceeded to the bridge.

We were on a mission to a planet called Crylson 4 I believe, too find out
about missing scientists or something like that, I don't really remember all
the details. Once we arrived at the planet we discovered that there was some
type of energy field surrounding the planet. I scanned it to see if there
was any health risk to the crew. I did not find any.

Once that was done, I asked how Ariell's children were. At my last check
they were in good health but Ariell told me that they weren't not doing very
well. This was most puzzling indeed, I went to Sickbay to sort it out.

I discovered that an Ens JoeBob, one of my staff members gave Ariell's twins
some Metrazine. Ordinarily this wouldn't be a problem, but in their weakened
condition, it made them even worse. There wasn't even a reason to give it to
them. I asked the computer where Ens JoeBob and to my astonishment, he was
not onboard. An investigation is underway.

Computer Close Duty Log.

[Return to Archives | Return to Listing ]

Duty Log SD 9609,17,1713 Loth Time.
Lt Dave,
Engineering,
Computer Systems.

Still two issues due to my remarkable sleep.

The TC Documentation and the Wormhole.

Again, I start with the damned Documentation. SD 9609,17,1735 Loth Time.

I decided first to analyze the last mission regarding the Captain's commands
to TC.
Everybody has it's own style to question someone, so I made sure he'll get
answers
to nearly everything he send to TC to process it.

Fixed a bug in TC's control routines at SD 9609,17,1910.

TC does a test drive in a public area. SD 9609,17,1941.

I need to get the news what's new on interesting files etc.
Got it and sent out two offers. SD 9609,17,2000.

Okay, now I'm adding some stuff the Captain would like TC to do.
Done and notified, SD 9609,17,2140.

Well, worked hard on the Documentation to include all Responses etc.
I need a break. At least the documentation will be ready in the next 20 hours
for sure.

Duty Log Paused, SD 9609,17,2335 Loth Time.
Lt Dave,
Engineering,
Computer Systems.

[Return to Archives | Return to Listing ]

Duty Log
SD: 9609.13
LT Josh
Assistant Chief Tactical Officer, U.S.S. Lothlorien

---------------------------------------------------------------------------------------------------------------------------

Man, this was on the MOST exciting day a man could have!!! While our
ship was in an orbit around a planet for a couple of hours, LT1 Feklhr
detected a minor object on our sensors that had popped up all of a sudden. I
decided to confirm that with my counsol since it had its own little power
source our engineer Dave had provided us and there was something out there.

As time passed, the object grew. Apparently it was a worm hole with a
very strong gravitational field. As more time passed, part of a star
appeared through the worm hole. The star was going in and out of the worm
hole, like it couldn't make up its mind on what to do.

I have two theories regarding this worm hole. If it was a natural one,
a star apparently pulled the worm hole into its gravitantional field. If
this is what had happended, I esitmate the proscess would have taken
centuries.

My other theory is if this is an unnatural worm hole, it too was created
away fom the star. The star's gravational field some how "grasped" it and
pulled it in. This proscess would have probably taken centuries to complete
too. If a ship were to get too close to the star and attempt to create a
worm hole, the risks would be too great. The ship would have a great risk of
being pulled into the sun's gravational field and colliding with it.

Apparently the star and the worm hole are toghter. The worm hole
follows the star since it is caught in its gravational field and cannot
escape, thus causing a VERY unstable wormhole. I estimate that if someone is
going to go through the worm hole, they would end up 3 billion light years
away but I wouldn't think we'd have any voulnteers to go prove that theory.
I also believe that the worm hole is in orbit around the star since part of
the star is coming in and out of the worm hole.


If this unstableness continue, it may cause the ENTIRE solar system to
go through the worm hole and colliding with the star. I intend to discovere
more about this avazing "thing".

[Return to Archives | Return to Listing ]

Duty Log SD 9609,20,1746 thru ,21,0017.
Lt Dave,
Engineering,
Computer Systems.

Okay then, the day starts as usual, it's afternoon / night, and I'm gonna run
some rough
tests with TC.

I made one important change, that will not be visible.
When you mix up who you should address, the Computer himself, or TC, TC keeps
track of what
you meant and routes your message to the Computer if appropriate.

Another BIG change is, that TCDEVICE now takes part to keep track of shields,
transporters,
weapons etc..

No messages waiting here, so I gotta make sure that both works as I expect it
too.

Well, I was ready at 2100 Loth Time when the mission begun.

It is remarkable, that someone is upset about TC, even before he's present.
Fear about something unknown ? I don't know.

My conclusion: There will be a command, so that everybody can exclude himself
from TC's
attention. The command will be "TC, forget me.".

Those, who don't access the Lothlorien's Database and don't read this, will
of cuz be bothered
further on, but may-be this will lead to more attention when it comes to Duty
Logs someone
writes, who does something (or is responsible for) what someone doesn't like.

The intentional disturbance by sending messages to TC will be subject to
changes too.
TC will flame them back.

We all survived the mission, so I'm gonna analyze the data.

Since lotsa folks left the ship and new ones arrived, TC must learn what they
mean with their
words.

I wrote an InterShip Memo about that,
but I'm not sure that everybody will read it.

TC simply doesn't know about the typical, personal style someone uses, unless
he heard him
several times. So I'm gonna eliminate every point where TC could not
understand the person,
and it needs a hint when TC runs in "Authorized Personnel Only" mode, cuz it
seems like an error
for those, who are not authorized.

This will be Part #1 of my work the next days,

Part #2 will be to enhance the reliability about TC's knowledge about the
different devices like shields and
weapons he keeps track of.

Part #3 will finally be the "star vs. wormhole" problem.
I expected some analysis from Science, but it doesn't matter that there is no
one, I wanna find an explanation myself anyway. I think I should work
together with Science more often, since I'm somehow
between these two departments anyway.

And most important,
Part #0, so to speak, must be the a coordination back to the Engineering
Department.

Gosh - I like old time music from my 1978 stay on planet earth, but we're not
playing "kitchen at parties" where everybody can come in to tamper on some
instruments.
I simply sealed Engineering to show a little bit, who's in control.
Folks are welcome to help and act, but it must be in a coordinated way.
I'm the last one to stop someone from working.
But I'm the first one who sees when something isn't organized, since I know
these Earthlings quiet good and worked as an organizer and analyst way back
their time.

I hope their will be done something about it on some higher decks.

End Duty Log SD 9609,21,0017
Lt Dave,
Engineering,
Computer Systems.

[Return to Archives | Return to Listing ]

Start Duty Log SD 9609,21,0056.
Lt Dave,
Engineering,
Computer Systems.

Remarkable our Captain's action to take a fighter to attack the warbird !!

Specially remarkable cuz we need to get a tight crew, which can operate
without
a Captain for some time.
(I don't see you lost, Captain, I admire the risk you've taken regarding the
helpless USS Lothlorien.)

When I just went thru all the data, I found a lot of stuff I really didn't
heard. (Sorry, Ariell.)
The most critical ones are automated right now.
And after all, Engineering might as well completely fail, if someone does the
nerve gas joke again or something.

The command "TC, forget me." is added.
There will be a hint at the "BEGIN SIM" sign.
The one who issues this command, does not get any replies, even no automatic
comments, warnings or hints. (Of course his ACTIONS will be traced.)

Everything that was addressed to TC or the Computer, and where the system
didn't replied
is now incorporated and the system will reply on these items next time.
(This is the way TC learns - by adding your words as keywords.)

Since it is extremely difficult to get a real reliable status of the
different devices (shields, weapons, energy etc.) as we found out during the
TC Project (LT1 Damara, LCdr Ahrele, LCdr Ariell, USF Tnagra), it needs
analysis of every data I've stored.
And this is nearly 1 MB on raw data.
It includes whispered words, mumbling sentences etc., because my opinion
towards a real computer aid is, that the comp must understand "help me too
sikbay" or "shilds up".

(For those who haven't read the TC.FAQ, I programmed a huge, mighty system
that way, where the error tolerance is extremely high. If you wanna know more
about or join the steady ongoing TC Project, feel invited !)

Well, all this may take more than a week, since I'll create a list of EVERY
word once spoken.
But my work on this sub-routine (TCDEVICE) doesn't disturb TC's functionary
as it is right now.

As stated above, I really haven't seen Ariell's cry for power. I could swear,
it wasn't on my windows (maybe the different versions the consoles are
equipped with? Some color jokes ? I dunno.)

Instead I was searching for Ariell. A joke, if it wasn't the truth.
Again the old topic, communication between carbon-based systems are far
slower and dangerous than between silicon-based ones.

Well, for this, some emergency routines have been added, so that no time
delay occurs.
(Even Bio-Neural components are still silicon based to me, the majority
counts.)

Well, so I added emergency power routing and emergency transport, both will
not be
controlled by Engineering, but initiated thru the "cry for help" itself.
This is much faster and I can not even guarantee for myself that I always
hear everybody.

Still to do:

#
Whenever I find the time:
The intentional disturbance by sending messages to TC.
TC will react, since it caused a blackout on TC for a minute or so.
Carbon-Copies obviously can't stick to rules.

#
Again a restructure to TC. One working day minimum.

#
A discussion with our Captain about the different switches. This will happen
in a private conversation.

#
The LOCATE command.
I see it is really a necessary one, and even tho this means loads of work,
I've put that on a higher priority.

#
Enhancing the reliability about TC's knowledge about the different devices
like shields and
weapons he keeps track of, as mentioned above. This takes longer than a week.
(For reason, see above.)

#
And finally, but before the next mission, the "star vs. wormhole" problem.
If Science has already some conclusions, please let me know, Dear Damara.

End Duty Log SD 9609,21,1144.
Lt Dave,
Engineering,
Computer Systems.

[Return to Archives | Return to Listing ]

First Lieutenant Damara Seven
Chief Science Officer
USS Lothlorien

DUTY LOG STARDATE 9609.20

::Damara is in Sick Bay::

Computer, open duty log for LT1 Damara.

C > Acknowledged.

The Lothlorien was assigned to pick up a Romulan Ambassador in the Galorndon
Core. The ship immediately cloaked and went to yellow alert because we had to
enter the Neutral Zone to accomplish this mission.

Almost immediately, we encountered a Romulan Warbird of some formerly unknown
class. Although we were cloaked, I detected that we were being scanned.
Apparently, this new Warbird had the ability to detect a cloaked ship.

The Captain ordered red alert as the Romulans targeted the bridge. The bridge
was hit and everything else is pretty much a blur for me. I remember falling
over the railing, but the next thing I knew, I'm waking up here in Sick Bay.

Computer, close duty log.

C > Duty log closed.

[Return to Archives | Return to Listing ]

===============================================
INTERSHIP MEMO
From: Dave, Computer Systems Specialist, Engineering Dept.
To: Tactical, Lt1 Feklhr, Lt Josh
===============================================

Hi Friends at TAC !!

I'm about to modify TC and the COMPUTER this week, and I would like to know
your opinions about it.

Since you are our brain during combat, I avoid that the Computer bothers you
with extra informations. Your experiences are more worthy than a computer
response, altho there are times where it makes sense to let the computer run
automatically procedures, to give you more room for thinking and acting.

If there is anything I can do for you, for instance keep away all messages
from the computer to you during combat, or building procedures, so that you
don't have to raise the shields manually, but a voice command would do that
etc., please let me know.

It is very important to me, that TAC is treated by the computer, the way TAC
wants.

Please answer in separate messages (Feklhr and Josh) so that I can modify the
way the computer acts even on an individual basis.

Hope to read you soon,
Lt Dave,
Computer Systems,
Engineering.

[Return to Archives | Return to Listing ]

Start Duty Log SD9609,22,2014.
Computer Systems Specialist Lt Dave,
USS Lothlorien, Engineering.

It's unbelievable how time consuming communications sometimes are.
But it's a very good sign that the Lothlorien is alive all day and all of the
night.
Of cuz file transfers took a big part of that time.

Plus I had to clear things with our Captain and tried to get suggestions from
Tactical regarding their wishes about the computer.

9609,22,2253, and I hope I can start work now, handling incoming messages as
they drop in.

#
I sent a message to Tactical, and I HOPE I'll get a reply from both
officers.
I hope they see how important this is.

#
The file transfer yesterday broke at 98 %, so I gotta get those 32 M again in
a second try.
It will last 15 hours aprox and is running since 9609,22,1952.
If it doesn't speed up I have to cancel it at 9609,23,0300.
Canceled the transfer at 9609,23,0037.

Now I gotta manage to be awake at 9609,23,1500 to start it again.
So this will be a short day, damned.

#
The mysterious Shield problem on last mission will ** NOT ** be analyzed
until it is confirmed that Engineering is no playing ground for visitors from
other ships and even their holo-toys. I can't do serious work when someone
tampers around at our main controls.

#
The command "TC, forget me." has a hint at the "BEGIN SIM" sign.
But on last mission, we didn't had a "BEGIN SIM" command.
So I extend it to "MISSION BRIEF".
Status: at work.

#
The re-re-re-restructure of TC is in the works.
Since I have to manage to start the day at ..23,1500 again, I hope it will be
done by 9609,24,2400.
Status: at work.

I'll just end this log cuz referring to Loth Time, another day begins.

End Duty Log SD9609,23,0049.
Computer Systems Specialist Lt Dave,
USS Lothlorien, Engineering.

[Return to Archives | Return to Listing ]

===============================================
INTERSHIP MEMO
From: Dave, Computer Systems Specialist, Engineering Dept.
To: ALL
===============================================

In a message dated 96-09-24 22:17:33 EDT, FsLtRogueQ wrote:

>
>
>I'M NOT LEAVING!!!!!!!!!!!!

I know that, C Rogue.

When I have sent the message, I took one of my famous naps.
(I'm working literally day and night on TC and stuff.)
Now when I was already in bed, had a smoke, I thought I should write another
message to all immediately.
I guessed, Ariell or someone would be very upset about my comment.

I fell asleep, and now it's about 7 hours later.

So NOW:

I STAY ON THE USS LOTHLORIEN, AND WHEN ALL THE SNOW BURNS DOWN !!!!!!

And I will even stay, if I got the rank of LCdr someday, and won't mind to
act as Chief of Science or Engineering, giving the Captain a hand "by the
way".

And I knew that YOU would stay too.

I hope these opinions won't change, and for this, I really would like to know
the REAL reason why this Club left. I know that some pretended reasons can't
be true, but I won't mention details.

I see no reason to leave, the lack of action in the past weeks are excused,
since our Captain is simply new and our Commander seems to be a bit too busy
to really join us, but that can be due to obligations in the past. So I think
this will change.
And another reason is, that I see that our Captain is very open minded to new
ideas, so I don't worry about interesting plots in the future.

I would like everybody who thinks to stay, to join and answer to this verbose
comment of mine.

It's a bit difficult to set up a rooster (no typo, I insist on the second
"o") with senior officers leaving every other day.
(BTW, I'm willing to take Science, IF I would still be involved in the
actual troubleshooting of the ship's systems when in 2 days the warp core
goes offline again...)

So come on everybody, answer to this message and say it loud, if you really
plan to stay!

Dave,
Engineering,
Computer Systems.

[Return to Archives | Return to Listing ]

First Lt. Feklhr
Duty Log
Stardate 9609.20

Today we encountered some sort of modified Romulan Warbird. It was not like
a normal one because this one had modified shields and weapons. We attempted
to hail it but to no avail. We eventually got into a grudge match and duked
it out and when another one came into play, we deployed three fighters to
help cover us and to get out. We sustatined heavy damage and it will take at
least 3 days to repair the weapon and shield systems.

[Return to Archives | Return to Listing ]

SD9609.21, afternoon

SECURITY REPORT
FstLt Rogue Quodlibet
Chief of Security
-------------------------------------------------------------
Lt. Josh has been placed in the brig for one week following the charge of
reckless and wanton destruction of Starfleet property. Said property is a
tree in the USS Lothlorien's arboretum.

>Computer, send extra copy to personnel file for Josh, Lieutenant
>Working.....complete.

[Return to Archives | Return to Listing ]

SD9609.26, early afternoon

Brig log, SD9609.26

Lt Josh has behaved rather well this week in the brig. I hope that his time
in there will teach him a lesson about messing around in the Arboretum. The
Arboretum was designed to be a place of relaxation for the crew and visitors
to this fine vessel.

Lt. Josh will be released this evening for good behavior. However, he must
perform 60 hours of community service in terms of upkeep of the arboretum, in
increments of 2 hour periods. He will need to check in with the science
department for all instructions.

[Return to Archives | Return to Listing ]

Start Duty Log SD9609,23,0058 thru SD9609,27,1418.
Lt Dave,
Computer Systems Specialist,
Co-Chief Engineer,
USS Lothlorien.

Short note about the Duty Log itself:

This log is a short one, simply because I even got no time to enhance it.

Everybody using the Computer System SHOULD READ THIS DUTY LOG, cuz there are
new features added.

I hope I will find the time to make a list of most of the commands, the
Computer System reacts to.
Until then, use the Computer in the way you expect it to work.

I configured it in the way you expect it, so most of the time you should get
the right results even without knowing the commands.
In general, no-one should really need a command list, after all the Computer
System is an aid and not an additional workload.

Most important are special commands that are only available to the Captain
and Commander,
and I'll compile those ASAP.
Meanwhile, just talk to the System intuitive. That's the way I set up the
commands anyway.

#
The mysterious Shield problem as well as the mysterious wormhole situation is
not yet enlightened.
I didn't had the time, cuz I was working the entire week on the Computer
System.
I did nothing else besides sleeping.
Maybe I get something done about the wormhole event yet today.

#
The new command "TC, forget me." gets a hint both at the "BEGIN SIM" command.
The result of this command is, that the member gets on an EXCLUDE List, and
does not receive any automatic comments, and even no answers if he questions
the Computer System.
To remove yourself from this list, the command "TC, include me" is added.
SD 9609,26,0817.

#
The re-re-re-restructure of TC took all week long.
At 9609,23,2228 it worked okay.
Additional changes were to be made to get the "Computer, locate ..." command
working
and the "Computer, Full Status" command, which refers to the devices Warp-
and Impulse Engines, Shields, Weapons, CloakingDevice etc.
Altho big changes were made, there is still a tiny bug that prevents the
system from giving the right results. I don't expect much trouble, but I'm
fighting time.

#
The discussion with Captain Sean about the different switches TC has, was
very fertile.
The greetings can still be switched on and off ("TC, greetings [ yes | no
]"), and access to TC and the COMPUTER can still be granted to "everybody"
(the default), "noone" or "Authorized Personnel Only".
("TC, AuthorizedMode [ noone | everybody | limited ]").

We agreed to let go a few switches and replace them with 3 levels.

Everybody should have a slight idea what's this about. So please continue
reading.
There are three levels, or "Runlevels".

Level 3 is the normal way, where both TC and the COMPUTER comment and reply
to everything and issue comments. The "verbose" mode.

Level 2 is a restriction of every other automatic message (these "comments").
There is no difference yet (SD9609,27,1327) to level 3, again, I'm fighting
time.

Level 1 is a totally restriction of automatic messages. But you still can
talk to them.

These levels are controlled by the system itself.
However, Authorized Personnel can alter them with the command "TC, level
(level)".

The Computer System enters Runlevel 1 whenever obviously "attention is paid".

The COMPUTER issues a message about this.

Normally this is at the beginning, when the MISSION BRIEF is issued.
The next 30 statements (that's what you talk) will not be interrupted, unless
you directly talk to TC or the COMPUTER.
After these 30 sentences, the system enters Runlevel 3 again.

Now in case the "MISSION BRIEF" comes later than these 30 sentences they
"skip", the system is already back to Runlevel 3 and would comment and greet.

In this case it immediately enters Runlevel 1 (without any notice) and waits
for another 15 sentences. No notice is given, cuz this would disturb the
briefing.

Everyone complaining about TC will get on a "Exlude-Me-List" for 10 minutes,
which is equivalent to Level 1.
But this is not yet ready, again, lack of tim

[Return to Archives | Return to Listing ]

Everyone complaining about TC will get on a "Exlude-Me-List" for 10 minutes,
which is equivalent to Level 1.
But this is not yet ready, again, lack of time.

Note, this will NOT BE A REPLACEMENT for the "TC, forget me" command, but an
automatic action.

All in all, I'm convinced that the Computer System will not disturb.
Additional actions the System takes automatically, like EMERGENCY TRANSPORT
etc. turned out to be very useful.
On the last 14 missions this automatic transport would have resulted in a far
quicker way to transport wounded to Sick Bay.
If anybody is in danger, just cry "EMERGENCY TRANSPORT!" and the Computer
System will help you immediately.

#
"Computer, open channel" and "Computer, hail ..." are added.

#
The "Computer, locate ..." is just added and will give more reliable results
from week to week.
It is however implemented, so you can use this command by now.
Just don't expect too much today.

#
I got a reply to my message to Tactical about special commands for their
procedures (Thanks Josh !), but I'm waiting for more details to customize
their wishes the way they want.

#
The file transfer, twice interrupted, has to get started at 9609,23,1500
SHARP.
Yo, at 9609,23,1510 it started again. Uh - I'm tired ... Time left:
101:52:15. Encouraging.
Good to have ones working consoles routed to his quarters. I'm gonna lay down
again.
The transfer is flowing, hope it ends correct this time (3rd attempt).
At 9609,23,2226 it just has 25% done. I fear I have to cancel it again if it
doesn't speed up in the next half hour.
Gotta take a walk - no, not to the arboretum, to the supply on deck 31. Fine
things to look at there too. Well, for someone like me ...
24 hours without a result. Fine.
As of now, SD9609,27,1322 these data could not be saved.

#
Everything that was addressed to TC or the Computer, and where the system
didn't replied,
must be added. There are still some missing replies.

#
Whenever I find the time:
The intentional disturbance by sending messages to TC.
TC will react, since it caused a blackout on TC for a minute or so.
Carbon-Copies obviously can't stick to rules.

End Duty Log SD9609,23,0058 thru SD9609,27,1318.
Lt Dave,
Computer Systems Specialist,
Co-Chief Engineer,
USS Lothlorien.

[Return to Archives | Return to Listing ]

Duty log- Weapons inventory #100 (Just about)
Stardate 9609.28
::Steps into weapons room, turns lights on. Glances around. There are many,
many shelves of weapons, not happy about checking them all.: So, how many do
I have to stare at today? Some people count sheep before they can go to
sleep, I'm starting to count phasers. ::Walks over to the nearest shelf.
Picks up first phaser, scans it, phaser is Okay. Scans several more. Noise
echoes around room. Pulls her phaser out of her belt and cautiously makes her
way down the isles. In the 5th isle is a man standing
with his back to her:: Don't move! ::Moves up beside the man, who turns
around:: Haveran? Ensign, what the hell are you doing in here?!
Ens> Uh., I can um.explain, sir.
::Scowls, lowers phaser:: You'd better be able to, Ensign.
Ens> Uh, yea, well.See I was.uh, checking the.uh.phasers.uh, sir.
Really, and who authorized this.
Ens> Well, I got a, um. a letter.
And who sent this letter to you. ::Eyes narrow, thinks Haveran is a bad
liar::
Ens> Uh, The chief, sir.
Oh, really. That's funny, she sent me the same letter.
Ens>Well, maybe she, ah.thought you needed help.
::Laughs humorlessly, then scowls at Havran:: Look Haveran, if you're gonna'
lie, you at least have to make it semi believable. Now tell me what you were
really doing in here. ::Havran says nothing, Wolfe shakes her head:: Ensign,
you know you're not supposed to be in here. All weapons rooms are for
authorized personnel only. If you wanted that phaser that's in your hand that
badly, you should've asked me. I am putting you under arrest for attempted
theft of StarFleet property.and making up a bad lie.
+Taps+ Wolfe to Farrah, report to weapons room #3 now!
Farrah>Aye, sir. ::Ens Farrah comes in a few minutes later:: Sir! ::Salutes
Wolfe::
Take Havran to the brig, Farrah.
Farrah>Sir? ::she glances at Haveran::
You heard me.
Farrah>Yes, sir. ::Takes Haveran's arm.:: What'd you do this time, Corey?
::Wolfe Sighs, continues checking weapons::

[Return to Archives | Return to Listing ]

Duty log For Lt. Jg. Anne Wolfe
Stardate 9609.27

This mission was a bit confusing (Considering I came in in the middle of
everything.) I had bridge duty, considering Rogue was on an away mission to a
nearby planet. We were investigating a star that had made its home in a worm
hole. That's impossible if you ask me, but then again, I was never very good
at quantum physics. As we were orbiting around, we ran into a Uridian
freighter that insisted we had stolen weapons from it. Of course that was
impossible, I had just checked the weapons inventory a few
days before. After a few nasty remarks, we decided to tractor them into
cargo bay 4. I ran down there as fast as I could, but the idiots had locked
their ship up. Then they tried to blow the whole place by a huge energy
overload. Luckily we jettisoned the ship and beamed all of the prisoners into
the brig. I ran to the brig and locked it <<He he, I like my new authority>>
I was yelling at the Uridians and they called me Federation Scum. It took
everything I was capable of to keep myself from shooting
them all, but I told them, that if I was not in StarFleet, I'd have killed
them by now.
The away team was apparently having trouble, and they needed to be beamed
up. But what couldn't get a lock on them? The transporter, of course. So I
volunteered to take a fighter and get them. Unfortunately, the star had
doubled in size and was going supernova in less than four minutes. So after a
couple of barrel rolls (I took advanced stunt piloting at the Academy) I was
on the planet, but, The star was going to blow any minute, and the away team
had taken off. ::Scowls:: I warped out of that
atmosphere like there was no tomorrow. The ship was trying to beam me back
aboard, but I told them it was too late, to save themselves, I'd catch up
with them. But they didn't go, they beamed me to Shuttle bay 2. Man! That was
a little closer that I would have liked, but I like to live dangerously, what
can I say. And look, I got to do stunts in one of those really cool fighters!
::Thinks she might just have to do that again:: After, Ensign Wusley got
promoted to Junior Lt. (Congrats, Wusley!)

[Return to Archives | Return to Listing ]

"Computer, open personnal logs for Lieutenant Wulsye and start new log."
'New log opened and recording...'

Today was a great day. I was promoted to the rank of Lieutenant, Junior
Grade and helped the ship narrowly(You wouldn't believe how narrow it was!
:-) avert a horrible disaster. Well, I didn't do that much, just take the
ship to warp in the knick of time, thanks to some brilliant work by
engineering. This new piece of jewlery on my collar looks nice in the mirror.
even nicer on this bright burgandy uniform I sport around. I reckon there'll
be many more to come.
I am also considering getting a pet. Something that holds a personnal
meaning. And speaking of personnal meaning, the return of my father has
brought an iron sledge hammer down on my life. He had not been a part of my
life for so long it was a complete shock when he showed up unexpectedly on
the holodeck. I missed him though and am happy he's back. I think I'll go
visit him now. Oh, computer... end log.

'BEEP'

::Wusley got out of his Klingon chair and exited his quarters into the
corridors of the ship::

[Return to Archives | Return to Listing ]

First Lt. Feklhr
Duty Log
Stardate 9609.28

::sits down and takes a sip of blood wine::
Computer open Duty Log
Yesterday was kind of a stressful day. Neil, Rogue, and I proceeded on our
shuttle mission down to the planets surface and tried to disable the
generator. Mr. Josh got sick and was transported back to the Loth and I
decided to put Doc Chid at tac. When we got to the generator there was a
lock on the panel and there was no visible way to open it. So natually I
punched it and it opened only to reveal a more sophisticated lock. I did cut
up my hand and needed stiches on my knuckles. When we got the
second lock opened it caused a stairwell to open in the corner of the room.
We proceeded down and then I went back up and got some charges to use to blow
the place to kingdom come. While I went back up Commander Neil and Rogue got
caught behind a force field. After much dilibiration we decided to blow a
hole around the field. We finally got out and made it of planet just before
a supernova shock wave hit the planet.
Computer Close log and secure

[Return to Archives | Return to Listing ]

LT1 Chid Chief Medical Officer
Duty Log SD 9609.27

::Sits in his office after Stiching Feklhr's hand::

Computer Begin Duty

Today was a most interesting day indeed, I did was not at my post of Chief
Medical Officer due to the fact that I wasn't needed there, instead I took on
the role of Tactical. While the Lothlorien was in orbit of planet Chyslon 4,
waiting for the away team to return, we encountered a group of Uridian
merchants. They hailed us from their merchant vessel and claimed that we had
taken some of their weapons. Of course we hadn't so we had no idea what they
were talking about. The Captain ordered me to scan
the ship for contraband and believe me the whole ship was full of it,
weapons. They threatened to attack us which was a joke. I disabled their
propulsion systems and took down their shields. After that I tractered them
in. The Captain sent LtJg Wolfe down to investigate, I don't know exactely
what happened down there but I started to pick up a power increase in their
ship. I immediately transported the crew to the brig, jettisoned their ship
and blew it up with a photon torpedo.

The sun in the Chyslon system was going Nova at this time and we needed to
get the away team back up immediately. We finnaly were able to contact them,
but we soon lost contact and couldn't transport them. Wolfe took one of the
fighter shuttles and went down to get them, but as they were returning, there
was no time to fly out. I transported the entire shuttle to the Shuttle bay
which is a feat in itself.

Feklhr was injured while punching threw a lock or something like that so he
needed stiches in his hand. I put them on and gave back the Tactical post to
him.

Note the crew is currently in excellent health and I would like to keep it
that way.

Computer close duty log

[Return to Archives | Return to Listing ]

Start Duty Log SD9609.29.1400 thru 2350.
Lt Dave,
Engineering,
Computer Systems.

Okay, the Captain wants more logs, so I'll return to daily logs.
I see that summarizing days of work makes my logs hard to decipher anyway.

#1 *** COMMENTS: ***

I continue to work on the Computer System, no matter who cares.
Comments like "Computer, get a virus" will now be processed.
Comments like "Dave stick to computer stuff" will be processed by me, in
person.
I'm totally fed up now with trying to enhance the StarShip atmosphere and
getting these rude comments even from an Ensign.

#2 *** BUGFIXES: ***

The Captain and Commander will be greeted correctly now.
(The words "Captain" and "Commander" appeared twice.)

The strange "Unable to comply, MPUTER2..." message is fixed.
It was a typical typo I make again and again ... (for years !! <BG>).

Some Computer System Responses on last mission "didn't came thru".
That means, the System did issued them, but they didn't appeared.
This is VERY difficult to adjust and it's more a problem of the InterCom
<<AOL>> than of the Computer System.
The System is designed as a Multitask System, that means whilst issuing a
Response, the System is already busy processing further lines or issuing the
next Response.
The InterCom <<AOL>> is just too slow for this.
I've changed the timing, I'll keep an eye on this, and I try to get an idea
how to work around this problem without decreasing the performance.

================================================================
#3 *** NOTE to CAPTAIN and COMMANDER: ***

You need not issue a "TC, Standby" or "Computer, Standby" command anymore.
(But you can of course.)
When one of you says "MISSION BRIEF", the Computer System will not interrupt
the next 30 lines.
It enters Runlevel 1 immediately and issues a note about this.
The same happens when you say "ATTENTION" ("ATTEN" is enough; but "ATTEND"
will of cuz not cause this effect).

BTW, that was the reason why you, Captain Sean, didn't got a reply to the
"Computer, Standby" command at the end of last mission. The System was
already in Runlevel 1 (quiet mode).

In case the Computer System starts too late, so you have already issued one
of these words,
or you use a totally different command to the crew to pay attention, the
System recognizes this too.
It hears, that other crewmembers pay attention by identifying the "::AA::"
lines.
When the Systems reads two "AA"s, back to back, it enters level 1 immediately
without notice.
================================================================

#4 ADDITIONAL NOTE to ALL:

Don't worry about "TC", "Computer", "Turbolift" etc. .
If anybody mixes up "TC" and "COMPUTER", it doesn't matter.
If TC has no answer, it calls the Computer, and vice-versa.
If no-one has a reply, you'll get an "Unable to comply" - message,
** IF ** "TC" or "COMPUTER" was your FIRST word.
Otherwise, nothing happens.
So you can talk about the Computer without having the risk that the Computer
will answer, unless you say something like "Hey, this Computer takes me to
deck 21.". In this case he thinks you wanna go there.

In general, talk to the COMPUTER.

TECHNICAL STUFF YOU CAN SKIP READING:
TC is just the sub-system that hears you, handles requests and operation of
the System, and memorizes changed situations.
When "free talk" (like in chat room) appears, TC is the one who answers, asks
for a coke, gives his age and other funny things, which generally not appear
on a mission.
TC recognizes nearly no COMMAND, it's the control module.
So just talk to the COMPUTER.

#5 *** DOCUMENTATION: ***
An updated documentation will be send this week, hopefully, to the Captain
and Commander.
(Doing documentations is the most hated thing for every Star Programmer.)

#6 *** COMMAND - LIST: ***
First, I'll compile a list of commands, and as soon as this list is ready and
checked, I'll send it out.

#7 *** NEW COMMANDS FOR TACTICAL: ***
Three commands were added in cooperation

[Return to Archives | Return to Listing ]

#7 *** NEW COMMANDS FOR TACTICAL: ***
Three commands were added in cooperation with Tactical Officer Lt Josh:

"Computer, TAC Alpha" - brings up the shields and powers up weapons
"Computer, TAC Phaser" - locks on target and fires phasers
"Computer, TAC Torp" - locks on target, powers up torpedoes and launches
three

#8 *** TURBOLIFT: ***
TCLOCATE (a sub-routine) is now extended to cover more commands issued to the
Turbolift or Computer.
It took 4 hours, including performance tuning inside TC, specially the
routing to the Computer or the TCTALK-module (the one that processes the few
commands that control the entire Computer System plus giving comments and
warnings).

#9 *** STILL TO DO: ***
Everything that was addressed to TC or the Computer, and where the system
didn't replied,
must be added. There are still some missing replies from later missions.
That means EVERY reply. PLUS EVERY INTENDED reply.

TCDEVICE doesn't work at all yet. Don't use the "Computer, Full Status"
command now.

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 "lost" responses, mentioned above, must be avoided.

The intentional disturbance by sending messages to TC must get handled.

End Duty Log SD9609.29.1400 thru 2350.
Lt Dave,
Engineering,
Computer Systems.

[Return to Archives | Return to Listing ]

Lt Feklhr
Chief of Tactical USS Lothlorien NCC-514251
Duty Log
Stardate 9609.30

I spent most of today looking over the various tactical programs and
manuvers. I was looking over some of them and adding a few of new manuvers I
have come up with. I also went down to the torpedo room and did an inventory
on the Mark V and Quantum torpedos. No need to worry all of them are all
there. During the past few days I have noticed something draining the phaser
grid and am currently doing an investigation, Hopefully Dave in enginering
can help me out in solving this problem. Otherwise the
other tactical systems seem to be in pretty good shape. One note, I hope to
overhaul the shield systems with the captains approval and increase their
strength.

[Return to Archives | Return to Listing ]

LT1 Chid Chief Medical Officer
Duty Log SD 9609.27

::Sits in his office after Stiching Feklhr's hand::

Computer Begin Duty

Today was a most interesting day indeed, I did was not at my post of Chief
Medical Officer due to the fact that I wasn't needed there, instead I took on
the role of Tactical. While the Lothlorien was in orbit of planet Chyslon 4,
waiting for the away team to return, we encountered a group of Uridian
merchants. They hailed us from their merchant vessel and claimed that we had
taken some of their weapons. Of course we hadn't so we had no idea what they
were talking about. The Captain ordered me to scan
the ship for contraband and believe me the whole ship was full of it,
weapons. They threatened to attack us which was a joke. I disabled their
propulsion systems and took down their shields. After that I tractered them
in. The Captain sent LtJg Wolfe down to investigate, I don't know exactely
what happened down there but I started to pick up a power increase in their
ship. I immediately transported the crew to the brig, jettisoned their ship
and blew it up with a photon torpedo.

The sun in the Chyslon system was going Nova at this time and we needed to
get the away team back up immediately. We finnaly were able to contact them,
but we soon lost contact and couldn't transport them. Wolfe took one of the
fighter shuttles and went down to get them, but as they were returning, there
was no time to fly out. I transported the entire shuttle to the Shuttle bay
which is a feat in itself.

Feklhr was injured while punching threw a lock or something like that so he
needed stiches in his hand. I put them on and gave back the Tactical post to
him.

Note the crew is currently in excellent health and I would like to keep it
that way.

Computer close duty log

[Return to Archives | Return to Listing ]

Start Duty Log SD9610.02.0638 Loth Time.
Lt Dave,
Engineering,
Computer Systems.

Well, it's Wednesday, noon, my time. That's early morning on the Loth,
it's quiet yet, but I'll end my nite's work now.
During the daytime there are too much disturbances.
I've always been a night owl.

I'm just done with the third technical document about the Computer System.

TC is processed to TC.TXT, at SD9609.30.1900 Loth
Time.
TCLOCATE is processed to TCLOCATE.TXT, at SD9610.01.1928 Loth Time.
TCCOMP is processed to TCCOMP.TXT, at SD9610.02.0607 Loth Time.

These are "Advanced User's Manuals", because it includes the commands in
detail.
There are three others to follow, but I should get this done in the next 24
hours. Hopefully.
After that, these technical letters are to be translated to a User Manual.

My idea is (altho it means extra work), to create TWO Manuals (just a few
pages),
one sorted by commands (or keywords)
one sorted by the System's Responses.

So one can easily see (on a printed sheet) which command to use to get which
result.

Available right now are the tech letters for TC, TCLOCATE and TCCOMP.
In case you wanna have a look at it, they are not classified. Lemme know.

The updated documentation for the Captain and Commander will be shortened.
I'll add the User Manual instead, as an appendix.
I'm not sure to have this done till the next mission.
But I'll do everything possible, to provide the crew with an easy to read
User Manual.

Please note, that what is easy to read for me, might be confusing to you.
I'm always open for suggestions and corrections or even just layout changes.
Lemme know !

The intentional disturbance by sending messages to TC might be solved.
I'll wait and see.

*** STILL TO DO: ***

The timing when sounds are issued must be changed in a flexible way.

Level 2 must be implemented.

HOST.SAY is to be included.

MACROM might be called from different directories to work around the "twice
problem".

Everything that was addressed to TC or the Computer, and where the system
didn't replied,
must be added.

TCDEVICE doesn't work at all yet. Don't use the "Computer, Full Status"
command now.

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.

End Duty Log SD9610.02.0638 Loth Time.
Lt Dave,
Engineering,
Computer Systems.

[Return to Archives | Return to Listing ]

===============================================
INTERSHIP MEMO
From: Dave, Computer Systems Specialist, Engineering Dept.
To: ALL
===============================================

This is no joke, no story, no drill, but the naked truth.
YOU ALL NEED TO READ IT !!!!

SPECIALLY CAPTAIN SEAN, COMMANDER NEIL, LT1 FEKHLR, LT JOSH

At SD9610.2.1502 I could not fell asleep but was disturbed by one of my
engineering consoles in my quarters giving Red Engineering Alert.

There was a forecast of a plasma injector problem in 15 minutes.

The plasma stream injectors would not have lead their impulses to the
nacelles with the right offset.
The nested subspace layers around our ship would have gone outta sync.
Since warp drive is an environmental catastrophe anyway, I can not tolerate
this.
A malfunctioning warp drive causes even more space-time disturbances, than a
good working one would do.
It violates the peace the Federation stands for.

Well, the quickest way to shutdown the warp drive is to shutdown the M/AM
Reactor, which I did immediately.

HELM: I did this WITHOUT checking our current velocity !!!!

In case we were still on warp 9, we would have remained beyond warp 1 for 2.5
minutes aprox.,
after that we are now at Impulse Speed.
No matter on which speed we were before.
I had no time to ask anybody, and this is my decision and responsibility
anyway.

Meanwhile the M/AM reactor is restarted. I set the energy flow to match a
warp 5 velocity.
You CAN NOT accelerate beyond warp 5 now, cuz you ain't got the energy.

All of you, please don't use much energy please.
Specially don't replicate complicated structures !!!

And don't panic, the Fusion Reactor is still working fine.

We are safe, but we can only move at warp 5 max.

Currently, the computer is checking the reactor and the plasma drain.

I want to have a look at the nacelles and NEED AUTHORIZATION to use a
shuttle, preferable "Katara" ASAP. And I mean "ASAP".

I NEED A TEMPORARY ASSISTANT in Engineering NOW !!!!!

I ask the Captain, Commander or Lt1 Fekhlr to "lend" me Lt Josh, cuz I need
someone who understands my meanings and orders on the fly with a gesture or
just a look.

ALL THIS IS VERY TIMELY in case you wanna go back to warp 9+ in the future.

Respond immediately please,
Lt Dave,
Chief-Engineer and
Computer Systems Specialist.

[Return to Archives | Return to Listing ]

Start Duty Log SD9610.02.0147 thru 2046 Loth Time.
Lt Dave,
Engineering,
Computer Systems.

Well, the following programs got their "tech letters" already:
TC: TC.TXT, as of SD9609.30.1900 Loth Time.
TCLOCATE: TCLOCATE.TXT, as of SD9610.01.1928 Loth Time.
TCCOMP: TCCOMP.TXT, as of SD9610.02.0607 Loth Time.

Now I got TCTALK ready, it's TCTALK.TXT, SD9610.02.1947 Loth Time (03.0147 my
time).

Couldn't sleep after the last period of awakeness, so I'm totally outta any
schedule again.

Okay, now at SD9610.02.2025 I need a break.
First cuz I'm that much outta schedule,
and second cuz I'm now at the most difficult part, namely TCDEVICE.
That's the one that doesn't work properly for a while.

Fortunately, doing a technical documentation forces you to go thru the entire
coding, so some mistakes or corrections can be done at the same time.

I look forward to find the errors and to get most of them corrected till the
next mission.
That does however not mean, that the "Computer, Full Status" command will be
available.
For this (it's nearly a joke, this is the part why I've started writing TC 4
months ago), well to allow this command (plus "Computer, shield status" etc.)
I need more test time.
I don't let a program system run with known bugs, showing wrong results.

Another problem is to get a readable User Manual done.
I still hope to find a working idea on how to provide both a User Manual that
is sorted by Commands, as well as by Responses.
I already got an idea, I'll check that when TCDEVICE.TXT is finished and I
start testing again.
As always I'm fighting time to get all this done till the next mission.

The situation in Engineering gets critical.

Lt1 Feklhr asked about an unknown energy problem with the phasers.
I told him to provide me with as much detailed information he can give me, to
narrow the problem down.

When I'll receive his data, I hope Lt Josh can lend me a hand in Engineering,
cuz there is too much to do for one person (namely me).

The User Manual is important because I owe the crew an explanation about the
System.
The Warp Drive is only capable of Warp 5 right now.
The third cylinder of the warp drive seems to be the problem.
The computer is working on it, good to have such a numbercruncher, thanks to
Captain Sean.

Captain, I still need the allowance to use a shuttle craft, as I wanna SEE
the warp nacelles.
Captain, BE AWARE of the fact, that we can only move BELOW WARP 5.1 RIGHT NOW
!!!!!
I only guarantee a working warp drive when I'm convinced about it.
And it takes a lot to convince me, as some of you might have already
experienced.
Until then, I've set up the AM reactor control to make it IMPOSSIBLE to
accelerate beyond Warp 5 !!
And in case the computer can't fix the warp drive problem itself, I need Josh
to assist me.
Please give your orders.

End Duty Log SD9610.02.0147 thru 2046 Loth Time.
Lt Dave,
Engineering,
Computer Systems.

[Return to Archives | Return to Listing ]

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

I'm fighting time as always.
The Loth, The Ship That Never Sleeps.
(Wasn't there a song about it way back in time ?)

I gotta summarize what happened, cuz I need to go back to work ASAP.

*** Phaser not at full capacity ***

Lt1 Feklhr mentioned an unknown energy problem with the phasers.
Altho I told him to provide me with more detailed information,
I haven't received any.
The plan was, that Lt Josh would lend me a hand in Engineering,
whilst I was checking the phaser problem.
I got Feklhr's OKAY for this, but since I haven't received more
information about what Feklhr has detected, I haven't done anything,
besides
letting the Computer check the phasers and the phaser arrays itself.
There was ** NO ** problem reported.

Please see the end of the following paragraph for this problem too !

*** The Warp 5+ Problem ***

At SD9610.03.1400 I checked the ship's warp drive nacelles.
The Captain gave me his OKAY and FsLtRogue was so kind to fly me
with a shuttle (the "Katara" shuttle) to both the nacelles,
cuz I wanted to check them from outside the ship.

I found out, that the plasma injector control subsystem changed
its frequency.

Because of this, the trimming provided by the third coil had
to be changed too. But the computer hasn't done this.
(I think he needs a lecture about warp physics.)

The wrong adjustment led to vibrations of the third coil,
and so to vibrations of the nacelles itself.
Until the problem wasn't solved, I disabled any speed above
Warp 5. Tactical got informed about this.

I adjusted the third coil to reflect the changed injection
frequency, so now there are no mismatches anymore.
There is no vibration anymore and I'll enable speeds above
Warp 5 at 9610.04.1800.
In case you don't get an INTERSHIP MEMO about it, you know
it now.
In case another problem shows up, I'll inform the ship ASAP of cuz.

Many thanks to FsLt Rogue, who did an excellent job to take
me outside the ship and near to both the nacelles.

Thanks to Lt Josh too, who offered to pilot me there.
Rogue did the flight cuz at the time she gave me clearance
to use a shuttle, she immediately offered to pilot me.

A mission log about this was recorded and will be posted
after FsLt Rogue has revised it.

Again, expect Warp 5+ available at 9610.04.1800 until further notice.

It is possible, that the coil's vibration, that causes the nacelles to
vibrate,
might have also effected the phaser arrays.
This is an assumption.
So if there still is a phaser problem, you gotta tell me.
The problem is closed for me now, and you gotta re-open it.



*** The Computer System ***

After major changes were done again,
the System must be checked on the third degree again.
I'll do this today, Priority #1.

The following programs have ** UPDATED ** Tech Letters:
TC: TC.TXT, as of SD9610.03.1724 Loth Time.
TCLOCATE: TCLOCATE.TXT, as of SD9610.01.1908 Loth Time.
TCCOMP: TCCOMP.TXT, as of SD9610.03.1633 Loth Time.
TCTALK: TCTALK.TXT, as of SD9610.03.1509 Loth Time.

At work and not yet complete:
TCDEVICE: TCDEVICE.TXT as of SD9610.02.2109 Loth Time.
I'll work on this one today. Priority #2.

REMINDER:
The "Computer, Full Status" command gives no reliable output yet.
Don't use this command.

USER MANUAL:
Is yet to be done.
I still hope to provide everybody with two lists,
one sorted by Commands,
one sorted by Responses.
I want everybody to be able to quickly see,
which command would simplify his/her work.

I'll work on this one today too, priority #3.

*** Full Computer System Documentation ***

The updated documentation for the Captain and Commander will be shortened.
I'll add the User Manual instead, as an appendix.
Priority is #4.

*** STILL TO DO ***

The timing when sounds are issued must be changed in a flexible way.

Level 2 mu

[Return to Archives | Return to Listing ]

*** STILL TO DO ***

The timing when sounds are issued must be changed in a flexible way.

Level 2 must be implemented.

HOST.SAY is to be included.

MACROM might be called from different devices to work around the "twice
problem".

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

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.

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

[Return to Archives | Return to Listing ]

Start Duty Log SD9610.04.1016 thru 9610.05.1253 Loth Time.
Lt Dave,
Acting Chief Engineer and
Computer Systems Specialist.

My cup~o~chino recipe for the replicators is improved. You gotta taste it to
believe it.

*** Work at the Warp Drive: ***

There is no vibration anymore and I've enable speeds above Warp 5 at
9610.04.1800.

It is possible, that the coil's vibration, that caused the nacelles to
vibrate,
might have also effected the phaser arrays problem, Lt1 Feklhr reported
about.
But to be honest, this is an assumption.

Since no problem was reported anymore, I guess both problems are fixed by my
operations on the Warp Drive.
The problem is herewith officially closed at the Engineering Department.

I'm very sorry I can't send the recorded log about the work at the Warp
Nacelles
to you and the Database, I'm still waiting for FsLt RogueQ's OKAY to post it.
I hope I receive the revised version soon. (I've done much work on it.)


*** Work on the Computer System: ***

Whenever the Computer System issues sounds,
it calculates the time needed to play this sound and pauses for this period.
Otherwise, a sound would not be heard. Implemented at SD9610.04.1116.

As you know, the Computer System consists of several Subsystems.
TC is just one of these.
The TC Subsystem now has again a couple of Subsystems.
For every TC Subsystem I've written a "Technical Manual", mainly working
sheet style.
If anybody is interested in, I'm willing to forward them to qualified
personnel.
Just lemme know.

There will however never be an available description about the receiving and
sending interfaces, for personal copyright reasons.
("How TC and the Computer "hear" and "speak".")

Available Technical Manuals are: TC.MAN, TCLOCATE.MAN, TCCOMP.MAN,
TCTALK.MAN.
Feel free to ask for details.

*** USER MANUAL, Availability of the Computer System: ***

The System is up and running all the time of cuz.
During a mission, TC starts and provides easy access to the Computer.

Easy Access FOR YOU is provided by a USER MANUAL, which is now available
anytime.

Since work on the Systems continues, both the Technical Manuals and the
USER MANUAL will be updated nearly daily.

I will send out an up-to-date USER MANUAL before every mission.
With this listing, you can work quicker and easier.

After all we have the M-13-C Bio Neural Duotronics Computer not for neat
computer games but to aid us steering the ship, operating the various
devices like shields and weapons, etc., so my advice is to use it.

This is (now) a 2 page listing, easy to read and easy to understand.
(If not, tell me.)

*** STILL TO DO ***

The Warp Core suffered severe damage on the last mission at SD9610.04.213604.
I'll ask Lt Josh for assistance, since my "Co-Chief Engineer" Mog didn't
showed up again.

A Duty Log about the mission itself has to be written.

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

The Turbolifts are acting up.
They nearly behave like those on the Heart Of Gold of my old friend Zaphod.
It was okay for us to have Turbolifts and Doors that have their own will,
but on the USS Lothlorien there are other standards to meet.

Level 2 of TC must be installed.

Variations must be implemented.

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.

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's too little
chocolate in it.

End Duty Log SD9610.04.1016 thru 9610.05.1253 Loth Time.
L

[Return to Archives | Return to Listing ]

===============================================
INTERSHIP MEMO
From: Dave, Computer Systems Specialist, Engineering Dept.
To: Captain Sean
CC: 1st Lt Feklhr, Lt Josh, USF DB
===============================================

Dear Captain,

I hereby request a repair team from Starbase Alpha where we are currently
docked.
The ejected Warp Core has to be replaced by an exactly identical one, since
all
control systems are adjusted to the specs of our lost Core.
This is VERY IMPORTANT.

We can't repair that on our own, it would last for a month with the crew
currently onboard.

I'm not familiar with any requests to any other Starfleet entity (sorry, you
know I'm a Computer Nerd and can maintain and adjust these devices like hell,
but I can't even write a normal request, in fact I've even never seen one).

So I ask you to either assist me in contacting the Starbase Alpha, I know you
got good connections, and I always prefer unofficial ways since they are
faster,
or I need you to give me detailed advice about the necessary procedure.

I'm depending on your help, and so is the Warp Drive.

Thanks a lot,
Dave,
Acting Chief Engineer and
Computer Systems Specialist.

[Return to Archives | Return to Listing ]

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

*** Mission 9610.04.210835 to 9610.04.215954: ***

It started peaceful. We were a small bunch only, but at least I had fun like
since who knows when.
We left SB Alpha for Promethius.
The atmosphere onboard was like a peaceful family trip or a walk downtown to
party till we puke. The pizza in Engineering was a bit old, but Josh enjoyed
it. The Captain got himself a fresh one, and Tamara got her share too.
Feklhr even established a subspace communication to gave us the latest
informations about a baseball game. Or was it football ? Anyway, we were very
comfortable.

Well, instead of pizza we were more or less suddenly surrounded by alpha
particles.
The particles were recognized by Lt1 Chid at a distance of 200,000 km of our
port bow.
(No, not from Sick Bay, our Doc can do fine with Tactical and Ops too.)
The USS Lothlorien experienced a couple of shakes.
Tamara did her best to try to get us outta the mess, but these particle cloud
seemed to have fallen in love with us.

I wonder how they could approach us that fast.
The ship dropped to zero velocity, and there were may-be minor hull
fractures.
("May-be", cuz the computer could not identify any damage.)
What I found out thru listening to the Bridge chat (Engineering got a steady
commlink to the Bridge, for those who're wondering), was that "creatures"
were connected with these particles. Maybe the spirits or old friend Katara
spoke about so often ?

Well, this phenomenon (whatever exactly it was) got us in big trouble.
First Feklhr TAC station blew up. Feklhr was hurt but Chid was close, so he
could bring him back online. Well, consciences I mean. 4 Engineering consoles
at the Bridge blew up.
The Computer System got unstable.
I was lucky to having something prepared for a disaster like this, I could
perform an Emergency Restart and the Computer System was okay again.

We finally decloaked and raised the shields, but of cuz we only catched this
phenomenon now between the shields and the ship. We should have done this
earlier.

A splendid idea from Lt Josh wasn't recognized, I didn't heard it too in all
that mess.
He suggested, to blow a plasma stream outta the ship. I'm sure this would
have been our rescue.
But - in all that mess I didn't heard it, just found it in the Computer's
Log.

The Warp Core went critical.
The Energy went critical.
The Captain did not went critical.
He surprised me a lot, when he gave the Computer the command to route all
available power down to us. He knew the command better than me !

Obviously outside the ship a creature appeared. The Commander's idea was to
catch it and get it to a secure area, so Josh and Feklhr quickly decided to
clear a shuttle bay to make room for this being.
The creature "stepped" into the shuttle bay as soon as Tamara opened the
doors.

Don't ask me questions, but the warp core decided to breech so we had to
eject this lovely thang. I erected a force field around the core and
instructed the Computer to prepare a restore. My idea was, that if the
ejected core didn't blew up (I saw no reason for this) I'd had a chance to
catch it again, since the seal procedure I used, follows a moving object.
So I hoped to get the core back. I don't like things in Engineering
vanishing.
Well, the core ejected.

There was some confusion whilst some of us used the Turbolifts, I gotta send
a note regarding this to the crew onboard later.

Not just Commander Neil, but 1st Lt Tamara too had obviously friendly
feelings towards this creature. They cared about whether it could survive in
an oxygen atmosphere and what might have hurt it.
(Again a hint, that it was a spirit, Katara told us about ?)
Chief Medical Chid agreed not to kill it.

I didn't understood why, whilst the creature was moving as in pain, Tamara
first suggested it might not be able to take the ships temperature (as a
being living in outta space where the temperature is

[Return to Archives | Return to Listing ]

I didn't understood why, whilst the creature was moving as in pain, Tamara
first suggested it might not be able to take the ships temperature (as a
being living in outta space where the temperature is a wee bit lower) and
then decided to warm it up.

But there was still not enough trouble.
Two Romulan Warbirds decloaked. They didn't attacked us, but we experienced a
hullbreech on deck 22.
It was like a no-win situation at the Academy, the Warp Core lost, the
Shields weren't up at 100 %, Tamara wanted the hull to be heated up (go
figure !!) and - a hullbreech.
And me in Engineering.
Gosh, lucky me, I had instructed the Computer System some weeks ago to erect
a force field immediately after having detected a hullbreech, so I was first
rid of that problem. But altho the Computer System announced it, I seemed to
be the only one having heard it. Maybe I should power up the volume a bit ?

"Davy, forget the hull breach! Get the ship in tip top shape"
Well, the chance for a comfortable party was absolutely gone.
Tamara requested to heat up the ship's hull to 100 degrees C.
Yo.
Did I mentioned I felt like in a no-win situation in an Academy simulator ?
Thanks God, in my mind there is no no-win situation.
But we don't have a heating at the hull ... not even at my chair.
I admit I had to think how to manage this.
The Warp Drive was gone, it was easy to heat the hull using the shields and a
plasma stream.

Computer, enter the following sentence to my working list.
TC demon: COMPUTER> to Dave: Recording ...

"Check out how to load the hull like I did on Mura with the O7."

Computer, stop the recording program.
TC demon: COMPUTER> OK, Dave, program ended.

Okay, back to the log.
To heat up the hull, I started the Impulse Engines with full capacity.
They responded, and they did it at full capacity.
I immediately reversed the thrust.
Thanks to the Computer System (and to the fact, that I allowed myself to
carry out any commands), these two actions were performed in less than a
second.
The Impulse Engines are fed by the Fusion Reactors on deck 28 (which also
feed a lot of other energy consuming devices, such as the life-support), and
they are Newtonian engines.

This is the point, as true rocket engines, they produce a high temperature
particle burst.
Immediately reversing the thrust if they are at full capacity heat them up
like hell, well, maybe a few degrees above that.
Since they are directly connected to the ship (I mean the construction), the
heat flows onto the ships hull.

BUT NEVER TRY THIS AT HOME, KIDS !!!!

Well, we got rid of the creature(s).
And we got safe to Starbase Alpha.

It was great, it was fun, it was like the Captain wanted to check my limits.
Ah - and the Turbolifts had their fun too.

BEST MISSION SINCE WHO KNOWS WHEN !!

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

[Return to Archives | Return to Listing ]

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

*** Warp Drive: ***

I sent a request for a Repair Team to the Captain, since I don't know how to
request it from another Starfleet entity.
Yes, I was sick when they told about command chains and formal procedures at
the Academy.
Captain Sean handled that at 9610.05.1502. (Thanks a lot !!)

The Repair Team arrived at 9610.05.1634, and they estimated 3 days to install
a new Warp Core, plus 1 hour to wipe away the remains of our pizza.
The new core matches exactly the specifications of the old one.
Of cuz I need to check that out, and I'll need a whole day to do that.

The Team is even doing shift work, and I withdraw to my quarters.
So I'm not disturbed, they are not, and I got all Engineering consoles at my
quarters anyway.
I expect to be able checking the Warp Drive at 9610.08.0000+.

*** TurboLift Computer Subsystem: ***

AT SD 9610.06.0500 My Time, whilst tuning up the System and adding some
features, I lost my sense about time again. (I'm not really sure if I really
have one.)

Okay, so the water for my bath got cold, and I got a heated debate with them
TurboLifts.

First, they insist on being called "TurboLifts" with a capital "L".
They think it's cooler.

And they insisted to invite everybody who's even near to a TurboLift.
They did this on the last mission and this caused quiet a confusion.

But they argued, they are offering a service and they were friendly devices,
so they wanna stick to this.
We agreed on a compromise.

They will still invite everybody near a TurboLift, even if the person didn't
mentiones a destination.
I guess, they invite them cuz of this and then to show everybody how fast
they are, moving them from top to bottom of the ship.
I asked if they could agree on inviting one person only once.
They asked for a time-out.

Today, round 9610.06.1900 turboliftd (that's the demon controlling the lifts,
so to say their "Boss") appeared on my console and told me he'd like to
continue the debate at 2200.
We agreed, that I would be in my quarters at my Engineering Consoles, and
turboliftd would enter the Main Computer System to be able to talk with me.

As I mentioned earlier, the TurboLift demon made friends with the doors on
Zaphod's "Heart Of Gold", and since then, the TurboLift absorbed the
controlling demon.

You might have noticed, that this demon even doesn't show up when starting
the entire Computer System.

At 2200 turboliftd showed up.
He had a log prepared that he threw onto my right console.

I was very surprised, that he even modified it to meet my wish not to be too
verbose.

On this log, the TurboLifts had issued 11 statements on the last mission.
3 of them were out of question.

Josh was correctly handled whilst moving to Main Engineering and the Bridge.
So was I, when I moved down to Engineering at the mission's start.

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
TurboLift