Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
bousozoku said:
Perhaps, separating the code so that the part which alters the partitions run as a daemon would avoid similar situations and allow the disk to be re-partioned regardless of GUI errors. Since you'd be past the point of no return, you really wouldn't need the GUI and could have the daemon re-boot the machine in case of GUI failure.

Yes, it would be nice to split the application, although having said that, we are 100% certain that we have fixed the problem in question (it was our bug :-(), and we haven't seen any further GUI problems like this since.
 
For what it's worth, I had need for this utility today, and version 1.06 worked flawlessly for me (third-party external FW drive, but an IBM DeathStar much like what Apple tend to ship OEM). Yay.
 
Out of curiosity, what changes did you make to the FW drive?

I noticed someone on VersionTracker recently claimed VolumeWorks is "much better than iPartition", without giving any reasons.
 
What I needed today was to shrink a 120GB HFS+ bootable partition down to about 80, and set up the remainder as ext2 for a porting project. That's my only bootable Jagwire partition, and the install media is an hour away, so that little exercise was very, very useful to me =)

I'm not really sure what features iPartition would suppsedly be missing. It manipulates partitions, there are only so many ways that can be done :D

The only "complaint" I might have is that the interface is so blatantly obvious that I ended up looking in the help, assuming that it had to be trickier than it looked.
 
Coriolis Sys said:
Yes, it would be nice to split the application, although having said that, we are 100% certain that we have fixed the problem in question (it was our bug :-(), and we haven't seen any further GUI problems like this since.

It's good to hear that your bug problem is solved. Hopefully, you'll have plenty of customers to exercise your software. There have been times when I needed it but isn't a current thing.

iMeowbot:

That's too funny. You want it more complicated? :D
 
bousozoku said:
That's too funny. You want it more complicated? :D
Absolutely! What's the deal with dragging handles on a pie chart and being finished? Partitioning programs are supposed to employ mysterious undocumented commands, and use terminology and device names that don't match what any other part of the OS uses. They're hard to use, that's how you know they do real work ;)
 
You can always fuddle around with pdisk, with its interesting man page containing this helpful comment:

-h Prints a rather lame set of help messages for the pdisk program.

:)

And fdisk, if that actually works on OS X.

What I want(ed) to do is shrink a media partition and add the reclaimed space, plus whatever extra the original Disk Utility partitioning wasted, to a boot partition. But I'll probably wait until I get another system and rethink/redo partitioning (again).
 
sjk said:
You can always fuddle around with pdisk, with its interesting man page containing this helpful comment:

-h Prints a rather lame set of help messages for the pdisk program.

:)

And fdisk, if that actually works on OS X.

What I want(ed) to do is shrink a media partition and add the reclaimed space, plus whatever extra the original Disk Utility partitioning wasted, to a boot partition. But I'll probably wait until I get another system and rethink/redo partitioning (again).

I've successfully used a lot of cryptic tools and read a lot of other developers' undocumentation, but pdisk really wins the award. After trying to use it to create partions for mkLinux years ago, I gave up.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.