Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: mittsy on September 22, 2016, 10:43:01 PM
-
Here's the issue.
I installed AH3 on my Windows 7 32 bit. I kept getting an NSIS error.
Finally I uninstalled Windows 7 and installed Window7 64 bit.
Installed AH3 - Same download as I tried to run previosly (I saved on my portable HD) installed and ran no problem. BUT the drivers for my SaitekX55 wont run on 64 bit - I guess there are problems with the 64 bit drivers.
Reinstalled Windows 7 32 bit - my stick works fine now, but I get the NSIS error (installer integrity check failed) again and cant install AH3.
I do not have an antivirus installed yet.
Fresh copy of windows7 32 bit, no updates - only installed Nvidia video drivers and saitek stick drivers, nothing else yet.
-
How much physical RAM does the computer have?
Did you use the Chrome browser to download the file?
-
AMD X64 duo core 2.4
4 gb ram
Nvidia GT 730 video
Downloaded with firefox
I also tries one downloaded with Ie.
Installed and Ran on 64bit but won't install on 32 bit. (Windows7)
Some of the Beta versions of AH3 had the same NSIS error some didnt
-
Is it the drivers for the stick or the software won't run in 64 bit?
If it is the software, I highly recommend Pinnacle Profiler software.
You can program your stick through it.
If it is stick not being recognized...have you tried drivers from other OS versions which are 64 bit? Win 8 or Win 10?
-
Need to see a DXDIAG output. What may be happening is the installer is running out of physical RAM when running in 32 bit mode. A DXDIAG output might show something.
-
Dobs...the driver for the stick will not work at all in 64bit. Stick is dead. Drivers cover Vista/7/8 program/profiler works fine, just Windows will not recognize the stick
Skuzzy, I'll run DXdiag when I get home and post it.
It gets to about 90% on the verifying installer pop-up, after I click the install, that's when the NSIS error comes up
-
If it is resource related, we can work around the installer issue.
I am just concerned the computer may not have the resources to run the game once it is installed.
-
Most of the Beta versions ran fine. Some of the patch versions I got the NSIS error, would have to wait for the next patch version and it would be fine
Doesn't get to the point of being Installed, it gets the error before the install is done. NSIS error says the installer is corrupt.
If I could run most of the Betas, and keep a frame rate of 20+, I don't think it's running out of resources, but I am not an expert. I did have the vid card overclocked but moderately.
Does the 32 bit use more resources than 64 bit?
-
Could a firewall do this?
-
Could a firewall do this?
It might be possible, but I'd rather blame the antivirus, especially if the name starts and ends with an "n".
-
Anti-xxxx is always a possibility. Those programs mess up a computer more than any application I have ever seen.
-
No antivirus installed yet and firewall is turned off
-
------------------
System Information
------------------
Time of this report: 9/23/2016, 20:48:39
Machine name: PATS_OLD
Operating System: Windows 7 Professional 32-bit (6.1, Build 7600) (7600.win7_rtm.090713-1255)
Language: English (Regional Setting: English)
System Manufacturer: Gateway
System Model: T5234
BIOS: )Phoenix - Award WorkstationBIOS v6.00PG
Processor: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ (2 CPUs), ~2.2GHz
Memory: 4096MB RAM
Available OS Memory: 3454MB RAM
Page File: 1277MB used, 5630MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7600.16385 32bit Unicode
------------
DxDiag Notes
------------
Display Tab 1: The file nvd3dum.dll,nvwgf2um.dll,nvwgf2um.dll is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo'd driver from the hardware manufacturer.
Sound Tab 1: No sound card was found. If one is expected, you should install a sound driver provided by the hardware manufacturer.
Input Tab: No problems found.
--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)
---------------
Display Devices
---------------
Card name: NVIDIA GeForce GT 730
Manufacturer: NVIDIA
Chip type: GeForce GT 730
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_1287&SUBSYS_37333842&REV_A1
Display Memory: 3465 MB
Dedicated Memory: 1994 MB
Shared Memory: 1471 MB
Current Mode: 1920 x 1200 (32 bit) (59Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: Philips 240BW
Monitor Id: PHL0872
Native Mode: 1920 x 1200(p) (59.950Hz)
Output Type: DVI
Driver Name: nvd3dum.dll,nvwgf2um.dll,nvwgf2um.dll
Driver File Version: 10.18.0013.5921 (English)
Driver Version: 10.18.13.5921
DDI Version: 10.1
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 12/22/2015 01:33:08, 12770944 bytes
WHQL Logo'd: No
WHQL Date Stamp: None
Device Identifier: {D7B71E3E-51C7-11CF-D34C-3E171CC2C735}
Vendor ID: 0x10DE
Device ID: 0x1287
SubSys ID: 0x37333842
Revision ID: 0x00A1
Driver Strong Name: oem8.inf:NVIDIA_Devices.NTx86.6.1:Section024:10.18.13.5921:pci\ven_10de&dev_1287
Rank Of Driver: 00E62001
Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C
-
Here is what may be happening. In a 32 bit OS, all memory addresses have to fit into the first 4GB of memory space. The 2GB your video card has for its dedicated RAM, has to map into that 4GB space and when it does, it leaves only 2GB of space for the OS and any other applications to run.
The installer has to load the entire file into RAM, which is about 1.3GB.
The reason it may work sometimes and not others is due to when the installer is running versus when that 2GB of video RAM maps into the 4GB address space. It does not always have to be there. Only when things need to be updated on the screen. And then, it may only need part of the memory.
If you are using the Aero desktop, shut it down as it uses a lot more video RAM and requires much more video memory to be swapped in when the updates happen. You really need to make sure you get your background processes down to 35, or so.
-
You are aware that your Windows 7 license allows you to install the 64 bit version as well, aren't you? That would solve the memory issue.
However, if you take that route it means you'd have to do a fresh install, having to reinstall everything from scratch. Not a bad idea at all if you have been using the computer for several years.
-
You are aware that your Windows 7 license allows you to install the 64 bit version as well, aren't you? That would solve the memory issue.
However, if you take that route it means you'd have to do a fresh install, having to reinstall everything from scratch. Not a bad idea at all if you have been using the computer for several years.
He has an issue in 64 with his stick.....
"Dobs...the driver for the stick will not work at all in 64bit. Stick is dead. Drivers cover Vista/7/8 program/profiler works fine, just Windows will not recognize the stick
Skuzzy, I'll run DXdiag when I get home and post it.
It gets to about 90% on the verifying installer pop-up, after I click the install, that's when the NSIS error comes up"
-
Oh, yes, I read about it yesterday but didn't re-read it now and forgot about that. Thanks Fugi.
-
You really need to make sure you get your background processes down to 35, or so.
http://www.razerzone.com/cortex/boost (http://www.razerzone.com/cortex/boost)
-
I formatted the HDD and did a clean install of win7 64 bit. FOund someone online who had an older saitek signed driver, and my stick works. Bad news is, I am getting the NSIS error now on 64 bit win 7.
F@@K!!!!!
-
I formatted the HDD and did a clean install of win7 64 bit. FOund someone online who had an older saitek signed driver, and my stick works. Bad news is, I am getting the NSIS error now on 64 bit win 7.
F@@K!!!!!
Did you install the 64 bit motherboard drivers or are you using the generic Windows ones?
-
The Windows mb drivers
-
That might very well be the culprit. The drivers you get during the Windows installation are for you being able to get the "real" drivers.
It's not an easy task to find the Win7 drivers, though. There's a lot of driver download sites, but I don't trust them. Same goes for automatic driver installing programs. Getting them from the motherboard manufacturer would be the best alternative but I couldn't find any site based on what your DxDiag told about the computer. The closest I could find was http://panam.gateway.com/us/en/emac/product/default.aspx?modelId=1628 (http://panam.gateway.com/us/en/emac/product/default.aspx?modelId=1628) but the site looks abandoned, most of the links didn't work.
The safest way would be to look for the manufacturer data in Device Manager and opening the Properties for each and every System device, not to mention those with an exclamation mark. Under the Details tab/Property drop down menu find Hardware Ids, copy the PCI/VEN value and google for it. You should soon find some information about the manufacturer and model of the devices. Then "just" find the right site to download and install the drivers.
An educated guess is that the chipset is made by nvidia so once you find the model you should get a whole bunch of system devices covered by a single installation.
Hope this helps, it's hard to give a 101 for obsolete hardware with that poor manufacturer support.
-
It's a Gateway, that should be easy to find drivers for.
-
It's a Gateway, that should be easy to find drivers for.
Yes, that's what I thought, too. A search for "Gateway T5234" gave no results I'd trust. "Gateway T5234 support" gives http://www.gateway.com/gw/en/US/content/drivers-downloads (http://www.gateway.com/gw/en/US/content/drivers-downloads) but T5234 gives no results there. Maybe with the SNID or Serial number, who knows?
Mittsy, give that last link a try if you can find either of those two. Maybe on a sticker?
-
Well, it is probably just a 5200 series, although you would want to be sure.
-
Chalenge, did you take a look at that link? The only T-models there are notebooks with two digits only in their ID.
-
Already been to that website, doesnt have anything related to my machine. Its an emachines T5234. The only 64bit specific drivers from them are for the soundcard.
I cant understand why it ran before on 64 bit and not now.
Maybe it needs a 12guage #7shot repair.
-
Already been to that website, doesnt have anything related to my machine. Its an emachines T5234. The only 64bit specific drivers from them are for the soundcard.
I cant understand why it ran before on 64 bit and not now.
That's because Windows and the programs you're using have evolved but the Windows driver pack is still in the caveman stage.
Since Acer/eMachines/Gateway doesn't want to help, you'll have to find the drivers the hard way. Here's a short illustrated explanation (http://www.pcworld.com/article/2089404/how-to-easily-find-drivers-for-unknown-devices-in-windows.html) about how it's done, and as I already said one single download can update a bunch of device drivers. Start with the System devices trying to find the "master" device something like "nvidia chipset". If you have "unknown devices" in your Device Manager, updating the system may change the status of those as well. "Universal" system devices should be the first in the update list, after getting them sorted move to network and audio.
It might also help to eyeball inside your case to see if there's any identifiable model markings on the motherboard and do a search by that. For an earlier post in this thread I searched for T5234 which led me to some review telling the mobo would be made by ECS, searching with that model name I got to the ECS support site but they didn't know about that exact model. Release your inner Sherlock!
-
Downloaded the latest patch version Of AH3 and it works no problem.
Next time it's getting a size 10 boot and I'll buy a new machine!
Still no idea what was wrong, as the same download worked previously.
Thanks for all the ideas and help.
See you in the sky...as I am going down in flames! Lol
FBMittsy