Message from discussion Outlook Express transfer to Vista

From: "Steve Cochran" <scoch...@oehelp.com>
References: <E20EE250-DFF8-4645-A510-1657A719DAC3@microsoft.com> <#nisn4UWHHA.3980@TK2MSFTNGP02.phx.gbl> <u8b0FGVWHHA.5060@TK2MSFTNGP06.phx.gbl> <8863F238-DB75-4479-AF76-16BE786D91A4@microsoft.com> <O9LB0ZkWHHA.1688@TK2MSFTNGP05.phx.gbl> <69FF5A7D-9966-473F-B5A8-4783B94CDE57@microsoft.com> <4C7E65F3-C960-411F-BBF6-B9BF059CD853@microsoft.com>
In-Reply-To: <4C7E65F3-C960-411F-BBF6-B9BF059CD853@microsoft.com>
Subject: Re: Outlook Express transfer to Vista
Date: Tue, 27 Feb 2007 09:32:28 -0500
Lines: 97
Message-ID: <17700213-F31D-473B-8959-CAA318FEF598@microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Windows Mail 6.0.6000.16386
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16386
X-MS-CommunityGroup-PostID: {17700213-F31D-473B-8959-CAA318FEF598}
X-MS-CommunityGroup-ThreadID: E20EE250-DFF8-4645-A510-1657A719DAC3
X-MS-CommunityGroup-ParentID: 4C7E65F3-C960-411F-BBF6-B9BF059CD853
Newsgroups: microsoft.public.windows.vista.mail
NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
Path: g2news2.google.com!news2.google.com!news4.google.com!border1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!newspeer1.nwr.nac.net!newsfeeds.ihug.co.nz!ihug.co.nz!TK2MSFTNGP01.phx.gbl!TK2MSFTNGHUB02.phx.gbl

Oh.  I hadn't thought of that.  I'll have to look and see how I did it.

But if you look at the Value Value (<G>) under Criteria for the rules(eg. 
HKEY_CURRENT_USER\Software\Microsoft\Windows 
Mail\Rules\Mail\000\Criteria\000), you'll see in XP (server 2003) that the 
string is not Unicode, but if you look at the same in Vista, you will see 
that it is in Unicode.  So I don't know how the export method would be 
involved.

steve

"Frank Saunders, MS-MVP OE/WM" <franksaund...@mvps.org> wrote in message 
news:4C7E65F3-C960-411F-BBF6-B9BF059CD853@microsoft.com...
> It may depend on whether it's exported as a Regedit 4 or Regedit 5 
> (Windows Registry Editor Version 5) file.
>
> "Steve Cochran" <scoch...@oehelp.com> wrote in message 
> news:69FF5A7D-9966-473F-B5A8-4783B94CDE57@microsoft.com...
>> As I indicated a ffew months ago, the actual rule is now a Unicode string 
>> and it wasn't before.  So one has to modify that.
>>
>> Here's what I posted on December 12th:
>>
>> <quote>
>> Okay there are actually 4 issues, but I figured out two of them.
>>
>> This is for a single rule at the moment.  I'll try and program it so it
>> doesn't have to be done rule by rule.
>>
>> First export the rule from the machine with OE:
>>
>> HKEY_CURRENT_USER\Identities\{GUID}\Software\Microsoft\Outlook
>> Express\5.0\Rules\Mail\002
>>
>> where GUID is the Identity and this is rule 3
>>
>> Then edit the reg file with Notepad.
>>
>> Do replace for
>>
>> HKEY_CURRENT_USER\Identities\{GUID}\Software\Microsoft\Outlook 
>> Express\5.0
>>
>> with
>>
>> HKEY_CURRENT_USER\Software\Microsoft\Windows Mail
>>
>> Then save the file.
>>
>> Then the search strings have been changed to Unicode so set the cursor 
>> where
>> the Rule Criteria start.  Then do a second replace until the end of the 
>> file
>> and search for
>>
>> ,
>>
>> replace with
>>
>> ,00,
>>
>> Then in the last line of each criteria add
>>
>> ,00
>>
>> Then save.
>>
>> Then create a mock rule in the registry with WinMail and close WinMail.
>> Then delete that mock key in the registry.  Make sure the rule number in 
>> the
>> saved reg file matches that that you just deleted.
>>
>> Then merge the file into the registry.
>>
>> Open WinMail and go to Tools | Message rules and you see the new message
>> rule spelled out okay when you click on it, except for the folder name. 
>> You
>> will still have to specify the folder names again because those are coded
>> numerically, I think.
>>
>> Anyway, that will work, but its a bit involved to do manually.
>>
>>
>> </quote>
>>
>> "Jerry S" <notdisclo...@nada.tld> wrote in message 
>> news:O9LB0ZkWHHA.1688@TK2MSFTNGP05.phx.gbl...
>>> That's odd, because in practice it works exactly as described.  If 
>>> you're
>>> referring to the location that the rules are stored, that's covered in 
>>> steps
>>> 3d - 3f.  If you're referring to the pointers within the rules that
>>> reference the objects within the OE data stores, that is covered in step 
>>> 5.
>
>