Tweet
I have a MF Digital Scribe of 2005 vintage that I am trying to use to rip my collection of cds. I initially had problems with the old hardware not wanting to run dBpoweramp and by extension batch ripper. I eventually overcame such struggles by acquiring a previous version which would run on the 32 bit version of XP that was original to the machine, but was unable to utilize AccurateRip due to the older version and networking limitations of the stock computer hardware/browser support. Particularly, it failed to find any metadata on all of the CDs I tested. After duplicating the boot drive and replacing it with a new one (after which I confirmed function)and installed vista (32 bit) in hopes that it would allow more recent software versions to run, which solved the metadata problem, but brought about the issue I am requesting help with here. Once Vista was installed and running, I was no longer able to control the loader of the Scribe machine. I was met with the following message upon attempting to test the CLIs when configuring Batch Ripper:
"Unable to find com port 'com1' Exiting ULCLI in ..."
I used the same CLI strings as worked before. I confirmed several times that this is the correct COM port and can control the loader manually by sending commands to it via PuTTY and the robot is recognized on COM1 in the MF Digital software. I have also duplicated this same error by replacing all of the physical computer hardware with an existing (and fully functional) PC running Windows 10 (64 bit), with the loader control board connected to the serial port header on the motherboard there. Windows 10 seems to gladly run the dBpoweramp and Batch Ripper software, but still fails to find the COM port only in Batch Ripper. I can still talk to the loader with PuTTY, but that isn't really the ultimate goal. Can anyone help me figure out why I am now having trouble establishing a serial connection with this loader?
"Unable to find com port 'com1' Exiting ULCLI in ..."
I used the same CLI strings as worked before. I confirmed several times that this is the correct COM port and can control the loader manually by sending commands to it via PuTTY and the robot is recognized on COM1 in the MF Digital software. I have also duplicated this same error by replacing all of the physical computer hardware with an existing (and fully functional) PC running Windows 10 (64 bit), with the loader control board connected to the serial port header on the motherboard there. Windows 10 seems to gladly run the dBpoweramp and Batch Ripper software, but still fails to find the COM port only in Batch Ripper. I can still talk to the loader with PuTTY, but that isn't really the ultimate goal. Can anyone help me figure out why I am now having trouble establishing a serial connection with this loader?
Comment