Archive for January, 2009

An Angelic Army

Monday, January 19th, 2009

A couple of Sundays before Christmas last, our pastor delivered a short devotional to accompany the church’s Christmas Cantata in the morning service, and one of his three points was something that really hadn’t occurred to me before…

And in the same region there were shepherds out in the field, keeping watch over their flock by night. And an angel of the Lord appeared to them, and the glory of the Lord shone around them, and they were filled with fear. And the angel said to them, “Fear not, for behold, I bring you good news of great joy that will be for all the people. For unto you is born this day in the city of David a Savior, who is Christ the Lord. And this will be a sign for you: you will find a baby wrapped in swaddling cloths and lying in a manger.”

And suddenly there was with the angel a multitude of the heavenly host praising God and saying,
“Glory to God in the highest,
and on earth peace among those with whom he is pleased!”

I always get goosebumps when I read the stories of angelic visits in the Bible and elsewhere; can you imagine the shock experienced by the shepherds when that angel popped in? “Fear not,” they always say… “Too late!” I’d say (if I could say anything, that is.) “‘Scuse me while I go clean out my drawers.” But did you catch that in the second paragraph? It was a heavenly host; not a choir, not a group, not a quartet. A host. The term “host” in medieval Latin literally means “army”. It was an army that was sent to announce the Savior’s birth!

While the message was delivered to the shepherds — they were the only ones mentioned in the narrative — the message was directed more at Satan, challenging the authority he held over the earth. The statement “Glory to God in the highest” was the angels’ way of putting Satan in his place in relation to God; God is in the highest place, and all else is under his dominion, even Satan. And that message delivered by a host — an army of angels… Imagine the sound of that; the mental image I get is of the Promise Keepers events I’ve attended with the sound of tens of thousands of voices chanting or singing in unison. (Like the time Steve Green led us in singing The Battle Hymn of the Republic for the closing song at the Boulder, CO, PK event some years ago. Goosebumps again!)

Back to the sermon; Pastor Petersen said it much better than I can rephrase it, so here’s a transcript of the second point from his message from that day (taken from the message posted online, from 11:43 to 16:20.)

Warfare.
Warfare!
Warfare?
Why are you talking about warfare at a time like this? A time like Christmas?
Because the glory of God is the focal point of all spiritual warfare. Satan, from the beginning, has desired God’s glory. He wanted it, and he did everything he could to get it. And as a result he ravaged the world, set it on a course for destruction.
Listen to what Isaiah wrote in Chapter 14 about Satan himself:
How you have fallen from heaven,
O morning star, son of the dawn!
You have been cast down to the earth,
you who once laid low the nations!
You said in your heart, ”

Now this is the heart of Satan himself…

“You said in your heart,
“I will ascend to heaven;
I will raise my throne
above the stars of God;
I will sit enthroned on the mount of assembly,
on the utmost heights of the sacred mountain. [a]
I will ascend above the tops of the clouds;
I will make myself like the Most High.”

Over & over Satan’s heart was to be above God!

Listen to what’s said at the birth of Jesus;
“Glory to God in the…” say it with me… “Highest!” The highest!

Now also note what we’re told in Luke chapter 2 verse 11. Please note, it doesn’t say there was a choir. There was no choir present at the birth of Jesus. Do you know what was present? A military unit. An army was at the birth of Jesus. Not a choir, not people dressed in white robes playing harps, it was a military campaign. “Heavenly host” means “heavenly army”, an army of God fitted with the angels of heaven. The mighty ones of God. And they were at the birth of Jesus. Not singing lullabies, but declaring warfare.

Satan has been against God from the beginning, he’s trying to take glory from God, and we’re here to tell you the gauntlet has been put down, the war has begun, the Son of God is here, Glory to God in the highest.

Is there another Amen here? Amen!

That little baby grew to be a boy and a man, and went right to the cross, and at the cross the climax of spiritual warfare occurred. where Jesus died for the sins of the world, so that anyone who would receive him would be forgiven of their sins, receive the very power of God in their lives to live for God and to do spiritual warfare in this world.

Because Paul says in the New Testament, Ephesians chapter 6, our battle is not against flesh and blood, but against the forces of darkness in this world. How on Earth do we have hope against the forces of darkness? Ahhh! Glory to God… In the highest. Jesus Christ makes it possible.

