Skip to main content

does anyone else have to use the tibmounter patch to mount 2016 images with 2017?

Thread needs solution

I was getting internal database errors when I tried to mount images (both original 2016 and mixed 2017), but running tib_mounter_setup_2637.msi seems to have resolved this issue.  I had also done that 'database transplant' trick to keep my old database, but why should the database disrupt mounting?  If it does, it shouldn't!!

0 Users found this helpful

I just mounted a *.tib file created with ATI 2016 without issue. It was unusally in mounting and assigning drive letters.

Ian