installing DAZ content to multiple drives

Fielran

I've recently gotten a new computer with a 256 GB SSD and a 2 TB mechanical drive. DS is installed to the SSD (C drive) along with the figures and morphs, since they wouldn't load from the D drive. I tried to install clothes to the mechanical (D) drive, using the install manager. The result was...not good.
I got a "Missing Files" message, which said:

Some assets needed to load the file were missing. The content may not work as expected. The following files could not be found:
/data/smay/SuperHerosuit_M6/SH_BodySuit_1/SHSuit_M6.dsf
/data/smay/SuperHerosuit_M6/SH_BodySuit_1/Morphs/smay/Base/Under_Boots.dsf

There was no option I could find to redirect the computer to the correct path, and other clothing yielded similar messages. Additionally, with both the G2F and G2M versions of the super hero suit the figure was surrounded by boxes. This did not happen with the Genesis supersuit or G-Suit, which simply became invisible.

I guess what I'm asking is whether it is possible to have DAZ Studio installed on a different drive than the content, or if I need to try to put studio on the D drive, and how to make it work with multiple content directories. Do I need to move the starter content so the figures are also on the D drive? Or is there some setting I'm missing to make it work? Both locations are listed in the content directory manager within studio, and were there automatically after changing the install directory in DIM.

I appreciate any help on this issue.

Szark

Yes you are missing something but I can't tell from what you wrote.

Yes DS can be installed anywhere any drive and yes content can be on the same or a different drive..mine is.

Using DIM set up the Paths for Daz Studio and the Paths for the content.....it is totally customisable. If you don't know how I will grab some screenshots and take you through the process.

Once that is done you then go into DS, Content Directory Manager and set up the content paths for both Daz Studio and Poser formats.

Fielran

I thought I had done that, but on closer inspection I realized that the 2 automatically recognized content directories did not, in fact, match the 2 specified in the DIM. Seems to be fixed now.