[QUOTE=iamthewalrus(:3=]
I got my BS three years ago. I find it hard to believe that so much has changed in academia in three years that everyone needs brand new computers to get by.
I love computers. I buy new ones about every 2 years. Sooner if I can talk myself into it. But I don’t for a second think that I need upgrades nearly that often. Certainly not for sending email and browsing websites and writing term papers. It’s clear from the OP’s post that budget is an important consideration, so dismissing a perfectly serviceable laptop out of hand because it’s too old is not being very helpful.
Here’s a link for Microsoft’s Powerpoint Viewer 2007. It’s free, and is only 25 MB. It works on Windows 2K and up.
Here’s a link to Microsoft’s Word, Excel, and Powerpoint Compatibility Pack. It’s free, is 28MB, and will enable users of Office 2000 and later to view, edit, and save files in 2007 compatible formats. It works on Windows 2000 and forward.
Here’s a link to Novell’s OpenOffice.org offering, a completely free office suite that opens Office 2007 documents. It’ll run on pretty much anything with a screen and a keyboard.
Got anything else?
[/QUOTE]
I’m going to graduate in May. I’m also a very successful IT professional. It’s fine to say you don’t need upgrades, but the reality is today’s bloatware doesn’t run well on yesterdays hardware. You can make it run, but that probably involves memory upgrades, software upgrades, compatibility upgrades, and so forth. You’re tech savvy - good for you. Most people aren’t, and would be bewildered trying to sort through the software compatibility add-ons you’re talking about here. Hell, I was apprehensive about Microsofts’s automated install I had to do to open the Office 2007 word doc with my Office 2003.
My wife is using my old laptop - all she really uses is word and i.e. I tried to install and run Google Earth on the old klunker last night - it installed but wouldn’t run. Maybe a poor example, but illustrative, I think, that yesterday’s hardware sometimes really won’t run todays software. Sure, I could have hammered at it and probably got it running, but even if I did, it would be a pain in the ass to get it going and it would just run like shit. What’s the sense in that? AND - I’m an IT professional and I can anticipate exactly how much of a frustrating (and ultimately fruitless) pain in the ass it would be. An average Joe is rightly apprehensive about tackling something like that.
You’re computer savvy. Good for you. Most folks aren’t.