KOTOR 1+2: Vista Fix & Windows 7 Report

[Q]

Try using the game's configuration utility to post your system specs:

Post your system specs

Sometimes we're just not going to be able to help you if we don't know what kind of hardware you have on your machine. If you don't know what you have on your machine, then follow these steps below:

• If you're using Vista or Windows 7, go into your game folder, find "launcher.exe" and "swconfig.exe". For each file, right-click on it, select "properties", then "compatibility", check the box beside "Run this program in compatibility mode for:" and select "Windows XP (Service Pack 2)". Then check the box next to "Run this program administrator" and hit "OK". (EDIT by Q)
  
• Bring up the launcher menu for Kotor 1 or 2 (by running "launcher.exe").
  
• Click on "Configure".
  
• Click the "Scan Hardware" button on the lower center of the window.
  
• Click "Yes" to continue.
  
• Click "Details" to view your system specs.
  
• Click "Save Report" and save the file to your desktop.
  
• Whenever you post your problem, open the file you just saved and copy and paste the contents to your post.

You can leave out the keymapping and everything after that.

[Anderill]

Thanks for the reply, but with the Steam installation, there is no "launcher or config exe"

[Q]

Steam must've changed to the newest version, which doesn't have it. The Steam version shouldn't require the guide, either.

 

Have you tried installing it like you would any other program?

[Anderill]

Not sure how to install a Steam app without Steam, there isn't any installer or similar thing in the folder.

[Q]

Well, yeah, but what I was talking about was installing the game using Steam, but without any of the fixes in the first two posts of this thread, because they shouldn't be necessary.

[Anderill]

Oh, yeah, I Installed it first without them, then applied what I could retroactively...

[Q]

The Steam version is patched to the newest version and is supposed to work with Windows 7 as-is.

 

Try reinstalling the game without any of the fixes.

[Anderill]

Nope, clean install, doesn't even get to the main menu...

[Q]

The Steam version is supposed to work right out of the box. Maybe you could try over at the Steam forums.

 

Sorry I couldn't be more help.

[iLoveLampXx]

Hey all!

 

I'm experiencing an error that I've never seen before when dealing with this game.

I tried setting my affinity when my game crashed and pops up this error message everytime:

( http://imgur.com/xGF3ORs )

 

 

------------------

System Information

------------------

Time of this report: 11/24/2013, 16:57:32

Machine name: ZEREF-PC

Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130801-1533)

Language: English (Regional Setting: English)

System Manufacturer: Acer

System Model: Aspire M3970

BIOS: BIOS Date: 10/31/11 10:13:44 Ver: 04.06.04

Processor: Intel® Core i7-2600 CPU @ 3.40GHz (8 CPUs), ~3.4GHz

Memory: 16384MB RAM

Available OS Memory: 16364MB RAM

Page File: 4061MB used, 28665MB 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.7601.17514 32bit Unicode

 

---------------

Display Devices

---------------

Card name: NVIDIA GeForce GT 530

Manufacturer: NVIDIA

Chip type: GeForce GT 530

DAC type: Integrated RAMDAC

Device Key: Enum\PCI\VEN_10DE&DEV_0DE5&SUBSYS_7162174B&REV_A1

Display Memory: 4062 MB

Dedicated Memory: 2014 MB

Shared Memory: 2047 MB

Current Mode: 1680 x 1050 (32 bit) (60Hz)

Monitor Name: Generic PnP Monitor

Monitor Model: SyncMaster

Monitor Id: SAM037C

Native Mode: 1680 x 1050(p) (59.883Hz)

Output Type: DVI

Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um

Driver File Version: 8.17.0012.6733 (English)

Driver Version: 8.17.12.6733

DDI Version: 11

Driver Model: WDDM 1.1

Driver Attributes: Final Retail

Driver Date/Size: 2/23/2011 22:44:00, 12870248 bytes

WHQL Logo'd: n/a

WHQL Date Stamp: n/a

Device Identifier: {D7B71E3E-4EA5-11CF-B66E-6E511FC2C535}

Vendor ID: 0x10DE

Device ID: 0x0DE5

SubSys ID: 0x7162174B

Revision ID: 0x00A1

Driver Strong Name: oem8.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section013:8.17.12.6733:pci\ven_10de&dev_0de5&subsys_7162174b

Rank Of Driver: 00E60001

Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C

Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

D3D9 Overlay: Supported

DXVA-HD: Supported

DDraw Status: Enabled

D3D Status: Enabled

AGP Status: Enabled

 

I've tried just about everything at this point with no luck, I tried reseting my entire computer to factory settings with also no luck, I'm on the brink of just re-formatting my drive because I may of screwed something up by accidentally typing the affinity code into a cmd.exe window as a command, but nothing seems to be working thusfar.

 

Any help is much appreciated!

Thanks.

[NADDZ]

Hi, I've got kotor working with the windowed ini fix, problem is now the movies wont play, I have downloaded bink video player and selected the in-game movies to "open with" bink, but still wont play, I also use the flawless wide screen fix to get the game to 2560x1600, just wondering if that has anything to do with it ?

I have kotor on steam and also have had it on disc since 2004, same result with both.

 

Does anyone have any ideas about the movies ?

 

windows 7 64-bit

AMD fx-8350 (with 990x chipset)

AMD R9 290 (latest drivers)

[paulodavidvic]

Ok, everyone... very long time since i last posted on these forums. First, i wanna give my thanks to everyone who helped to make the amazing and useful installation guide for

 

KOTOR/KOTOR2 on Windows VISTA and 7, especially Q. It's fantastic to see the huge number of people the guide has helped in the last years (me included)!

 

That being said, i wanted to point out some curious facts about KOTOR.

 

First, i own ALMOST ALL original editions of KOTOR for PC, except the Steam version.

