import 2GB PST from OL2000 into OL2003 UNICODE PST

[Kevin]

I have discovered too late that OL2000 SP-3 (9.0.0.8954), IMO - Security
Update, cannot handle PST files that approach the 2GB file size limitation
(my outlook.pst is 2,074,425 KB [Properties: 1.97 GB (2,124,211,200 bytes)])
and now am trying to recover from this MS design limitation that has
precipitated, w/o warning(s), an inability to access my stored e-mail
contacts, messages, ect.

If I get OL 2003 and install it on top of (or in place of, as the case may
be) my OL2000 installation, then try to import my old 2GB PST file into a
newly created UNICODE PST file in OL2003, will I meet with success, or, will
the operation fail because the old PST file already has issues ... vis-a-vis
the file size?

Background info about what I've tried so far:

I have experimented with MS' PST2GB.exe and have also tried 'Kernel for
Outlook Evaluation ver 7.02.01' and 'Stellar Phoenix Mailbox Professional -
2.0 (Demo Version)'.

The PST2GB solution is not appealing as I have found that a significant
chunk of data has to be cropped in order to get the file size down to a level
manageable by OL2000.
I tried cropping 1 MB then running the Inbox Repair Tool but the IRT added
8.5~MB to the truncated file, making it a fair bit larger than it was to
begin with, and, presumably un-useful.

The Kernel demo crashes while scanning (encryption error dialog - resolution
from their support people pending). FYI - to the best of my knowledge, I did
not ever specify Compressible Encryption for my 'outlook.pst', unless that it
is a retained setting (I did export a password-protected PST once) or a
default setting.

The Stellar demo installation routine required access to my Office 2000
Premium CD for 'required components' and wound up changing a registry setting
(HKEY_LOCAL_MACHINE\Software\Microsoft\Office\9.0\Outlook\Setup -
MailSupport) from IMO to CW (a problem I've since resolved by changing the
MailSupport setting from '1' to '0').
Upon launch of a Stellar scan, the Windows Installer was invoked again and
failed with a 'Microsoft Office 2000 SR-1 Premium' error dialog: "Error 1706.
No valid source could be found ... ", however, the scan progressed to
conclusion but with no recovered items displayed in the GUID. As Stellar
Support has yet to reply to my requests for support, I am unable to interpret
the results.

 

[DL]

All OL pst's prior to 2003 unicode have this well documented size
limitation.
If this was me I would create copies of the faulting pst to work on.
You can try OL 2003 with a unicode pst and import from your copy.
Though Import is not reccommended for transfering data between pst's
I assume you cannot open the pst to copy data across to the unicode pst, if
you can this is the prefered method.
I assume also that in OL2k you are unable to use the archive option.

I have discovered too late that OL2000 SP-3 (9.0.0.8954), IMO - Security
Update, cannot handle PST files that approach the 2GB file size limitation
(my outlook.pst is 2,074,425 KB [Properties: 1.97 GB (2,124,211,200 bytes)])
and now am trying to recover from this MS design limitation that has
precipitated, w/o warning(s), an inability to access my stored e-mail
contacts, messages, ect.

If I get OL 2003 and install it on top of (or in place of, as the case may
be) my OL2000 installation, then try to import my old 2GB PST file into a
newly created UNICODE PST file in OL2003, will I meet with success, or, will
the operation fail because the old PST file already has issues ... vis-a-vis
the file size?

Background info about what I've tried so far:

I have experimented with MS' PST2GB.exe and have also tried 'Kernel for
Outlook Evaluation ver 7.02.01' and 'Stellar Phoenix Mailbox Professional -
2.0 (Demo Version)'.

The PST2GB solution is not appealing as I have found that a significant
chunk of data has to be cropped in order to get the file size down to a level
manageable by OL2000.
I tried cropping 1 MB then running the Inbox Repair Tool but the IRT added
8.5~MB to the truncated file, making it a fair bit larger than it was to
begin with, and, presumably un-useful.

The Kernel demo crashes while scanning (encryption error dialog - resolution
from their support people pending). FYI - to the best of my knowledge, I did
not ever specify Compressible Encryption for my 'outlook.pst', unless that it
is a retained setting (I did export a password-protected PST once) or a
default setting.

The Stellar demo installation routine required access to my Office 2000
Premium CD for 'required components' and wound up changing a registry setting
(HKEY_LOCAL_MACHINE\Software\Microsoft\Office\9.0\Outlook\Setup -
MailSupport) from IMO to CW (a problem I've since resolved by changing the
MailSupport setting from '1' to '0').
Upon launch of a Stellar scan, the Windows Installer was invoked again and
failed with a 'Microsoft Office 2000 SR-1 Premium' error dialog: "Error 1706.
No valid source could be found ... ", however, the scan progressed to
conclusion but with no recovered items displayed in the GUID. As Stellar
Support has yet to reply to my requests for support, I am unable to interpret
the results.

 

[Kevin]

DL ... thanks for helping out ... I have created copies of the faulting pst
to work on and your assumptions are all correct. MS says OL2000 updates
SR-1, SR-1a prevent the user from going above a 2GB pst - I have updated to
SP-3 and I can say that is just not the case.

Should I expect that OL2003 will be able to open my faulting OL2000 pst if I
leave it in its' normally installed location? IOW, wherein lies the 2GB
limitation - in the old pst file structure itself, or, in the OL2000
application?

You see, I hadn't planned on shelling out for Office 2003 as I don't really
need it otherwise. If there are any confirmed successes of opening (or,
alternatively, importing - my understanding is that some specific data types
are lost using import so this is the less attractive option) the old pst
in(to) OL2000, then I would gladly bear the expense (at this point) to
recover my e-mails, ect. going back to 1996.

All OL pst's prior to 2003 unicode have this well documented size
limitation.
If this was me I would create copies of the faulting pst to work on.
You can try OL 2003 with a unicode pst and import from your copy.
Though Import is not reccommended for transfering data between pst's
I assume you cannot open the pst to copy data across to the unicode pst, if
you can this is the prefered method.
I assume also that in OL2k you are unable to use the archive option.

I have discovered too late that OL2000 SP-3 (9.0.0.8954), IMO - Security
Update, cannot handle PST files that approach the 2GB file size limitation
(my outlook.pst is 2,074,425 KB [Properties: 1.97 GB (2,124,211,200 bytes)])
and now am trying to recover from this MS design limitation that has
precipitated, w/o warning(s), an inability to access my stored e-mail
contacts, messages, ect.

If I get OL 2003 and install it on top of (or in place of, as the case may
be) my OL2000 installation, then try to import my old 2GB PST file into a
newly created UNICODE PST file in OL2003, will I meet with success, or, will
the operation fail because the old PST file already has issues ... vis-a-vis
the file size?

Background info about what I've tried so far:

I have experimented with MS' PST2GB.exe and have also tried 'Kernel for
Outlook Evaluation ver 7.02.01' and 'Stellar Phoenix Mailbox Professional -
2.0 (Demo Version)'.

The PST2GB solution is not appealing as I have found that a significant
chunk of data has to be cropped in order to get the file size down to a level
manageable by OL2000.
I tried cropping 1 MB then running the Inbox Repair Tool but the IRT added
8.5~MB to the truncated file, making it a fair bit larger than it was to
begin with, and, presumably un-useful.

The Kernel demo crashes while scanning (encryption error dialog - resolution
from their support people pending). FYI - to the best of my knowledge, I did
not ever specify Compressible Encryption for my 'outlook.pst', unless that it
is a retained setting (I did export a password-protected PST once) or a
default setting.

The Stellar demo installation routine required access to my Office 2000
Premium CD for 'required components' and wound up changing a registry setting
(HKEY_LOCAL_MACHINE\Software\Microsoft\Office\9.0\Outlook\Setup -
MailSupport) from IMO to CW (a problem I've since resolved by changing the
MailSupport setting from '1' to '0').
Upon launch of a Stellar scan, the Windows Installer was invoked again and
failed with a 'Microsoft Office 2000 SR-1 Premium' error dialog: "Error 1706.
No valid source could be found ... ", however, the scan progressed to
conclusion but with no recovered items displayed in the GUID. As Stellar
Support has yet to reply to my requests for support, I am unable to interpret
the results.

 

[Kevin]

my last post has a typo in the last paragraph:
"the old pst in(to) OL2003"

All OL pst's prior to 2003 unicode have this well documented size
limitation.
If this was me I would create copies of the faulting pst to work on.
You can try OL 2003 with a unicode pst and import from your copy.
Though Import is not reccommended for transfering data between pst's
I assume you cannot open the pst to copy data across to the unicode pst, if
you can this is the prefered method.
I assume also that in OL2k you are unable to use the archive option.

I have discovered too late that OL2000 SP-3 (9.0.0.8954), IMO - Security
Update, cannot handle PST files that approach the 2GB file size limitation
(my outlook.pst is 2,074,425 KB [Properties: 1.97 GB (2,124,211,200 bytes)])
and now am trying to recover from this MS design limitation that has
precipitated, w/o warning(s), an inability to access my stored e-mail
contacts, messages, ect.

If I get OL 2003 and install it on top of (or in place of, as the case may
be) my OL2000 installation, then try to import my old 2GB PST file into a
newly created UNICODE PST file in OL2003, will I meet with success, or, will
the operation fail because the old PST file already has issues ... vis-a-vis
the file size?

Background info about what I've tried so far:

I have experimented with MS' PST2GB.exe and have also tried 'Kernel for
Outlook Evaluation ver 7.02.01' and 'Stellar Phoenix Mailbox Professional -
2.0 (Demo Version)'.

