10-04-2020, 05:14 PM
I am perplexed as well. I have not installed any new USB devices. The FTDI driver installed is the latest one (from 2018 as I recall). I even unplugged all USB devices except the KB and mouse which did not help. I did just notice that if I unselect 'Re-seek track 0' I will get a red line the first time it tries to read that track and if I try it again the red line is gone. If I re-enable the 'Re-seek track 0' of course I get the red line.
As I was writing the above I got to wondering if there was any sort of configuration file somewhere other than C:\Program Files(x86)\SCP. I found C:\Users\**user**\AppData\Local\SCP\scp.ini. Nothing really looked odd but I added a '.x' to the end of the file name and when I started SCP it created a new .ini file.
After it generated a new .ini file it now works fine! What the heck?? That only thing that is really different, other than file paths and disk type settings, is the 'Past Radix' under the Analyzer section. Maybe there is some garbage character throwing off the parser? I did not look at look at the files with a hex editor. I put both in a ZIP file and attached to this post.
I'm glad that was it but am really curious what was wrong with the original .ini file.
As I was writing the above I got to wondering if there was any sort of configuration file somewhere other than C:\Program Files(x86)\SCP. I found C:\Users\**user**\AppData\Local\SCP\scp.ini. Nothing really looked odd but I added a '.x' to the end of the file name and when I started SCP it created a new .ini file.
After it generated a new .ini file it now works fine! What the heck?? That only thing that is really different, other than file paths and disk type settings, is the 'Past Radix' under the Analyzer section. Maybe there is some garbage character throwing off the parser? I did not look at look at the files with a hex editor. I put both in a ZIP file and attached to this post.
I'm glad that was it but am really curious what was wrong with the original .ini file.