Windows Mail

You might want to post this on the Calendar tutorial. Someone over there might have a better idea of the internals.

RKelly5327 said:

..... After I did this WIndows Mail launched right off the bat.

However I cannot get Calendar to work in 8. I followed the tute for Calendar, right to a T. Alll went well up to where I was to select the Reminders file. That part seemed to work okay, but when I tried to select the configuration OS at the bottom, I got an error message saying "the specified account name is not valid."

I tried it for all of the options, but none worked. I have no idea what the error message is talking about, nor where to even find the name of the mystery accout so I can remedy it.

Ron K.

RKelly: Thanks again, it helps everyone understand. Have you tried asking a question in the Calendar tutorial? You might get better feedback there.

RKelly5327 said:

SlartyBart- the tut worked great. I didn't have any problems at all with it. I was just trying to do the same thing with 8 to see how it would work. That's when I ran across the info about the missing dll file. So far I haven't been able to get Calendar to work in 8, but that's really no big deal. It all works fine in 7 and that's the main thing.
RK

RKelly5327 said:

[...] I know some have done the same with Windows 8, which I tried to do but could not get Mail to launch in 8. I hunted all around the net and found that 8 was lacking a dll file- msidcrl30.dll. The following is what I found that makes it work in 8. [...]

Many of us have it installed on Win8 already.
All the information that you posted was covered last year on post 1262
and before that on post 1181 with the links where to go to get the information to do it.

..or just go directly to the WinMail on Win8 thread at the EightForums Here







...

I have not run through the entire thread so possibly what I am saying could have been mentioned previously.
Although I had no problem installing WM on W7Pro(64bit) with the tut as of 2012-05-19 (page I saved *.mht and *.pdf at the time), thanks to SlartyBart, it did not resolve the "time stamp" issue I have with *.eml files on W7, in that their "modified date" is changed when using the W7 search or browsing a Folder (DIR) with Windows Explorer (WE) to "current date". I had just hoped that by installing WM changes would be made to the registry that would prevent this annoying feature of W7 from happening. It is not very conducive to data integrity in the OS and after searching for solutions during which I found some very lame reasons on one of the MS-Answer Forums, why the OS is behaving this way. Has this issue been raised in this thread?

I am still using OE6 on a WXP-Pro-SP3 VMware machine on my W7Pro(64bit) box for my e-Mails side-stepping W7-Updates from removing the WM, bypassing the lack of W7 drivers for our office printer and have also stopped saving e-Mails to Hard drive (HDD) in the *.eml format. The latter dose not resolve the date issue on the W7Box for existing files, some of which are +10years old. The date issue of course dose not happen if I search or browse from within the WXP-VM-Box on the same HDD!
Of course I use a work around in the form of a "live" backup but it is time consuming and laborious when syncing as the *.eml files that have had their dates changed, due to a search or browsing, will show up as newer versions of the same file.

The eventual migration from OE to OL (Outlook) and Schedule to OL is a dark cloud on the horizon that I still have to face in order to come in line with the rest of the office and my smartphone (iPhone).

I know that this is not directly pertaining to installing WM on W7 but at least you have feedback that the tut is great and works fine and the issue relates to WM (OE) on W7.
Looking forward to some constructive input.

Renamo3: I apprciate your feedback and sympathisize with you on the eMail variations (shortcomings). You're using OE in an XP Virtual Machine on Win7 an you have WM reinstated on Win7.

I'm not sure that I understand the rest of the issue, though. There are a lot of concerns expressed and I'm want to be certain anything suggested fits your needs.

OE stores the eMail in .dbx fles, extracting (exporting/saving as eml) creates a new file, hence a new date. I'll need your help testing this as two of my machines bit the dust over the past year. My memory is good, but limited.

Does using Win7 search with eMail filters help as a workaround?
In the search box enter:
type:eml

then arrange the resulting window to include the following column headings
date sent
date received
date created
date modified
To
From
Subject

This is a sticky wicket, there are a number of factors affecting the issue - the OS and eMail client(s)

Before I suggest anything, I'll need to reasrch; and sine my older machines bit the dust, I'll need your help
This will take some time and I'm not sure there is a good answer, but if you're will, so am I
Let's start with: What import / export options exist in both OE and WM.
If we can go from OE .dbx format to .eml format and preserve the internal dates - great.

