Simple Blog Update

Well, we’ve got 2 projects drawing to a close and they’ve been really spectacular ones to handle. I’m truly sorry for the lack of updates but I’m having a little bit of writers block, not to mention the additional work clients might have in store for us.

The Hargrave Corporation website I admit isn’t the best of my design work but a designer can never be too happy for their work half the time. The company deals with a lot of heavy duty industrial pumps and working with them was definetely an added experience to our environment. Instead of a boring old corporate website, we introduced to them the idea in giving all their visitors a ‘pumped’ up education.

The funny thing about this project is that it’s crashing Internet Explorer in some way. It happens when your cache is empty and surf to every page before it finishes loading. We’ve tried asking in some forums but there still ain’t a reply. Here’s a screenshot of the weird error. You got any remedies?

Oh yeah, this only happens on this website and not on other clients like; arkitekainonali.com

We’re almost wrapping up the new corporate website for UNIPAC Engineering as well. It was quite a long duration to get this to happen but it was a lesson learnt to improve the business further. The great thing is that through the duration we’ve gotten to know one another really well and they’ve become one of our closer friends now.

Anyway, if you’ll excuse me I have a little more work to do for UNIPAC or the boss will be speed dialing my mobile soon. :P

4 thoughts on “Simple Blog Update”

  1. the “weird error” looks like a hardware error. It could caused by fault RAM. Do you get same error on other computers?

  2. Most of the friends I’ve asked to check seems to have this problem. You’re saying faulty RAM on the server right?

  3. no, server hardware problem does not send to your computer. :)

    It is weird if all people get the same error. Use any script on the page?

  4. That’s the weird thing… there’s no javascript being used at all. The only thing i can think of is either the xhtml/css that is being parsed is somehow “bad”.

    However both of it validate fine.

Leave a comment