TeraByte Unlimited

I enlarged an OS partition size using Win7. On reboot, BIBM error msg. In
PW, see error, overlapping with next partition. Deleted partition that I
enlarged. This fixed problem, but I had to recreate the original partition
which I then enlarged using BIBM.
Questions:
1) Obviously solution was draconian. Can I fix the overlap without deleting
the partition, that is, can I set the end point [move it] not to overlap?
2) I have resized many partitions in BING/BIBM without issues such as this.
Is the Win7 utility more susceptible to creating errors such as this? It
appears it created an incorrect end point.

If you're using an EMBR type drive, was the partition located directly after the OS partition visible to Windows 7 (loaded into the MBR)?

I was using an EBMR type drive and I do not remember if I included it into
the MBR at that time, but I am inclined to think I had not. To extrapolate
on where you might be going, if Windows cannot see a partition, it may
overwrite its space and to avoid this, the following or boundary partition
must be visible [in MBR]. Correct? If I added less than the available space
between the 2 partitions, would the overlap be avoided?
Does Windows always enlarge a partition by adding from the end of a
partition?


"TeraByte Support (PP)" wrote in message news:5489@public.bootitbm...

If you're using an EMBR type drive, was the partition located directly after
the OS partition visible to Windows 7 (loaded into the MBR)?

Correct. If Windows can't see the partition it will assume the space is unallocated and that it's available for use. If you don't expand the partition into space occupied by another partition it won't overlap. Windows will expand and shrink from the end of the partition.

When using EMBR type drives it's recommended to only use software that supports EMBR (e.g. BIBM, IFW, IFL, IFD, TBOSDT) to avoid those types of problems. Otherwise, what I usually do is make sure the partition being modified is surrounded by other partitions (where applicable) so the partitioning program knows the limits. This may require setting up a temporary boot item or manually loading the MBR before making the changes.

Thanks.
I usually use BING[in past]/BIBM to work with partitions but I was in Win7
when it asked for more room, updating to Win8.
Can this overlap issue be fixed without deleting partition? If so, how?


"TeraByte Support (PP)" wrote in message news:5495@public.bootitbm...

Correct. If Windows can't see the partition it will assume the space is
unallocated and that it's available for use. If you don't expand the
partition into space occupied by another partition it won't overlap. Windows
will expand and shrink from the end of the partition.

When using EMBR type drives it's recommended to only use software that
supports EMBR (e.g. BIBM, IFW, IFL, IFD, TBOSDT) to avoid those types of
problems. Otherwise, what I usually do is make sure the partition being
modified is surrounded by other partitions (where applicable) so the
partitioning program knows the limits. This may require setting up a
temporary boot item or manually loading the MBR before making the changes.

On Thu, 16 May 2013 11:16:55 PDT, just as I was about to take a herb,
TeraByte Support(PP) disturbed my reverie and wrote:

>When using EMBR type drives it's recommended to only use software that supports EMBR (e.g. BIBM, IFW, IFL, IFD, TBOSDT) to avoid those types of problems

ISOBuster also supports EMBR type drives.
--

Cheers,

DrT

** Stress - the condition brought about by having to
** resist the temptation to beat the living daylights
** out of someone who richly deserves it.

In case this was lost in the thread:
Can this overlap issue be fixed without deleting partition? If so, how?



"skipro" wrote in message news:5496@public.bootitbm...

Thanks.
I usually use BING[in past]/BIBM to work with partitions but I was in Win7
when it asked for more room, updating to Win8.
Can this overlap issue be fixed without deleting partition? If so, how?


"TeraByte Support (PP)" wrote in message news:5495@public.bootitbm...

Correct. If Windows can't see the partition it will assume the space is
unallocated and that it's available for use. If you don't expand the
partition into space occupied by another partition it won't overlap. Windows
will expand and shrink from the end of the partition.

When using EMBR type drives it's recommended to only use software that
supports EMBR (e.g. BIBM, IFW, IFL, IFD, TBOSDT) to avoid those types of
problems. Otherwise, what I usually do is make sure the partition being
modified is surrounded by other partitions (where applicable) so the
partitioning program knows the limits. This may require setting up a
temporary boot item or manually loading the MBR before making the changes.

skipro wrote:
> In case this was lost in the thread:
> Can this overlap issue be fixed without deleting partition? If so, how?

You're going to have to make partitioning changes to fix the problem. At least one of them will have to be removed. You might have been able to delete the second partition and then resize the first one to its original size (or smaller). After that undelete the second partition. In either case, note that the partition that was overlapped may have been corrupted.

I recommend creating a backup of a drive before making partitioning changes on it (assuming the contents are important).

On Fri, 17 May 2013 16:59:44 PDT, just as I was about to take a herb,
TeraByte Support(PP) disturbed my reverie and wrote:

>I recommend creating a backup of a drive before making partitioning changes on it (assuming the contents are important).

The only time I have come across this issue, using unlimited
primaries, is when another piece of software (yes Windows, I'm looking
at YOU) makes unexpected partition changes.
--

Cheers,

DrT

** Stress - the condition brought about by having to
** resist the temptation to beat the living daylights
** out of someone who richly deserves it.