The PST2GB solution is not appealing as I have found that a significant
chunk of data has to be cropped in order to get the file size down to a level
manageable by OL2000.
I tried cropping 1 MB then running the Inbox Repair Tool but the IRT added
8.5~MB to the truncated file, making it a fair bit larger than it was to
begin with, and, presumably un-useful.

The Kernel demo crashes while scanning (encryption error dialog - resolution
from their support people pending). FYI - to the best of my knowledge, I did
not ever specify Compressible Encryption for my 'outlook.pst', unless that it
is a retained setting (I did export a password-protected PST once) or a
default setting.

The Stellar demo installation routine required access to my Office 2000
Premium CD for 'required components' and wound up changing a registry setting
(HKEY_LOCAL_MACHINE\Software\Microsoft\Office\9.0\Outlook\Setup -
MailSupport) from IMO to CW (a problem I've since resolved by changing the
MailSupport setting from '1' to '0').
Upon launch of a Stellar scan, the Windows Installer was invoked again and
failed with a 'Microsoft Office 2000 SR-1 Premium' error dialog: "Error 1706.
No valid source could be found ... ", however, the scan progressed to
conclusion but with no recovered items displayed in the GUID. As Stellar
Support has yet to reply to my requests for support, I am unable to interpret
the results.

 

[DL]

Its immaterial as to the sp version, its a limitation, I believe solely, of
the pst structure.

If you cannot start/open OL2k when connected to this pst then I believe if
you connect this pst to an OL2003 installation you will have the same
problem. The size causes corruption of the pst, which may prevent any OL
vesrion opening/accessing it.
If the pst is corrupt then importing to an unicode pst will likely fail, or
at best result in data loss.
Its immaterial as to the location of the pst (other than being on a hd)

I have to assume that you never used the archive option, nor have any
earlier data backups, which is any 'case playing with fire.'

There are third party companies, I believe, that specialise in recovering
corrupt pst files. Only you know whether the expense would be warranted, as
apposed to using the MS Crop tool.

DL ... thanks for helping out ... I have created copies of the faulting pst
to work on and your assumptions are all correct. MS says OL2000 updates
SR-1, SR-1a prevent the user from going above a 2GB pst - I have updated to
SP-3 and I can say that is just not the case.

Should I expect that OL2003 will be able to open my faulting OL2000 pst if I
leave it in its' normally installed location? IOW, wherein lies the 2GB
limitation - in the old pst file structure itself, or, in the OL2000
application?

You see, I hadn't planned on shelling out for Office 2003 as I don't really
need it otherwise. If there are any confirmed successes of opening (or,
alternatively, importing - my understanding is that some specific data types
are lost using import so this is the less attractive option) the old pst
in(to) OL2000, then I would gladly bear the expense (at this point) to
recover my e-mails, ect. going back to 1996.

All OL pst's prior to 2003 unicode have this well documented size
limitation.
If this was me I would create copies of the faulting pst to work on.
You can try OL 2003 with a unicode pst and import from your copy.
Though Import is not reccommended for transfering data between pst's
I assume you cannot open the pst to copy data across to the unicode pst, if
you can this is the prefered method.
I assume also that in OL2k you are unable to use the archive option.

I have discovered too late that OL2000 SP-3 (9.0.0.8954), IMO - Security
Update, cannot handle PST files that approach the 2GB file size limitation
(my outlook.pst is 2,074,425 KB [Properties: 1.97 GB (2,124,211,200 bytes)])
and now am trying to recover from this MS design limitation that has
precipitated, w/o warning(s), an inability to access my stored e-mail
contacts, messages, ect.

If I get OL 2003 and install it on top of (or in place of, as the case may
be) my OL2000 installation, then try to import my old 2GB PST file into a
newly created UNICODE PST file in OL2003, will I meet with success,

or,
will

the operation fail because the old PST file already has issues ... vis-a-vis
the file size?

Background info about what I've tried so far:

I have experimented with MS' PST2GB.exe and have also tried 'Kernel for
Outlook Evaluation ver 7.02.01' and 'Stellar Phoenix Mailbox Professional -
2.0 (Demo Version)'.

The PST2GB solution is not appealing as I have found that a significant
chunk of data has to be cropped in order to get the file size down to

a
level

manageable by OL2000.
I tried cropping 1 MB then running the Inbox Repair Tool but the IRT added
8.5~MB to the truncated file, making it a fair bit larger than it was to
begin with, and, presumably un-useful.

The Kernel demo crashes while scanning (encryption error dialog - resolution
from their support people pending). FYI - to the best of my

knowledge, I
did

not ever specify Compressible Encryption for my 'outlook.pst', unless

that
it

is a retained setting (I did export a password-protected PST once) or a
default setting.

The Stellar demo installation routine required access to my Office 2000
Premium CD for 'required components' and wound up changing a registry setting
(HKEY_LOCAL_MACHINE\Software\Microsoft\Office\9.0\Outlook\Setup -
MailSupport) from IMO to CW (a problem I've since resolved by changing the
MailSupport setting from '1' to '0').
Upon launch of a Stellar scan, the Windows Installer was invoked again and
failed with a 'Microsoft Office 2000 SR-1 Premium' error dialog:

"Error
1706.

No valid source could be found ... ", however, the scan progressed to
conclusion but with no recovered items displayed in the GUID. As Stellar
Support has yet to reply to my requests for support, I am unable to interpret
the results.

 

[Kevin]

Reply to DL's 2/18/2007 3:35 PM PST post

DL ... thanks again for helping out ...

Your insights on my proposed use of OL2003 are helpful and I thank you for
illuminating the subject as best you were able ... I have decided to next
finish trying 3rd party software solutions and have support requests in with
Kernel and Stellar to see about exhausting those routes (more info about the
problems encountered with each in my earlier posts). Beyond that, if
required, I will still try OL2003 and will post back here with my results as
I progress.

You are correct in your assumption that I never used the archive option (I
like[d] the convenience of being able to instantly access e-mails going all
the way back to 1996 and had assumed the archiving of e-mail would make easy
referencing back to items problematic - would it?).

I do have a complete C:\ drive image from last April that will save me from
a worst case scenario loss of e-mails from APR06 going back to 1996, so, yes,
I do have a backup of the pst file, just not a very current one.

Which brings up this notion: I have been unable to determine for myself in
what manner the PST2GB crop tool truncates the pst data. Does it crop the
earliest items or the most recent items or does it crop the data according to
some other variable(s)?

Also, if you don't mind and can think of the names of the third party
companies (if different from Kernel or Stellar as I have mentioned earlier)
that specialise in recovering corrupt pst files that you mention in your last
post, please, by all means, let me know.

Thanks again for all the help DL ... Kevin

:

Its immaterial as to the sp version, its a limitation, I believe solely, of
the pst structure.

If you cannot start/open OL2k when connected to this pst then I believe if
you connect this pst to an OL2003 installation you will have the same
problem. The size causes corruption of the pst, which may prevent any OL
vesrion opening/accessing it.
If the pst is corrupt then importing to an unicode pst will likely fail, or
at best result in data loss.
Its immaterial as to the location of the pst (other than being on a hd)

I have to assume that you never used the archive option, nor have any
earlier data backups, which is any 'case playing with fire.'

There are third party companies, I believe, that specialise in recovering
corrupt pst files. Only you know whether the expense would be warranted, as
apposed to using the MS Crop tool.

my last post has a typo in the last paragraph:
"the old pst in(to) OL2003"

All OL pst's prior to 2003 unicode have this well documented size
limitation.
If this was me I would create copies of the faulting pst to work on.
You can try OL 2003 with a unicode pst and import from your copy.
Though Import is not reccommended for transfering data between pst's
I assume you cannot open the pst to copy data across to the unicode pst, if
you can this is the prefered method.
I assume also that in OL2k you are unable to use the archive option.

I have discovered too late that OL2000 SP-3 (9.0.0.8954), IMO - Security
Update, cannot handle PST files that approach the 2GB file size limitation
(my outlook.pst is 2,074,425 KB [Properties: 1.97 GB (2,124,211,200 bytes)])
and now am trying to recover from this MS design limitation that has
precipitated, w/o warning(s), an inability to access my stored e-mail
contacts, messages, ect.

If I get OL 2003 and install it on top of (or in place of, as the case may
be) my OL2000 installation, then try to import my old 2GB PST file into a
newly created UNICODE PST file in OL2003, will I meet with success, or, will
the operation fail because the old PST file already has issues ... vis-a-vis
the file size?

Background info about what I've tried so far:

I have experimented with MS' PST2GB.exe and have also tried 'Kernel for
Outlook Evaluation ver 7.02.01' and 'Stellar Phoenix Mailbox Professional -
2.0 (Demo Version)'.

The PST2GB solution is not appealing as I have found that a significant
chunk of data has to be cropped in order to get the file size down to a level
manageable by OL2000.
I tried cropping 1 MB then running the Inbox Repair Tool but the IRT added
8.5~MB to the truncated file, making it a fair bit larger than it was to
begin with, and, presumably un-useful.

The Kernel demo crashes while scanning (encryption error dialog - resolution
from their support people pending). FYI - to the best of my knowledge, I did
not ever specify Compressible Encryption for my 'outlook.pst', unless that it
is a retained setting (I did export a password-protected PST once) or a
default setting.

The Stellar demo installation routine required access to my Office 2000
Premium CD for 'required components' and wound up changing a registry setting
(HKEY_LOCAL_MACHINE\Software\Microsoft\Office\9.0\Outlook\Setup -
MailSupport) from IMO to CW (a problem I've since resolved by changing the
MailSupport setting from '1' to '0').
Upon launch of a Stellar scan, the Windows Installer was invoked again and
failed with a 'Microsoft Office 2000 SR-1 Premium' error dialog: "Error 1706.
No valid source could be found ... ", however, the scan progressed to
conclusion but with no recovered items displayed in the GUID. As Stellar
Support has yet to reply to my requests for support, I am unable to interpret
the results.

 

