Forum: DAZ|Studio


Subject: Update to Daz Studio 1.2 - Thank you, Mr. Gates

Natolii opened this issue on Jan 19, 2006 ยท 8 posts


Natolii posted Thu, 19 January 2006 at 8:02 PM

Attached Link: http://forum.daz3d.com/viewtopic.php?t=30892

Translation: An out of date DLL file that was not updated for every MS Window's user was the culprit behind a number of crashes. I think all those that accused Daz of not Testing properly, owe those people an apology...

Natolii posted Thu, 19 January 2006 at 8:34 PM

Site is under going maintance...


ren_mem posted Thu, 19 January 2006 at 10:24 PM

Well, those kind of issues are some of the most common so you can't really blame that any more on MS than DAZ...just gotta have a plan ab and c and keep files up to date.I had some horrible experience with what appeared to be sun jvm and my video driver on XP...took it off and won't put it back on til I need it. Took a bit to track down since it wasn't too obvious.:D Unfortunately there IS no perfect world.

No need to think outside the box....
    Just make it invisible.


ren_mem posted Thu, 19 January 2006 at 10:57 PM

I just looked and I have 19 copies of that file, but they're all same version and size...all current.I guess DAZ didn't include it in their directory which is always preferable than counting on windows shared.

No need to think outside the box....
    Just make it invisible.


Natolii posted Fri, 20 January 2006 at 6:45 AM

Oh, It's included. But it doesn't get installed if it sees a newer copy. Since the developers all have teh latest copy on their systems, of course the bugs are not going to show.


ren_mem posted Tue, 24 January 2006 at 7:38 PM

Yeah, I saw the post, but they are counting on a shared update whereas MANY put it in their program directory which is a much better method to avoid this very problem. (we are talking best practices here)Leaving the windows directory alone and not leaving trash on your computer. Anything you can install in it's own directory is always preferred.

No need to think outside the box....
    Just make it invisible.


jfike posted Wed, 25 January 2006 at 9:05 PM

The file in question here is msvcr71.dll. This is a Microsoft Visual Studio .NET file. It is going to change as MS develops it's .net (and other) software. If a developer uses it, they have to be aware that there are (or may be) different versions depending on the customers installed software. Blaming MS for this is way out of line. I checked my computer and have 8 copies of this dll. The .net 2.0 framework uses a newer version than the DAZ supplied copy. Applications such as Poser 6, Shade, and Vcom Powerdesk, install the required version (for their application) in their own directory. This ensures the customer application uses the (hopefully) tested version because the application looks for the dll in the applications directory. DAZ just released version 1.2.0.1. Guess what file is now included in the DAZ Studio directory? It's so easy to blame MS for every problem we have. I guess that's why they get the big bucks.


ren_mem posted Thu, 26 January 2006 at 6:40 PM

There is plenty to blame MS for, but this one ain't it. :D

No need to think outside the box....
    Just make it invisible.