K-3D Forums

Seven Degrees of Freedom

1. 

   Timothy Shead
   Moderator

   This message was originally posted by Dale Johnstone on 02/09/2009 12:45:55

   Hi,

   I just tried/uninstalled the K-3D app (WinXP), and I found my ATI control panel no longer started up as it should, instead I got a nice error every time on bootup. Thanks for that.

   I was quite surprised to find info on the Windows Installers page telling me the installer will actually break my systems path variable by changing the registry key type!

   I don’t like criticising free software, by seriously guys, this isn’t on. Offering a python script to fix a bug in the installer is not a solution either.

   Fortunately being a developer myself I could read the python code and manually changed the registry key type back which fixed the problem, but most artists are not going to know why other software is now failing on their machines because of this.

   You should take this down until you have a proper fix for it. Doing no harm to your users should take precedence.

   I hope this helps improve your software. Thanks.

   Posted 4 months ago #
2. 

   Timothy Shead
   Moderator

   This message was originally posted by Bart Janssens on 02/09/2009 13:03:01

   Hi Dale,

   Can you please provide details on what installer you used, exactly? I was under the impression that this issue had been resolved quite some time ago.

   Cheers,

   Bart

   Posted 4 months ago #
3. 

   Timothy Shead
   Moderator

   This message was originally posted by Dale Johnstone on 02/09/2009 13:33:33

   Hi,

   Thanks for the quick reply.

   It was the k3d-all-in-one-setup-0.6.7.0.exe installer (34,313,284 bytes).

   The machine is running WinXP SP3, (plus lots of MS dev stuff). I don’t have any of the python of gtk libraries on my machine so it went through a chain of about 5 different installers.

   I’m assuming it was the Aqsis installer since this is what the wiki page said was the cause of the path registry key problem.

   I can confirm that my registry key was set to REG_SZ type and changing it back (via regedit) to REG_EXPAND_SZ fixed the issue.

   The error the ATI Catalyst Control Center gave on startup said something like I didn’t have permission to change settings. Since I’m running as administrator it can’t be that. I’m assuming the ATI CCC simply failed when accessing the path registry key and that’s the only error message they have for a registry key access exception.

   Hope that helps. Thanks.

   Posted 4 months ago #
4. 

   Timothy Shead
   Moderator

   This message was originally posted by joa on 02/09/2009 15:35:19

   Bart:
   I think this issue was solved on 0.7 version, but not on 0.6 version, since this version got frozen in time.
   I think the best thing is fixing this, since some people can use 0.6 and not 0.7

   Cheers!
   Joaquín

   Posted 4 months ago #
5. 

   Timothy Shead
   Moderator

   This message was originally posted by Bart Janssens on 02/09/2009 16:41:11

   Yes, this issue is resolved in 0.7, although I noticed the 0.7.10 release has a non-working Aqsis, most likely because I forgot to include the mrvcrt libs that are required by aqsis 1.4.

   Anyway, I have uploaded a new 0.6 all-in-one installer. The file is at the same location as the old one, I’d be grateful if someone can confirm the problem is gone now.

   Cheers,

   Bart

   Posted 4 months ago #

RSS feed for this topic

Reply

You must log in to post.