[Alan]

Hi,

You can try our product Advanced Outlook Repair to repair your PST
file. It is a powerful tool to recover messages and other objects from
corrupt or damaged Microsoft Outlook PST files. It can also split the
output PST file into several small ones if the original PST file is
oversized.

Please visit http://www.datanumen.com/aor/index.htm for detailed
information about Advanced Outlook Repair.

And you can also download a free demo version at http://www.datanumen.com/aor/aor.exe

Alan Chen
DataNumen, Inc. - World leader in data recovery technologies
Website: http://www.datanumen.com
Fax: +1-800-9917-FAX (US Toll-Free), +852-31829286 (HONG KONG)

Reply to DL's 2/18/2007 3:35 PM PST post

DL ... thanks again for helping out ...

Your insights on my proposed use of OL2003 are helpful and I thank you for
illuminating the subject as best you were able ... I have decided to next
finish trying 3rd party software solutions and have support requests in with
Kernel and Stellar to see about exhausting those routes (more info about the
problems encountered with each in my earlier posts). Beyond that, if
required, I will still try OL2003 and will post back here with my results as
I progress.

You are correct in your assumption that I never used the archive option (I
like[d] the convenience of being able to instantly access e-mails going all
the way back to 1996 and had assumed the archiving of e-mail would make easy
referencing back to items problematic - would it?).

I do have a complete C:\ drive image from last April that will save me from
a worst case scenario loss of e-mails from APR06 going back to 1996, so, yes,
I do have a backup of the pst file, just not a very current one.

Which brings up this notion: I have been unable to determine for myself in
what manner the PST2GB crop tool truncates the pst data. Does it crop the
earliest items or the most recent items or does it crop the data according to
some other variable(s)?

Also, if you don't mind and can think of the names of the third party
companies (if different from Kernel or Stellar as I have mentioned earlier)
that specialise in recoveringcorrupt pstfiles that you mention in your last
post, please, by all means, let me know.

Thanks again for all the help DL ... Kevin

:

Its immaterial as to the sp version, its a limitation, I believe solely, of
the pst structure.

If you cannot start/open OL2k when connected to this pst then I believe if
you connect this pst to an OL2003 installation you will have the same
problem. The size causes corruption of the pst, which may prevent any OL
vesrion opening/accessing it.
If the pst is corrupt then importing to an unicode pst will likely fail, or
at best result in data loss.
Its immaterial as to the location of the pst (other than being on a hd)

I have to assume that you never used the archive option, nor have any
earlier data backups, which is any 'case playing with fire.'

There are third party companies, I believe, that specialise in recoveringcorrupt pstfiles. Only you know whether the expense would be warranted, as
apposed to using the MS Crop tool.

my last post has a typo in the last paragraph:
"the old pst in(to) OL2003"

All OL pst's prior to 2003 unicode have this well documented size
limitation.
If this was me I would create copies of the faulting pst to work on.
You can try OL 2003 with a unicode pst and import from your copy.
Though Import is not reccommended for transfering data between pst's
I assume you cannot open the pst to copy data across to the unicode pst, if
you can this is the prefered method.
I assume also that in OL2k you are unable to use the archive option.
I have discovered too late that OL2000 SP-3 (9.0.0.8954), IMO - Security
Update, cannot handle PST files that approach the 2GB file size limitation
(my outlook.pst is 2,074,425 KB [Properties: 1.97 GB (2,124,211,200
bytes)])
and now am trying to recover from this MS design limitation that has
precipitated, w/o warning(s), an inability to access my stored e-mail
contacts, messages, ect.
If I get OL 2003 and install it on top of (or in place of, as the case may
be) my OL2000 installation, then try to import my old 2GB PST file into a
newly created UNICODE PST file in OL2003, will I meet with success, or,
will
the operation fail because the old PST file already has issues ...
vis-a-vis
the file size?
Background info about what I've tried so far:
I have experimented with MS' PST2GB.exe and have also tried 'Kernel for
Outlook Evaluation ver 7.02.01' and 'Stellar Phoenix Mailbox
Professional -
2.0 (Demo Version)'.
The PST2GB solution is not appealing as I have found that a significant
chunk of data has to be cropped in order to get the file size down to a
level
manageable by OL2000.
I tried cropping 1 MB then running the Inbox Repair Tool but the IRT added
8.5~MB to the truncated file, making it a fair bit larger than it was to
begin with, and, presumably un-useful.
The Kernel demo crashes while scanning (encryption error dialog -
resolution
from their support people pending). FYI - to the best of my knowledge, I
did
not ever specify Compressible Encryption for my 'outlook.pst', unless that
it
is a retained setting (I did export a password-protected PST once) or a
default setting.
The Stellar demo installation routine required access to my Office 2000
Premium CD for 'required components' and wound up changing a registry
setting
(HKEY_LOCAL_MACHINE\Software\Microsoft\Office\9.0\Outlook\Setup -
MailSupport) from IMO to CW (a problem I've since resolved by changing the
MailSupport setting from '1' to '0').
Upon launch of a Stellar scan, the Windows Installer was invoked again and
failed with a 'Microsoft Office 2000 SR-1 Premium' error dialog: "Error
1706.
No valid source could be found ... ", however, the scan progressed to
conclusion but with no recovered items displayed in the GUID. As Stellar
Support has yet to reply to my requests for support, I am unable to
interpret
the results.- Hide quoted text -

- Show quoted text -

 

[DL]

Depending how you configure Archive it removes mail from the default pst to
a seperate pst.
You can have multiple pst's open within OL, and since the archive is simply
a pst you would still have access.

Personally I archive to a year specific archive pst, eg Archive2001,
Archive2002 etc

Reply to DL's 2/18/2007 3:35 PM PST post

DL ... thanks again for helping out ...

Your insights on my proposed use of OL2003 are helpful and I thank you for
illuminating the subject as best you were able ... I have decided to next
finish trying 3rd party software solutions and have support requests in with
Kernel and Stellar to see about exhausting those routes (more info about the
problems encountered with each in my earlier posts). Beyond that, if
required, I will still try OL2003 and will post back here with my results as
I progress.

You are correct in your assumption that I never used the archive option (I
like[d] the convenience of being able to instantly access e-mails going all
the way back to 1996 and had assumed the archiving of e-mail would make easy
referencing back to items problematic - would it?).

I do have a complete C:\ drive image from last April that will save me from
a worst case scenario loss of e-mails from APR06 going back to 1996, so, yes,
I do have a backup of the pst file, just not a very current one.

Which brings up this notion: I have been unable to determine for myself in
what manner the PST2GB crop tool truncates the pst data. Does it crop the
earliest items or the most recent items or does it crop the data according to
some other variable(s)?

Also, if you don't mind and can think of the names of the third party
companies (if different from Kernel or Stellar as I have mentioned earlier)
that specialise in recovering corrupt pst files that you mention in your last
post, please, by all means, let me know.

Thanks again for all the help DL ... Kevin

:

Its immaterial as to the sp version, its a limitation, I believe solely, of
the pst structure.

If you cannot start/open OL2k when connected to this pst then I believe if
you connect this pst to an OL2003 installation you will have the same
problem. The size causes corruption of the pst, which may prevent any OL
vesrion opening/accessing it.
If the pst is corrupt then importing to an unicode pst will likely fail, or
at best result in data loss.
Its immaterial as to the location of the pst (other than being on a hd)

I have to assume that you never used the archive option, nor have any
earlier data backups, which is any 'case playing with fire.'

There are third party companies, I believe, that specialise in recovering
corrupt pst files. Only you know whether the expense would be warranted, as
apposed to using the MS Crop tool.

my last post has a typo in the last paragraph:
"the old pst in(to) OL2003"

All OL pst's prior to 2003 unicode have this well documented size
limitation.
If this was me I would create copies of the faulting pst to work on.
You can try OL 2003 with a unicode pst and import from your copy.
Though Import is not reccommended for transfering data between pst's
I assume you cannot open the pst to copy data across to the unicode pst, if
you can this is the prefered method.
I assume also that in OL2k you are unable to use the archive option.

I have discovered too late that OL2000 SP-3 (9.0.0.8954), IMO - Security
Update, cannot handle PST files that approach the 2GB file size limitation
(my outlook.pst is 2,074,425 KB [Properties: 1.97 GB (2,124,211,200
bytes)])
and now am trying to recover from this MS design limitation that has
precipitated, w/o warning(s), an inability to access my stored e-mail
contacts, messages, ect.

If I get OL 2003 and install it on top of (or in place of, as the case may
be) my OL2000 installation, then try to import my old 2GB PST file into a
newly created UNICODE PST file in OL2003, will I meet with success, or,
will
the operation fail because the old PST file already has issues ...
vis-a-vis
the file size?

Background info about what I've tried so far:

I have experimented with MS' PST2GB.exe and have also tried 'Kernel for
Outlook Evaluation ver 7.02.01' and 'Stellar Phoenix Mailbox
Professional -
2.0 (Demo Version)'.

The PST2GB solution is not appealing as I have found that a significant
chunk of data has to be cropped in order to get the file size down to a
level
manageable by OL2000.
I tried cropping 1 MB then running the Inbox Repair Tool but the IRT added
8.5~MB to the truncated file, making it a fair bit larger than it was to
begin with, and, presumably un-useful.

The Kernel demo crashes while scanning (encryption error dialog -
resolution
from their support people pending). FYI - to the best of my knowledge, I
did
not ever specify Compressible Encryption for my 'outlook.pst', unless that
it
is a retained setting (I did export a password-protected PST once) or a
default setting.