In all the times I’ve heard that story, that’s the first I can recall where the angelic host was referred to as something other than musical accompaniment to the arrival of the Christ Child. The image of a choir of angels never seemed quite right or satisfying to me… The story of the birth of Jesus plays an important part in the whole of the Gospel narrative, but the glurge that often goes with it can be a bit much. Jesus came to Earth to set things right, and God knew that’s something Satan wouldn’t like. It would take more than a choir to send the proper message, so the angelic army was to show that God meant business; that Jesus had at his disposal all the power of God.

Too many people want to keep Jesus in the manger; he’s safer and more controllable there, but that’s not what Jesus’ mission was. He came to shake things up, and for that I am thankful.

Many people who think of themselves as Christians and “good people” only want to see the calm and peace-loving side of Jesus. I remember arguing with some friends about this subject during the run-up to the Iraq war; they questioned how I could, as a Christian, support the war, because after all, Jesus said to “turn the other cheek”, so Christians were supposed to be all about peace and happiness and forgiving those who’ve wronged us. But Jesus was very upfront about his purpose on Earth;

“Do not suppose that I have come to bring peace to the earth. I did not come to bring peace, but a sword. For I have come to turn
” ‘a man against his father,
a daughter against her mother,
a daughter-in-law against her motherinlaw—
a man’s enemies will be the members of his own household.’
Jesus — Matthew 10:34-36

I don’t write this trying to justify the wars in Iraq and Afghanistan — that’s far too complicated for one so easily distracted as me — but Jesus knew that his coming would bring conflict, and because he is both God and Man, that conflict crosses over from the spiritual realm to the physical. He also warned his followers that the enemy’s hatred would carry over to them — and to us, two centuries removed. The Fall was a the first earthly manifestation of that conflict, and we’ve been suffering in it ever since. The problem is that whether we acknowledge it or not, we’re in a war. I firmly believe that the negative attitudes toward and persecution of Christians and Jews throughout the ages are a direct result of that war, but many think that if we can only convince those doing the persecuting that we aren’t so bad, they’ll be nicer.

The trouble is that there is no logical earthly cause behind their hatred, and all the peace talks in the world won’t end it. The conflict will only end with the triumphant return of Jesus, accompanied by that same angelic host, in even greater force, and with even more to say than on that starry night oh so long ago.

image; “White Rose” by Gustave Doré.

Why Is Cloning A PC Drive So Difficult?

Monday, January 19th, 2009

One of the desktop machines at work had an alert come up a while back — Disk in Predictive Failure — so I made preparations to replace it. From what I’d read, when the SMART status on a disk tells you something like that, the drive will be toast; it could be an hour or it could be a year, but sooner or later it’s gonna bite the dust.

Having done this numerous times on Macs, the process of replacing a drive ought to be the same, right? So first things first, I installed Retrospect Client on it (we use Retrospect for backing up the company servers, and have unlimited licenses for clients) and backed up the whole drive, then bought a replacement drive. The machine is a Dell Dimension, and it had the original Seagate 160GB SATA drive; I didn’t think it was important to replace it with an identical drive, so I bought a Hitachi replacement of the same size. I wasn’t excited about the whole reinstall-from-scratch prospect, so I asked around for recommendations for a good Windows disk cloning solution — Norton’s Ghost is probably the industry leader, but I heard good recommendations for Acronis as well, so I downloaded a copy of their Migrate Easy software to try out.

The first go didn’t go well; Migrate Easy seemed to clone the disk alright, but when I pulled out the original drive and tried booting from the new it errored on something or other. I tried it again, varying the settings a bit to see if I could work through the problem; same result. One more try; ditto. I checked the Acronis support page, but found no help there other than an email submission form. I filled it out, describing my problem, then put the machine back together with the original drive, and left it as is; I didn’t have any more time to mess with it that day. I still haven’t heard anything back from Acronis.

Things got really busy at work after that, plus the machine’s user seems to be there every day but weekends (I hate working Saturdays, and won’t work Sundays) so procrastination set in. Thankfully the drive kept humming along, and I was able to work on it when I chose. I wanted to be able to set aside at least a couple of hours so that if I had some success I could make sure the job was complete and everything was working. Well, days turned into weeks, and before I knew it more than a month had gone by, and my trial version expired before I got back to it. Wanting to see if I could work out the issues I had with Acronis, I spent the $40 or so to buy a license and took another stab at it a week ago, but got much the same results. I went through the clone procedure a number of different ways and still came up with the blue screen when it was booting up. Crud. If it’s duplicating the disk block-for-block as I’m assuming it does, why is it that there is something obviously wrong with the OS on the new disk that keeps it from booting properly?

