Yummy!
-
Tuesday, December 21, 2010
Court of Honor Chili
I threw in what I had in the house - garlic, onions, some beans, tomato sauce, chili powder, meat, and what I got at the local grocery store - more beans, and pepperoni.
Yummy!
Yummy!
Tuesday, December 14, 2010
OA LodgeMaster Client Server testing
The Order of the Arrow membership database system is called LodgeMaster, also known as "OALM" once you've said "Order of the Arrow Lodge Master" too many times. I tried out the client / server set up for practice. It works, but there are things to be aware of. Below are many screen shots; I'll talk about them in this beginning text.
Let's see, over 15 images of 50KB each or so, that's 750KB. Should not take too long to download...
Image (1) show what the server screen looks like, once you've switched on the feature. I am not showing the setup screen, but there is a key that is generated which each client will need to enter to connect.
Image (2) shows what a client looks like, after connecting. While the client machine will still have a database running, user screens will be connected to the database on the remote server.
Since clients will use one central database, rather than the distributed databases, I would make sure no client machines enter data except in the server/client connection during an event. Otherwise, no new or changed records on the client machine will be visible to anyone else until after all have synchronized later.
Images (3) and (4) show the error messages if a client machine does not have the server's IP address and current key (which changes on each open and close of the server).
So what about synchronization? Neither the server nor the clients can synchronize to the central database (in the cloud) while either are running remotely. See image (5). Because "all the eggs are in one basket", I would recommend trying take check points during the event, such as late night, early morning, or maybe mid-day. All clients need to disconnect, the remote server needs to be switched to normal mode, then synchronization started. That way, all is not lost should that machine crash, especially since the clients databases have no records of any entries during their remote access time.
Image (6) shows what happens when the server goes back to normal mode.
Most of the remainder of the images were recorded during test scenarios where I shut down either the internet connection, the server, or crashed the client process to see how the client/server behaves. Unfortunately, while one message claims "returning to logon screen" I was never able to re-connect a client process once the linkage dropped.
Stopping the client SQLServer process did nothing to restore a live connection; the MSACCESS process apparently manages the menu screens. That makes sense once you realize the client connects to the SQLServer database on the remote machine.
If the remote server is stopped and started again, a new key is generated, meaning each client will need to start up again with that key.
Some of the error messages are not connection-related, but due to bugs in OALM or Microsoft software. "Invalid object names" seem to be due to broken records inside the database. The "Microsoft Office Access has encountered an error" could be due to a bad call, or just general bugginess. Business as usual in the software world.
Despite these test results, I didn't lose any data or need to reboot either system. Given this will be used in a field situation, with lines of people sometimes waiting for check-in, it's important to practice under adverse conditions to anticipate and avoid problems. Motto of the Scouts, right?
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
(15)
(16)
(17)
Let's see, over 15 images of 50KB each or so, that's 750KB. Should not take too long to download...
Image (1) show what the server screen looks like, once you've switched on the feature. I am not showing the setup screen, but there is a key that is generated which each client will need to enter to connect.
Image (2) shows what a client looks like, after connecting. While the client machine will still have a database running, user screens will be connected to the database on the remote server.
Since clients will use one central database, rather than the distributed databases, I would make sure no client machines enter data except in the server/client connection during an event. Otherwise, no new or changed records on the client machine will be visible to anyone else until after all have synchronized later.
Images (3) and (4) show the error messages if a client machine does not have the server's IP address and current key (which changes on each open and close of the server).
So what about synchronization? Neither the server nor the clients can synchronize to the central database (in the cloud) while either are running remotely. See image (5). Because "all the eggs are in one basket", I would recommend trying take check points during the event, such as late night, early morning, or maybe mid-day. All clients need to disconnect, the remote server needs to be switched to normal mode, then synchronization started. That way, all is not lost should that machine crash, especially since the clients databases have no records of any entries during their remote access time.
Image (6) shows what happens when the server goes back to normal mode.
Most of the remainder of the images were recorded during test scenarios where I shut down either the internet connection, the server, or crashed the client process to see how the client/server behaves. Unfortunately, while one message claims "returning to logon screen" I was never able to re-connect a client process once the linkage dropped.
Stopping the client SQLServer process did nothing to restore a live connection; the MSACCESS process apparently manages the menu screens. That makes sense once you realize the client connects to the SQLServer database on the remote machine.
If the remote server is stopped and started again, a new key is generated, meaning each client will need to start up again with that key.
Some of the error messages are not connection-related, but due to bugs in OALM or Microsoft software. "Invalid object names" seem to be due to broken records inside the database. The "Microsoft Office Access has encountered an error" could be due to a bad call, or just general bugginess. Business as usual in the software world.
Despite these test results, I didn't lose any data or need to reboot either system. Given this will be used in a field situation, with lines of people sometimes waiting for check-in, it's important to practice under adverse conditions to anticipate and avoid problems. Motto of the Scouts, right?
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
(15)
(16)
(17)
Monday, December 6, 2010
Winter Camping, LNT Style
The troop camped at Broad Creek this weekend, where lows on Saturday morning were around 26 degrees F. To get the cheerfulness going, we had a small wood fire, in a commercially available fire pan. We didn't cook in the big pan; we had propane-fired camp stoves to boil water.
The breakfast was "eggs-in-a-bag", with whatever ingredients we had, tossed into a plastic bag, and then boiled until appropriately consistent. I had brought my wood-burning backpack stove, so I took a few charcoals from the troop fire and boiled my own cooking/cleaning water.
Yum! Hot breakfast, Leave No Trace way -- with no cleanup, plus a built-in hand warmer.
Too bad I forgot the chili powder. "Bam!"
The breakfast was "eggs-in-a-bag", with whatever ingredients we had, tossed into a plastic bag, and then boiled until appropriately consistent. I had brought my wood-burning backpack stove, so I took a few charcoals from the troop fire and boiled my own cooking/cleaning water.
Yum! Hot breakfast, Leave No Trace way -- with no cleanup, plus a built-in hand warmer.
Too bad I forgot the chili powder. "Bam!"
Thursday, December 2, 2010
Bengies 2010, Top 10, and More
I listed "top 10" movies at the Bengies Drive-In Movie Theatre on Netflix while that site had decent user community access tools. Fortunately, I copied off the 8 years of content, and published it as:
http://jspath55.blogspot.com/2010/03/lists-of-movies-that-played-at-bengies.html
That list included an updated "Top 10" for 2009. In 2010, I visited the Bengies as much as possible, not just to see the shows, but also checking out the marquee nearly every week. Below are 28 photos of the marquee, from the operating weeks between April and November. I missed a few, but not many.
On FaceBook, the Bengies admins asked "What was your favorite DouBBle or TriPPPle feature this season?" I'll avoid the easy answer of the Dusk-To-Dawn shows on Memorial and Labor Day weekend (on the grounds that those were not strictly 2 or 3 movies).
I'm going with the September 24-26 weekend line up, known as "Face Fleas thank you Please, Owls Flipped on Inception" on the email list, which included:
Top 10
And now for the top 10. As in earlier lists, I saw each of these at the Bengies, at least once, during the current year.
Honorable Mention (from "FaceBook Night At The Bengies"):
E. T. The EXTRA TERRESTRIAL
NORTH BY NORTHWEST
List culled from the Bengies email service for 2010, not necessarily complete, or in chronological order, but mostly.
Key: "Y" = saw it; "!" = on Top 10 list for 2010; "?" = saw part of it (or can't remember it); " " pretty sure I missed it.
http://jspath55.blogspot.com/2010/03/lists-of-movies-that-played-at-bengies.html
That list included an updated "Top 10" for 2009. In 2010, I visited the Bengies as much as possible, not just to see the shows, but also checking out the marquee nearly every week. Below are 28 photos of the marquee, from the operating weeks between April and November. I missed a few, but not many.
On FaceBook, the Bengies admins asked "What was your favorite DouBBle or TriPPPle feature this season?" I'll avoid the easy answer of the Dusk-To-Dawn shows on Memorial and Labor Day weekend (on the grounds that those were not strictly 2 or 3 movies).
I'm going with the September 24-26 weekend line up, known as "Face Fleas thank you Please, Owls Flipped on Inception" on the email list, which included:
- Legend of the Guardians: The Owls of Ga'Hoole
- FLIPPED
- INCEPTION
Top 10
And now for the top 10. As in earlier lists, I saw each of these at the Bengies, at least once, during the current year.
- Inception
- Get Low
- Megamind
- Shrek Forever After
- Iron Man 2
- How To Train Your Dragon
- Despicable Me
- Secretariat
- RED
- Robin Hood
Honorable Mention (from "FaceBook Night At The Bengies"):
E. T. The EXTRA TERRESTRIAL
NORTH BY NORTHWEST
List culled from the Bengies email service for 2010, not necessarily complete, or in chronological order, but mostly.
Key: "Y" = saw it; "!" = on Top 10 list for 2010; "?" = saw part of it (or can't remember it); " " pretty sure I missed it.
Y THE SPY NEXT DOOR
Y COP OUT
? IT'S COMPLICATED
Y KICK-ASS
Y HOT TUB TIME MACHINE
! HOW TO TRAIN YOUR DRAGON
Y THE BOUNTY HUNTER
! IRON MAN 2
! SHREK FOREVER AFTER
! ROBIN HOOD
Y SHUTTER ISLAND
Y THE KARATE KID
KILLERS
Y THE LAST AIRBENDER
? GROWN UPS
! INCEPTION
! DESPICABLE ME
The Twilight Saga: ECLIPSE
Y SALT
Y DINNER FOR SCHMUCKS
VAMPIRES SUCK
THE SORCERER'S APPRENTICE
Y TOY STORY 3
? The SWITCH
Y THE EXPENDABLES
Y The OTHER GUYS
THE LAST EXORCISM
Y Legend of the Guardians: The Owls of Ga'Hoole
Y TAKERS
Y GOING THE DISTANCE
? THE LOTTERY TICKET
Y FLIPPED
? The TOWN
Y E. T. The EXTRA TERRESTRIAL
Y NORTH BY NORTHWEST
! RED
Y GET LOW
GREASE SING-A-LONG
! SECRETARIAT
! MEGAMIND
Y DEVIL
PARANORMAL ACTIVITY 2
HEREAFTER
Y DUE DATE
Y THE SOCIAL NETWORK
Subscribe to:
Posts (Atom)