The Stellar demo installation routine required access to my Office 2000
Premium CD for 'required components' and wound up changing a registry
setting
(HKEY_LOCAL_MACHINE\Software\Microsoft\Office\9.0\Outlook\Setup -
MailSupport) from IMO to CW (a problem I've since resolved by changing the
MailSupport setting from '1' to '0').
Upon launch of a Stellar scan, the Windows Installer was invoked again and
failed with a 'Microsoft Office 2000 SR-1 Premium' error dialog: "Error
1706.
No valid source could be found ... ", however, the scan progressed to
conclusion but with no recovered items displayed in the GUID. As Stellar
Support has yet to reply to my requests for support, I am unable to
interpret
the results.

 

[Kevin]

Thank you very much for the input Alan ... I'll give your s/w a look ... I'm
just curious though, if the old adage 'you get what you pay for' holds true
in the realm of s/w, what makes your s/w worth $120.95 more than Stellar
Phoenix and $200.95USD more than Nucleus / Kernel?

Hi,

You can try our product Advanced Outlook Repair to repair your PST
file. It is a powerful tool to recover messages and other objects from
corrupt or damaged Microsoft Outlook PST files. It can also split the
output PST file into several small ones if the original PST file is
oversized.

Please visit http://www.datanumen.com/aor/index.htm for detailed
information about Advanced Outlook Repair.

And you can also download a free demo version at http://www.datanumen.com/aor/aor.exe

Alan Chen
DataNumen, Inc. - World leader in data recovery technologies
Website: http://www.datanumen.com
Fax: +1-800-9917-FAX (US Toll-Free), +852-31829286 (HONG KONG)

Reply to DL's 2/18/2007 3:35 PM PST post

DL ... thanks again for helping out ...

Your insights on my proposed use of OL2003 are helpful and I thank you for
illuminating the subject as best you were able ... I have decided to next
finish trying 3rd party software solutions and have support requests in with
Kernel and Stellar to see about exhausting those routes (more info about the
problems encountered with each in my earlier posts). Beyond that, if
required, I will still try OL2003 and will post back here with my results as
I progress.

You are correct in your assumption that I never used the archive option (I
like[d] the convenience of being able to instantly access e-mails going all
the way back to 1996 and had assumed the archiving of e-mail would make easy
referencing back to items problematic - would it?).

I do have a complete C:\ drive image from last April that will save me from
a worst case scenario loss of e-mails from APR06 going back to 1996, so, yes,
I do have a backup of the pst file, just not a very current one.

Which brings up this notion: I have been unable to determine for myself in
what manner the PST2GB crop tool truncates the pst data. Does it crop the
earliest items or the most recent items or does it crop the data according to
some other variable(s)?

Also, if you don't mind and can think of the names of the third party
companies (if different from Kernel or Stellar as I have mentioned earlier)
that specialise in recoveringcorrupt pstfiles that you mention in your last
post, please, by all means, let me know.

Thanks again for all the help DL ... Kevin

:

Its immaterial as to the sp version, its a limitation, I believe solely, of
the pst structure.

If you cannot start/open OL2k when connected to this pst then I believe if
you connect this pst to an OL2003 installation you will have the same
problem. The size causes corruption of the pst, which may prevent any OL
vesrion opening/accessing it.
If the pst is corrupt then importing to an unicode pst will likely fail, or
at best result in data loss.
Its immaterial as to the location of the pst (other than being on a hd)

I have to assume that you never used the archive option, nor have any
earlier data backups, which is any 'case playing with fire.'

There are third party companies, I believe, that specialise in recoveringcorrupt pstfiles. Only you know whether the expense would be warranted, as
apposed to using the MS Crop tool.

my last post has a typo in the last paragraph:
"the old pst in(to) OL2003"

"DL" wrote:

All OL pst's prior to 2003 unicode have this well documented size
limitation.
If this was me I would create copies of the faulting pst to work on.
You can try OL 2003 with a unicode pst and import from your copy.
Though Import is not reccommended for transfering data between pst's
I assume you cannot open the pst to copy data across to the unicode pst, if
you can this is the prefered method.
I assume also that in OL2k you are unable to use the archive option.

I have discovered too late that OL2000 SP-3 (9.0.0.8954), IMO - Security
Update, cannot handle PST files that approach the 2GB file size limitation
(my outlook.pst is 2,074,425 KB [Properties: 1.97 GB (2,124,211,200
bytes)])
and now am trying to recover from this MS design limitation that has
precipitated, w/o warning(s), an inability to access my stored e-mail
contacts, messages, ect.

If I get OL 2003 and install it on top of (or in place of, as the case may
be) my OL2000 installation, then try to import my old 2GB PST file into a
newly created UNICODE PST file in OL2003, will I meet with success, or,
will
the operation fail because the old PST file already has issues ...
vis-a-vis
the file size?

Background info about what I've tried so far:

I have experimented with MS' PST2GB.exe and have also tried 'Kernel for
Outlook Evaluation ver 7.02.01' and 'Stellar Phoenix Mailbox
Professional -
2.0 (Demo Version)'.

The PST2GB solution is not appealing as I have found that a significant
chunk of data has to be cropped in order to get the file size down to a
level
manageable by OL2000.
I tried cropping 1 MB then running the Inbox Repair Tool but the IRT added
8.5~MB to the truncated file, making it a fair bit larger than it was to
begin with, and, presumably un-useful.

The Kernel demo crashes while scanning (encryption error dialog -
resolution
from their support people pending). FYI - to the best of my knowledge, I
did
not ever specify Compressible Encryption for my 'outlook.pst', unless that
it
is a retained setting (I did export a password-protected PST once) or a
default setting.

The Stellar demo installation routine required access to my Office 2000
Premium CD for 'required components' and wound up changing a registry
setting
(HKEY_LOCAL_MACHINE\Software\Microsoft\Office\9.0\Outlook\Setup -
MailSupport) from IMO to CW (a problem I've since resolved by changing the
MailSupport setting from '1' to '0').
Upon launch of a Stellar scan, the Windows Installer was invoked again and
failed with a 'Microsoft Office 2000 SR-1 Premium' error dialog: "Error
1706.
No valid source could be found ... ", however, the scan progressed to
conclusion but with no recovered items displayed in the GUID. As Stellar
Support has yet to reply to my requests for support, I am unable to
interpret
the results.- Hide quoted text -

- Show quoted text -

 

[Kevin]

Thanks DL ... I guess once I get sorted out (resolution to my dilema
pending), I better start looking into archiving - your method strikes me as a
good one. That and the discarding of a lot of UFI that I've been hanging on
to.
Did you happen to have any opinion as to what MS' PST2GB cropping tool does
to the pst file? Whether it crops old vs. recent items, or, crops the file
according to some other variable(s)?
Thanks again for the help.

Depending how you configure Archive it removes mail from the default pst to
a seperate pst.
You can have multiple pst's open within OL, and since the archive is simply
a pst you would still have access.

Personally I archive to a year specific archive pst, eg Archive2001,
Archive2002 etc

Reply to DL's 2/18/2007 3:35 PM PST post

DL ... thanks again for helping out ...

Your insights on my proposed use of OL2003 are helpful and I thank you for
illuminating the subject as best you were able ... I have decided to next
finish trying 3rd party software solutions and have support requests in with
Kernel and Stellar to see about exhausting those routes (more info about the
problems encountered with each in my earlier posts). Beyond that, if
required, I will still try OL2003 and will post back here with my results as
I progress.

You are correct in your assumption that I never used the archive option (I
like[d] the convenience of being able to instantly access e-mails going all
the way back to 1996 and had assumed the archiving of e-mail would make easy
referencing back to items problematic - would it?).

I do have a complete C:\ drive image from last April that will save me from
a worst case scenario loss of e-mails from APR06 going back to 1996, so, yes,
I do have a backup of the pst file, just not a very current one.

Which brings up this notion: I have been unable to determine for myself in
what manner the PST2GB crop tool truncates the pst data. Does it crop the
earliest items or the most recent items or does it crop the data according to
some other variable(s)?

Also, if you don't mind and can think of the names of the third party
companies (if different from Kernel or Stellar as I have mentioned earlier)
that specialise in recovering corrupt pst files that you mention in your last
post, please, by all means, let me know.

Thanks again for all the help DL ... Kevin

:

Its immaterial as to the sp version, its a limitation, I believe solely, of
the pst structure.

If you cannot start/open OL2k when connected to this pst then I believe if
you connect this pst to an OL2003 installation you will have the same
problem. The size causes corruption of the pst, which may prevent any OL
vesrion opening/accessing it.
If the pst is corrupt then importing to an unicode pst will likely fail, or
at best result in data loss.
Its immaterial as to the location of the pst (other than being on a hd)

I have to assume that you never used the archive option, nor have any
earlier data backups, which is any 'case playing with fire.'

There are third party companies, I believe, that specialise in recovering
corrupt pst files. Only you know whether the expense would be warranted, as
apposed to using the MS Crop tool.

my last post has a typo in the last paragraph:
"the old pst in(to) OL2003"

:

All OL pst's prior to 2003 unicode have this well documented size
limitation.
If this was me I would create copies of the faulting pst to work on.
You can try OL 2003 with a unicode pst and import from your copy.
Though Import is not reccommended for transfering data between pst's
I assume you cannot open the pst to copy data across to the unicode pst, if
you can this is the prefered method.
I assume also that in OL2k you are unable to use the archive option.

I have discovered too late that OL2000 SP-3 (9.0.0.8954), IMO - Security
Update, cannot handle PST files that approach the 2GB file size limitation
(my outlook.pst is 2,074,425 KB [Properties: 1.97 GB (2,124,211,200
bytes)])
and now am trying to recover from this MS design limitation that has
precipitated, w/o warning(s), an inability to access my stored e-mail
contacts, messages, ect.

If I get OL 2003 and install it on top of (or in place of, as the case may
be) my OL2000 installation, then try to import my old 2GB PST file into a
newly created UNICODE PST file in OL2003, will I meet with success, or,
will
the operation fail because the old PST file already has issues ...
vis-a-vis
the file size?

Background info about what I've tried so far:

I have experimented with MS' PST2GB.exe and have also tried 'Kernel for
Outlook Evaluation ver 7.02.01' and 'Stellar Phoenix Mailbox
Professional -
2.0 (Demo Version)'.

The PST2GB solution is not appealing as I have found that a significant
chunk of data has to be cropped in order to get the file size down to a
level
manageable by OL2000.
I tried cropping 1 MB then running the Inbox Repair Tool but the IRT added
8.5~MB to the truncated file, making it a fair bit larger than it was to
begin with, and, presumably un-useful.

The Kernel demo crashes while scanning (encryption error dialog -
resolution
from their support people pending). FYI - to the best of my knowledge, I
did
not ever specify Compressible Encryption for my 'outlook.pst', unless that
it
is a retained setting (I did export a password-protected PST once) or a
default setting.

The Stellar demo installation routine required access to my Office 2000
Premium CD for 'required components' and wound up changing a registry
setting
(HKEY_LOCAL_MACHINE\Software\Microsoft\Office\9.0\Outlook\Setup -
MailSupport) from IMO to CW (a problem I've since resolved by changing the
MailSupport setting from '1' to '0').
Upon launch of a Stellar scan, the Windows Installer was invoked again and
failed with a 'Microsoft Office 2000 SR-1 Premium' error dialog: "Error
1706.
No valid source could be found ... ", however, the scan progressed to
conclusion but with no recovered items displayed in the GUID. As Stellar
Support has yet to reply to my requests for support, I am unable to
interpret
the results.

 

[DL]

I'm afraid I dont know the criteria that the crop tool uses to delete

Thanks DL ... I guess once I get sorted out (resolution to my dilema
pending), I better start looking into archiving - your method strikes me as a
good one. That and the discarding of a lot of UFI that I've been hanging on
to.
Did you happen to have any opinion as to what MS' PST2GB cropping tool does
to the pst file? Whether it crops old vs. recent items, or, crops the file
according to some other variable(s)?
Thanks again for the help.

Depending how you configure Archive it removes mail from the default pst to
a seperate pst.
You can have multiple pst's open within OL, and since the archive is simply
a pst you would still have access.

Personally I archive to a year specific archive pst, eg Archive2001,
Archive2002 etc

Reply to DL's 2/18/2007 3:35 PM PST post

DL ... thanks again for helping out ...

Your insights on my proposed use of OL2003 are helpful and I thank you for
illuminating the subject as best you were able ... I have decided to next
finish trying 3rd party software solutions and have support requests

in
with

Kernel and Stellar to see about exhausting those routes (more info

about
the

problems encountered with each in my earlier posts). Beyond that, if
required, I will still try OL2003 and will post back here with my

results
as

I progress.

You are correct in your assumption that I never used the archive option (I
like[d] the convenience of being able to instantly access e-mails

going
all

the way back to 1996 and had assumed the archiving of e-mail would

make
easy

referencing back to items problematic - would it?).

I do have a complete C:\ drive image from last April that will save me from
a worst case scenario loss of e-mails from APR06 going back to 1996,

so,
yes,

I do have a backup of the pst file, just not a very current one.

Which brings up this notion: I have been unable to determine for myself in
what manner the PST2GB crop tool truncates the pst data. Does it crop the
earliest items or the most recent items or does it crop the data

according
to

some other variable(s)?

Also, if you don't mind and can think of the names of the third party
companies (if different from Kernel or Stellar as I have mentioned earlier)
that specialise in recovering corrupt pst files that you mention in

your
last

post, please, by all means, let me know.

Thanks again for all the help DL ... Kevin

:

Its immaterial as to the sp version, its a limitation, I believe

solely,
of

the pst structure.

If you cannot start/open OL2k when connected to this pst then I believe if
you connect this pst to an OL2003 installation you will have the same
problem. The size causes corruption of the pst, which may prevent any OL
vesrion opening/accessing it.
If the pst is corrupt then importing to an unicode pst will likely

fail,
or

at best result in data loss.
Its immaterial as to the location of the pst (other than being on a hd)

I have to assume that you never used the archive option, nor have any
earlier data backups, which is any 'case playing with fire.'

There are third party companies, I believe, that specialise in recovering
corrupt pst files. Only you know whether the expense would be

warranted,
as

apposed to using the MS Crop tool.


:

my last post has a typo in the last paragraph:
"the old pst in(to) OL2003"

:

All OL pst's prior to 2003 unicode have this well documented size
limitation.
If this was me I would create copies of the faulting pst to work on.
You can try OL 2003 with a unicode pst and import from your copy.
Though Import is not reccommended for transfering data between pst's
I assume you cannot open the pst to copy data across to the

unicode
pst, if

you can this is the prefered method.
I assume also that in OL2k you are unable to use the archive option.

I have discovered too late that OL2000 SP-3 (9.0.0.8954), IMO - Security
Update, cannot handle PST files that approach the 2GB file size limitation
(my outlook.pst is 2,074,425 KB [Properties: 1.97 GB

(2,124,211,200

bytes)])
and now am trying to recover from this MS design limitation that has
precipitated, w/o warning(s), an inability to access my stored e-mail
contacts, messages, ect.

If I get OL 2003 and install it on top of (or in place of, as

the
case may

be) my OL2000 installation, then try to import my old 2GB PST

file
into a

newly created UNICODE PST file in OL2003, will I meet with

success,
or,

will
the operation fail because the old PST file already has issues ....
vis-a-vis
the file size?

Background info about what I've tried so far:

I have experimented with MS' PST2GB.exe and have also tried

'Kernel
for

Outlook Evaluation ver 7.02.01' and 'Stellar Phoenix Mailbox
Professional -
2.0 (Demo Version)'.

The PST2GB solution is not appealing as I have found that a significant
chunk of data has to be cropped in order to get the file size

down
to a

level
manageable by OL2000.
I tried cropping 1 MB then running the Inbox Repair Tool but the

IRT
added

8.5~MB to the truncated file, making it a fair bit larger than

it
was to

begin with, and, presumably un-useful.

The Kernel demo crashes while scanning (encryption error dialog -
resolution
from their support people pending). FYI - to the best of my knowledge, I
did
not ever specify Compressible Encryption for my 'outlook.pst', unless that
it
is a retained setting (I did export a password-protected PST

once)
or a

default setting.

The Stellar demo installation routine required access to my

Office
2000

Premium CD for 'required components' and wound up changing a registry
setting
(HKEY_LOCAL_MACHINE\Software\Microsoft\Office\9.0\Outlook\Setup -
MailSupport) from IMO to CW (a problem I've since resolved by changing the
MailSupport setting from '1' to '0').
Upon launch of a Stellar scan, the Windows Installer was invoked again and
failed with a 'Microsoft Office 2000 SR-1 Premium' error dialog: "Error
1706.
No valid source could be found ... ", however, the scan

progressed
to

conclusion but with no recovered items displayed in the GUID.

As
Stellar

Support has yet to reply to my requests for support, I am unable to
interpret
the results.

 

[Kevin]

OK then ... thanks DL ... I'll post back again with my OL2003 results ...
pending.

I'm afraid I dont know the criteria that the crop tool uses to delete

Thanks DL ... I guess once I get sorted out (resolution to my dilema
pending), I better start looking into archiving - your method strikes me as a
good one. That and the discarding of a lot of UFI that I've been hanging on
to.
Did you happen to have any opinion as to what MS' PST2GB cropping tool does
to the pst file? Whether it crops old vs. recent items, or, crops the file
according to some other variable(s)?
Thanks again for the help.

Depending how you configure Archive it removes mail from the default pst to
a seperate pst.
You can have multiple pst's open within OL, and since the archive is simply
a pst you would still have access.

Personally I archive to a year specific archive pst, eg Archive2001,
Archive2002 etc

Reply to DL's 2/18/2007 3:35 PM PST post

DL ... thanks again for helping out ...

Your insights on my proposed use of OL2003 are helpful and I thank you for
illuminating the subject as best you were able ... I have decided to next
finish trying 3rd party software solutions and have support requests in
with
Kernel and Stellar to see about exhausting those routes (more info about
the
problems encountered with each in my earlier posts). Beyond that, if
required, I will still try OL2003 and will post back here with my results
as
I progress.

You are correct in your assumption that I never used the archive option (I
like[d] the convenience of being able to instantly access e-mails going
all
the way back to 1996 and had assumed the archiving of e-mail would make
easy
referencing back to items problematic - would it?).

I do have a complete C:\ drive image from last April that will save me
from
a worst case scenario loss of e-mails from APR06 going back to 1996, so,
yes,
I do have a backup of the pst file, just not a very current one.

Which brings up this notion: I have been unable to determine for myself in
what manner the PST2GB crop tool truncates the pst data. Does it crop the
earliest items or the most recent items or does it crop the data according
to
some other variable(s)?

Also, if you don't mind and can think of the names of the third party
companies (if different from Kernel or Stellar as I have mentioned
earlier)
that specialise in recovering corrupt pst files that you mention in your
last
post, please, by all means, let me know.

Thanks again for all the help DL ... Kevin

:

Its immaterial as to the sp version, its a limitation, I believe solely,
of
the pst structure.

If you cannot start/open OL2k when connected to this pst then I believe if
you connect this pst to an OL2003 installation you will have the same
problem. The size causes corruption of the pst, which may prevent any OL
vesrion opening/accessing it.
If the pst is corrupt then importing to an unicode pst will likely fail,
or
at best result in data loss.
Its immaterial as to the location of the pst (other than being on a hd)

I have to assume that you never used the archive option, nor have any
earlier data backups, which is any 'case playing with fire.'

There are third party companies, I believe, that specialise in recovering
corrupt pst files. Only you know whether the expense would be warranted,
as
apposed to using the MS Crop tool.


:

my last post has a typo in the last paragraph:
"the old pst in(to) OL2003"

:

All OL pst's prior to 2003 unicode have this well documented size
limitation.
If this was me I would create copies of the faulting pst to work on.
You can try OL 2003 with a unicode pst and import from your copy.
Though Import is not reccommended for transfering data between pst's
I assume you cannot open the pst to copy data across to the unicode
pst, if
you can this is the prefered method.
I assume also that in OL2k you are unable to use the archive option.

I have discovered too late that OL2000 SP-3 (9.0.0.8954), IMO -
Security
Update, cannot handle PST files that approach the 2GB file size
limitation
(my outlook.pst is 2,074,425 KB [Properties: 1.97 GB (2,124,211,200

bytes)])
and now am trying to recover from this MS design limitation that has
precipitated, w/o warning(s), an inability to access my stored
e-mail
contacts, messages, ect.

If I get OL 2003 and install it on top of (or in place of, as the
case may
be) my OL2000 installation, then try to import my old 2GB PST file
into a
newly created UNICODE PST file in OL2003, will I meet with success,
or,
will
the operation fail because the old PST file already has issues ....
vis-a-vis
the file size?

Background info about what I've tried so far:

I have experimented with MS' PST2GB.exe and have also tried 'Kernel
for
Outlook Evaluation ver 7.02.01' and 'Stellar Phoenix Mailbox
Professional -
2.0 (Demo Version)'.

The PST2GB solution is not appealing as I have found that a
significant
chunk of data has to be cropped in order to get the file size down
to a
level
manageable by OL2000.
I tried cropping 1 MB then running the Inbox Repair Tool but the IRT
added
8.5~MB to the truncated file, making it a fair bit larger than it
was to
begin with, and, presumably un-useful.

The Kernel demo crashes while scanning (encryption error dialog -
resolution
from their support people pending). FYI - to the best of my
knowledge, I
did
not ever specify Compressible Encryption for my 'outlook.pst',
unless that
it
is a retained setting (I did export a password-protected PST once)
or a
default setting.

The Stellar demo installation routine required access to my Office
2000
Premium CD for 'required components' and wound up changing a
registry
setting
(HKEY_LOCAL_MACHINE\Software\Microsoft\Office\9.0\Outlook\Setup -
MailSupport) from IMO to CW (a problem I've since resolved by
changing the
MailSupport setting from '1' to '0').
Upon launch of a Stellar scan, the Windows Installer was invoked
again and
failed with a 'Microsoft Office 2000 SR-1 Premium' error dialog:
"Error
1706.
No valid source could be found ... ", however, the scan progressed
to
conclusion but with no recovered items displayed in the GUID. As
Stellar
Support has yet to reply to my requests for support, I am unable to
interpret
the results.

 

[Kevin]

Well DL ... and, for anyone else who may be following this thread ... OL2003
was not able to directly read or import my problematic (too big, therefore
corrupted) OL2000 pst file. The same error dialog suggesting the use of the
Inbox Repair Tool pops up either way. Was worth a shot.

I'm afraid I dont know the criteria that the crop tool uses to delete

Thanks DL ... I guess once I get sorted out (resolution to my dilema
pending), I better start looking into archiving - your method strikes me as a
good one. That and the discarding of a lot of UFI that I've been hanging on
to.
Did you happen to have any opinion as to what MS' PST2GB cropping tool does
to the pst file? Whether it crops old vs. recent items, or, crops the file
according to some other variable(s)?
Thanks again for the help.

Depending how you configure Archive it removes mail from the default pst to
a seperate pst.
You can have multiple pst's open within OL, and since the archive is simply
a pst you would still have access.

Personally I archive to a year specific archive pst, eg Archive2001,
Archive2002 etc

Reply to DL's 2/18/2007 3:35 PM PST post

DL ... thanks again for helping out ...

Your insights on my proposed use of OL2003 are helpful and I thank you for
illuminating the subject as best you were able ... I have decided to next
finish trying 3rd party software solutions and have support requests in
with
Kernel and Stellar to see about exhausting those routes (more info about
the
problems encountered with each in my earlier posts). Beyond that, if
required, I will still try OL2003 and will post back here with my results
as
I progress.

You are correct in your assumption that I never used the archive option (I
like[d] the convenience of being able to instantly access e-mails going
all
the way back to 1996 and had assumed the archiving of e-mail would make
easy
referencing back to items problematic - would it?).

I do have a complete C:\ drive image from last April that will save me
from
a worst case scenario loss of e-mails from APR06 going back to 1996, so,
yes,
I do have a backup of the pst file, just not a very current one.

Which brings up this notion: I have been unable to determine for myself in
what manner the PST2GB crop tool truncates the pst data. Does it crop the
earliest items or the most recent items or does it crop the data according
to
some other variable(s)?

Also, if you don't mind and can think of the names of the third party
companies (if different from Kernel or Stellar as I have mentioned
earlier)
that specialise in recovering corrupt pst files that you mention in your
last
post, please, by all means, let me know.

Thanks again for all the help DL ... Kevin

:

Its immaterial as to the sp version, its a limitation, I believe solely,
of
the pst structure.

If you cannot start/open OL2k when connected to this pst then I believe if
you connect this pst to an OL2003 installation you will have the same
problem. The size causes corruption of the pst, which may prevent any OL
vesrion opening/accessing it.
If the pst is corrupt then importing to an unicode pst will likely fail,
or
at best result in data loss.
Its immaterial as to the location of the pst (other than being on a hd)

I have to assume that you never used the archive option, nor have any
earlier data backups, which is any 'case playing with fire.'

There are third party companies, I believe, that specialise in recovering
corrupt pst files. Only you know whether the expense would be warranted,
as
apposed to using the MS Crop tool.


:

my last post has a typo in the last paragraph:
"the old pst in(to) OL2003"

:

All OL pst's prior to 2003 unicode have this well documented size
limitation.
If this was me I would create copies of the faulting pst to work on.
You can try OL 2003 with a unicode pst and import from your copy.
Though Import is not reccommended for transfering data between pst's
I assume you cannot open the pst to copy data across to the unicode
pst, if
you can this is the prefered method.
I assume also that in OL2k you are unable to use the archive option.

I have discovered too late that OL2000 SP-3 (9.0.0.8954), IMO -
Security
Update, cannot handle PST files that approach the 2GB file size
limitation
(my outlook.pst is 2,074,425 KB [Properties: 1.97 GB (2,124,211,200

bytes)])
and now am trying to recover from this MS design limitation that has
precipitated, w/o warning(s), an inability to access my stored
e-mail
contacts, messages, ect.

If I get OL 2003 and install it on top of (or in place of, as the
case may
be) my OL2000 installation, then try to import my old 2GB PST file
into a
newly created UNICODE PST file in OL2003, will I meet with success,
or,
will
the operation fail because the old PST file already has issues ....
vis-a-vis
the file size?

Background info about what I've tried so far:

I have experimented with MS' PST2GB.exe and have also tried 'Kernel
for
Outlook Evaluation ver 7.02.01' and 'Stellar Phoenix Mailbox
Professional -
2.0 (Demo Version)'.

The PST2GB solution is not appealing as I have found that a
significant
chunk of data has to be cropped in order to get the file size down
to a
level
manageable by OL2000.
I tried cropping 1 MB then running the Inbox Repair Tool but the IRT
added
8.5~MB to the truncated file, making it a fair bit larger than it
was to
begin with, and, presumably un-useful.

The Kernel demo crashes while scanning (encryption error dialog -
resolution
from their support people pending). FYI - to the best of my
knowledge, I
did
not ever specify Compressible Encryption for my 'outlook.pst',
unless that
it
is a retained setting (I did export a password-protected PST once)
or a
default setting.

The Stellar demo installation routine required access to my Office
2000
Premium CD for 'required components' and wound up changing a
registry
setting
(HKEY_LOCAL_MACHINE\Software\Microsoft\Office\9.0\Outlook\Setup -
MailSupport) from IMO to CW (a problem I've since resolved by
changing the
MailSupport setting from '1' to '0').
Upon launch of a Stellar scan, the Windows Installer was invoked
again and
failed with a 'Microsoft Office 2000 SR-1 Premium' error dialog:
"Error
1706.
No valid source could be found ... ", however, the scan progressed
to
conclusion but with no recovered items displayed in the GUID. As
Stellar
Support has yet to reply to my requests for support, I am unable to
interpret
the results.

 

[Marie]

Kevin, did you ever learn the answer to your question:

Did you happen to have any opinion as to what MS' PST2GB cropping tool does
to the pst file? Whether it crops old vs. recent items, or, crops the file
according to some other variable(s)?

I have to use the crop tool. I followed the whole thread--how did it work
for you?

Marie.

Thanks DL ... I guess once I get sorted out (resolution to my dilema
pending), I better start looking into archiving - your method strikes me as a
good one. That and the discarding of a lot of UFI that I've been hanging on
to.
Did you happen to have any opinion as to what MS' PST2GB cropping tool does
to the pst file? Whether it crops old vs. recent items, or, crops the file
according to some other variable(s)?
Thanks again for the help.

Depending how you configure Archive it removes mail from the default pst to
a seperate pst.
You can have multiple pst's open within OL, and since the archive is simply
a pst you would still have access.