Last weekend — another Saturday, of course — I jumped on the project again, and finally completed it. What ended up working was to use Acronis to duplicate the disk, then boot up from the OEM installer CD and reinstall the OS. I was hoping the installer could just repair the installation, but nope… so I just had it install a clean OS (which was of course XP Pro SP 2, whereas the machine had been running SP 3.) Once I tracked down the NIC drivers & got them installed, I was able to get on the network and install the Retrospect Client software. When that was done I configured the machine as a client on the server that did the backup, and told it to restore the disk. In spite of some warnings from Retrospect against restoring an OS that’s newer than what’s running, everything went great.

After Retrospect finished, I rebooted the client, and Retrospect did a little housecleaning, then automatically rebooted again and ran its cleanup utility, again. But it sure seemed to be a solid running machine. It still had the second Windows install folder, so that got trashed, then I ran a defrag on the hard drive… So far, so good.

But I’m still left wondering why the whole procedure had to be so difficult… On it’s own, Acronis failed. I read something online about Acronis not being fond of cloning to a different type of disk; maybe I’d have had better luck if the replacement disk was the same brand/size. I dunno. I probably should’ve done the whole thing with Retrospect and saved myself some hassle; it still would’ve involved installing an operating system the new drive, but it wouldn’t have duplicated the two hidden partitions on the drive. I guess I won’t know if Norton would’ve done the job without getting Retrospect involved unless another machine gives the same problem and I try it, or I test it just for fun.

What I do know is that the same job on a Mac would’ve been much more straightforward; using Carbon Copy Cloner, the job would’ve been done the first time around. And if it were in OS 9… No 3rd-party utilities needed; just hook up the new drive to the machine, format the drive & let the Finder copy everything over. So much easier. But like cockroaches, Windows boxes are pretty well entrenched, and they aren’t going away any time soon. Sigh.

Twenty-Three Below Zero

Thursday, January 15th, 2009

Yes, that’s right; twenty-stinkin’-three degrees below zero, as evidenced by my trusty outside thermometer…

.

That’s the same as -30.55° Celsius. Brrr. But that seems balmy to Aberdeen’s low of -42° this morning.

According to the National Weather Service office in Sioux Falls, that’s the coldest it’s been since sometime in the mid 1990’s (didn’t catch the exact date) but it’s still not a record low. The record on this date in 1972 was -32°.

Even now, at almost noon, the temp has risen to only -13°, shooting for a ‘high’ of -1°. Can’t wait. But it’s supposed to be in the 20’s or 30’s by the weekend. We’ll be running around in shirtsleeves by then I’m sure.

Review — NuShield AG™

Tuesday, January 13th, 2009

My apologies to those who have been asking for this follow-up review; it’s been a long time coming. Since I wrote about the new iMac that was purchased for work and the trouble with it’s glossy screen (link), it’s been a crazy busy time at work with a major system upgrade, followed closely by the Christmas & New Year holidays, and trouble getting decent photos of the film installed on the iMac (and I’m still not happy with what I’ve got…) Now, finally, the planets seem to be in alignment and everything is coming together; if only I could sit down for more than a five minute stretch to finish this…

I ordered two NuShield AG™ Antiglare Screen Protectors for 24″ iMacs ($35 each) and one for my G4 PowerBook — it was inexpensive ($15) and I thought it might help avoid the scuff marks the keyboard was leaving on the original. They all arrived in a sturdy cardboard tube a week or so later, and I installed the film on my PowerBook that day, and the iMac the next day. The PowerBook went pretty smoothly; clean the ‘Book’s screen, clean the NuShield, pop the sides under the edges of the display bezel, and you’re done. The iMac? A little more involved.

