No, I don't allow that. There is no way I can ensure that a share exists (and admin$ much likely exists on every computer). There was a problem with using of driver letters in the URL of the MCE EPG engine. While the internet explorer converts urls like file://c:/path into correct local path, the MCE EPG engine may not accept such a path.
What is the reason to move the megaepg out of ehome directory? Vista doesn't work because the engine doesn't accept a "file://" URL and not because the ehome directory has bad permissions.
The format is almost the same, it just doesn't work with file:// urls... M$ people used BITS to transfer the EPG and will work only with HTTP and HTTPS :(
You can move and edit HTML files manually but the EPGDataMetaInfo is recreated automatically every time and that would be problematic to edit the path manually again and again. I'm going to make the required changes in the upcoming version of the MegaEPG. There are some other changes to support Vista but they are minor.
Re: Installing out of ehome directory
No, I don't allow that. There is no way I can ensure that a share exists (and admin$ much likely exists on every computer). There was a problem with using of driver letters in the URL of the MCE EPG engine. While the internet explorer converts urls like file://c:/path into correct local path, the MCE EPG engine may not accept such a path.
What is the reason to move the megaepg out of ehome directory? Vista doesn't work because the engine doesn't accept a "file://" URL and not because the ehome directory has bad permissions.
Re: Installing out of ehome directory
I was sure the format is the same....
Anyhow, I guess we can use the same method as in: http://www.planetnana.co.il/ishaydahan/
To use local IIS to respond the HTTP request.
The question is: Can I just edit the HTML files for that, or something had to be changed in the code (signature??)?
Ravid
Re: Installing out of ehome directory
The format is almost the same, it just doesn't work with file:// urls... M$ people used BITS to transfer the EPG and will work only with HTTP and HTTPS :(
You can move and edit HTML files manually but the EPGDataMetaInfo is recreated automatically every time and that would be problematic to edit the path manually again and again. I'm going to make the required changes in the upcoming version of the MegaEPG. There are some other changes to support Vista but they are minor.