Just found out about the 2 gig limit on dbx files, the hard way. Is there
an easy quick way to work arround this problem?

Did you lose messages? What exactly happened?
--
Bruce Hagen
MS MVP - Outlook Express
~IB-CA~

"Brett" wrote in message
...
Just found out about the 2 gig limit on dbx files, the hard way. Is there
an easy quick way to work arround this problem?

The dbx files should be keep under 100 MG.
Move email into user created folders.
Backup the dbx files and compact the OE folders while working offline.

No
There is no easy or quick fix.
--
Ron Sommer

"Brett" wrote in message
...
Just found out about the 2 gig limit on dbx files, the hard way. Is there
an easy quick way to work arround this problem?

Nothing showed in OE in the folder in question after the limit was hit.
The dbx was 2,097,000 bytes in size. Throwing it in a hex editor showed the
data was still there. I assume the file has an integer index in it that
overflows at 2 gig.

I found a tool with source that reads dbx's and dumps them to mbox format.
It also saw no messages. I then modified it to to use unsigned integers
rather than signed in order to double the number of ints available (assuming
the integer overflow) but also no luck. Was not worth spending more time on
this tract, so I purchased DBXpress, and 4 hours later had 12,000 + .msg
files, which I was able to import into smaller folders. The customer was
happy, but I was very preturbed at the lack of robustness displayed by the
dbx format.

Needless to say, MS should have a corrupt dbx recovery tool. From what I
have read the dbx structure is complete crap, and the people that designed
and approved the design should be taken out and be whipped, kicked, beaten,
strangled, stabbed, shot, then fed to rats, and then the rats need to be
shot.



"Bruce Hagen" wrote in message
...
Did you lose messages? What exactly happened?
--
Bruce Hagen
MS MVP - Outlook Express
~IB-CA~

"Brett" wrote in message
...
Just found out about the 2 gig limit on dbx files, the hard way. Is
there an easy quick way to work arround this problem?

The dbx file structure is exactly what you say. The next OS, Windows Vista,
will have a completely restructured e-mail client, Windows Mail. Alas, too
late for many.
--
Bruce Hagen
MS MVP - Outlook Express
~IB-CA~

"Brett" wrote in message
...
Nothing showed in OE in the folder in question after the limit was hit.
The dbx was 2,097,000 bytes in size. Throwing it in a hex editor showed
the data was still there. I assume the file has an integer index in it
that overflows at 2 gig.

I found a tool with source that reads dbx's and dumps them to mbox format.
It also saw no messages. I then modified it to to use unsigned integers
rather than signed in order to double the number of ints available
(assuming the integer overflow) but also no luck. Was not worth spending
more time on this tract, so I purchased DBXpress, and 4 hours later had
12,000 + .msg files, which I was able to import into smaller folders.
The customer was happy, but I was very preturbed at the lack of robustness
displayed by the dbx format.

Needless to say, MS should have a corrupt dbx recovery tool. From what I
have read the dbx structure is complete crap, and the people that designed
and approved the design should be taken out and be whipped, kicked,
beaten, strangled, stabbed, shot, then fed to rats, and then the rats need
to be shot.



"Bruce Hagen" wrote in message
...
Did you lose messages? What exactly happened?
--
Bruce Hagen
MS MVP - Outlook Express
~IB-CA~

"Brett" wrote in message
...
Just found out about the 2 gig limit on dbx files, the hard way. Is
there an easy quick way to work arround this problem?

"Brett" wrote in message
...

Needless to say, MS should have a corrupt dbx recovery tool. From what I
have read the dbx structure is complete crap, and the people that designed
and approved the design should be taken out and be whipped, kicked,
beaten, strangled, stabbed, shot, then fed to rats, and then the rats need
to be shot.


There is a rumor (and only that), that the designer of the DBX file
structure has since been confined to a "rubber room" where his/her cackling
can be heard in between episodes of beating his/her head against the walls.
vbg Most of us in these groups have contended the same thing in similar
fashion to MS but it's taken many years and now we're still told that it
will be changed in the next version of Windows but that's not much help to
those still using older operating systems who will not upgrade for economic
reasons, or just because they would rather have the devil they know than use
one they know nothing about.
--
Jim Pickering, MVP, Outlook Express
https://mvp.support.microsoft.com/pr...8-1171988A62D6
Please deliver feedback to the newsgroup, so that others can be helped.
Thanks.

"Brett" wrote in message
...
Nothing showed in OE in the folder in question after the limit was hit.
The dbx was 2,097,000 bytes in size. Throwing it in a hex editor showed
the data was still there. I assume the file has an integer index in it
that overflows at 2 gig.

I found a tool with source that reads dbx's and dumps them to mbox format.
It also saw no messages. I then modified it to to use unsigned integers
rather than signed in order to double the number of ints available
(assuming the integer overflow) but also no luck. Was not worth spending
more time on this tract, so I purchased DBXpress, and 4 hours later had
12,000 + .msg files, which I was able to import into smaller folders.
The customer was happy, but I was very preturbed at the lack of robustness
displayed by the dbx format.

Needless to say, MS should have a corrupt dbx recovery tool.

Its called DBXpress. G I'd be happy to sell them the exclusive
distributions rights for only 10 cents per Windows user. VBG

From what I have read the dbx structure is complete crap, and the people
that designed and approved the design should be taken out and be whipped,
kicked, beaten, strangled, stabbed, shot, then fed to rats, and then the
rats need to be shot.


This has already happened. Unfortunately the important part -- fixing the
actual problem -- hasn't yet occured. And won't until Vista.

I know more about the dbx file structure than anybody, but unfortunately
knowledge can come at a high price.

cheers,

steve




"Bruce Hagen" wrote in message
...
Did you lose messages? What exactly happened?
--
Bruce Hagen
MS MVP - Outlook Express
~IB-CA~

"Brett" wrote in message
...
Just found out about the 2 gig limit on dbx files, the hard way. Is
there an easy quick way to work arround this problem?