The display fronts on the new-generation iMacs are flush with the aluminum case, so the NuShield film, as packaged for the iMac, is basically a rectangular sheet of their antiglare material with narrow adhesive strips around the perimeter that holds it in place. It’s cut to the same width as the display area on the front of the iMac, but the height is just a little shorter than the display to keep it from obscuring the iSight lens at the top-center of the screen. Of course the documentation accompanying the film says nothing about where it should be positioned, so it took a few tries to get it aligned just right. The CSI team would have no trouble figuring out who installed it; my fingerprints are all over that stickyback.

The fit & finish of the installed product was less than impressive. When examined up close it looks exactly like what it is — a piece of film tacked to the display. From a distance it looks fine, but up close the edges of the film stand out against the glossy black of the display frame, and the adhesive strips are easily seen. The corners are cut square, and at the bottom the corners extend past the black frame to overlap onto the aluminum case. You’d think it’d be an easy matter to match the radius of the display’s corners at the bottom; that would give it a more finished look.

After all the futzing around trying to get the thing on straight, I’m still not totally convinced that the sheet is cut square; no matter how I tried, I couldn’t get it quite straight. The edges still look like they’re not parallel with the adjacent display edges. After several attempts, I gave up & left it at somewhat of a happy medium that I’m not terribly happy with. But then again, I’m not looking at it 8 hours a day either.

Getting it positioned was about as easy as making sure that it & the screen on the iMac were dust free; as in, not very. I have to admit that I handicapped the process a little, as this particular user isn’t known for her housekeeping abilities and I didn’t take the time to clean the area first. It’s necessary to lay the sheet out flat during the installation, and any little speck of dust gets sucked right to the static-filled film. Note to self: if ever installing one of these again, make sure the desk and surrounding area are thoroughly cleaned first. And if I’d been thinking, I would’ve borrowed some dust elimination tools from our platemaking area; they used a roller with a slightly tacky surface to remove dust from plates, film and the vacuum exposure unit before exposing. That was all before we purchased a digital plate imager, but the roller is still around. That would’ve worked a treat for this! Next time. Yes, next time.

But once the film was installed, it did do a decent job of reducing the glare produced by the standard office lighting. Personally, I wasn’t too bothered by the glare, but the user for whom this iMac is home was bothered, and I haven’t heard a peep from her since installing the NuShield regarding glare, so that’s one measure of success.

There is a side effect produced by the film that is a bit bothersome; to reduce the glare, the NuShield film has a bit of a graininess to it — I suppose it’s the grainy surface that breaks up the reflections that would otherwise appear as glare to the user. But when the grainy surface is against the glossy front of the iMac, it produces a moiré-like pattern. Unfortunately, photographing this pattern is beyond the limited abilities of my equipment and me, so I can’t really show it well. But the graininess of the film and display’s pixels work together to make strange patterns on the screen. The severity of the pattern seems to vary according to the color on the display and how busy a pattern is displayed. To me, personally, this issue is more of a nuisance than the glare. But again, the user doesn’t seem to mind it at all. So for this particular installation, it does the job.

All in all, if the glare produced on your new iMac is an issue, the NuShield is an ok option. Not wonderful, but adequate. Were the glossy-screen iMac my primary computer, the glare would need to be pretty bad to make me want to install this product; the attachment method and moiré-like pattern produced by the film are big negatives to me, and the need for glare reduction would need to be pretty dire to offset those negatives. But again, that’s just me. A couple of small things NuShield could do to improve the product…

  1. … put a radius on the bottom corners of the film to match the display. I suppose I could do that myself, but…
  2. … the installation instructions that came with the film were pretty generic and didn’t cover the adhesive method used on the iMac at all; lots of room for improvement there.

The dearth of instructions specific to the iMac gives me the feeling that this is fairly new territory for NuShield. At least I hope that’s the case.

Since that first article I purchased and installed a second 24″ iMac with the glossy screen — I ordered the second NuShield knowing this purchase was coming up. However the guy using the second iMac isn’t bothered by the glare, so the film is still in its container. I’ll probably hang onto it in case we get another iMac that needs de-glossing.

Two Things That Bug Me…

Tuesday, January 13th, 2009

Not to complain, but there are some elements of some websites that make me just a little crazy sometimes…

One of them is the “Close Window” button you sometimes see. I just saw it on a window that popped up when I clicked on a link to view an enlarged image of a product at a retailer’s website. It’s a normal window, one that could be closed by clicking on the X (or the red dot) in the top corner of the window, or by a Ctrl-W (or Command-W) keyboard command, or even clicking to FileClose Window. But no; some web designer in his/her wisdom thought it would be a good idea to a button that can be clicked that will do it for you. It’s usually just one of those things I ignore, but for some reason(?) I clicked on that button today and got an alert from IE (on Windows XP):

