title
Products            Buy            Support Forum            Professional            About            Codec Central
 
Results 1 to 5 of 5

Thread: "Error unable to open File" while ripping; filename spaces replaced with "&*9837;"

  1. #1

    "Error unable to open File" while ripping; filename spaces replaced with "&*9837;"

    I've started getting the strangest error when I try to rip a disc. The filenames that the Ripper is trying to write seems corrupted -- it's writing a music note flat character instead of spaces (see image). I've reinstalled the latest version of dBpoweramp, rebooted, etc. No changes. Running Windows 10. Everything worked fine a year ago (handed used ripper since then). I've tried multiple harddrives (C:, D:, NAS)-- same behavior across all:

    error picture.png

    etc.

    Any thoughts from anyone?

    thank you
    Marty
    Last edited by Pgh_Marty; 02-21-2022 at 08:52 PM.

  2. #2
    dBpoweramp Guru
    Join Date
    Nov 2007
    Location
    Florida, USA
    Posts
    5,498

    Re: "Error unable to open File" while ripping; filename spaces replaced with "&*9837;

    Last edited by garym; 02-21-2022 at 08:57 PM.

  3. #3
    dBpoweramp Guru
    Join Date
    Nov 2013
    Location
    New York
    Posts
    450

    Re: "Error unable to open File" while ripping; filename spaces replaced with "&*9837;

    What is the naming string? What is the list of substituted characters? The substituted characters list may have a space being replaced by the "9837" character which may well be an illegal character in a filename??? Re installation without removing the settings probably maintains the existing substitute character table and possibly the naming string.

    The "Filename Restricted characters" table in the Windows version is in the control center under "Configuration" "advanced settings". After clicking on "set" which opens the list, there is a button for resetting the list to default, which may well solve this issue. There is also a box to tick (apparently unticked by default) that restricts filenames to ANSI characters. That would probably prevent this issue (depending on which has priority in the software (the table or the prohibition on non-ANSI characters). But that might have an unintended problem if the poster has some foreign language titled CDs. Microsoft. at least, does allow some foreign language filename characters. I have a few files from CDs with Japanese characters and Windows recognizes them.

  4. #4

    Re: "Error unable to open File" while ripping; filename spaces replaced with "&*9837;

    eureka! Thank you schmidj! That was exactly the problem. Don't know how, but the list in "Filename Restricted Characters" was all gibberish. I restored it to the defaults and now everything works. MANY THANKS!

  5. #5
    dBpoweramp Guru
    Join Date
    Nov 2013
    Location
    New York
    Posts
    450

    Re: "Error unable to open File" while ripping; filename spaces replaced with "&*9837;

    I am glad that solved your issue. I couldn't think of very many things that could cause that. Good luck and let us hope that the table doesn't get corrupted again. Let us also hope that there aren't other things on your PC that got corrupted. You might want to check your hard drive(s) for problems. This is probably a good time to think about backing things up, both your music files and your whole drive(s).

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •