Installshield Woes

**LeftEyeNine** · 09-18-2010, 18:21

How I got this for endless times:

When I had that little, lovely, problem-free and obedient Windows 7 Ultimate x86, all I had to do was downloading the demo and installing it in order to experience what Pro Evolution Soccer 2011 feels like this season.

But, thanks to the technological developments I've been forced through, now that I have to use a Windows 7 Ultimate x64 in order to benefit all of the 6GB RAMs I've recently bought, I had to be tested how far it can go before I berserk-rage and burn this city to the ground.

The same demo file that I could succesfully install no longer wanted to do it giving the error message above. So I re-downloaded the whole file (1.3 GB something, actually I'm downloading the same file from a different mirror as I speak) from the same mirror, the official homepage of PES 2011, assuming it would terminate the problem in an instant. Of course, it did not.

Several advices to overcome "the 1152" were:

Having huge amouns of spaces where the file or the temp location is (~100 or so in C)
Changing the temp location from e.g. C to D etc. (check)
Re-downloading the installer (check)
Running it as administrator (check)

all of which were to no avail.

I've closed down every other program as well as MSE, deleted what I could find in the Temp folder, made a registry cleaning with TuneUp and rebooted and gave it another shot eventually. No, the stubborn

is there to stay.

Anything to say about it or should I admit that some x64 OS is bigger than me ?

**Tellos Athenaios** · 09-18-2010, 19:34

You know that screenshot would be useful if it weren't for the fact... drum kettle roll...

Spoiler Alert, click show to read:

Have you tried cleaning up the temp files, using the Windows Disk Cleanup utility from the Control Panel? I find I have a few GB worth of old temp files after half a year of casual use...

**Tellos Athenaios** · 09-18-2010, 19:39

And useful: http://www.legroom.net/software/uniextract in case you need to extract files from the installer.

**Beskar** · 09-18-2010, 19:41

Originally Posted by Tellos Athenaios

And useful: http://www.legroom.net/software/uniextract in case you need to extract files from the installer.

Why didn't you tell me about that in the other thread? Apparently it is specially made for extracting problem files too. :O

**LeftEyeNine** · 09-18-2010, 19:48

Originally Posted by Tellos Athenaios

You know that screenshot would be useful if it weren't for the fact... drum kettle roll...

Spoiler Alert, click show to read:

Have you tried cleaning up the temp files, using the Windows Disk Cleanup utility from the Control Panel? I find I have a few GB worth of old temp files after half a year of casual use...

Error codes are standardized now, aren't they ? :)

I'll check the tool.

**LeftEyeNine** · 09-18-2010, 20:10

Oh deep bowels of hell, whose children did I murder such that I'm suffering through this ?

**Tellos Athenaios** · 09-18-2010, 20:48

Originally Posted by Beskar

Why didn't you tell me about that in the other thread? Apparently it is specially made for extracting problem files too. :O

You pick:

(a) LeftEye is a luckier Turk than you are.
(b) I didn't know about that utility until that post.

**Beskar** · 09-18-2010, 22:20

Originally Posted by Tellos Athenaios

(a) LeftEye is a luckier Turk than you are.

Except for his missing eye and finger, I think he is. He still manages to carry off his looks, very well.

@LeftEyeNine
Have tried re-downloading the demo? It might have been corrupted or similar.

**LeftEyeNine** · 09-19-2010, 00:05

Oh, that's almost as handsome as old me. I take it as a compliment.

As for the series of problems I've been swamped for almost a period of seamless 2 days , I've been assured by some other InstallShield installation issue that my whole OS is problemous. I'll be renewing it.

**Whacker** · 09-19-2010, 00:19

My guess is that you've experienced some data/file corruption due to your RAM not being acclimated yet, as discussed in the other threads. It may not be bad, but it could also mean your Windoze installation is partially hosed and unstable from bad read/writes to memory. My advice is burn-in your RAM, then reinstall. You are using your system while it's still unstable and I am 99.999% positive this is a direct result of that.

Edit - I should mention that I experienced the exact same thing when I ran into this issue with my first system I had to burn-in. My entire windows installation became corrupted, and I had to reinstall after burning in the RAM. After that it was fine.

**LeftEyeNine** · 09-19-2010, 00:21

I got a total of 6 BSODs since the OS installation which is a record for at least the time I could remember being on a PC.

As you've suggested, I'm leaving the computer for more MemTest tonight and tomorrow will be making a fresh OS injection.

Thanks for the help so far.

**LeftEyeNine** · 09-19-2010, 00:36

Pass #0 %20 completed
Test #5
34304 errors already.

By the way, I've configured the RAM according to the exact manual values suggested by the moderator of the official forum of GSkill.

Jeebus.

**Beskar** · 09-19-2010, 01:02

It might be broken. I remember having a faulty stick.

However, the error I kept getting what "Your graphics device failed and had to be restarted."

The weird thing is, from that ever, you would assume it was the graphcs card was broken, but it wasn't, it was the ram, as I would be playing a game, the ram crashed/errored, causing the game to error, which resulted in the graphics card crashing.

**Whacker** · 09-19-2010, 03:08

IMO having a bad stick of ram is going to be one of the last things to be the culprit. RAM manufs. do a series of tests in factory before releasing anything, that's how they come up with the EPP profiles which the mobos can read for "factory overclocking". In my first system, it was just getting the RAM to play nice with the mobo. It was an Nforce4 (I think?) mobo, which historically didn't get along well with some specific RAM sticks by a few of the major manufacturers, because of the components the RAM manuf. used for those specific SKUs. With some finagling it worked.

My second and current system turned out to be more insidious. Long story short, eVGA didn't do a good job of putting a cooling solution on the MOSFETs near the cpu socket. Several were flat out not cooled, the ones that were cooled had bent heatsinks with horrible thermal pads underneath which didn't achieve full contact. I had to manually pull both of these off, straighten them (which was gut-wrenching stressful), and then reattach with a good brand thermal paste. RAM problems went away after that. eVGA caught some real flak from this problem too.

So, LEN, if you still have problems after a week, you'll want to start investigating your mobo and determine if you have cooling issues there. It will deal with either the cooling the northbridge, MOSFETs, airflow over the RAM sticks, or a combination of all of the above.