How stupid is that? I can see how IE would maybe want to alert the user that something in the web page was trying to trigger something in the application, but why would closing the page be a concern? Shouldn’t the app be aware that it was a user’s mouseclick that initiated what was going on? Aside from that, just the presence of that button means that someone somewhere thinks that people using a computer aren’t smart enough to figure out that closing the window that just popped up involves clicking on the same user interface element as closing any other window. Excuse me, but it’s not exactly rocket science.

The second thing that bugs me is when a website displays an image that is either click-able or has a link nearby to view an enlarged image, and when clicked you get the same image with no enlargement in a different window. I realize that most of the times this happens is when a retailer gets its product images from a vendor, they only get one size — small — and the pages are automatically built from a template. But would it really that difficult to code so that nothing happens if there isn’t a larger image available? Or that no link is generated in the first place?

Probably not much of an issue with a faster computer and connection, but still, how annoying; if a site shows a tiny product image and I want to take a closer look, when the page tells me to click here for a closer look, I’d like to get a closer look. Is that too much to ask?

Ok. I feel a little better now.

Tagged

Sunday, January 11th, 2009

I guess I’ve been tagged — but thankfully not like the poor old bovine above. According to Rick’s post, what I have to do is…

… list seven random or weird facts about myself and then tag seven other people.


So, here goes, whether it’s right or not. But if it’s not, well I guess it’s not. And here goes in spite of the 49 posts stacked up in Draft status waiting to be finished. Guess a backlog like that is what happens when someone with SODS (Shiny Object Distraction Syndrome) tries to run a blog (does that count as a weird or random fact about me? Or two?)

  1. My first name is not David (not telling what it really is!)
  2. I got my driver’s license two weeks before my 16th birthday, but got picked up for speeding the same day and subsequently lost said license. Yeah; not one of my better moments.
  3. I met, fell in love with, proposed to, and married my charming & gracious Yvonne in a span of about 8 months. Yup; that was one of my better moments!
  4. My first job out of high school was with a casket manufacturer.
  5. I have no idea how many computers I have in my house right now, but I do know that none of them are PC’s. run Window$ as a native OS. (better?)
  6. I was a registered Democrat until 1994.
  7. My longest term of employment was with CCL Label — 1991 to 2005. The shortest? John Morrell & Co. — 7.5 hours. Yup; didn’t even finish my first shift. When I’d had my fill of the place, I tracked down my foreman & told him off, threw my checked out equipment at him, stormed off in a rage, then got hopelessly lost trying to find my way out of the building. (The decision to take the job there was definitely not a shining moment in the history of me.)

Well, there’s my seven. I don’t know how random or weird any of them are, but that’s what I could come up with on a Sunday afternoon. I think I’ll just leave it at that.

But now, who to tag…

BMWotD — The One That Got Away

Saturday, January 3rd, 2009

Missed it by this much!

I first saw the ad for this 1984 528e on CraigsList in early December, but kind of dismissed it because the price sounded too low, and the seller posted only one photo. The ad came back in late December; it hadn’t sold first time around. This time the seller included a link with a slideshow of about 40 images, and it looked very clean, and the price was still the same. I emailed the owner and got a lengthy response back; obviously a BMW nut aficionado, and a big fan of the E28 model, as he currently owns — or rather ‘owned’ — two of them.

He had owned this particular example since 1994; a feat I consider to be nothing short of amazing because I’m unable to stick with one vehicle for more than five years or so. His email described his “affair with Bimmers”, how he came to own this particular E28, and a bit of its history. The reason he’s selling it is that he’s got too many BMW’s; a 2000 528i, an ’88 E28 that his wife drives, and a ’99 K1200LT touring bike. He wrote that he picked up the 2000, “in Feb 2007 and thought it was time to put the ’84 up for sale. I couldn’t do it. I kept it in the garage until now. My bride says her ’88 goes in the garage this winter or I go sleep in the shed…so here it is for sale.”

