When I launch the Wizardry 8 desktop icon the mouse cursor shows activity for a few seconds and then nothing else happens. I have tried running as admin but nothing changes. The process Wiz8 *32 appears in the process list for some seconds and then disappears. No feedback or anything that gives a clue.

I have tried wiz8_fix.exe as well, but it does not seem to make it work either.

Any help will be very welcome. My system is Win7 - 64


Thanks!

I've never had problems running wiz8 at win7 x64 (no compability modes or whatever). Did you install your game into /Program Files folder? That's a common problem so try something else (like /games/wizardy 8).
You might also look for no-cd.exe (remember to make backup of your original .exe). One is here (almost at the bottom, just above red text): http://www.zimlab.com/wizardry/ Yeah, I know that gog version is already no-cd compatibile and whatever but you can try.

Hi Hemaka,

Yes, I installed the game where the installer sugested, in "C:\GoG Games\Wizardry 8".

I have tried the nocd exe and the result is the same. I also have tried the game in a pretty old laptop with Windows Vista and it works well.

I have read somewhere that it might be a conflict with the language package, as I don't have the english package installed in win7. I am currently downloading it through the Windows update service. I'll post if that works.


Thank you for the suggestions.

I have installed and activated as default the english language package and the result is the same. I have tried all (or almost) combinations in compatibility mode, and nothing changes. This is Win7 professional 64bits.

*sigh*

Adding some info in case it may help. This is an instance of the event record in Windows. In the EventData node, the bold font is the same in all instances of this error, the other data varies from one to the next:


- <Event xmlns="...">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-07-10T13:49:36.000000000Z" />
<EventRecordID>12418</EventRecordID>
<Channel>Application</Channel>
<Computer>JoseIgnacio-PC</Computer>
<Security />
</System>
- <EventData>
<Data>Wiz8.exe</Data>
<Data>0.0.0.0</Data>
<Data>3c26eee6</Data>
<Data>Wiz8.exe</Data>
<Data>0.0.0.0</Data>
<Data>3c26eee6</Data>
<Data>c0000005</Data>
<Data>001ff467</Data>
<Data>1018</Data>
<Data>01ce7d744f4928e1</Data>
<Data>C:\GOG Games\Wizardry 8\Wiz8.exe</Data>
<Data>C:\GOG Games\Wizardry 8\Wiz8.exe</Data>
<Data>8e2b26a5-e967-11e2-bff3-902b34bd9236</Data>
</EventData>
</Event>

I also have tried almost everything in this support thread:

www.gog.com/support/wizardry_8/ibread_first_pc_windowsb_common_troubleshooting_stepsi


I am currently downloading the June 2010 DirectX redist to try that too (as per the support thread above). This is the only thing left to try.

No results. I have posted the issue to support, hope they can help.

I had the same issue. Tried the same things. Support was not able to help and offered a refund. I'd rather play the game so I'm hoping that we are not just an edge case and GOG fixes this issue.

Hi Nehaektas,

What machine type eg. Asus sonicmaster & which antivirus software are you running on it?

have you tried turning the antivirus off?

I don't use nocd for several reasons but did you also install a cd version of the game on that system... I have the old box set and had to uninstall it before using the Gog game.
p.s. IME saves carry over without issue.

It’s almost always an access denied issue but there are several things that can cause it.

From Dxdiag:

System Manufacturer: Gigabyte Technology Co., Ltd.
Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130318-1533)
Processor: Intel(R) Pentium(R) CPU G860 @ 3.00GHz (2 CPUs), ~3.0GHz
Card name: NVIDIA GeForce GT 630

I also have an external sound interface (M-Audio) as sound device, so I have tried disabling the sound from 3DSetup, just to check if that weas causing any trouble, but nope.

antivirus: I am using the default windows security and windows Defender as antivirus. I have just tried disabling real time protection and still get the same.

About the box version, I have not got it.


Thanks for helping.

I have got to the same point. Refund offered.

FInally I have tried Win XP professional in Virtual Box. It works (after some tweaking with the graphics), but there are usability issues with resolution and mouse look control that make playing the game an unpleasant experience. I will post if I get somewhere with this...

Maybe a long shot, but one thing comes to mind:

Read over this thread a bit:
http://www.gog.com/forum/wizardry_series/wizardry_8_resolution

Backup any relevant files first. From there, what I'd suggest is to do as one of the posters in that thread did and remove the nGlide/3Dfx stuff, then run 3dsetup. Try to select DirectX7 and a reasonable resolution. See how/if that works.

Manually editing the 3DVideo.CFG to set DirectX7, resolution, and bit depth would also be an option. Another user in that thread posted some details on that.

I don't have any experience with the nGlide wrapper, but I have a disc version of wizardry 8 that works extremely well with Win7 64bit using DX7 at 1920x1080 resolution (my display's native resolution).

I also have an external USB sound card. The ASUS Xonar. I bet it is the common factor. I tried turning off sound as well, no luck.

Hmm. Could you open up your 3DVideo.CFG from the Wizardry 8 folder/directory and copy/paste what it says here? That may shed some light on the matter.

Thanks for pointing the thread, very informative. I have tried removing the nglide files and also editing 3DVideo.CFG, with many combinations (Glide2x, DirectX7, DirectX6, OpenGL and MMX, each with 640x480, 800x600 up to my native display 1680x1050, depths 16 and 32). Directly editing the file is certainly a quick way to test all the posibilities. Unfortunately the game crashes just the same. I have even tried leaving the file empty and with bad data.

All this testing resulting in the exact same crash, seems to point an issue in the execution before video/audio setup, but I am only guessing.


Cheers.