I retract my statement. Wally Herger is a fucking tool.
Original post:
"Although I don't want to defend such a dismal example of a politician, he is doing what he said he would do. What did he say he would do? He quite clearly said he would follow the vote of the Republican party, and he has done that overwhelmingly well.
He's a puppet, and a moron, but he's not a liar. He's just doesn't have any opinion; except that of the Republican party."
Wednesday, December 12, 2007
Tuesday, October 30, 2007
joys of network ghosting
At my work I use norton ghost 7.5. laugh it up; I know it's archaic. It may be archaic, but ghost is one of the most useful pieces of software I have in my daily battle with the computer illiterate masses. It allows me to take the complete image of a particular computer I set up and broadcast it to all of the machines in a computer lab with minimal setup.
My problem with it now, though, is with finding the proper LAN drivers to get the software to recognize. I have to ghost 20 machines, 10 are with a really old asus motherboard with an nForce2 chipset. Piles of crap, essentially. I wouldn't choose to do this type of work with such obsolete piles of garbage, but my services were volunteered by my boss as these machines are being donated to a school in oakland which can't otherwise afford computers. so we're giving them crap, to rub it in their face I suppose. This is what happens when religion does charity; they give malnourished children(whose families are killed by war and famine) a jesus t-shirt and a stack of bibles.
Back to the problem at hand. after searching for a day(a full 8-hour work period) for a driver network DOS driver called nvndis.dos, I almost gave up. Now I've found it, which is a small victory for me. The battle rages on though, as now I'm having a problem with the ghost program bootup in DOS actually seeing the driver and being able to bind it.
Like I said, I never volunteered to do this project, and I knew from the beginning that it was going to be somewhat painful. Luckily I have until the 8th to finish, and if I don't finish, I'm not taking responsibility.
My problem with it now, though, is with finding the proper LAN drivers to get the software to recognize. I have to ghost 20 machines, 10 are with a really old asus motherboard with an nForce2 chipset. Piles of crap, essentially. I wouldn't choose to do this type of work with such obsolete piles of garbage, but my services were volunteered by my boss as these machines are being donated to a school in oakland which can't otherwise afford computers. so we're giving them crap, to rub it in their face I suppose. This is what happens when religion does charity; they give malnourished children(whose families are killed by war and famine) a jesus t-shirt and a stack of bibles.
Back to the problem at hand. after searching for a day(a full 8-hour work period) for a driver network DOS driver called nvndis.dos, I almost gave up. Now I've found it, which is a small victory for me. The battle rages on though, as now I'm having a problem with the ghost program bootup in DOS actually seeing the driver and being able to bind it.
Like I said, I never volunteered to do this project, and I knew from the beginning that it was going to be somewhat painful. Luckily I have until the 8th to finish, and if I don't finish, I'm not taking responsibility.
Subscribe to:
Posts (Atom)