December 10, 2008

nonsense redefined

i tried. i really tried.

i'm just not a tech person. this morning, i decided it was time to face the monsters head on. the papers have been peeking at me for 3 days, taunting and daring me, as if they knew i couldn't handle cyberspace.

i couldn't hide them under stacks of magazine anymore. they invaded my space, messed up my racks and just stubbornly refused to go away, no matter how i wished they would. i had to deal with it.

and so i did.

and yucks.

just looking at them gave me a literal headache and i felt like throwing up. this must be what stage fright feels like.

tentatively, i picked up the sheaves of papers i was supposed to upload into that unknown-cyber-space-out-there. holding the papers, i wondered if i could just pull open some 'drawer like' space in the CPU and chuck them in. that'd be more my definition of efficiency.

but ok. here goes. i spent 3 minutes pulling up the website that was to allow us to get into and edit the public site and i spent another 3 minutes trying to recall what it was called. a dummy site, that's it [and i totally agree, dummy indeed].

anyway, faced with the maze of icons and different pages to navigate, i just sat and stared for another 2 minutes.

after a very deep breath, i began to click on what seemed to make sense to me. come on, i'm a writer. i can read. surely it can't be too difficult. i'll just follow whatever it says. and click yes/no. simple right?

nope. i did what seemed logical, painfully going step by step, avoiding wrong clicks and doubtful icons. i stayed away from gibberish and i still got this -

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off".






Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's configuration tag to point to a custom error page URL.


bla bla bla. that's not english!

when that popped up, my mind went blank. it's ridiculous. i can handle languages well. lines upon lines of legal jargons are surmountable. tomes of the queen's english; not a problem. but those few lines????

ok. time for lunch.

ps: i'm a really simple girl. maybe ancient. maybe even [god forbid] archaic. but i definitely prefer certain aspects of the bygones.

No comments: