Jump to content

cddumat

  • Posts

    5
  • Joined

  • Last visited

  • Country

    Germany

Retained

  • Member Title
    Newbie
  1. Sorry, did not wanted to be rude, just to point out a bit about the network stuff that's going on. Strange, as i can rip with 'My Network' being turned on in my 752BD. So that does not seem to be an absolute showstoppper, but clearly for your situation. No idea why you are having these problems, i'm at a loss.
  2. Thanks for pointing that out. I did some more tests (on an azur 752BD) and these were my findings: What did work for me: - Using a USB stick with a partition table with only one partition (the first). The partition table could be MBR or GPT, both did work fine. - The stick had to be formatted with FAT16, FAT32, ExFAT or even NTFS, all worked fine. Actually the FAT variants most probably were with VFAT extensions (is it possible to have them without these days?) What did NOT work for me: - using a stick without a partition table at all (be it mbr or gpt). No matter what filesystem has been used, it did not work. That is in line with the AutoScript line ".. cp /mnt/sda1/...", the 1 of sda1 specifying the first partition on a storage medium. - using a stick with more than one partition: The tray opens and then quickly closes again before it is fully opened. Inserting a SACD after this does not help, the daemon is not reachable. No idea why this is the case, but it easily could be repeated. - using a stick with a partition table (gpt or mbr), and using ext2fs filesystem. What i did not try: - using a partitioned USB stick with the appropriate partition not beeing the first, and then adjusting the AutoScript file to something as "... cp /mnt/sda2/... " - Using other filesystems than FAT16, FAT32, NTFS, ExFAT, ext2fs Hope this info helps some. The most important fact as i see it, is the necessity to use the first partition on a partitioned USB stick, at least for an azur 752BD. Filesystem seems to be fairly irrelevant, as long it is a microsoft one. Feel free to correct me if your findings do disagree.
  3. Maybe to clarify something on the theoretical background: DHCP only sets the address (and gateway and DNS servers), but NOT the port. The port is requested by the appropriate server process, in this case sacd_extract. This is basic TCP/IP stuff, and nothing that could be done differently on these SACD Players than on other network devices. Why it did suddenly work for Jarmo i have no idea, but i suspect that there has been more changes in his configuration that most probably were overlooked.
  4. Here's to the people having problems with players that are supposed to work: It is vital that the USB stick is partitioned similarily as a HD, with (at least) the first primary partition as FAT(32). It won't work if your stick is formatted as a floppy with no MBR. So repartition your stick (easy with Linux, for windows i recommend something as Bootice 1.332, as windows itself sometimes lies about whether or not a MBR exists on a USB stick). So download Bootice, run it, select your stick, select 'Parts Manage', then 'Re-Partitioning', then 'USB-HDD mode (Single Partition)", FAT32, and click 'OK'. Afterwards copy the AutoScript Folder onto the stick, and you should be fine. That did work for me (on an Azur 752BD) , as before i had troubles myself getting it to work (USB stick has been without partitions and MBR) Good luck and fun ripping..
  5. Hello ted_b, here's another request for your SACD ripping guide, if you would be so kind. Thanks a lot already, Clemens
×
×
  • Create New...