Let's try and get 1,000,000 replies to this post

I have a flu. I need to go out to buy stuff to eat. It's 160km/h wind outside. Unless I find some special item nearby, I'm gonna fail this quest...
 
  • Like
Reactions: Yax
Awaiting the delivery of our new, over sized couch.
The couch/room size ratio weighs to the couch side of the scale to say the least :p...
 
Travis The Dragon said:
Normally the Grammys suck, but...
l4tVQbo.jpg
Click to expand...

Go Weird Al!

Also, in case you haven't heard, Tenacious D won the award for Best Metal Performance for covering a Dio song. :D
 
Woke up this morning to find my daughter sleeping on the living room floor.
Leak in the roof developed overnight, right above her bed.
Just had the house re-roofed a couple years ago. :mad:
 
mckindog said:
Woke up this morning to find my daughter sleeping on the living room floor.
Leak in the roof developed overnight, right above her bed.
Just had the house re-roofed a couple years ago. :mad:
Click to expand...

That reminds me of a personal episode, "Why is there a pond on my laptop?". A classic tragedy.
 
mckindog said:
Woke up this morning to find my daughter sleeping on the living room floor.
Leak in the roof developed overnight, right above her bed.
Just had the house re-roofed a couple years ago. :mad:
Click to expand...

:O

I used to have a crap roof. New one was built almost exactly 10 years ago.
 
mckindog said:
Woke up this morning to find my daughter sleeping on the living room floor.
Leak in the roof developed overnight, right above her bed.
Just had the house re-roofed a couple years ago. :mad:
Click to expand...
Ohhh buddy I'd be livid. Someone call Mike Holmes!
 
Here's today's IT story for you.

The program I support runs on Java. Specifically, it requires Java 1.6.0_37 - 1.7.0_71 to run. Once the program is open, it uses its own internal install of Java 1.7.0_45, which is why such a broad range of Java will run it. We updated an Alberta client on the weekend to the newest version. 2 of their 70 workstations were not working. One of the guys I work with determined that it was because those workstations had 1.6.0_25 on it. Update Java on those workstations, no problem.

They call back 2 hours later. Their IT department, rather than update those 2 computers manually, pushed out Java 1.6.0_30 through the Windows Server update feature to all the workstations. Unfortunately, this sucked for two reasons. 1) it was the wrong version of Java. 2) The workstations that had our program opening had javaw.exe in active memory, so it didn't overwrite that. In fact, it removed the file, but did not write the new version of javaw.exe. Once they closed our program and javaw.exe disappeared from active memory, Windows acted as if java had never been installed and jar files would not open.

The punishment as ordered by support? Take a copy of 1.7.0_45 to every computer manually and install it.

Fuckwits.
 
LooseCannon said:
Here's today's IT story for you.

The program I support runs on Java. Specifically, it requires Java 1.6.0_37 - 1.7.0_71 to run. Once the program is open, it uses its own internal install of Java 1.7.0_45, which is why such a broad range of Java will run it. We updated an Alberta client on the weekend to the newest version. 2 of their 70 workstations were not working. One of the guys I work with determined that it was because those workstations had 1.6.0_25 on it. Update Java on those workstations, no problem.

They call back 2 hours later. Their IT department, rather than update those 2 computers manually, pushed out Java 1.6.0_30 through the Windows Server update feature to all the workstations. Unfortunately, this sucked for two reasons. 1) it was the wrong version of Java. 2) The workstations that had our program opening had javaw.exe in active memory, so it didn't overwrite that. In fact, it removed the file, but did not write the new version of javaw.exe. Once they closed our program and javaw.exe disappeared from active memory, Windows acted as if java had never been installed and jar files would not open.

The punishment as ordered by support? Take a copy of 1.7.0_45 to every computer manually and install it.

Fuckwits.
Click to expand...

Wow.
 
LooseCannon said:
Here's today's IT story for you.

The program I support runs on Java. Specifically, it requires Java 1.6.0_37 - 1.7.0_71 to run. Once the program is open, it uses its own internal install of Java 1.7.0_45, which is why such a broad range of Java will run it. We updated an Alberta client on the weekend to the newest version. 2 of their 70 workstations were not working. One of the guys I work with determined that it was because those workstations had 1.6.0_25 on it. Update Java on those workstations, no problem.

They call back 2 hours later. Their IT department, rather than update those 2 computers manually, pushed out Java 1.6.0_30 through the Windows Server update feature to all the workstations. Unfortunately, this sucked for two reasons. 1) it was the wrong version of Java. 2) The workstations that had our program opening had javaw.exe in active memory, so it didn't overwrite that. In fact, it removed the file, but did not write the new version of javaw.exe. Once they closed our program and javaw.exe disappeared from active memory, Windows acted as if java had never been installed and jar files would not open.

The punishment as ordered by support? Take a copy of 1.7.0_45 to every computer manually and install it.

Fuckwits.
Click to expand...

Lovely.
 
You must log in or register to reply here.
Back
Top