Daz Install Manager (DIM) 1.1.0.100, Now Available! (*UPDATED*)
Daz 3D is pleased to announce the next public version of Daz Install Manager
- Version: 1.1.0.100
- Date: June 25, 2018
What is new in this version?
The 1.1.0.100 version makes improvements to, or fixes issues discovered since, the 1.1.0.74 General Release. More detail on specific fixes/changes/improvements can be found in the Change Log, which can be viewed online within the Documentation Center portion of our site. All new downloads of DAZ Install Manager will be of this version.
Highlights:
1.1.0.100 (June 25, 2018)
- New Feature: Re-Install Package
- Added “Re-Install Package(s)” menu and options to the context menu for packages on the Installed page
- Uninstalls the package(s) and re-installs using the 'current' (NOT previous) installation path(s)
- Enabled only if the associated installation package exists on disk
- Added “Re-Install the % package” to the options menu for a package on the Installed page
- Uninstalls the package(s) and re-installs using the 'current' (NOT previous) installation path(s)
- Enabled only if the associated installation package exists on disk
- Added “Re-Install Package(s)” menu and options to the context menu for packages on the Installed page
- Bug fixes:
- Fixed an issue with doubling up of “(64-bit)” in shortcut names on Windows
- Fixed an issue with requiring installation by root user on Mac
1.1.0.98 (June 4, 2018)
- Added 64-bit support
- Starting with this build, the 32-bit version running on a 64-bit OS will automatically switch to the 64-bit version during an update
- All versions prior to 1.1.0.98 are 32-bit and do not contain the logic to perform an automatic switch to the 64-bit version
- To force an update from the 32-bit version to the 64-bit version from within Install Manager, once 1.1.0.98 32-bit or later is installed, press and hold the [ALT] key on your keyboard and click the Refresh Button; this will bypass an internal version check and allow the switching mechanism to perform its job
- On OS X 10.6 and OS X 10.7 running the 64-bit kernel, you will also need to press and hold the [SHIFT] key; this is not needed for OS X 10.8 or above
- Running the primary application with elevated permissions on Windows is now prevented; running with elevated permissions can cause conflicts with accessing folder/files/registry keys; the application itself does not (and should not) require elevated permissions to run; a helper application requests elevation as required and is limited to necessary operations
How do I get the latest version?
If you have previously installed the Install Manager application and the computer it is installed on is connected to the internet, you can simply launch the application and log into your account. Once connected, you will be notified that an update has been detected and you will be prompted to "Update" or "Work Offline". Click the "Update" button and the application will take care of the rest.
Optionally, you can locate, download and install the application from the Product Library [once you are logged into your account] by entering "Install Manager" into the text field near the top left of the page and clicking the "Filter" button, or by clicking one of the following links:
If this is your first time downloading and/or installing Install Manager, simply follow this link, click the "download free now" button on the page and then run the downloaded installer.
*Note: If you experience a crash during the uninstaller phase of the update, it is recommended that you download the installer from the Product Library (see above) and run it manually.
Is there any documentation?
Yes, documentation is located here. Clicking the "Help" button in the top right corner of the application main window will launch your [default] browser to the same location.
Comments
crashes on osx 10.8.
What crashes?
Do you have a DIM crashlog?
copy the first 100-ish lines and post here and I can see if I understand what crashes and why.
Now I am seeing two entries for DIM in Add/Remove Programs list. Win 10 64-bit here.
Does it do an in-place upgrade of the earlier 32-bit app? I did not see any notification to choose a location for install. The earlier DIM was installed in a location reserved for 32-bit program files.
Read the Highlights in the first post carefully. Read each sub-bullet under "Added 64-bit support."
None of that explains why DIM should install the 64 bit version in a location reserved for 32 bit programs even though DIM has knowledge of both 32-bit and 64-bit program locations which are specified under Settings > Installation. Also that doesn't explains why we should see two different entries for DIM under add/remove programs.
Ideally, the installer should have offered to uninstall the previous version and then prompt for the location to install the new version as this is different from other DIM updates. The DIM settings are stored outside the program files location so they should not get impacted due to the uninstall.
Works fine for me, uninstalled the previous version and put the 64-bit program right where it should be. I am on Win 7, though, if that makes a difference.
Process: DAZ3DIM [397]
Path: /Applications/DAZ 3D/*/DAZ3DIM.app/Contents/MacOS/DAZ3DIM
Identifier: com.DAZ.DAZ3DIM
Version: 1.0 (1.1.0.98)
Code Type: X86-64 (Native)
Parent Process: launchd [142]
User ID: 501
Date/Time: 2018-06-05 13:15:40.520 -0400
OS Version: Mac OS X 10.8 (12A269)
Report Version: 10
Interval Since Last Report: 162559 sec
Crashes Since Last Report: 34
Per-App Crashes Since Last Report: 25
Anonymous UUID: 94F9EDF7-3A0F-4A58-A494-3BCB445E8206
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
abort() called
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff952ce212 __pthread_kill + 10
1 libsystem_c.dylib 0x00007fff8cd62b34 pthread_kill + 90
2 libsystem_c.dylib 0x00007fff8cda6dfa abort + 143
3 QtCore 0x0000000100b82255 qt_message_output(QtMsgType, char const*) + 149
4 QtCore 0x0000000100b8244e qt_message(QtMsgType, char const*, __va_list_tag*) + 446
5 QtCore 0x0000000100b8268d qFatal(char const*, ...) + 141
6 QtCore 0x0000000100b826be qt_assert_x(char const*, char const*, char const*, int) + 30
7 com.DAZ.DAZ3DIM 0x000000010000d821 __static_initialization_and_destruction_0(int, int) + 12009
8 dyld 0x00007fff628c7378 ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 236
9 dyld 0x00007fff628c7762 ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) + 46
10 dyld 0x00007fff628c406e ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) + 380
11 dyld 0x00007fff628c3eba ImageLoader::runInitializers(ImageLoader::LinkContext const&, ImageLoader::InitializerTimingList&) + 54
12 dyld 0x00007fff628b5fc0 dyld::initializeMainExecutable() + 207
13 dyld 0x00007fff628b9b04 dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*) + 3060
14 dyld 0x00007fff628b5397 dyldbootstrap::start(macho_header const*, int, char const**, long, macho_header const*, unsigned long*) + 761
15 dyld 0x00007fff628b505e _dyld_start + 54
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff952ced16 kevent + 10
1 libdispatch.dylib 0x00007fff9057de26 _dispatch_mgr_invoke + 883
2 libdispatch.dylib 0x00007fff9057da2a _dispatch_mgr_thread + 54
Thread 2:: QProcessManager
0 libsystem_kernel.dylib 0x00007fff952ce322 __select + 10
1 QtCore 0x0000000100c5af7e QProcessManager::run() + 214
2 QtCore 0x0000000100b8c5ca QThreadPrivate::start(void*) + 464
3 libsystem_c.dylib 0x00007fff8cd61782 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff8cd4e1c1 thread_start + 13
Thread 3:
0 libsystem_kernel.dylib 0x00007fff952ce6d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff8cd63f2c _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff8cd63cf3 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff8cd4e1b1 start_wqthread + 13
Thread 4:
0 libsystem_kernel.dylib 0x00007fff952ce6d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff8cd63f2c _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff8cd63cf3 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff8cd4e1b1 start_wqthread + 13
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000000000006 rcx: 0x00007fff5fbfe168 rdx: 0x0000000000000000
rdi: 0x0000000000000c07 rsi: 0x0000000000000006 rbp: 0x00007fff5fbfe190 rsp: 0x00007fff5fbfe168
r8: 0x00007fff7ad3f278 r9: 0x00007fff5fbfe180 r10: 0x0000000020000000 r11: 0x0000000000000206
r12: 0x000000010028eeec r13: 0x00007fff5fbfe4c0 r14: 0x00007fff7ad40180 r15: 0x0000000000000003
rip: 0x00007fff952ce212 rfl: 0x0000000000000206 cr2: 0x00007fff7ad38fe8
Logical CPU: 0
Wow I just noticed this when I went to see the Bryce download size. I was going to see if there was still a 32 bit version of the DIM. Do not have much time as my ride should be here soon.
Thank you very much!
edit: so I can no longer use 32 bit DIM on my 64 bit system?
That tells me that there should be a log entry in the logfile, found at ~/Library/Application Support/DAZ 3D/InstallManager/log.txt
The last ten-ish lines will probably explain why Qt choked with a fatal error (and after that crashed).
The 64 bit update did, for me, go to Program Files - and it has removed the 32 bit version of DIM. it's possible that something (such as a security application or disc cleaner) removed the uninstall files for the 32 bit version, and that you had the wrong directory set when installing the 64 bit version (it does prompt for directory, though mine defaulted to the correct location).
I manually installed the 64 bit version so do I need to uninstall the 32 bit version manually?
Correct, as the next update would detect the OS bit architecture and automatically switch. There is no advantage to be had by sticking to 32-bit.
Yes.
I only have studio4 and cms folders in Library/Application Support/DAZ 3D
Strangely, for me, it didn't. Or rather it did, then it didn't ... I downlaoded the install manually and ran it, and ended up with 2 installs, 1 32-bit, the otehr 64-bit. So I uninstalled the 64-bit version and let DIM downlaod an ddo the work. It uninstalled the 32-bit version and installed the 64-bit version into C:\Program Files (x86)\DAZ 3D\DAZ3DIM1
Did you follow these steps in the announcement post:
To force an update from the 32-bit version to the 64-bit version from within Install Manager, once 1.1.0.98 32-bit or later is installed, press and hold the [ALT] key on your keyboard and click the Refresh Button; this will bypass an internal version check and allow the switching mechanism to perform its job.
The 64-bit should be installed in C:\Program Files\DAZ 3D\ and not C:\Program Files (x86)\DAZ 3D\
I have no idea what version I had as it told me there was an update straight away and I coudl eitehr work off line or instal lit ... so I installed.
Unless you follow the instructions and hold ALT while clicking the refresh button *after the 1.1.0.98 update is installed*, the update to the 32-bit version of any version installed prior to 1.1.0.98 (i.e. every single one prior to this one), you will have the 32-bit version of 1.1.0.98 installed; the logic to automatically switch did not exist.
heres the error I ge specifically. this was after upgrading from the previous version whn I t said there was an update.
Ok, it seems to have updated the to the 1.1.0.98 version and to the 64 bit version after refreshing with the Alt key. Thanks DAZ.
However the 1.1.0.74 version remains in the C:\Program Files (x86)\DAZ3DIM1\ . Should I just manually delete that dir OR run its uninstaller ''Remove-DAZ3DIM1_Win32.exe' in its Uninstallers dir?
Just run the Uninstaller.
Great! 64bit.
is there a way to download veriosn 1.1.0.74 of install Manager?
Unfortunately, no.
Same here would, have been nice to have got some sort of warning that this wasn't just a straight forward update. Now I have no idea if DIM is working as it should or not.
I just looked and it seems I've still got 32 bit version is there any reason why I need to update it to 64 bit, its working and I don't really want to mess with it.
If your OS is 64-bit, then you'll need to update. There is no reason to stick to 32-bit. Just read the instructions in the original post carefully.
The reason I have for wanting to stick to 32 bit is because that is what it updated to (my OS is 64bit) if it had warned me at the time I would have done what needed to be done then, not after the fact, I was only aware of this thread after seeing it mentioned somewhere else, presumably all those DS users that don't visit the forums may well remain unaware that there is a 64 bit version of DIM, and will be running 32 bit DIMs on 64 bit systems. So is there an actual problem with continuing with the 32bit version?
No problem, but each time there is an update DIM will try to switch to 64-bit.