Scared stiff to upgrade to V1.02 (1 Viewer)

[Grahamgo]

Here's why. I have installed V1.02 approx 5 times, 2 times doing a Hard drive format and clean XP Pro install, SP3 etc. I tried everything, used the latest drivers, did registry cleaning. But always faced the same problem which was that the TV-server appeared to be working, but MediaPortal stopped on the TV-setup screen asking for a server name or IP. I have posted quite a few times on this forum and got some ideas but without success.

Anyway today I decided to try V1.01 and guess what, lo and behold it works! This time I just did a full delete of MediaPortal and a registry clean and re-boot. The install and setup went exactly as per the guideline.

Now I am looking forward to actually using it. I naturally have a hesitation to upgrade - too much pain!

Unfortunately this is still one problem. If I allow the program to start in the full screen mode the PC mostly crashes (blue screen of death). If I start in a window and then go to full screen - no problem. But I see plenty of threads on this so I will do some Forum reading.

Thanks again for the help.

 

[acorn]

I too was suffering this problem, however it seemed to be a network issue. My setup would be fine for a day and then I'd get the can't connect to database/enter server name problem.

I solved it by setting a static IP and then pointing MediaPortal and TV Server to the IP address not the name of the PC. All has been running fine now for 4 days... not long I know but better than before.

Good luck!

 

[Grahamgo]

I tried setting the IP, the MSLoopback, disabling firewall's etc. But it wouldn't work for me. I read that 1.02 internal TV tuner has DVB-S problems. but 1.01 doesn't. I am guessing that a big majority of users have taken the upgrade path and have not started at 1.02. Just an idea...

 

[chemelli]

Here's why. I have installed V1.02 approx 5 times, 2 times doing a Hard drive format and clean XP Pro install, SP3 etc. I tried everything, used the latest drivers, did registry cleaning. But always faced the same problem which was that the TV-server appeared to be working, but MediaPortal stopped on the TV-setup screen asking for a server name or IP. I have posted quite a few times on this forum and got some ideas but without success.

Where are your logs ?

Simone

 

[Grahamgo]

Hi, sorry I read this too late. I have done a restore using Acronis to a basic XP Pro after reading the XP installation again. Because I realized that I did not have .net1.1 or its hotfix installed. I only had .net2.0 - 3.5 SP1.

This info was buried in the suggested Windows section.

"run Microsoft Updtes as many times, until there are no new updates left. make sure that .net1.1 + servicepack, .net2 and .net3 got installed."

I will go ahead and install v1.02 again and I hope the Blue screen and network problems go away. If they don't I will send you the logs. - :sorry:

 

[tourettes]

I will go ahead and install v1.02 again and I hope the Blue screen and network problems go away. If they don't I will send you the logs. - :sorry:

Blue screens are almost always (99.99%) caused by either faulty hardware or buggy drivers, so most likyl you are still going to see those.

 

[Grahamgo]

Message to tourettes.

Hi, I restored my Acronis image again, and added .net1.1 + .net1.1 Hotfix (which I had never loaded) and a couple of latest MS security updates. I installed MediaPortal v1.02.

The Tv-server/MediaPortal is now working and so far I can start MediaPortal in full screen and the blue screen problem appear to have been fixed.

In my case I am pretty sure the .net1.1 omissions caused my problems, but that is optimism on my part. Perhaps you can comment.