I have the original USA, UK and Asia/Pacific/Australia boxed editions (no real differences on data or the executable, except the USA has an extra movie ad for hyperspace and the Asia/Pacific/Australia edition usually comes with a fifth CD with a black and white version of the pdf manual); the Best of PC version (patched to version 1.03 and NO securom) and the USA and UK editions of The Collection.

 

Apparently i've always been lucky because i've managed to install and run all those game editions on VISTA and 7 without any problems... until recently, when i changed to Windows 7 64 bits and i got a new graphics card (Nvidia GeForce GTX 750 Ti)... I still manage to install all editions of KOTOR but i started having random crashes, even after following all the instructions on the main guide.

 

I then started experimenting with settings and configurations and tried all sorts of things until i went and bought yet another version of KOTOR, this time the so called GOG edition...

As you guys probably noticed already, and i'll stand by what i'm saying here, guys at GOG ship their games using modified executables to remove DRM. But just how do they usually do this? They usually get some well known working crack from some "scene group" and modify it to remove any reference to the original cracker... Ironic isn't it?

 

For KOTOR, they released the game patched to version 1.03 along with the Fairlight group cracked exe (they edited out the line saying "Hellspawn Reborn" left by the cracker)... So, yes, people are actually paying for recycled cracked exes, which is ok as long as the game works, so fine with me...

 

In GOG's case, it did for me... Not because of the game exe, but because of the compatibility settings they used for the exe to run in the first place! That did the trick for me...

 

On the compatibility settings for the swkotor.exe file they marked three boxes, leaving all others unmarked: Disable visual themes, Disable desktop composition and Disable display scaling on high DPI settings. I haven't tried changing these options to figure out which ones (maybe all) actually make the game run better on Windows 7 but the thing is it worked without having to do anything else. In case you're wondering, using those options also works with the original 1.03 exe, the one from Best of PC and even the securom fixed ones (i have two different ones), the Collection ones or other different cracked executables.

 

Other curious thing is that the Best of PC version of KOTOR is also patched to version 1.03 and has no DRM at all! That's right, the swkotor.exe there has no securom at all, so people at GOG could have used that, but they went with Fairlight's crack instead...

 

Another thing i noticed is that the so called "kotor_2_vista_fix" is just the Mss32.dll file from KOTOR 1! It's present on all patches (1.01, 1.02 and 1.03) and i guess that's the reason why it says on the guide there is no need to copy the Mss32.dll file to the KOTOR installation dir (it gets installed automatically with any of those patches anyway!)... The readme file on that fix says that the author, some guy nicknamed "A_Dead_Jedi" and some "friends were able to make it almost exactly like the Kotor one (but not exactly the same)", and i'm quoting from the same readme file... That's odd, because the file on that fix is precisely the same on those KOTOR patches i mentioned... What's even more interesting is that at a very known site for game cracks there's another file, this one is called "kotor1-2_vista-w7_fixed_dll", which indeed has a modified version of the Mss32.dll file. Maybe this is the one that "A_Dead_Jedi" and his friends modified? I have no way of knowing because the readme file on this fix only has this:

SW KotOR 1 & 2 Vista/Win7 Crashfix

this is for both Star Wars Knights of the Old Republic 1 & 2

This DLL solves startup crash on Vista and Windows 7.

Unpack to the game folder and play!

 

 

but the files are indeed different... I have no idea about what the differences actually are but i used it before too and also didn't help fixing the startup crashes on KOTOR (no idea about KOTOR 2 yet).

 

One last thing i should mention is that there are actually two official 1.03 patches for KOTOR. They have the same name but the older one was released March 1, 2004 (26.026.060 bytes) while the newer one (and final) was released two days later on March 3, 2004 (this one has 26.027.813 bytes). Only difference between the two is on the DIALOG.TLK file they install. From what i can tell, people using the older patch will have problems somewhere during the game (no idea where or what kind of problems) but back in 2004, Bioware released the DIALOG.TLK file to people who had used the older patch (or people can just update the game again using the newer one). Apparently, the Bioware autoupdater still works too!

 

I hope these informations are useful to someone and i wanna thank again all the people who made the guide at the beginning of this thread! Cheers!

[Rigas]

I just can't get Knights of the Old Republic to work properly in Windows 7. It crashes randomly every 2-4 minutes. I've tried setting core affinity to single both by using a modified shortcut, and by setting it manually through Task Manager. No success. Got any other ideas? I'm running Windows 7 Ultimate Service Pack 1, with a 2-core 2.25 Ghz processor.

[spjaymo117]

Hey All,

Recently purchused KOTOR 2 again on Steam as it was one of my favorite games growing up, unfortunately though it cuts out during movie scene after character creation with an error message.

 

I've tried most of the fixes I could find but no luck yet.

 

I've been running it as admin, with vista service pack 2 compatibility, in windowed mode, with updated graphics drivers (tried messing with settings didn't even seem to have relevant ones as options), turned off steam overlay setting in game, and took off buffer setting (I think that's what it's called) on in game graphic options.

 

System specs

Processor: Intel® Core i7-4510U CPU @ 2.00GHz 2.60 GHz

Ram 8.00 GB (7.88 usable)

System: 64-bit operating system, x64

Graphics: Intel® HD Graphics Family

Running windows 10

 

Sidenote: I do have 6 steam workshop items active. That mess with anything?

[Hot_ice]

The fix is a tiny file >> mss32.dll (372kb) HERE

-Cheers to Qliveur for the updated link

 

Hello,

 

it looks like this link is gone again. Or at least I can not access it.

 

 

I have never experienced KotoR, but I really want to now (win7)! Hence I did find this forum post at least!

 

Could anyone share this file with me, or give a working link?