Showing posts with label troubleshooting. Show all posts
Showing posts with label troubleshooting. Show all posts

Wednesday, January 02, 2008

The Joy Was Short Lived

The joy was short lived. I'm still struggling with Vista crashes related to the ATI video drivers on this iMac. Sigh. I hate Windows.

Monday, December 31, 2007

Fixing yet another problem in Vista on the iMac

I know I said I wasn't wasting any more of my precious time fixing crap in Vista... but about once a day, Vista blue screens on me while playing my game, requiring a complete reboot. It's annoying.

Googling led me to the problem and the solution.

Note: This applies to the 2.4GHz 20" iMac with the 256MB video card, and Vista 32-bit.

Vista incorrectly detects the installed video card as the ATI Radeon Mobility HD 2600 XT. It should be the ATI Radeon HD 2600 Pro.

Fixing the problem involves downloading the correct driver from ATI's web site and manually forcing Vista to use it (despite it's freak-out warnings that it can't verify it's the correct driver for your hardware). Relax, Vista. It's the correct driver.

Problem solved. No more crashes.

I found full instructions in an Apple support forum discussion on the topic. Be sure to get the latest ATI drivers. (The one I used wasn't the same as the one mentioned in that conversation - the current version as of this writing is 7.12. The process described, however, worked perfectly substituting the latest drivers).

Another reason why Vista sucks vs Leopard

I've come across another reason why I'm the happiest clam alive to be using Macs with Leopard instead of PC's with Vista (or any other Windows operating system).

A few weeks ago, I upgraded my 20" iMac to 4GB of RAM (see my "taste the kool-aid" joy).

My iMac dual-boots Vista so that I can play some games that are not compatible with OS X (the only thing left in my life that requires me to touch a Windows box).

Today, I just happened to notice when I booted into Windows to play my game that Vista is only seeing 3GB of my 4GB of RAM. Wha???? I know that OS X Leopard is seeing all of my RAM and splashing around blissfully in it. What's up with Vista?

Googling revealed much discussion - and confusion - on the topic. Like everything else, it seems that Microsoft's claims of Vista's RAM capabilities come with small print disclaimers attached.

Microsoft's official claim is that 32-bit versions of Windows Vista Home Basic, Home Premium, Business, Enterprise, and Ultimate support 4GB of RAM. I've got the 32-bit version of Vista Business. Why does my System panel say: Memory (RAM): 3054 MB

3054? What kind of number IS that, even? My Computer shows it abbreviated as 2.98 GB. I know there's some integrated video memory going on here, but come on! The ATI Mobility Radeon HD 2600 XT video card in this iMac is 256MB. Where's the rest of my 4th gig of RAM?

Shared video RAM aside, where has the rest gone? I found a snippet on the topic at Vista Clues:

...a high performance x86-based computer may allocate 512 MB to more than 1 GB for the PCI memory address range before any RAM (physical user memory) addresses are allocated.

I found all sorts of things about a 3GB switch in Windows to allow applications to access more than the default 2GB of RAM, yada yada yada.

As I read through tweaking guides, I stopped and thought to myself, What am I doing? I don't want to have to fiddle with my machines to get them to work properly with the hardware installed in them! THAT'S WHY I SWITCHED TO MAC!!!

A big ol' Up Yours to Windows. I'm not going to try and figure out how to get you to see my full 4GB of RAM. I'm not wasting my time with you. You only exist in my life for entertainment purposes anyway, and I'll live with the 3GB of RAM that your dumb OS is able to see. My time is too valuable to spend trying to make you work the way you SHOULD work out of the box!

Wednesday, October 31, 2007

Problems Using PC-Formatted Drive with Leopard & Time Machine

Whew! I was pretty excited tonight when Leopard was in my mailbox. Finally! (It was supposed to be here yesterday, grumble grumble grumble). I'll save my Leopard thoughts for later - just wanted to document my first Leopard problem (which, SURPRISE, was indirectly caused by my old Windows PC).

I have a 750GB Western Digital MyBook. It's pretty sweet. I was using it as my backup drive for my Windows PC, and it was formatted FAT32. When I trashed my PC and got an iMac a couple weeks ago, I checked WD's web site and sure enough, they had a Mac version of their backup software. Sweet!

Then came Leopard and Time Machine... automatic backups that can be accessed in a completely granular fashion. Imagine! Buh-bye, WD Backup. Hello, Time Machine!

I plugged in my WD MyBook after installing Leopard, and like promised, Leopard asked if I wanted to use that drive to backup with Time Machine. Absolutely! Time Machine said it needed to be reformatted to the Mac format. Sure, no problem.

Except that the format failed.

Disk erase failed with the error: File system formatter failed.

Yikes!

I tried using Disk Utility to no avail. It would format fine as FAT32, but not as any Mac format.

Already-too-long-story-short:

Gizmodo saved me!

Thankfully, the fix is easy.

• Go to the Partition tab. Create two partitions. Under Options, select GUID Partition Table (what you would use to make a Mac OS boot disk) and click OK then Apply.

• Once your partitions are in place, do it again, reverting back to just one partition, but still keeping the GUID Partition Table option. Click OK and Apply again, and at this point you should be cool.

• To be safe, you can then go to Erase and set formatting for Mac OS Extended (Journaled), then format it once and for all. But when you get there, you will probably see that your volume is already formatted in the right way.

Gizmodo reports that some users were able to get this solution working only creating one partition, and that the key seems to be using the GUID Partition Table option.

Whatever the case, these steps worked for me, and Time Machine is now happily chugging way with its first full backup of my new iMac - now dressed in Leopard skin :)

Monday, September 10, 2007

