list of daz to move if setting up new drive?

alan bard newcomer

obviously daz 3d folders from prog and prog 86
and my daz lib from documents 
but specifically what to copy from the roaming folders ... the secret hidden ones which can screw up things if you don't copy them. 
--
ie to set up a new C drive
copy this, this, this and that

jbowler

alan bard newcomer said:

ie to set up a new C drive
copy this, this, this and that

The easy way is to take it to a shop where they can transplant your current C: onto the new drive and replace the old drive in the box.  I.e. pay someone else to do it.

If you are really only concerned about Daz; moving the C: drive has major implications for the whole of Windows, then the Content Directory Manager is the only real issue I can think of.  Simply edit it to add NewC: to all of the directories, in addition to C:, copy then all over to NewC: and swap.  I think that will work for Daz, I'm pretty sure it won't for Windoz.

alan bard newcomer

jbowler said:

alan bard newcomer said:

ie to set up a new C drive
copy this, this, this and that

The easy way is to take it to a shop where they can transplant your current C: onto the new drive and replace the old drive in the box.  I.e. pay someone else to do it.

If you are really only concerned about Daz; moving the C: drive has major implications for the whole of Windows, then the Content Directory Manager is the only real issue I can think of.  Simply edit it to add NewC: to all of the directories, in addition to C:, copy then all over to NewC: and swap.  I think that will work for Daz, I'm pretty sure it won't for Windoz.

I've done almost everything computer wise in past 44 years... (hey, I did n't start until I was 32 .. but they didn't have many computers before then)
---
I'm doing my pre copy off for a new daz install...
backing the old installer out of the download file and copying the daz folders to another drive. 
--
Was hoping there might be some clear listing of what daz data is in the  App data folder because since it's a place programs put stuff they don't want you to know about... just copying it all and copying it back to restore daz would probably be a mess
Was just hoping for an official listing from daz on what data is not it the standard three places (my lib, daz 3d in prog and prog 86) I know to look in app data.. but was wondering if there are any other bits floating around. 
In the app data folder , Facegen has a folder in local ...  abalone and daz have folders in romaing 
just crossing ts ... 

 

namffuak

You'll want everything under DAZ 3D in Users - Users/Public/Public Documents/DAZ 3D, Users/<logonid>/AppData/Roaming/DAZ 3D, Users/All Users/DAZ 3D plus the assorted registry entries. The best way to get the registry info is to copy all the /Users material first, then install (not copy) DIM; fire it up and verify the configuration info, correct if necessary, and then use DIM to install Postgres and Studio. Then fire up Studio and verify its configuration.

alan bard newcomer

namffuak said:

You'll want everything under DAZ 3D in Users - Users/Public/Public Documents/DAZ 3D, Users/<logonid>/AppData/Roaming/DAZ 3D, Users/All Users/DAZ 3D plus the assorted registry entries. The best way to get the registry info is to copy all the /Users material first, then install (not copy) DIM; fire it up and verify the configuration info, correct if necessary, and then use DIM to install Postgres and Studio. Then fire up Studio and verify its configuration.

thanks that confirms what I was hoping was all the data. 
Not changing the C drive ... just going let dim install 4.21 but decided to add backing the appdata stuff just to be double safe. 
If for some reason the new install doesn't work or sucks (oh my, could that happen?) I know I can run  the copied older dazs from their folders on the backup drive.
--
I've learned to be paranoid about computers and their data since the day the 2m hard drive (20 in metal drum) crashed in the pdp 8 .... and even if new crashes are quieter the can still set you back if you aren't mostly covered.  

---
my new C has daz on it... but a crash took out some items in the win 32 folder and since it's a server install... trusted server has to reintall and despite a lot of attempts via scandisk and others of that ilk...  it won't do it. 
some my last ditch attempt will be a new install of server on another disk and then copying the win 32 folder from the new drive to the broken drive. 
I do not want to go through all the server setup again. considering that server is so paranoid it won't even install it's own stuff without seven levels of hellish permissions and that's on a happy day. 
But alas the dual asus board flattly refuses to take a win 10 install ... 

 

nicstt

don't forget to take the reg edit export too

Computer\HKEY_CURRENT_USER\SOFTWARE\DAZ\Studio4

That's the key you can use to find what you need, if you use public build like I do, then that is next to it.

After you have exported it, I would delete most from the key, leaving just the additional folders you have.

NOTE: Messing in the Regestry can be dangerous. Replacing keys like this could mess up your Studio installation, requiring a reinstall. Messing up something else could mean you need to re-install Windows.

I believe there is a script somewhere for getting what you need from the regestry.

I have copied the whole keys from a Beta Export changed the Studio4PublicBuild from keys such as [HKEY_CURRENT_USER\SOFTWARE\DAZ\Studio4PublicBuild] and anywhere else it occurs to Studio4 [HKEY_CURRENT_USER\SOFTWARE\DAZ\Studio4]

It doesn't appear to have caused issues, which is actually quite surprising, but I don't use the Release build that often.

alan bard newcomer

nicstt said:

don't forget to take the reg edit export too

Computer\HKEY_CURRENT_USER\SOFTWARE\DAZ\Studio4

That's the key you can use to find what you need, if you use public build like I do, then that is next to it.

After you have exported it, I would delete most from the key, leaving just the additional folders you have.

NOTE: Messing in the Regestry can be dangerous. Replacing keys like this could mess up your Studio installation, requiring a reinstall. Messing up something else could mean you need to re-install Windows.

I believe there is a script somewhere for getting what you need from the regestry.

I have copied the whole keys from a Beta Export changed the Studio4PublicBuild from keys such as [HKEY_CURRENT_USER\SOFTWARE\DAZ\Studio4PublicBuild] and anywhere else it occurs to Studio4 [HKEY_CURRENT_USER\SOFTWARE\DAZ\Studio4]

It doesn't appear to have caused issues, which is actually quite surprising, but I don't use the Release build that often.

thanks for the  feedback... 
Basically Daz doesn't have issues reistalling the new version where the old one was but it does overwrite the old installer if you don't copy it before downloading the new one
and likewise if overwrites the current daz install.  But if you copy your current daz 3d folder to another drive ... that install will still run 
(I think for fun once I actually had 4.8 thru  4.14 all open at the same time. 
Backing the app data covers you in case daz loses it or messes up that data. 
So I''m not going to remove/unstall the old one just let daz write over it... and daz must have a fairly generic registry entry because all installed dazs will run off it.
---
My Daz 3d library is minimul all other data on other drives which are backed up and can be replaced simply by changing the drive letter on the backup to that of the one that is not functioning. 
---
I have deliberately steered clear of messing with the registry --- becasue I can't really learn it... I can do it with close attention to instructions but I'm never going to do it everyday so it becomes ingrained.
Same reason I'm trying to salvage the current server 19 disk...  I did all the work to set all the hard stuff up .. but doing it once doesn't mean I learned and to do it again would requre doing the study all over. 
And it crashed out while I was still fine tuning it, using it but still tweaking and cloneiing it now would just clone the bad stuff.