[pinkkillersheep]

ok, so i was recently going through my old games and came across king's quest VII. obviously i had to play it. the problem is when i go to play it, i get a little window saying 'An priviledged instruction was executed at address (insert numbers here)'. is there anything i can do about this? thanks for your help,
~PKS

[fov]

Welcome to the forum! Since this is a tech problem, I moved it into the hints / tech forum for you.

First of all - what operating system are you using? If it's XP, have you tried putting the game in compatibility mode?

Is this the DOS version of KQ7, or the Windows version?

Please also tell us what you've done up until this point. Have you installed the game but are unable to launch it? Or do you get this message when you try to install? What did you do just before the message appeared?

emily

[Captain Blondebeard]

Originally Posted by pinkkillersheep

ok, so i was recently going through my old games and came across king's quest VII. obviously i had to play it. the problem is when i go to play it, i get a little window saying 'An priviledged instruction was executed at address (insert numbers here)'. is there anything i can do about this? thanks for your help,
~PKS

I have windows XP and when i recently installed Torrins Passage I got a similiar message. Both of these games were Sierra products and came out around the same time. I had to run the game in Windows 95 compatibilty. Right click on the launch icon and click on properties, compatibility and choose windows 95. You may have to lower the graphic setting in the same box.

[morriam]

I folowed your tips. Now it says that "DLL is not initialised" and then "the instruction at 00000000 referenced memory at 00000000 cannot be read from". It says this when I try to start the game up. I also have XP. Any tips, idea's? You'd do me a huge favor!!!!

[fov]

Did you also set the game to compatibility mode before starting it?

-emily

[morriam]

I don't know. What is it and how do I do it?

[RLacey]

Originally Posted by morriam

I don't know. What is it and how do I do it?

It's a system that can help you to run a lot of old Windows games. Here's how:

Right-click on the shortcut to the game (on on the game .exe file itself).
Click the tab marked 'Compatability'.
You should now be presented with a list of options. Click the box next to 'Run this program in compatability mode for:', and then choose Windows 95. Click OK, and try running the game. If this setting doesn't work, try tinkering with some of the other settings on the 'Compatability' tab.

If none of this works, check to see if your copy of King's Quest VII has a DOS mode (mine does). It requires you to run a separate install program. Once you have this version installed, you could try running it using DosBox.

I hope this helps.

[morriam]

I tried your tips. unfortinatly it still doesn't work. I can't install a dos version. Thanks for your reply though. Does anyone else have an idea?

[morriam]

I actually was able to solve the problem through the Sierra website. Here's the answer...

Solution:
If you get a message like "...referenced memory at xxxx....the memory could not be read from," it typically indicates a memory conflict between Microsoft's Win32S (used by the game to speed up graphics), and something else in the system. You can generally correct it by disabling the game's use of Microsoft's Win32S.


To do this:
1) Copy the File SIERRAW.EXE from the King's Quest 7 CD to the game's directory on your hard drive (usually C:\SIERRA\KQ7).


2) Highlight the icon for King's Quest 7. Press ALT+Enter on the keyboard to bring up the FILE PROPERTIES box. Go into the Command Line box. Move over in the box until you find SIERRAWS.EXE. Delete the S following the W, so it becomes SIERRAW.EXE. Do not change or adjust anything else. Click on the OK button. You should see your King's Quest icon change if you did everything correctly.


Note that this may slow gameplay a little, but you should not experience the problem any longer.


Hope this helps someone else as well....

[fov]

Thanks for posting the response! That is such a weird solution. I wonder what changing the name of the .exe has to do with anything.

I'll stick this info in my box of Sierra tricks for the next time something like this comes up...

emily

[Antti-san]

Hi, I'm new to this board and I'm not sure if there's an answer for this kind of problem but I'll ask anyway

When I try to play the game I get an error "Windows title not found", I've tried every compatibility modes but they don't work either. Does anyone have any idea of what to do?

[fov]

Welcome to the forum.

Are you on XP? Is it a Windows version of the game (installed using setup.exe), or a DOS version (installed using install.exe)?

I feel like I've heard of this problem before, but can't remember where or when. Sorry, not much help.

[plattyaj]

Originally Posted by fov

Thanks for posting the response! That is such a weird solution. I wonder what changing the name of the .exe has to do with anything.

I'll stick this info in my box of Sierra tricks for the next time something like this comes up...

emily

It's not changing the name of the executable, it's using a different executable. The CD came with two versions. The instructions get you to copy the other one off the CD and then change the shortcut to point to that one.

This works for some other Sierra games too - one of the Phantasmagoria games if memory serves me right.

Andy.

[poco_87]

I tried copying the file and changing the path, I set the compatibility for Windows 95, I set it to run at 640 x 480, in 256 colors, but now it gives the error, "Windows Title Not Found". What is causing this?

[fov]

Welcome to the forum, Poco. :) Are you trying to run the DOS or Windows version of the game? How are you trying to launch it? (i.e. desktop shortcut, start menu, etc.)

Do you have Service Pack 2 installed?

EDIT: I found this on NT Compatible. Try it and see if it fixes the problem:

The basic problem is, the game fails to add shortcuts to the Windows Start Menu under Win2K and later - therefore the previous "Windows Title Not Found Error". That isn't an incompatibility issue, Sierra seems to have used some quite advanced techniques in its' Windows 3.11 games, including some sort of universal game loader - the SIERRAW.EXE file.

SIERRAW.EXE is -not- the game's exe file, and it requires the respective RESOURCE.WIN file passed to it as the command-line parameter - which I found out after a quick googling for some help. That however didn't solve all my problems, so here's a quick guide to what should work anytime - e.g. if it works on my buggy machine, it has to work on yours...

1) Copy all the files into a directory of your choice on the hard drive - a rather crude method, but with today's hard drives and CD-ROM speeds, not much of a problem. I used the directory the installation uses by default - C:\SIERRA\KQ7\ - if there are problems, try and use a directory that's pre-Win95 compatible (directory names under eight characters, no characters that aren't 7-bit ASCII). I'll call this KQ7 Path from now on.

2) Copy KQ7 Path\English into KQ7 Path

3) Edit KQ7 Path\SIERRA.INF, and add the lines:

[Misc]
SourceDir=c:\sierra\kq7

4) Edit KQ7 Path\RESOURCE.WIN, and add the lines:

resAud = KQ7 Path\
resSfx = KQ7 Path\
patchDir = KQ7 Path\
movieDir = KQ7 Path\AVI\
robot = KQ7 Path\AVI\
audio = KQ7 Path\
resMap = KQ7 Path\;KQ7 Path\

[poco_87]

It worked! Thanks so much. I've been wanting to play this game for the longest time!

[RockChalk]

Hello! I just purchased the King's Quest Collection (so happy I finally found them compatible for XP); all of them are working fine, except VII which gives the error message "Cwindows\system32\autoexec.nt the system file is not suitable for running ms-dos and microsoft windows applications" any ideas?

any help would be greatly greatly appreciated!

[fov]

It's a Service Pack 2 issue. This thread should tell you everything you need to know.

[RockChalk]

Man your quick! I just came back to recant my question since I found the error in another forum (probably the same link you put) and copying the autoexec.nt file fixed it. Thanks again for your help and your prompt response!

[fov]

I just happened to be in the right place at the right time. Glad you figured it out.