Cheating On The Beans

(Still Life With Red Peppers and Miss Emily)
Well, I did make the Hearty Tuscan Bean Stew after all.
CI's recipe starts off by noting the area's residents' fame as
mangiafagioli (bean eaters), but the test chef (Charles Kelsey) allowed as
how he wasn't going to soak his beans in rainwater or put them in a used wine
bottle to soften by a dying fire. He did try a number of soaking methods,
finding them roughly equivalent. The biggest difference, which ended up
with soft beans with creamy interiors was slow-cooking in a 250-degree oven.
The recipe calls for dried cannellini beans, pancetta, onion, celery, carrots,
garlic, canned tomatoes, bay leaf and kale (or collard greens if you're into
Soul Food). I decided not to search around (or drive down to Boulder's
Whole Foods) for the pancetta and just substituted 4 strips of bacon instead.
These I cut up and sautéed with a chopped large onion, 8 garlic cloves, celery
sliced in perfect little quarter-moons, and carrots. The carrots were the
bagged little ones that Junie left me and worked fine. The celery was the
last few stalks of what I had in the vegetable crisper. The bacon was the
last of what was in the freezer (and has been for months). Since I was
trying to make this a really easy recipe with whatever I had around, I used the
diced tomatoes that I usually have a dozen cans of anyway. I intended
using the same low-sodium low-fat chicken stock that I have lots of (in those
handy cardboardish two-pint cartons). I broke down and made a
wine-and-kale run, though, picking up a nice Tuscan red that was on sale, and
running into Safeway to grab a bunch of kale. The CI recipe has you use
about half and half water and stock, but I just used stock (hey, it's low-cal,
low-fat and low-sodium, why use water?). At this point, I had very little
invested in time or materials. After the sautéing was done (in a few
tablespoons of olive oil), I threw in a pint of chicken stock and brought it to
a boil. While that was happening, I washed and chopped up the kale.
Jeez Louise, that was a lot of kale, even though I know it cooks down.
When the broth was boiling I started adding kale, filling up the pot, letting
the kale reduce in size, and then doing it again. Even at that, I only
used two-thirds of a bunch and bagged the rest. When the kale was ready, I
did something diabolical. I poured in two big cans of Great Northern
beans, waited 5 minutes and started ladling it out for my dinner. Because
I didn't cook the beans, they were very nice and didn't require soaking
overnight, much less rainwater. The whole recipe took 15 minutes or so,
and was delicious. Tonight, I will take the rest of it and doctor it up
with sautéed red peppers and some Tabasco. Safeway is having a sale on red
peppers ($1.79 a pound in the dead of winter!) and I'm a sucker for red peppers.
Here's a Microsoft IT problem someone can help me with. Lord knows that
googling my brains out on it hasn't been much use. I have a rather large
office in my home, in fact it's the entire basement except for that big wine
rack over by the hot water heater. Between Junie's office, my office, and
the downstairs lab, I have something like 20 systems, mostly Windows XP, but a
couple of Vista machines and 4 Windows Server 2003 machines for websites, domain
server, FTP server, VPN server, mail server and so on. I love Remote
Desktop and use it all the time, bouncing around from machine to machine from my
desk, or from East Jesus, Wyoming if I happen to be in a motel there with a fast
Internet connection. Two of the systems, one XP and one Server 2003 both
lock out Remote Desktop from time to time. I found that what happens is
that, even though it's an "automatic start" service, Remote Desktop Help Session
Manager stops at some point, and I'm locked out. All I have to do is run
over to the machine and start it again, but invariably, within the next couple
of days, it stops again. Any ideas?
Comments
Anything being logged in the logfiles?
What is that "Remote Desktop Help Session Manager" service logging in as?
Are the account permissions OK for that account?
Can you do a net start and stop for that service (remotely) OK?
You can email me if you want.
Posted by: Jilly | January 30, 2008 06:09 PM
Jeff,
I ran into this problem when I was setting up terminal services for a client of mine. Basically, WinServ 2k3 comes with 1 or 2 licenses of terminal services activated (I can';t remember). If you don't log out properly from the server, it ties up the license in limbo. And when you don't log out properly the second time, terminal services is like, "Nope! all of your licenses are being used right now, eff off!" and doesn't let you remote into the computer, and thus you have to a.) restart the service or b.) "disconnect" the other two sessions in the terminal services control panel. I hope this helps!
--Matt Paulsen
Posted by: Matthew Paulsen | January 30, 2008 06:47 PM
Dear Jilly and Matthew: Thanks! The hint about the WinServ 2k3 explains one behavior that I can now fix (thanks, Matthew). Jilly, I've looked at the log files and nothing *obvious* pops up. I CAN net start/stop the RD Help Session Manager while connected via RD. I *think* the permissions are OK since 1) my domain account is both a domain administrator and an administrator on the local machine, 2) I can RD in to that box easily and do all the time (it's my accounting system), except when I can't and that's when I noticed that the Remote Desktop Help Session Manager had stopped.
Now one thing that's interesting is I noticed that if I keep RD open to that system, it stays up forever. AND, I just noticed that the RD Help Session Manager (let's just call it RDHSM) has stopped again, and I can start it from within RD. RD is logged in as "Local System".
As for log files, there's nothing of note in Application, IE and Security logs are empty. System has some warnings, information and errors.
The Information log entries are mainly about me restarting RDHSM, but there are also some entries:
The Remote Desktop Session Manager service entered the stopped state, Event ID 7036.
Now, that's nice of Windows to tell me, but I wish it just wouldn't do it in the first place.
The Warning entries are pretty much:
1. Can't establish a secure connection to DNS/prisoner.iana.org. Maybe some screwup in our DNS setup?
2. The time service can't synch up.
The Errors are pretty much all about VC89.MFCLOC, which I can go look up. The Source is SideBySide, which I thought was adware, but I actually can't find it running as a service or in the registry.
Thanks for your help!
Posted by: jbahr | January 31, 2008 07:05 AM