PDA

View Full Version : AnyDVD 6.1.13 Bugs?


CaribbeanBlues
28th January 2007, 03:44
As soon as I installed this version, I began to have numerous problems. DVDs were not recognized, read errors occurred on discs known to be good, software relying on AnyDVD hung. When I uninstalled the update and re-installed a prior version, all these problems went away. My system is not unique, P4, Windows XP Pro, NEC 3540A drive updated to fw 1.04. Is anyone else having similar problems?

troybal
28th January 2007, 04:15
I did not have any issues with the latest update.

Aaron
28th January 2007, 04:19
yes i have the same problem my dvd player on my computer dosint work whit anydvd i dont now why and when i swicth the any dvd works evry think ok:mad:

David McRobie
28th January 2007, 04:20
mine is working so far as well.

David

Franchise
28th January 2007, 04:32
I don't have any problems on my end either.

Terrabyte
28th January 2007, 04:42
I updated to the latest version and have no no problems at all.

Perhaps the reason why I don't suffer very many problems with the software I use, is because I am quite fanatical in keeping my computer operating in peak condition by cleaning the registry, defragging and keeping track of everything I load and unload etc.......

I have found that quite a lot of people have software problems that are due to other problems relating to the uncared-for condition of their OS.

As I said: The latest version of AnyDVD has run perfect on my system "using XP Pro." :)

ITSE
28th January 2007, 06:18
No bugs detected at the moment.
U may use another software wich makes problems with it?

ITSE

McstylisT
28th January 2007, 06:19
Nope,,, all working fine this end too. :agree:

vinman
28th January 2007, 06:24
maybe you got a bad download have you tried to redownload and a complete
reinstallof the new version?

ETP
28th January 2007, 07:20
The site download is on the old file as of 10 minutes ago.

PSI_Orion
28th January 2007, 07:54
I've been trying to update to 6.1.13 since I was told of a new update by AnyDVD but everytime I download it and check the version number during install it says it's 6.1.0.7. Therefore, I guess their cache hasn't flushed yet or someone has uploaded the wrong file. All those that are saying they are having issues with 6.1.13, can you check your version numbers to confirm which version you are using and post here. Thanks.

ETP
28th January 2007, 07:57
Ditto! This seems to happen for every update for me.

Matt
28th January 2007, 08:25
...software relying on AnyDVD hung...Which software?

riceman
28th January 2007, 09:50
After Downloading 6.1.13 clonedvd2 And dvdshink give me errors, Never Had This before. but works With Anydvd In Safe Mode .

Clone Me
28th January 2007, 11:36
After Downloading 6.1.13 clonedvd2 And dvdshink give me errors, Never Had This before. but works With Anydvd In Safe Mode .

What errors? Can you be specific? Which DVD title?

I'm using both now, no problems so far...

jeffcobb
28th January 2007, 11:49
After Downloading 6.1.13 clonedvd2 And dvdshink give me errors, Never Had This before. but works With Anydvd In Safe Mode .

I am using AnyDVD 6.1.13 with Handbrake under Win2KPro running on a VMWare image on a 64-bit Linux box. With the exception of one set of titles (Stargate) it has been invincible. Now if only they would sell a linux version I could ditch the VMWare for good.

itchykaboom
28th January 2007, 12:52
mine has been running perfect here too

Shardel
28th January 2007, 13:37
I've been trying to update to 6.1.13 since I was told of a new update by AnyDVD but everytime I download it and check the version number during install it says it's 6.1.0.7. Therefore, I guess their cache hasn't flushed yet or someone has uploaded the wrong file. All those that are saying they are having issues with 6.1.13, can you check your version numbers to confirm which version you are using and post here. Thanks.

I have been having this same problem for about 7 weeks. I went through
several expert forums and took my tower to 2 tech places. I also worked
through the support at slysoft with no workable solution. Still I ended
up with the same problem. Finally yesterday I found the answer. With the
new Vista coming out several of the ISPs have changed the way they work.
I had a dial up ISP. I can not use their browser to go to slysoft and
download the update or I have this problem. (I also had this problem
when I tried to register on this forum.) What I had to do was connect to
my ISP. Then minimize it to the task bar. Then open internet browser
and type in the slysoft address. Then I downloaded the update as usual
and everything worked fine.
Hope this works for you.

riceman
28th January 2007, 18:52
What errors? Can you be specific? Which DVD title?

I'm using both now, no problems so far...

I uninstalled Anydvd And reinstalled, Seems To be working fine now. thanks

mmdavis
28th January 2007, 22:10
As has been stated in several of these threads, there seemed to have been some problems with v6.1.1.3. They seem to have been corrected in v6.1.1.4.

DetroitBaseball
28th January 2007, 22:11
As has been stated in several of these threads, there seemed to have been some problems with v6.1.1.3. They seem to have been corrected in v6.1.1.4.
A problem with fluxDVD protection in 6.1.1.3 was corrected in 6.1.1.4.

CaribbeanBlues
28th January 2007, 22:50
Which software?

Hey, Matt!

It is definitely 6.1.1.3. I went backwards to 6.1.0.2 and instantly all the same discs and drives worked.

CaribbeanBlues
31st January 2007, 11:53
I suppose the problem relates to something specific in my environment since the thread stopped here. However, I can't think of a thing that would make it unique. I tried installing 6.1.1.4 and immediately EVERY DVD I own had read errors! I don't think so! lol So I re-installed 6.1.0.2 and suddenly all of my DVDs were healed! It's a miracle!

So... I worry about any company that routinely puts out updates/patches/fixes every few days. In this case, I hope someone is reading these posts and puts out another fix SOON.

I appreciate all the responses! It really helps determine where the problem might be...