Some Blog Site

Warning: Engineering / computer science discussion ahead. Proceed with caution. Actually, it’s not that bad. Non-engineers might also appreciate this post, as long as they are familiar with the 80s.

I was given the assignment at work of providing a summary of RTOS (real-time operating system) differences. We use 3 different types of embedded operating systems in our various modules, and management was looking at another one to meet customer requirements.

For this application, there is a regular RTOS and a safety (or safe) RTOS for critical equipment. (If you are unfamiliar with those options, here are search results for safe RTOS so you can get more details.)

My summary is that a normal RTOS runs the expected tasks in one common environment, whereas the safety OS runs different tasks in different threads so they are isolated from each other memory- and context-wise.

If that’s still not making sense, maybe this will:

You can task if you want to
You can leave your threads behind
Because your threads don’t task
And if they don’t task
Well they’re no threads of mine

Safety
OS

I’m hoping management wants me to present my summary at the next department meeting so I can put that on a slide.

Quick Quiz:
Of what is this a picture?

If you said “a desktop computer from around 2004” you are correct.
If you said “not a Mac” you are also correct.
If you said “Some Guy’s computer” you are also correct.

Thursday night, after all the non-festivities of the day, my wife started the computer but the screen was misbehaving. The picture was choppy and repeated and pixels were not where they should have been. I shut it off and figured I’d look at it the next day.

The next day, there was no picture at all. The monitor told us “No Signal”.

So I replaced the video card. I went from this:

to this:

No, I did not mix up those photos. The desktop computer had a fancy graphics card. I had to add the cooling system (heat sinks! heat-transfer tubes! a fan!) after the card kept resetting during Command & Conquer. That was years ago.

On Saturday, I pulled a video card out of one of my previous computers and plopped that one in the current desktop. Other than having to grab a VGA cable because the old card doesn’t support DVI, I had no problems.

Here’s how the cards compare:

I can’t run CnC anymore, but at least I know what I want for Christmas now.

In case there are students who are struggling in the beginning circuits course, I am providing this little jingle to help you remember stuff.

You should be able to figure out the tune once you start reading.

Verse 1
Ohmic Donald had a circuit.
E-I-E-Diode
And on that circuit he had a …
… resistor!
E-I-E-Diode
With a voltage drop here and a voltage drop there.
Here a drop, there a drop, everywhere a drop-drop.
Ohmic Donald had a circuit.
E-I-E-Diode

Verse 2
Ohmic Donald had a circuit.
E-I-E-Diode
And on that circuit he had a …
… capacitor!
E-I-E-Diode
With a stored charge here and a stored charge there.
Here a charge, there a charge, everywhere a charge-charge.
Ohmic Donald had a circuit.
E-I-E-Diode

Verse 3
Ohmic Donald had a circuit.
E-I-E-Diode
And on that circuit he had a …
… inductor!
E-I-E-Diode
With magnetic flux here and magnetic flux there.
Here a flux, there a flux, everywhere a flux-flux.
Ohmic Donald had a circuit.
E-I-E-Diode

Verse 4
Ohmic Donald had a circuit.
E-I-E-Diode
And on that circuit he had a …
… transistor!
E-I-E-Diode
With a switch-switch here and a switch-switch there.
Here a switch, there a switch, everywhere a switch-switch.
Ohmic Donald had a circuit.
E-I-E-Diode

Any other components that a young student of electronics should know?

And yes, I know that inductors deal more with Faraday’s Law than with Ohm’s Law. If we stuck only with Ohm’s Law, there would not be very many verses.

In C, we call functions:

"Hello, is function there?"

If we have something to tell the function, we pass arguments to the functions:

value = GetValue("did not", 
                 "did too");

And if there are many arguments, we will group them and then pass pointers as arguments to the function:

value = GetValue("he did it", 
                 "no, he did it", 
                 "yeah, but he started it");

I don’t like confrontation, so I prefer the term “parameter” instead of “argument”.

In setting up a new page on Social Biblia, I had to provide profile photos for Midianite soldiers.

The Midianites were not exactly friendly people. The image that came to mind when I pictured unfriendly soldiers was the orcs from Warcraft. Not this fancy online World of Warcraft, but its grandfather – the old-school Warcraft II.

Back when games were games and ran on DOS.

Which was a problem because DOS-based games don’t like to run on Windows 7 laptops.

But I’m getting ahead of myself a little – let me rewind a bit.
(more…)

Now that I have accounts to make and sell T-shirts, I figured I’d create something else.

Green Programming

Make sure your functions and methods are environmentally responsible.

Go buy it at Printfection.

There are two types of people in the world: those who don’t really think about Comic Sans and those who disdain Comic Sans.

I was wondering why there are so many people against the poor font. I came up with the answer of “Sans”. Maybe the problem is that there are no serifs.

What if someone added serifs to Comic Sans?

What would it be called then? Sans means without. What is the opposite of sans? Con means with. I thought about Comic Con, but that name is already taken. Not for a font, but instantly recognizable to those who care about fonts. I guess the next best thing is the name Comic Serif.

So, here is Comic Serif. Go download it from fontgrill.com, if you want.

The nice thing about spoofing Comic Sans is that you can’t get it wrong. If you make a good font, people will be impressed. And if you do a poor job on the font, people will think you’re trying to be funny by mocking Comic Sans.