Opened 15 years ago
Closed 15 years ago
#4416 closed bug (invalid)
Disable "Initialize" for unformated diskspace
Reported by: | humdinger | Owned by: | stippi |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Applications/DriveSetup | Version: | R1/pre-alpha1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
This is hrev32931.
If you have an <empty> unpartitioned space selected, the "Initialize" menu should be disabled.
Change History (2)
comment:1 by , 15 years ago
comment:2 by , 15 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Ah, OK. But DriveSetup could be intelligent enough to distinguish these different circumstances. If it's smart enough to put up an alert informing me to first create a partition before initializing, it could disable the option in the first place.
Having written that, it occurs to me, that you then maybe wonder "Why is "Initialize" sometimes available, sometimes not?". The alert informs you what you have to do to make it work.
So... er... I think I'll mark that thing "invalid", then. Thanks!
This is not that simple. Technically you can have unpartitioned space that is initialized with a file system. This happens all the time with SD cards, for example.