The asking price of $1,799 sounded a bit too good to be true at first, but this guy sounded legit, and from the pictures, the car certainly looked clean. Figuring that purchasing this car could be funded by selling the Suzuki — which in its present condition ought to fetch an easy $2,000 this time of year — I thought I’d go for it. The biggest issue I had with the 528 was it’s location; just north of Chicago, or roughly 550 miles from home. Even the seller, when he figured out where I was located, was pretty dumbfounded that I’d consider driving that far for it. “Yep, you’ve got the bug,” was all he could say about it.

But after running the idea past Yvonne, she gave me a green flag on the project, and the Chicago road trip didn’t really faze her at all. I emailed the seller, asking if he’d be around over the New Years holiday weekend, and yes, he would. But… He had a couple of other local prospects on the line who would be stopping by on the 1st and the 2nd. Then this morning (Jan. 2) he emailed me that someone who had contacted him after running the first ad called yesterday and stopped by last night; the deal was made, and the car is gone, gone, gone. Rats.

It’s probably a good thing that it sold; there’s snow in the forecast for the next couple of days, so a ‘quick’ trip to Chicago could get quite interesting. That and the fact that I still have the Suzuki makes the funding issue a bit questionable. I could probably have scrounged up enough for it today, but it would likely have been kind of tight getting it together on such short notice. But I think the plan hatched through this little adventure is a good start; if I want a car like that I should first spiff up and sell the Suzuki then start shopping, using one of the kids’ cars in the interim. That way when a deal like that comes available, I’ll be much more able to jump on it quickly. After shopping around a bit tonight, my hunch that clean E28’s are hard to find was pretty much confirmed, so finding another like this one might take a while. But the seller mentioned that he may be selling his ’88 in the spring…

Although the car deal didn’t work out, and that’s disappointing, my correspondence with the seller did yield some good BMW-related links… like bimmertraderonline.com and roadfly.com, which both have classified ads for classy import cars. Of course, the one I missed out on is the nicest/cheapest car on either site, but I digress… Then there is bimmer-mag.com; of course there is a magazine specifically for BMW owners. I wouldn’t be surprised to find a dozen or so more. bavauto.com has a ton of performance parts for BMW’s, and mye28.com looks like a great forum for BMW nuts. So, it’s not a total loss. Sigh.

My No-Year’s Resolutions

Thursday, January 1st, 2009

Since my track record for keeping past New Year’s Resolutions has been pretty poor — I usually end up headed in the opposite direction of what I resolve to do — I thought this year I’d maybe try a little reverse psychology. Maybe I’ll actually get where I want to go.

So, I hereby resolve to…

  1. Gain weight. I’m thinking at least 40 pounds. Just more of me to love, right?
  2. Not even think about exercising. I’d resolve to quit exercising, but I can’t very well stop if I’m not doing it in the first place. Total waste of time.
  3. Read less, and I’ll hide my Bible. Quiet time? Devotions? Spiritual disciplines? Who needs them?
  4. Watch more TV. I might even break down and get cable. From what people at work talk about, I’ve been missing some good stuff.
  5. Procrastinate more. Then again, maybe I’ll wait & do that next year.
  6. Take up a new habit: Maybe drinking. And smoking would be good too. And as long as I’m at it, I’ll start hitting the casinos.
  7. Spend more time at work.
  8. Spend less time with the wife & kids. That only deepen any emotional attachment to them, which interferes with #7.
  9. Take a vacation to someplace important: like to see the largest ball of twine.
  10. Stop going home for lunch or bringing a sack lunch to work: We all need to do our part for stimulating the economy, and fast food restaurants play an important role in that, right?
  11. Quit giving money & time to charity. It’s time to let someone else develop character in that way.
  12. Sell my car and buy a mid-’70’s Camaro or Monte Carlo with a really loud stereo system, mag wheels, air shocks and wide tires in back. I’ll also need to grow a mullet to complete the image.
  13. Shower and change clothes once a week, whether I need it or not. A guy has to do his part to to reduce water usage.
  14. Cash out my 401k accounts. The markets are going nowhere fast, and just think of the fun I could have with all that money.
  15. Stay up later still every night. Think of all the late-night TV and web browsing I can get done instead of sleeping. Most days at work I feel like I’m spinning wheels anyway, so showing up half asleep shouldn’t affect a thing productivity-wise.

Well, that should pretty much do it. Here’s hoping I keep a perfect track record. Of failing to achieve what I resolve to do.