(no subject)
Mar. 12th, 2008 05:12 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
sessifetI'm just having a marvelously wonderful day today. Really.
It starts by the alarm going off at 5:55. I press snooze. My alarm goes off at 6:05. I press snooze. I wake up at 6:13 in a panic because really? I should have been in the car in about 2 minutes. I run around getting ready, and I think there's a chance I woke up housemate by running into the table in the living room.
Get in the car and notice it's a bit blustery as stuff has fallen over, making getting past the roadworks even more interesting than usual. Mutter to myself about how these foolish Brits don't seem to be able to drive in anything other than sunny weather, because come on people, it's only a bit of wind. This is nothing compared to some of the storms I...Erm...why is the car suddenly going sideways?
So yes, it was slightly windier than I expected. I was fine until I hit the top of a hill and the car decided it really wanted to explore the hedge on the opposite side of the road. Fortunately there were no people or cars there and I quickly got back on my own side.
Get to work, boot up PC and insert my card. I insert my card. 'The card you have supplied cannot be recognised.' I take out my card. I insert my card. 'The card you have supplied cannot be recognised.' I sigh. I take out my card. I clean my card. I insert my card. 'The card you have supplied cannot be recognised.' I flail and log on with my emergency password instead, resolving to fix that problem when it is not busy.*
I get a few calls, all easily resolved and just when I'm hitting my stride, I get a fun one. A really fun one. It's two conflicting '< application1> versions on one PC. Sounds easy, right? Wrong. First I have to figure out what both versions are called. They are not called '< application1>'. They're called < gibber> and < whimper> respectively. Now I have to figure out which version is causing the conflict.
*time passes*
Apparently neither. Hmmm. Let's try repairing the software. I have to log-on as admin, because the customer does not have the needed rights to repair that software. I get an error when doing it the straightforward way. I do the work-around. This works. I repair < gibber>. It is happy and repaired. I start < gibber>. < gibber> politely tells me to go sodomise myself with a candlestick. I sulk. I ask one of the product specialists. They tell me to get rid of < whimper>. < whimper> sulks at me and tells me it does not like me at all and it won't go away unless its original friend tells it to.
This is an issue. Original friend, unfortunately, is not around. Even more unfortunate, this person no longer works there. This does not, however, mean that the customer's PC will allow me to get rid of the offending file on said original friend's profile. Customer then has brilliant insight. < application1> and < application2> do the same thing! They've the same username and password too! Great! Load up < application2>. It...starts installing?
It's going to take 45 minutes? At this point both customer, product specialist and I are thoroughly confused and fed up so we decide to dump the whole thing on 2nd line.**
*time passes*
Customer cannot open PDF files. Whoo! I know this! < foo> has to be installed, otherwise PDFs can't be read. The customer confuses me momentarily by mentioning he's 'always been able to open them before'. But then I remember the important question: 'Is this your own computer?'. I grin happily when I am told no. So < foo> is not installed. Easy-peasy.
Okay, it is installed. Well, then all I have to do is repair the software. Also easy-peasy.
Or not. There is no repair option, only remove.
We'll do that, then. Ah. We can't because it can't find the relevant files to be removed. Look up file-path. Find empty < foo> folder. Hmmm. Go to shared drive and copy files to C:. We can't access the shared drive because of a rights issue. Log-on as admin and try again. Aha. We can access the shared drive. Copy files to relevant C: path. We can't because the moon is in Virgo. Try installing directly from shared drive via admin command line prompt***. We can't because Venus is ascending.
Use a nifty tool and open up the customer's C: drive on my machine (ALERT ALERT! Lie to children!). By this time we've been going for 30 minutes and the customer and I are giggling like loons because what else can happen? Copy files straight from my distribution server. It will take 10 minutes! We go 'Bugger this for a game of soldiers,' in unison and agree to meet back at the same spot in 10 minutes.
*more time passes*
We return refreshed and full of hope. This must have fixed the issue. Press 'remove'. It doesn't because Mars is currently off shagging Jupiter in the sign of Taurus and the rest of the planets just really don't want to know. I flail. The customer flails. The PS flails. I go 'Fuck it' and force the installation through the command line prompt****. It works. We are flabbergasted and not a little impressed.
I go home and decide to go have my walk. I nearly get blown off the bridge. I turn back. I nearly get clobbered by a flailing tree limb. I come home and decide to make hot chocolate. I forget my milk. I realise this and am just in time to spend the next ten minutes scrubbing burnt milk off the hob.
In short, I've been having a lovely day. I can't wait for it to be weekend.
* I end up having to request a new card because mine's fucked.
** Who promptly solve the fucking thing in five minutes. There is no god.
*** I may sound like I know what I'm doing, but I've no idea why command line prompt should work there. By this time, one of the PSs was looking over my shoulder and telling me what to do.
**** I fail at independent geeking at this stage, but I'm very good at being a trained monkey.
It starts by the alarm going off at 5:55. I press snooze. My alarm goes off at 6:05. I press snooze. I wake up at 6:13 in a panic because really? I should have been in the car in about 2 minutes. I run around getting ready, and I think there's a chance I woke up housemate by running into the table in the living room.
Get in the car and notice it's a bit blustery as stuff has fallen over, making getting past the roadworks even more interesting than usual. Mutter to myself about how these foolish Brits don't seem to be able to drive in anything other than sunny weather, because come on people, it's only a bit of wind. This is nothing compared to some of the storms I...Erm...why is the car suddenly going sideways?
So yes, it was slightly windier than I expected. I was fine until I hit the top of a hill and the car decided it really wanted to explore the hedge on the opposite side of the road. Fortunately there were no people or cars there and I quickly got back on my own side.
Get to work, boot up PC and insert my card. I insert my card. 'The card you have supplied cannot be recognised.' I take out my card. I insert my card. 'The card you have supplied cannot be recognised.' I sigh. I take out my card. I clean my card. I insert my card. 'The card you have supplied cannot be recognised.' I flail and log on with my emergency password instead, resolving to fix that problem when it is not busy.*
I get a few calls, all easily resolved and just when I'm hitting my stride, I get a fun one. A really fun one. It's two conflicting '< application1> versions on one PC. Sounds easy, right? Wrong. First I have to figure out what both versions are called. They are not called '< application1>'. They're called < gibber> and < whimper> respectively. Now I have to figure out which version is causing the conflict.
*time passes*
Apparently neither. Hmmm. Let's try repairing the software. I have to log-on as admin, because the customer does not have the needed rights to repair that software. I get an error when doing it the straightforward way. I do the work-around. This works. I repair < gibber>. It is happy and repaired. I start < gibber>. < gibber> politely tells me to go sodomise myself with a candlestick. I sulk. I ask one of the product specialists. They tell me to get rid of < whimper>. < whimper> sulks at me and tells me it does not like me at all and it won't go away unless its original friend tells it to.
This is an issue. Original friend, unfortunately, is not around. Even more unfortunate, this person no longer works there. This does not, however, mean that the customer's PC will allow me to get rid of the offending file on said original friend's profile. Customer then has brilliant insight. < application1> and < application2> do the same thing! They've the same username and password too! Great! Load up < application2>. It...starts installing?
It's going to take 45 minutes? At this point both customer, product specialist and I are thoroughly confused and fed up so we decide to dump the whole thing on 2nd line.**
*time passes*
Customer cannot open PDF files. Whoo! I know this! < foo> has to be installed, otherwise PDFs can't be read. The customer confuses me momentarily by mentioning he's 'always been able to open them before'. But then I remember the important question: 'Is this your own computer?'. I grin happily when I am told no. So < foo> is not installed. Easy-peasy.
Okay, it is installed. Well, then all I have to do is repair the software. Also easy-peasy.
Or not. There is no repair option, only remove.
We'll do that, then. Ah. We can't because it can't find the relevant files to be removed. Look up file-path. Find empty < foo> folder. Hmmm. Go to shared drive and copy files to C:. We can't access the shared drive because of a rights issue. Log-on as admin and try again. Aha. We can access the shared drive. Copy files to relevant C: path. We can't because the moon is in Virgo. Try installing directly from shared drive via admin command line prompt***. We can't because Venus is ascending.
Use a nifty tool and open up the customer's C: drive on my machine (ALERT ALERT! Lie to children!). By this time we've been going for 30 minutes and the customer and I are giggling like loons because what else can happen? Copy files straight from my distribution server. It will take 10 minutes! We go 'Bugger this for a game of soldiers,' in unison and agree to meet back at the same spot in 10 minutes.
*more time passes*
We return refreshed and full of hope. This must have fixed the issue. Press 'remove'. It doesn't because Mars is currently off shagging Jupiter in the sign of Taurus and the rest of the planets just really don't want to know. I flail. The customer flails. The PS flails. I go 'Fuck it' and force the installation through the command line prompt****. It works. We are flabbergasted and not a little impressed.
I go home and decide to go have my walk. I nearly get blown off the bridge. I turn back. I nearly get clobbered by a flailing tree limb. I come home and decide to make hot chocolate. I forget my milk. I realise this and am just in time to spend the next ten minutes scrubbing burnt milk off the hob.
In short, I've been having a lovely day. I can't wait for it to be weekend.
* I end up having to request a new card because mine's fucked.
** Who promptly solve the fucking thing in five minutes. There is no god.
*** I may sound like I know what I'm doing, but I've no idea why command line prompt should work there. By this time, one of the PSs was looking over my shoulder and telling me what to do.
**** I fail at independent geeking at this stage, but I'm very good at being a trained monkey.