The file creation/modification dates cannot be altered unless you use a third party utility (on Unix it's touch). I used one utility a very long time ago (Win98 perhaps), so more research is needed. I really don't like using third party solutions unless there is no native Windows feature and.... and it is absolutely necessary. The user assumes all risks of mucking with file timestamps.

Your intermediate goal is to migrate from OE to WM reinstated on Win7, and then eventually to Outlook - correct? I'd like to suggest going from OE to OL without WM in between. There are a few bumps from OE to WM and a few more from WM to OL.

Some references you might want to review:
Import messages into Windows Mail from Outlook Express (don't worry about it saying Vista... Vista or Win7 is more correct, but MS didn't include WM in Win7, so they didn't change it)

Import your messages or account from Outlook Express to Outlook - Outlook - Office.com

@Renamo: Great information, thanks.

To keep the focus of this tutorial on reinstating WM on Win7 and the issue your machine has is OE / Win7, please open a new thread in Browsers & Mail - Windows 7 Support Forums. You'll get more people looking at a solution. Post a link to the new thread here and I'll follow it.

In the meantime, I'll read the doc you attached.

I'll double check this, but I don't believe that I've ever seen Windows changing the dates of exisitng files unless something does actually affect the date. Each machine is different so who knows?

Renamo3 said:

..... Windows 7 changes the "modified date" of already existing *.eml files to the "current date" when using the search, browsing a folder or hovering over the file with the mouse.
Say you have a file mark.eml with a modified date 2001-10-26 on your HDD and you execute any of the functions mentioned above the W7 OS will change the "modified date" to 2013-02-10.

I know I've never seen Windows search change dates - that's very odd that it happens on your machine. It would be helpful to see a screen shot of the issue you describe. Show both examples, I guess one from OE (correct date) and one from Windows search using the coulmns I suggested (dates differ).

If you take a look at the attached search in post# 1361, you'll see all of the dates are different (mostly). These are existing .eml files on my machine.

There definitely is a change to the way dates are presented in Win7 (not sure about Vista) - I believe the generic Date field is used to simplify date presentation (sent / received / created /modified).

Please make a backup to avoid the issue you describe

Renamo3 said:

..... The W7 search with e-Mail filters, "type:eml" compound the issue, especially if you do the search from root e.g. D:\ as it will change all *.eml files "modified date" to the current date on that drive. Do not try this on files for which you need to maintain the date integrity, if you do not have a back up on a machine with an older OS (pre Vista).

Ok, I'm confused... I must not understand the issue - I thought this was the issue. Open a new thread, I'll read your doc.

Renamo3 said:

..... I have not come across a problem to go: "from OE .dbx format to .eml format and preserve the internal dates", even with very old *.dbx files ...
..... This method also works for WE and keeps the "live data" in the program down to a reasonable size especially if saving the "Deleted Items" *.dbx from time to time.
..... The issue at hand is that W7 as OS is "mucking with file timestamps"

No I have no intentions of "migrate from OE to WM reinstated on Windows 7". As stated I only installed WM in the hope of resolving the "timestamps" issue on the W7 box. I will use the OL on the WXP-WM to migrate from OE6 to OL03k and then use the *.pst file to migrate to the W7 box, just as you suggested.

OE and OL store contacts differently, you won't be able to preserve the "wab" format. You can always keep the wab on file, it's just that OL won't actually use it. You'll need to import the contacts to OL. Again, this will take some testing, but I think you'll still be able to open the WAB, just not in OL.

I'm not certain, but I seem to recall that some contacts fields (group/category) just can't get migrated to OL. Same is true for WE. It is a pain, but a one time manual "reorg" solves that.

Renamo3 said:

..... migrate my extensive *.wab Address Book to OL-Contacts without loosing the *.wab internal folder structure and found a resolution to the office printer driver on W7.

@Renamo: Yeah, that's quite a book. After reading it, I don't think I'm qualified to help as I think itlies in the Server-Client arena.

EDIT: A quick look in Technet took me here. This is only a reference, not a suggested solution. It certainly sounds similar to the issue you're describing. The HOTfix is quite old, another reason I ask you be be absolutely clear on the versions.
DO NOT apply the hotifx in the link.

At this point, I simply guessing.

Please open a new thread as I previously asked and I'll request help from other members.

Please make sure that all of the versions and names of Servers and clients match. I read the doc and saw

DUNE1 Win7Pro(x64) and JUGASVR W08R2SVR

but when I went back to your post 1362, I saw

"SERVER" = W2kSVR
"DUNE1" = W7Pro(64bit)-SP1

I'm asking so that no one suggests updating software that you already update Win7 to Win7-SP1. I think you recorded the process you tried very well.

When you open a new thread, please indicate the registry changes you've made to which OS. I'll check for a new thread as this is not within the scope of this tutorial.

Thanks.