Observation is that normally, you put in the disc and hit the power button. Experienced the same problem that about 8-9 disc, the unit seem to stop executing the script and may have reinitialize itself. It's just my comment.Īnother Win10 user here with S5100. I don't know where is the problem and what is the solution. When my PC successfully switched back to port 49925, I was able to rip continuously 14 SACD (with max port 64254!) again. Sometimes the blinking OFF has gone to continuous OFF, but most often server unavailability error. I saw that reaching the 65535 limit was perhaps a problem. Transmission Control Protocol, Src Port: 54978, Dst Port: 2002, Seq: 10, Ack: 6, Len: 8Īnd so one: taking on a new SACD, the port number of the PC is always growing. Transmission Control Protocol, Src Port: 53903, Dst Port: 2002, Seq: 18, Ack: 454682, Len: 0ĭuring you open the door, change SACD, power OFF - your PC and BD send to each other many hundreds of blocks first my PC begins from port: 54787 to BD port: 50001 and finally they reach ports: 5483 When the rip ends, the closing ACK from Wireshark for example: I'v seen on Whireshark, during DSF ripping my BDP-S490 uses port 2002, but my PC uses another port from dynamic/privat port range 49152.65535 I found an interesting thing in the communication. Although there is not a big problem with restarting the ripping, the possible cause of the jam is important. Click to expand.As I said before, I'm not an expert on this issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |