I've mounted a windows drive on USB as N: When I run Fabs I select the source drive N:, it finds the correct N:\Windows directory. In the Select Users list it displays the root directory of my C: drive.
explorer.exe: 6.00.2900.5512 Win XP SP3. Is that supported?
I've mounted a windows drive on USB as N: When I run Fabs I select the source drive N:, it finds the correct N:\Windows directory. In the Select Users list it displays the root directory of my C: drive.
explorer.exe: 6.00.2900.5512 Win XP SP3. Is that supported?
I have seen this yesterday but had no time to fix it. I should have more time today. This happens when the software registry hive cannot be loaded. If you rename the n:\windows into something like n:\windows.old, can you see the users profiles? I have not tried this trick but it may work.
I will fix this asap.
I have seen this yesterday but had no time to fix it. I should have more time today. This happens when the software registry hive cannot be loaded. If you rename the n:\windows into something like n:\windows.old, can you see the users profiles? I have not tried this trick but it may work.
I will fix this asap.
Ok. Might need some feedback on the gui if it can't find the registry. Had to do the backup the long way No other XP boxes in the shop at the moment so I can't test your workaround. That's good right ?
Cheers!
Ok. Might need some feedback on the gui if it can't find the registry. Had to do the backup the long way No other XP boxes in the shop at the moment so I can't test your workaround. That's good right ?
Cheers!
It should show the users profiles anyway and show a warning about this in the public data tab. Also, this is not related to XP and happens with every other Windows versions. I am on it.
Ok. Might need some feedback on the gui if it can't find the registry. Had to do the backup the long way No other XP boxes in the shop at the moment so I can't test your workaround. That's good right ?
Cheers!
It looks like I have sorted it out. I have just sent you a test version. The process is quite easy to reproduce: just rename the Config folder inside X:\Windows\System32 into something else and see what happens.
Well, I think I will release this version, even with no more feedback on it. In this case, the actual version just cannot work, so, that cannot be worse. I got the expected behavior with it so, I will release it soon. I cannot let this bug out there anymore.