"Paul" wrote in message
...
R.H. Breener wrote:
""...winston‫"" wrote in message
...
R.H. Breener wrote:
"Paul" wrote in message
...
R.H. Breener wrote:
I just bought a new laptop with W 8 and have a few questions. How do
I get rid of having to constantly put in a password to use it? It's
frigging annoying as hell. The other question is how do I hack in
WindowsMail like I did in W 7? WindowsMail works great in W 7 so I
moved the folder to W 8 but it wont open. How can I get it to open?
Please don't suggest other mail programs as I've tried most of the
years and can't stand them. Thanks.
You can use your search engine, like this
"windows mail" site:sevenforums.com
"windows mail" site:eightforums.com
and get a solution for each OS.
The second article mentions a DLL that has
to be moved and registered so the OS knows
it is there.
http://www.sevenforums.com/tutorials...dows-mail.html
http://www.eightforums.com/browsers-...ndows-8-a.html
On the first article, there is a download, but you can just
as easily open the ZIP with 7-ZIP, take note of what
files they're using, and copy over your Vista ones.
In the first article, there is a .reg file. It may look
like loads of "hex", but in fact those are text strings.
The text strings use wide 16 bit characters. For English
participants, the second byte of a pair is usually 0x00.
The net result is, it looks like hex, when on a previous
OS without wide character support, you'd be looking at an
easy to read %path% type thing. So don't be freaked
out by the hex look of the .reg file. It can be translated
to something readable, with a moderate amount of effort.
The contents aren't totally mysterious. (There are some
things that are pure hex in Windows, but these aren't
examples of that.) It's the inability of Microsoft to
create a decent representation, that makes us go through
this hell (of translation).
At some point in the past, one of these USENET groups
has had a posting on installing WM, but since there is
no archive on Google, it's pretty hard to search what
has already been posted here, when you need an answer.
New groups added to alt.*, are not automatically added
at Google headquarters.
Have fun,
Paul
Thanks Paul. There seems to be several ways to do it and I'll look
into
all. The biggest problem is deleting the WindowsMail from W 8 that it
came with. It wont let me delete the copy it came with. Is there a way
to get past that Trusted Installer BS? I have Unlocker but it wont
work
on W 8 64 bit. Any suggestions to get around this problem?
On Win8 the mail client is an app. Uninstall it via the Modern UI.
- rt click the Mail app icon, scroll and select 'Uninstall'
Note: doing so will also remove all other apps that are packaged with
the Win8x mail client.
--
...winston
msft mvp consumer apps
No working mail client came with W-8, only a crippled copy of
WindowsMail.
I got rid of the crippled WindowsMail on W-8 and installed a copy from
Vista of WindowsMail... but there's still the problem of MSOE.dll not
being able to be used. How do I get W-8 to see and load that dll so I can
use WM on W-8? I get this error: WindowsMail could not be started because
MSOE.dll could not be loaded.
See post #10 here. It was last edited two weeks ago, to include
a Windows 10 Preview picture of WM from Vista running in Win10 TP.
http://www.eightforums.com/browsers-...ndows-8-a.html
But I can't get past this step
"d) Now , we have to register the above dll. Open cmd and type : regsvr32
"c:/windows/system32\msidcrl30.dll" and press enter."
I press enter and nothing happens on W8. I can't run the Command Prompt as
Administrator as there is no choice in the menu to Run As Admin.
The problem for a person like yourself, is most all of the threads
I've seen so far, are not using tech writer techniques to make the
procedure clear.
There is also some disagreement on the best way to do it, with
respect to the msidcrl30.dll file. While it can be placed in
System32, if the program would accept it, it would be easier
to place it in the Winmail folder,
I tried placing it in both. I still got the MSOE.DLL error - that WM can't
start because MSOE.DLL could not be loaded. I've read endless pages of info
and still haven't found how to get this dll to load.
winmail.exe -- version consistent with 32 bit or 64 bit OS
msoe??.dll -- version consistent with 32 bit or 64 bit OS
msidcrl30.dll --- and so on
There are two Program Files folders, one for 32 bit programs,
one for 64 bit programs. This "recipe" is going to work better,
if your "donor" OS (the one where you have the working WLMail)
matches the bitness of the OS on the target machine. It would
be a poor fit, to go from a 32 bit Vista to a 64 bit Windows 8,
and expect an entirely smooth transition. You need to stick the
files in a different Program Files folder, as well as use
files which are appropriate for that folder (32 or 64 bit versions).
The computer these files were taken from are a 32-bit Vista. But they also
worked on my 64-bit W7 back home. I took the entire folder from the W7 and
the Vista and tried both. But I keep getting that MSOE.DLL could not be
loaded error.
AFAIK, if you stick msidcrl30.dll in the winmail folder, that
isn't likely to need regsvr32.
In (x86) or under regular Programs? OK, I put it both and still get the
MSOE.DLL could not be loaded error.
The other part of this recipe I don't understand, is the two
places you're working (some Program Files x86 work, and
alternately if you use the method, the System32). Those
are owned by TrustedInstaller. While you could use a tool
like TakeOwn right-click menu, to obtain ownership and
jam in your stuff, that's not the best thing to do. And
I'd surprised the people espousing this recipe, haven't
run into permission problems because neither they or
the administrator account, own the folders.
I've run into no problems with WindowsMail and adding that msidcrl30.dll.
So it should
be tough, to jam a folder in there. (TrustedInstaller
is actually a service and not an account as such.) It can be
fixed with TakeOwn, but don't be careless with that thing.
For example, do not click on the entire C: drive and do a
TakeOwn. That'll make a mess you'll regret later (like the
very next rollup package perhaps).
Rollup package?
I don't think any of these methods are sufficiently
automated for you. Too many variables left uncontrolled.
Make a backup first, then go nuts :-)
The "Tut" tutorial package mentioned in post #10, I
indicated in another posting, that it contains a
.reg file that needs to be merged. (Right-click the
file in File Explorer, and there should be a "merge"
option in the menu.) That installs the registry
entries in there. If you convert those strings to ASCII,
you can see what paths the registry file specifies. It
likely uses %% style environment variables, so you
would not need to add "RHBreener" into any of the
registry strings. The registry file should work
for anyone, as long as it is designed that way.
A clever person, could take that registry file,
and compare the entries (key names) to regedit
in Vista, and verify they're all the same
registry settings.
Way over my head. I just want to mention I can't follow #10 because I have
a Command Prompt but no choice to "Run as Administrator." How can I change
that? Google brought up endless pages with no explination how to add it to
the prompt's dropdown menu.
The thing is, if you accept "automation" from anyone
on the Internet, you're taking a chance. I usually
eyeball .reg files before I even consider using them,
just to be on the safe side. For example, all it
would take is a slightly wrong typo, to delete
a whole chunk of registry (because a .reg has both
(+) and (-) entries, and the (-) ones delete stuff).
Leaving me to scramble for a registry recovery recipe
(System Restore will do it for you, if you set a
restore point before doing this stuff).
I also always export the Reg when I change something there - which is rare.
If you feel up to experimenting, give it a go.
Otherwise, forget it. The instructions leave
a lot to the imagination (TrustedInstaller).
HTH,
Paul