Beta 1 bugs?     (Moderator: Hell Raiser) Previous Topic | Next Topic
Page 2 of 2 Goto page Previous  1, 2
 Author 
 Post 
Hell Raiser
Site Developer
Post 25-Feb-2006 19:27        

Yes, it's big, but hey, it's DirectX and the age of Broadband.

Ya, you have to validate windows at that particular location. It shouldn't be a problem. Razz
Post 25-Feb-2006 19:41        

It is, though. I found it on a different site. Let's see if it helps. *crosses fingers*
Post 25-Feb-2006 20:03        

Ok...

I updated DirectX, but leaving dinput.dll in there still gives me the same error. When I take out dinput.dll, JK Patcher works!

I tried to let it load my mod by giving it a commandline to my JKPatch folder, but that's not working. I know mods aren't supported in this release, but I just tried entering the command line to see if that would work. So you probably already know this.
Hell Raiser
Site Developer
Post 25-Feb-2006 20:14        

Ok cool. So it's just dinput.dll then? Cogext.dll is in your Jedi Knight directory with no problems?

And the command line parameters should work afaik. -path AnyDirWithAGob should work.
Post 25-Feb-2006 20:39        

Yeah it's just dinput.dll. Cogext.dll is sitting there without problems, and I can play with both patches.

Although the -windowgui command line parameter works, the path to my gob folder does not. And I swear I have it right:

-windowgui -path JKPatch\active


Odd, hm?
ZeqMacaw
Site Admin
Post 10-Apr-2006 03:50        

ZeqMacaw's report on 1.0 Beta:

* I hate the exe installer. I would rather have a zip of all needed files and a brief text-only file with instructions of where to put the files and what they do.

* Complaints about the installer:
- It takes up entire screen (even taskbar), which made it annoying to find the program for pasting a screenshot of an error message (see next complaint) into.
- At the end of installation, a window showed this message (shortened): "JK Patcher has not been totally installed [...]: CRC error - cannaot install [...] On.wav [...]". Indeed, the off.wav file existed in the location given, but not on.wav.
- In the window for entering the JK folder, I left it blank, so the installer installed into D:\ (which was fine with me, for this test). I noticed that the Uninstall.exe was placed in this folder. It should not be in that folder, but rather placed in the JKPatcher folder.
- Running the JKPatcher from D:\JKPatcher folder resulted in a "This program has performed an illegal operation [...]" window. And no, JK was not installed in D:\.
- I re-ran the installer to see if the on.wav would be installed; it was not.
- I then re-ran the installer into the JK folder as suggested. The on.wav error message still appeared, and the on.wav file still did not show up.

* Running the JKPatcher from the proper place (the JKPatcher folder that is in the JK folder) still resulted in the "illegal operation" error window.

* Uninstalling it showed a window saying it had been uninstalled, but the folder and files still remained, except for the uninstall.exe itself.
ZeqMacaw
Site Admin
Post 11-Apr-2006 20:31        

Another complaint about the installer:
- It placed an icon on my Windows desktop without asking me. This is BAD.
Hell Raiser
Site Developer
Post 13-Apr-2006 02:34        

Try to make it easy for some people, and it gets complicated for others. *slaps Install Maker Pro*

I think for now the files in zip is a good idea. Also, uh, I guess I'll just cater to everyone in a general manner, and forget about having things organized. (Where JK Patcher gets installed)
*** Post commands are unavailable for guests. ***