A second bootable partition with tools on it is within most users' grasp now, especially now that disk utility can do non-destructive repartitioning. IMHO the edrive is approaching obsolescence. Some binaries in /bin, /sbin, /usr/bin, etc may not be present on the edrive. The only catch you may run into is the edrive is trimmed down quite a bit and may be lacking important files the other software expects. Don't expect any support from micromat OR the other vendor - it's SOP to not help anyone with compatibility with your competitor's products.
#Dasboot diskwarrior install#
Micromat maybe doesn't want you to install a competitor's software on their edrive, but there's no specific reason not to. The eDrive should be usable to store any tools you need.
(can't burn it to a bootable CD for example) I've gotten around this a few times by creating a symbolic link where the reg file is, pointing to BootCD's temp scratch partition and let it write there. (bug?) This means that once you license it, you can't run it on a read-only media. UUNNfortunately, it insists on writing to this file every time it launches, even after it's licensed. This code is written into the diskwarrior app package itself, so if you drag the app to another drive, the license (and your name) goes with it. When DiskWarrior is running from a non-locked volume, (not the CD it came on) it will attempt to license itself and prompt for code etc.
0 kommentar(er)
