Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Checking Very Large Time Machine Volumes' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Checking Very Large Time Machine Volumes
Authored by: drudus on Sep 06, '11 09:28:12AM

Are you sure Disk Warrior has a command line interface?
Does it have a manual -> 'man diskwarrior'

I can't see any mention of it on the Alsoft site ot the manual perhaps a message to support would get the answer, if you find out post it here since it would be great to get some extra speed from such a great disk tool.

I suspect any binaries will be inside the Disk Warrior Application bundle so perhaps you need to call it directly with a -h or --help option to see an arguments it supports.



[ Reply to This | # ]
Checking Very Large Time Machine Volumes
Authored by: david-bo on Sep 06, '11 12:36:28PM

Yes, I dug into the bundle and you could launch some of the binaries in there but they quit immediately because they needed input. This is completely undocumented and I did a quick strings on the different binaries but couldn't find anything useful. However, a combination of strings and decompilation probably would reveal some interesting stuff.

No man page or help switch.

Try it yourself.

---
link



[ Reply to This | # ]
Checking Very Large Time Machine Volumes
Authored by: drudus on Sep 06, '11 12:53:38PM

I tried with Disk Warrior 4, the DiskWarrior binary launched the the GUI app from Terminal. There seems to be some helper daemons & server binaries too, but I don't know how they would be run correctly without the app setting them up correctly.

Contact the developer, it would be easiest if they checked the disk size, available RAM & use appropriate values when using the GUI.

The same RAM usage argument may not even be relevant depending on how the scanner/ repair processes run.



[ Reply to This | # ]
Checking Very Large Time Machine Volumes
Authored by: david-bo on Sep 07, '11 12:39:26AM

I have talked to Alsoft about this and it is not supported - which I think sucks. They really need to update to a more modern GUI and/or support memory intensive operations at least from the command line.

---
link



[ Reply to This | # ]