100% All-Natural Composition
No Artificial Intelligence!
Showing posts with label technical issues. Show all posts
Showing posts with label technical issues. Show all posts

Thursday, October 23, 2014

Fixing iPad and iPhone "bricked" by iOS 8.1

So the other week I upgraded my iPad (it's an iPad 2) to iOS 8.0 and since then there was some significant slowdown of apps, and Safari seemed especially effected.  Oh it worked, just not at the brisk pace that I'm used to.  Anyway, last night I finally updated to iOS 8.1

Never, never again will I do such an upgrade to my ever-trusty iPad 2.  And yes, I know that I should upgrade the iPad itself.  It's three and a half years old, after all.  I guess it's seen me through an awful lot so there's that sentimental value.  If and when I finally retire it I'm thinking of putting it in a shadowbox and hang it on my wall.  But until then I'd still like to get at least a little life out of it.

Anyway, I started the update and went to sleep and when I woke up this morning it was supposed to have been all ready to go.  Except that it was even slower than it had been before.  So, I powered-down and waited 30 seconds then turned it on again.  And for the next 30 minutes or so I was staring at the silver Apple logo in the middle of a black screen and going nowhere fast.

I was immediately terrified that my iPad had become broken or bricked or something and that I would never see it or the data I had stored on it ever again.

Some Google-ing however indicated that I was far from alone: many people using older iPads (I've seen reports of iPad 3 and perhaps the generation after that) have been affected by iOS 8.1 and many iPhones going back to iPhone 5.  You would think that there would be some kind of thorough analysis and de-bugging, and at the very least have the device inform users when the newest iOS is incompatible with their device.  Some are wondering if this is apparently Apple's way of compelling consumers to buy the latest version of the hardware.

I know that the newest iPad Air is out this week, and I'm considering getting it soon.  In the meantime I do need my iPad now to be working.

Well, it took me an a hour and a half, but I did come up with something that gets the iPad un-bricked and if there's any consistency between the device itself and iTunes (note: make sure your iTunes is updated to the latest version) this will probably work for you too if your own device is hit with a "black screen of death"...

1.  Open up iTunes on your PC or Mac (I'm using Windows Vista... yeah yeah I'm a glutton for punishment).

2.  With your device unconnected to your computer, make sure your iPad or iPhone is already powered-on.  It's okay if it's still showing the black screen and logo: we're about to fix that!

3.  Connect the iGimmick to your computer/iTunes through the cable.

4.You should see iTunes acknowledging the presence of the device.  If your computer is anything like mine you will see that it's setting up new device stuff through the USB.  THIS IS A GOOD THING!  DON'T UNCONNECT YOUR iTHINGY UNTIL IT'S FINISHED DOING THIS!  You should know when it's done when your iPhone or iPad screen comes up as usual, with all your icons and wallpaper and whatnot.  If you can maneuver around the screen with your finger like usual that should indicate that the device has been re-set and back to normal.  But just in case I would leave it still communicating with iTunes for a little while (say, 10 minutes or so).

5.  While you're waiting for that, it's a good time to start backing up your iToy... so do that.  Do it now.  Or perish in flames.  It's your choice, but not really.

6.  After the backup is done (it took mine about 15 minutes because I had so many space-hoggin' apps on it... and other stuff) it is probably good to do.  Disconnect as normal and proceed to continue enjoying your iGadget as normal.

Last night I updated over the house network via wi-fi instead of going through iTunes, and I'm wondering if that is what was part of the problem.  Maybe, maybe not.  Worth pondering.  All I know is that once it was physically hooked-up with iTunes things started going back to normal.

Now, there's one thing that I haven't done so far.  I haven't powered-down and tried to turn it back on.  Because I'm kinda leery about doing so and having to go through this crap all over again.  I may try it tomorrow if I'm brave enough (I'm trying to get some book written  this afternoon/evening so while I'm in that groove).  If it works I'll let y'all know.  Or if it works for you, feel free to leave a comment about it.

Guess I'll have to get an iPad Air 2 sooner than later.  But that's okay.  I've had my eye on getting a 128-gigabites model for awhile now anyway :-)

EDIT 5:02 p.m. EST:  I should have mentioned earlier that after applying this fix following the upgrade to iOS 8.1, that my iPad 2 is functioning MUCH faster than it had been prior.  It's now comparable to the speed it was on iOS .  Even Safari.  And the touch screen seems a tad more responsive now also.

Thursday, September 15, 2011

Pssst... Hey, iTunes Store not opening for ya?

So for the past several weeks my iTunes hasn't been up to snuff. iTunes starts up okay... but when it comes to the iTunes Store it did nothing but show a blank white page with "iTunes Store" printed in the center. And whatever has been the problem with that, it also has kept iTunes from properly updating my iPad. I'm still using Windows Vista (no jokes, please :-P)

I tried everything but nothing worked to make iTunes Store functioning on my computer. I even uninstalled and re-installed iTunes... three times! And still the iTunes Store wouldn't come up. When I ran the Diagnostics tool it gave me some crap about how iTunes Store couldn't make a secure connection.

Well, as of about an hour ago it's finally working again! It took me the better part of three days of actively addressing the issue and a whole wazooload of Google searches. Lo and behold the solution came from a YouTube user named audsmithl15, who posted it as a comment on a video demonstrating the exact same problem.

Here is what audsmithl15 came up with. I'm re-posting it here, for sake of anyone else who might be searching for the fix...

1. Go to C:\ProgramData\Apple\Installer­Cache\AppleApplicationSupport 2.0.1

2. Right click

3. UNinstall

4. Go to C:\ProgramData\Apple\Installer­Cache\AppleApplicationSupport 1.5.2

5. Right click

6. INstall

7. Restart PC

Took less than 10 minutes to apply the fix and after that, iTunes Store comes up fine!

Bigtime props to audsmithl15 on YouTube for hitting on the solution :-)

Friday, February 18, 2011

Didja know that STARCRAFT II don't run so well on multi-core systems?

Well, you do now! But be of good cheer: I'm about to tell you how to fix that.

I've had StarCraft II for awhile now, but haven't played even anywhere close to finishing the first campaign. Among other reasons, I've been frustrated by what I have been certain is too slow performance for the high-end rig I've got it installed on. And yesterday, I finally set out to find out why (or if I was even right about that).

Turns out that StarCraft II doesn't like multiple CPUs all that well. Optimally it should be running on two cores, not three or four. So Yours Truly went searching for a way to bring it down to operating on only two processors. Lo and behold: it can be done! Start up StarCraft II from the desktop, then bring up Task Manager (usually done through CTRL+ALT+Delete), go to the sc2.exe process and right-click on it and look for "Set Affinity". From here you can specify which CPUs you want to run the game on and which ones to turn off.

I tried it yesterday and the game performed significantly faster than it had before.

But, there was one hitch: every time the game is exited, doing Set Affinity through Task Manager must be done all over again. Leaving the program causes CPU affinity to revert to the default four cores (or whatever is the number of cores on your computer).

This is the kind of problem that, I can sometimes be awake for days trying to solve. I just don't like it when I've a gut feeling that a technical issue can be resolved, given enough time and thinkin' about it.

Well dear readers, a short while ago I came across a fix.

Actually, good friend Adam Smith located the substance of the solution, so credit goes to where it must :-) If you're trying to get StarCraft II - or any program that might run faster on one or two cores instead of four or five or seven - downshifted from too much processing power, then PriFinitty is the tool you need. PriFinitty (currently at version 2.47) sets affinity for whatever executable programs you need to do it for, and it keeps the affinity settings in a profile that loads automatically whenever you launch PriFinitty (which can be set to load at startup). I set StarCraft II to use CPUs 2 and 3, ignoring the rest, and it worked beautifully! Then I exited the game, and re-launched it. The affinity settings were still binding just those two cores! So... color me impressed :-)

There is just one thing that I need to say about using PriFinitty with StarCraft II: you should have PriFinitty set affinity for both "starcraft ii.exe" and "sc2.exe". But there are more than one version of sc2.exe to consider: they're all in the Versions folder of the StarCraft II main folder. And then you'll have to look in the folders in the Versions folder that say "Base..." (my install has six of 'em currently). So, I'd recommend going into all of the Base* folders, and adding each sc2.exe to your PriFinitty profile and adjusting the affinity for each. Y'know, just to be on the safe side. I don't see how doing it to any extra sc2 executables is going to do any harm.

Then make sure that PriFinitty is running in the background with your profile and launch StarCraft II and prepare to take the fight to the Zerg faster than ever!

(And a tip o' the hat to Adam Smith for pointing me toward PriFinnity :-)

Sunday, February 22, 2009

For those having tech issues playing FALLOUT 3 on a Windows machine...

Two days ago I wrote how I was currently hooked on Fallout 3, Bethesday Softworks' amazing continuation of the classic Fallout video games from the late Nineties.

Well since I wrote that, I had to take my copy of the game back to the Target store that I bought it from. Why? 'Cuz my copy of the Windows version didn't have the white sticker inside the box that had the Windows LIVE Access Key printed on it for that particular DVD. So I uninstalled Fallout 3, exchanged the original copy for one that did have the sticker with the key numeral, and installed the game fresh.

So everything was cool... except that the game "hung" shortly after the birth/character creation scene started, and would go no further.

Some reading on the Intertubes showed that a lot of people have been having this problem also.

Well, this morning I worked at it a bit, and I found a solution. So I thought it'd be a good thing to share it with others who are also going through this...

If you are playing Fallout 3 on Windows Vista or XP, uninstall the game. Make sure that the Bethesda Softworks folder that's within your Program Files folder is deleted also.

Now here's the messy part that requires a bit of daring: use Regedit (you can run it from the Start button) and do a search in your Windows registry for all entries containing "Bethesda" or "Fallout3". This is what I figured had snagged me: my computer was having an "identity crisis" as to which copy of Fallout 3 it was supposed to be running. So scour your registry and carefully delete anything that refers to Bethesda Softworks or Fallout 3.

When that is done, close out Regedit. Then reboot Windows.

You should now have a fresh, pristine machine on which to re-install Fallout 3, that so far as it's concerned there'll be no evidence that the previous install ever happened. Since going through this procedure I haven't had any further problems with Fallout 3: it's running perfectly, and I also ran the update to version 1.1.0.35, again without any trouble.

Hope this helps some folks out. Now go gird up and get ready to take the Capital Wasteland by storm :-)

Saturday, February 14, 2009

"We're fine. We're all here, fine. How are you?"

Something screwy is amiss with this blog on the technical backside of things. It looked fine yesterday (so far as I can tell) but in both Firefox and Internet Explorer, stuff is missing.

If this place looks more whacked than usual, it's prolly just me monkeying around behind the scenes trying to get it all fixed :-)

Sunday, February 08, 2009

Johnny Robertson is paying good money for this...?

Very strange night of cult leader Johnny Robertson's usual broadcast on WGSR this evening. The first hour was a recording of this morning's "service" at Martinsville Church of Christ. And that in itself was notable because to the best of my knowledge, this is the first time that I've ever seen Johnny Robertson praying. Except that his "prayer" was straight out of Luke chapter 18, in that it was practically the same as that of the Pharisee in the temple who prays "God, I thank you that I am not like other men—robbers, evildoers, adulterers..." etc. Yes folks, that apparently is the substance of "prayer" among the cult (which again, is not the real Churches of Christ at all).

Then Robertson went on a vicious rant, boasting about how his "church is the most authoritarian!" among other things, and then devoted much of the rest of the "sermon" to evolution and Charles Darwin, mostly in order to attack that same museum in Danville that he has some kind of beef with.

And then the recorded service ended and the program went to this...

That's it. For the next half-hour, it was a DVD menu that went out on live television. People who happened to tune in to WGSR between 9:30 and 10 got to see waves rolling on a beach as earthy "New Age" music played in the background of the DVD main menu, and nothing else.

So unless I'm mistaken, Johnny Robertson paid between $500 and $1000 to broadcast a DVD menu on television tonight.

Parse this as you will.

Thursday, September 06, 2007

Screen burn-in on an LCD HDTV? Yup

We bought a 37-inch LCD high-definition television set last November. It's specifically an LCD screen because when I was doing research before we went out to look at sets the widespread consensus was that LCD screens don't "burn-in" like plasma screens do.

Well, guess what?

I can't show what this looks like because it doesn't show up well in photos, but there are two very fine vertical lines running down the entire height of the screen: one line running equidistant from each of the left and right sides of the image. They are exactly where the borders of the "pillars" are when you watch a standard (not high-def) image without "stretching" it to fill the screen. Since most of the interesting programming around here is standard definition and I don't like distorted images, the tendency is to watch television "pillarboxed". I guess that's how the lines got in there: with the borders always being "on".

It's supposed to not be a permanent condition of LCD screens. And technically it's not "burn-in" at all, in the sense that plasma screens can get it. It's properly called "image retention"... but that doesn't keep it from being any less a nuisance. Right now I've got the TV on with the image stretched to fill the screen, so that the pixels making up those lines will get "exercised" and start working right again. I'm hoping this will work. If not, looks like that service plan is going to turn out to have been a great investment after all.

In the meantime, if anyone's ever had any experience with this kind of an issue, I'd sure appreciate some advice. I like to try to fix things "in-house" as much as possible, without having to lug something as big as an HDTV back to the store :-)