Personally I archive to a year specific archive pst, eg Archive2001,
Archive2002 etc

Reply to DL's 2/18/2007 3:35 PM PST post

DL ... thanks again for helping out ...

Your insights on my proposed use of OL2003 are helpful and I thank you for
illuminating the subject as best you were able ... I have decided to next
finish trying 3rd party software solutions and have support requests in with
Kernel and Stellar to see about exhausting those routes (more info about the
problems encountered with each in my earlier posts). Beyond that, if
required, I will still try OL2003 and will post back here with my results as
I progress.

You are correct in your assumption that I never used the archive option (I
like[d] the convenience of being able to instantly access e-mails going all
the way back to 1996 and had assumed the archiving of e-mail would make easy
referencing back to items problematic - would it?).

I do have a complete C:\ drive image from last April that will save me from
a worst case scenario loss of e-mails from APR06 going back to 1996, so, yes,
I do have a backup of the pst file, just not a very current one.

Which brings up this notion: I have been unable to determine for myself in
what manner the PST2GB crop tool truncates the pst data. Does it crop the
earliest items or the most recent items or does it crop the data according to
some other variable(s)?

Also, if you don't mind and can think of the names of the third party
companies (if different from Kernel or Stellar as I have mentioned earlier)
that specialise in recovering corrupt pst files that you mention in your last
post, please, by all means, let me know.

Thanks again for all the help DL ... Kevin

:

Its immaterial as to the sp version, its a limitation, I believe solely, of
the pst structure.

If you cannot start/open OL2k when connected to this pst then I believe if
you connect this pst to an OL2003 installation you will have the same
problem. The size causes corruption of the pst, which may prevent any OL
vesrion opening/accessing it.
If the pst is corrupt then importing to an unicode pst will likely fail, or
at best result in data loss.
Its immaterial as to the location of the pst (other than being on a hd)

I have to assume that you never used the archive option, nor have any
earlier data backups, which is any 'case playing with fire.'

There are third party companies, I believe, that specialise in recovering
corrupt pst files. Only you know whether the expense would be warranted, as
apposed to using the MS Crop tool.


:

my last post has a typo in the last paragraph:
"the old pst in(to) OL2003"

:

All OL pst's prior to 2003 unicode have this well documented size
limitation.
If this was me I would create copies of the faulting pst to work on.
You can try OL 2003 with a unicode pst and import from your copy.
Though Import is not reccommended for transfering data between pst's
I assume you cannot open the pst to copy data across to the unicode pst, if
you can this is the prefered method.
I assume also that in OL2k you are unable to use the archive option.

I have discovered too late that OL2000 SP-3 (9.0.0.8954), IMO - Security
Update, cannot handle PST files that approach the 2GB file size limitation
(my outlook.pst is 2,074,425 KB [Properties: 1.97 GB (2,124,211,200

bytes)])
and now am trying to recover from this MS design limitation that has
precipitated, w/o warning(s), an inability to access my stored e-mail
contacts, messages, ect.

If I get OL 2003 and install it on top of (or in place of, as the case may
be) my OL2000 installation, then try to import my old 2GB PST file into a
newly created UNICODE PST file in OL2003, will I meet with success, or,
will
the operation fail because the old PST file already has issues ...
vis-a-vis
the file size?

Background info about what I've tried so far:

I have experimented with MS' PST2GB.exe and have also tried 'Kernel for
Outlook Evaluation ver 7.02.01' and 'Stellar Phoenix Mailbox
Professional -
2.0 (Demo Version)'.

The PST2GB solution is not appealing as I have found that a significant
chunk of data has to be cropped in order to get the file size down to a
level
manageable by OL2000.
I tried cropping 1 MB then running the Inbox Repair Tool but the IRT added
8.5~MB to the truncated file, making it a fair bit larger than it was to
begin with, and, presumably un-useful.

The Kernel demo crashes while scanning (encryption error dialog -
resolution
from their support people pending). FYI - to the best of my knowledge, I
did
not ever specify Compressible Encryption for my 'outlook.pst', unless that
it
is a retained setting (I did export a password-protected PST once) or a
default setting.

The Stellar demo installation routine required access to my Office 2000
Premium CD for 'required components' and wound up changing a registry
setting
(HKEY_LOCAL_MACHINE\Software\Microsoft\Office\9.0\Outlook\Setup -
MailSupport) from IMO to CW (a problem I've since resolved by changing the
MailSupport setting from '1' to '0').
Upon launch of a Stellar scan, the Windows Installer was invoked again and
failed with a 'Microsoft Office 2000 SR-1 Premium' error dialog: "Error
1706.
No valid source could be found ... ", however, the scan progressed to
conclusion but with no recovered items displayed in the GUID. As Stellar
Support has yet to reply to my requests for support, I am unable to
interpret
the results.

 

[Kevin]

Marie ...
Never did find out exactly how PST2GB works.
I went with Stellar Phoenix Mailbox Professional v2.0 (full version,
$129.00USD) ... results were less than promised ... here's an excerpt of my
complaint to Stellar:

With respect to the program and whether it delivered on it's promise to
recover all of my Outlook items ...

- none of my four pre-existing internet e-mail accounts are visible in
Outlook 2000 and they cannot be re-created because they are being rejected
when created with the same friendly names, as has been outlined by me in
detail already. They evidently exist in the Registry but Stellar P M Pro
failed to import them and the other aspects of my old profile.
- none of my recovered Contacts has e-mail addresses anymore and the
integrated Address Book feature is blank whereas it used to reflect all the
Contact names and e-mail addresses.
- many folders and subfolders (a couple of dozen or so) from my Deleted
Items folder were put above the level of the Deleted Items folder (top level)
and were empty, their contents missing.
- there are 625 individual e-mails that got sent to the Lost&Found folder
.... a real dog's breakfast.
- most of my Read Receipts are gone and the ones that remain have been
re-dated 31-Dec-69.
- there could be much more missing / wrong that I have not yet discovered.

I am trying to get my money back from Stellar and am considering investing
in DataNumen - Advanced Outlook Repair v1.2 ($249.95USD). Further info
request with them / Alan Chen pending.

Kevin

Kevin, did you ever learn the answer to your question:

Did you happen to have any opinion as to what MS' PST2GB cropping tool does
to the pst file? Whether it crops old vs. recent items, or, crops the file
according to some other variable(s)?

I have to use the crop tool. I followed the whole thread--how did it work
for you?

Marie.

Thanks DL ... I guess once I get sorted out (resolution to my dilema
pending), I better start looking into archiving - your method strikes me as a
good one. That and the discarding of a lot of UFI that I've been hanging on
to.
Did you happen to have any opinion as to what MS' PST2GB cropping tool does
to the pst file? Whether it crops old vs. recent items, or, crops the file
according to some other variable(s)?
Thanks again for the help.

Depending how you configure Archive it removes mail from the default pst to
a seperate pst.
You can have multiple pst's open within OL, and since the archive is simply
a pst you would still have access.

Personally I archive to a year specific archive pst, eg Archive2001,
Archive2002 etc

Reply to DL's 2/18/2007 3:35 PM PST post

DL ... thanks again for helping out ...

Your insights on my proposed use of OL2003 are helpful and I thank you for
illuminating the subject as best you were able ... I have decided to next
finish trying 3rd party software solutions and have support requests in
with
Kernel and Stellar to see about exhausting those routes (more info about
the
problems encountered with each in my earlier posts). Beyond that, if
required, I will still try OL2003 and will post back here with my results
as
I progress.

You are correct in your assumption that I never used the archive option (I
like[d] the convenience of being able to instantly access e-mails going
all
the way back to 1996 and had assumed the archiving of e-mail would make
easy
referencing back to items problematic - would it?).

I do have a complete C:\ drive image from last April that will save me
from
a worst case scenario loss of e-mails from APR06 going back to 1996, so,
yes,
I do have a backup of the pst file, just not a very current one.

Which brings up this notion: I have been unable to determine for myself in
what manner the PST2GB crop tool truncates the pst data. Does it crop the
earliest items or the most recent items or does it crop the data according
to
some other variable(s)?

Also, if you don't mind and can think of the names of the third party
companies (if different from Kernel or Stellar as I have mentioned
earlier)
that specialise in recovering corrupt pst files that you mention in your
last
post, please, by all means, let me know.

Thanks again for all the help DL ... Kevin

:

Its immaterial as to the sp version, its a limitation, I believe solely,
of
the pst structure.

If you cannot start/open OL2k when connected to this pst then I believe if
you connect this pst to an OL2003 installation you will have the same
problem. The size causes corruption of the pst, which may prevent any OL
vesrion opening/accessing it.
If the pst is corrupt then importing to an unicode pst will likely fail,
or
at best result in data loss.
Its immaterial as to the location of the pst (other than being on a hd)

I have to assume that you never used the archive option, nor have any
earlier data backups, which is any 'case playing with fire.'

There are third party companies, I believe, that specialise in recovering
corrupt pst files. Only you know whether the expense would be warranted,
as
apposed to using the MS Crop tool.


:

my last post has a typo in the last paragraph:
"the old pst in(to) OL2003"

:

All OL pst's prior to 2003 unicode have this well documented size
limitation.
If this was me I would create copies of the faulting pst to work on.
You can try OL 2003 with a unicode pst and import from your copy.
Though Import is not reccommended for transfering data between pst's
I assume you cannot open the pst to copy data across to the unicode
pst, if
you can this is the prefered method.
I assume also that in OL2k you are unable to use the archive option.

I have discovered too late that OL2000 SP-3 (9.0.0.8954), IMO -
Security
Update, cannot handle PST files that approach the 2GB file size
limitation
(my outlook.pst is 2,074,425 KB [Properties: 1.97 GB (2,124,211,200

bytes)])
and now am trying to recover from this MS design limitation that has
precipitated, w/o warning(s), an inability to access my stored
e-mail
contacts, messages, ect.