When Adobe CS3 crashes with that "license has stopped working" error

Note to self:

When Adobe CS3 crashes with that "licensing subsystem has failed catastrophically" or "licensing has stopped working for this program" error, check the Services in Windows:

Solution 2: Restart and enable the FLEXnet Licensing Service. (Windows Only)

1. Open the Administrative Tools control panel.
2. Double click "Services".
3. Scroll down to FLEXnet Licensing Service on the list of service and double-click the service to open its properties.
4. Change the Startup type to Manual.
5. Click the Start button to start the service.
6. Restart your Creative Suite 3 application.

(This isn't the first time I've run into this problem. Oy!)

Sunday, September 09, 2007

AMD's Non-Existent Warranty for OEM CPU's

Remember that great processor I bought for my computer? The one I was so lucky to find, because they don't make them anymore and it's the fastest available CPU that my old motherboard will support?

It's dead. 3 weeks past the warranty return date.

You see, normally you get a 3 year warranty on CPU's. However, that's only for retail boxed CPU's. If you buy a component that is not packaged for retail sale - an OEM component (typically sold to companies that make computers - original equipment manufacturers) - at least by AMD's terms, your warranty is limited to whatever warranty your place of sale provides. AMD provides NO warranty on OEM CPU's, at least not to consumers.

My place of sale (newegg.com) provides a 30 day warranty on OEM CPU's.

I have never liked newegg to begin with. I prefer zipzoomfly.com, but ZZF didn't have the CPU I needed in stock back on July 15, 2007 when I was ordering it.

I woke up this morning to a black screen on my monitor. I noticed that my keyboard LED's were off (the backlighting to the keys on my keyboard). Weird, but the system still had power. It was on. The monitor was getting no signal. Alrighty, whatever. Reboot.

The talking lady inside my computer came on and, in a very concerned voice, repeated incessantly, "System reports CPU failure! System reports CPU failure!"

Fuck.

Except I didn't really say "fuck" at that time. I sighed, shut the machine down, and started taking it apart, knowing I still had my old CPU tucked safely away in its protective case. (Good thing I didn't sell it on ebay last week when I was all about getting rid of my old computer parts).
I took the "new" CPU out (it was HOT as hell) and put my old CPU back in. Closed her up, powered on, booted up, and here I am.

Then I went to newegg.com to print out my invoice and get the date of purchase. I was shocked that it was 7 weeks ago, really. It felt more like 3. I was sure I'd be within the 30 day time frame. Not so.

I've done RMA's (return merchandise authorizations) on computer parts before, and have never really had any trouble. Western Digital has a good RMA service, as does Maxtor (though I've used Maxtor's WAY more than anybody should - I mean, it's great that they make it easy to return their failed components, but their components shouldn't fail so friggin much). Anyway, after a mildly frustrating experience discovering that AMD's RMA web site requires Internet Explorer (no, they don't mention it - it just doesn't work in Firefox), I entered all of my CPU information only to find that my CPU was not in their database. Then, this notation:

The processor serial number you have entered has not been found in our records and the processor cannot be registered online.

If this is an AMD retail packaged Processor in a Box and you have proof of purchase, please contact your regional Technical Service Center to request an RMA.

If this processor is not an AMD retail packaged Processor in a Box you will need to contact the company from which you purchased your processor or computer system to obtain any warranty replacement to which you may be entitled.

Not found in AMD database.


Oh my. This is not a retail box processor. That means I'm limited to newegg.com's return policy.

That's 30 days.

It has been more than 30 days.

(Here's where the "Fuck" came in. Sorry for the premature slinging of profanities).

It's just my luck, really. $95.99 down the drain. Gone. Vanished. Up in smoke. All for 7 weeks of fast computer processing speeds. That's almost $14/week.

It was not worth it.

You're probably asking, "Well, why didn't you buy the retail boxed version, then?"

2 reasons:

1. There wasn't one available (I do prefer retail boxed components whenever possible).

2. Most manufacturers still support returns of OEM equipment as long as you have proof of purchase, which I have. The terms are usually shorter. In fact, when I worked at the computer shop, AMD OEM CPU's had a 1 year warranty, while boxed chips had the 3 year warranty.

At any rate, I'd have never guessed a 30 day warranty on a CPU. Never. Actually, I've never seen a manufacturer NOT support their OEM products! AMD offers NO warranty on an OEM CPU! That's just ridiculous. What do PC manufacturers do when they get dead parts (which DOES happen)? Maybe this is just their policy with private consumers.

I don't know, but my opinion of AMD has just dropped HUGE.

Anyone want a dead AMD 64 X2 4200+ dual core CPU? They make great keychains.

Thursday, June 28, 2007

That didn't do it

Well, the Vista net connection fix I posted in my last message didn't solve my problem. I still have occasionally awful lag on the web, despite tests showing me getting full bandwidth.

I'm currently testing a new theory: that my old Vonage phone box is slowing me down.

I have one of the first Motorola Vonage phone boxes - before Vonage came packaged inside Linksys cable modems. Currently, the Vonage box lives outside of my LAN. My network goes - internal LAN --> wireless router --> cable modem --> Vonage box.

Right now, I've disconnected the Vonage box, and I'm just running with the cable modem and the router. I'm hard-wired via RJ45 jack on this particular PC (the one with the problems), so as to rule out all wireless issues.

The good news is, even if the problem is with my phone box, a new Linksys Vonage phone adapter is only $50. I was fearing much worse.

Honestly, I hope this is the problem so I can get back to carefree surfing. I pay an arm and a leg for my internet service - I'd like to use it without suffering the urge to punch the screen or throw my tower out the window!