If I get OL 2003 and install it on top of (or in place of, as the
case may
be) my OL2000 installation, then try to import my old 2GB PST file
into a
newly created UNICODE PST file in OL2003, will I meet with success,
or,
will
the operation fail because the old PST file already has issues ...
vis-a-vis
the file size?

Background info about what I've tried so far:

I have experimented with MS' PST2GB.exe and have also tried 'Kernel
for
Outlook Evaluation ver 7.02.01' and 'Stellar Phoenix Mailbox
Professional -
2.0 (Demo Version)'.

The PST2GB solution is not appealing as I have found that a
significant
chunk of data has to be cropped in order to get the file size down
to a
level
manageable by OL2000.
I tried cropping 1 MB then running the Inbox Repair Tool but the IRT
added
8.5~MB to the truncated file, making it a fair bit larger than it
was to
begin with, and, presumably un-useful.

The Kernel demo crashes while scanning (encryption error dialog -
resolution
from their support people pending). FYI - to the best of my
knowledge, I
did
not ever specify Compressible Encryption for my 'outlook.pst',
unless that
it
is a retained setting (I did export a password-protected PST once)
or a
default setting.

The Stellar demo installation routine required access to my Office
2000
Premium CD for 'required components' and wound up changing a
registry
setting
(HKEY_LOCAL_MACHINE\Software\Microsoft\Office\9.0\Outlook\Setup -
MailSupport) from IMO to CW (a problem I've since resolved by
changing the
MailSupport setting from '1' to '0').
Upon launch of a Stellar scan, the Windows Installer was invoked
again and
failed with a 'Microsoft Office 2000 SR-1 Premium' error dialog:
"Error
1706.
No valid source could be found ... ", however, the scan progressed
to
conclusion but with no recovered items displayed in the GUID. As
Stellar
Support has yet to reply to my requests for support, I am unable to
interpret
the results.

 

[Marie]

Thanks for your response. What a shame for you to have to go through all
that! It's good to have your insight. Good luck to you.

Marie.

Marie ...
Never did find out exactly how PST2GB works.
I went with Stellar Phoenix Mailbox Professional v2.0 (full version,
$129.00USD) ... results were less than promised ... here's an excerpt of my
complaint to Stellar:

With respect to the program and whether it delivered on it's promise to
recover all of my Outlook items ...

- none of my four pre-existing internet e-mail accounts are visible in
Outlook 2000 and they cannot be re-created because they are being rejected
when created with the same friendly names, as has been outlined by me in
detail already. They evidently exist in the Registry but Stellar P M Pro
failed to import them and the other aspects of my old profile.
- none of my recovered Contacts has e-mail addresses anymore and the
integrated Address Book feature is blank whereas it used to reflect all the
Contact names and e-mail addresses.
- many folders and subfolders (a couple of dozen or so) from my Deleted
Items folder were put above the level of the Deleted Items folder (top level)
and were empty, their contents missing.
- there are 625 individual e-mails that got sent to the Lost&Found folder
... a real dog's breakfast.
- most of my Read Receipts are gone and the ones that remain have been
re-dated 31-Dec-69.
- there could be much more missing / wrong that I have not yet discovered.

I am trying to get my money back from Stellar and am considering investing
in DataNumen - Advanced Outlook Repair v1.2 ($249.95USD). Further info
request with them / Alan Chen pending.

Kevin

Kevin, did you ever learn the answer to your question:

Did you happen to have any opinion as to what MS' PST2GB cropping tool does
to the pst file? Whether it crops old vs. recent items, or, crops the file
according to some other variable(s)?

I have to use the crop tool. I followed the whole thread--how did it work
for you?

Marie.

Thanks DL ... I guess once I get sorted out (resolution to my dilema
pending), I better start looking into archiving - your method strikes me as a
good one. That and the discarding of a lot of UFI that I've been hanging on
to.
Did you happen to have any opinion as to what MS' PST2GB cropping tool does
to the pst file? Whether it crops old vs. recent items, or, crops the file
according to some other variable(s)?
Thanks again for the help.

:

Depending how you configure Archive it removes mail from the default pst to
a seperate pst.
You can have multiple pst's open within OL, and since the archive is simply
a pst you would still have access.

Personally I archive to a year specific archive pst, eg Archive2001,
Archive2002 etc

Reply to DL's 2/18/2007 3:35 PM PST post

DL ... thanks again for helping out ...

Your insights on my proposed use of OL2003 are helpful and I thank you for
illuminating the subject as best you were able ... I have decided to next
finish trying 3rd party software solutions and have support requests in
with
Kernel and Stellar to see about exhausting those routes (more info about
the
problems encountered with each in my earlier posts). Beyond that, if
required, I will still try OL2003 and will post back here with my results
as
I progress.

You are correct in your assumption that I never used the archive option (I
like[d] the convenience of being able to instantly access e-mails going
all
the way back to 1996 and had assumed the archiving of e-mail would make
easy
referencing back to items problematic - would it?).

I do have a complete C:\ drive image from last April that will save me
from
a worst case scenario loss of e-mails from APR06 going back to 1996, so,
yes,
I do have a backup of the pst file, just not a very current one.

Which brings up this notion: I have been unable to determine for myself in
what manner the PST2GB crop tool truncates the pst data. Does it crop the
earliest items or the most recent items or does it crop the data according
to
some other variable(s)?

Also, if you don't mind and can think of the names of the third party
companies (if different from Kernel or Stellar as I have mentioned
earlier)
that specialise in recovering corrupt pst files that you mention in your
last
post, please, by all means, let me know.

Thanks again for all the help DL ... Kevin

:

Its immaterial as to the sp version, its a limitation, I believe solely,
of
the pst structure.

If you cannot start/open OL2k when connected to this pst then I believe if
you connect this pst to an OL2003 installation you will have the same
problem. The size causes corruption of the pst, which may prevent any OL
vesrion opening/accessing it.
If the pst is corrupt then importing to an unicode pst will likely fail,
or
at best result in data loss.
Its immaterial as to the location of the pst (other than being on a hd)

I have to assume that you never used the archive option, nor have any
earlier data backups, which is any 'case playing with fire.'

There are third party companies, I believe, that specialise in recovering
corrupt pst files. Only you know whether the expense would be warranted,
as
apposed to using the MS Crop tool.


:

my last post has a typo in the last paragraph:
"the old pst in(to) OL2003"

:

All OL pst's prior to 2003 unicode have this well documented size
limitation.
If this was me I would create copies of the faulting pst to work on.
You can try OL 2003 with a unicode pst and import from your copy.
Though Import is not reccommended for transfering data between pst's
I assume you cannot open the pst to copy data across to the unicode
pst, if
you can this is the prefered method.
I assume also that in OL2k you are unable to use the archive option.

I have discovered too late that OL2000 SP-3 (9.0.0.8954), IMO -
Security
Update, cannot handle PST files that approach the 2GB file size
limitation
(my outlook.pst is 2,074,425 KB [Properties: 1.97 GB (2,124,211,200

bytes)])
and now am trying to recover from this MS design limitation that has
precipitated, w/o warning(s), an inability to access my stored
e-mail
contacts, messages, ect.

If I get OL 2003 and install it on top of (or in place of, as the
case may
be) my OL2000 installation, then try to import my old 2GB PST file
into a
newly created UNICODE PST file in OL2003, will I meet with success,
or,
will
the operation fail because the old PST file already has issues ...
vis-a-vis
the file size?

Background info about what I've tried so far:

I have experimented with MS' PST2GB.exe and have also tried 'Kernel
for
Outlook Evaluation ver 7.02.01' and 'Stellar Phoenix Mailbox
Professional -
2.0 (Demo Version)'.

The PST2GB solution is not appealing as I have found that a
significant
chunk of data has to be cropped in order to get the file size down
to a
level
manageable by OL2000.
I tried cropping 1 MB then running the Inbox Repair Tool but the IRT
added
8.5~MB to the truncated file, making it a fair bit larger than it
was to
begin with, and, presumably un-useful.

The Kernel demo crashes while scanning (encryption error dialog -
resolution
from their support people pending). FYI - to the best of my
knowledge, I
did
not ever specify Compressible Encryption for my 'outlook.pst',
unless that
it
is a retained setting (I did export a password-protected PST once)
or a
default setting.

The Stellar demo installation routine required access to my Office
2000
Premium CD for 'required components' and wound up changing a
registry
setting
(HKEY_LOCAL_MACHINE\Software\Microsoft\Office\9.0\Outlook\Setup -
MailSupport) from IMO to CW (a problem I've since resolved by
changing the
MailSupport setting from '1' to '0').
Upon launch of a Stellar scan, the Windows Installer was invoked
again and
failed with a 'Microsoft Office 2000 SR-1 Premium' error dialog:
"Error
1706.
No valid source could be found ... ", however, the scan progressed
to
conclusion but with no recovered items displayed in the GUID. As
Stellar
Support has yet to reply to my requests for support, I am unable to
interpret
the results.

 

[Alan]

Hi,

You may try our product Advanced Outlook Repair to repair and convert
your PST file. By selecting the source file as your Outlook 2000 PST
file and setting the destination file as "Outlook 2003" format, you
can convert your PST file into 2003 Unicode format easily.

Please visit http://www.datanumen.com/aor/index.htm for detailed
information about Advanced Outlook Repair.

And you can also download a free demo version at http://www.datanumen.com/aor/aor.exe

Alan Chen
DataNumen, Inc. - World leader in data recovery technologies
Website: http://www.datanumen.com
Fax: +1-800-9917-FAX (US Toll-Free)