Today, I burned a few more Ritek Mini CD-R media, where I found out they have a surface issue:
I didn’t realized this, but it seems to be a plant manufacture problem. I opened another of the 100-pack I have and it have the same problem.
The problem is that the data was burning fine, with no errors on my Lite-On iHAS524, but it failed to verify on some parts of the disk, as it was approaching the end. I was burning them at 24x, the maximum speed it supports on the writer.
I decided to use the Optiarc AD-7561A drive I have to see if it would burn fine with it, since slim drives usually burns at a lower speed.
When the CD is inserted in this drive, it is detected as a 10x media:
I burned the CD with this drive, where it was able to both burn and verify successfully. It also seems that the drive burned surface is a bit darker than with the LiteOn drive, so maybe that makes it handle the bad surface better.
I burned 2 CD’s with the Lite-On drive where both burned successfully but didn’t read fine. One was able to read completely, but lowering the read speed at the bad section. The other one failed with unrecoverable errors.
Let’s see their quality tests with the LiteOn drive first, followed with the Optiarc drive:
CD #1 – LiteOn
This is the CD that was able to read completely but lowers the speed. When playing it back, it pauses while reading the wrong area. It can be ripped, but will struggle in the bad area. The ripped file appears to be fine, but EAC reports timing problems. Listening to the track didn’t revealed any issues.
You can see the excesive amounts of C1 and C2 errors.
CD #2 – Optiarc
Here is another burn of the same data, burned with the Optiarc drive and tested on the LiteOn drive. You can see that it only reports a maximum of 10 C1 errors and no C2 errors. The quality score is 99%. Same media, but burned on a different drive, at 10x speed.
CD #3 – LiteOn
This CD failed to test properly. Once again, you can see the excessive amounts of C1 and C2 errors. The positions of the C1 and C2 errors seem to match the ones of the previous LiteOn burn.
CD #4 – Optiarc
Here is another burn of the same data of the previous burn. You can see this time it was successful, with only a maximum of 8 C1 errors and a total of 19. Again, the quality score is 99%, which is the same as the other Optiarc-burned media.
As seen from the above tests, it seems the Optiarc AD-7561A drive can successfully burn these discs if we intend to use all of its capacity. Maybe it is because of the slower burning speed, or because the optical laser can burn them better than the one on the LiteOn drive.
The LiteOn drive can only burn these CDs at 16x and 24x, while the Optiarc can only burn them at 10x. I’ll test burning a disc at 16x at a later time and see if it works. If not, I’ll continue using the Optiarc drive, which has proven to burn them correctly and without any issues.
Today, I’ll guide you through the steps of installing Node.js 10.x on Ubuntu Focal (20.04) which is stated to be officially released on April 23, 2020.
Right now, installing Node.js using the NodeSource Node.js official repositories do not work because they do not support unreleased versions of Ubuntu.
You may think of using a previous Ubuntu repository in order to install Node.js, but this will actually not work. This is because Ubuntu 20.04 renamed the Python 2 packages from
Trying to install Node.js using the NodeSource repositories
The easiest way to normally install Node.js 10.x is by using the official NodeSource repository. For this, we follow their steps.
curl -sL https://deb.nodesource.com/setup_10.x | sudo -E bash
The problem is that because the OS hasn’t been officially released, we get the following issue:
No problem. Let’s move to the manual installation method:
- Add the NodeSource package signing key:
curl -sSL https://deb.nodesource.com/gpgkey/nodesource.gpg.key | sudo apt-key add -
- Set the version to node_10.x:
- Let’s set the distro to
eoan, the current stable Ubuntu version:
- Now, we need to add the repository to our Linux installation:
echo "deb https://deb.nodesource.com/$VERSION $DISTRO main" | sudo tee /etc/apt/sources.list.d/nodesource.list
echo "deb-src https://deb.nodesource.com/$VERSION $DISTRO main" | sudo tee -a /etc/apt/sources.list.d/nodesource.list
- The commands should like this in the terminal:
- We can now run
sudo apt updateto update the repository information:
- We will now attempt to install the nodejs package by running
sudo apt install nodejs:
As you can see above, following the manual installation steps fails as well because there is no
python-minimal package in Ubuntu 20.04. To solve this, we will manually download the Node.js Debian package and modify it to have it refer to
python2-minimal instead of
Manually downloading, modifying and installing Node.js 10.x
- We will manually navigate to the repository to download the file here: https://deb.nodesource.com/node_10.x/pool/main/n/nodejs/
- From there, just copy the desired Node.js package link to the clipboard. Then, use
wgetto download it on the terminal. I recommend downloading it to a clean directory since we will run some commands to extract and perform some modifications to it:
- Once the download finishes, we need to extract the downloaded debian package with the
ar x nodejs_10.19.0-1nodesource1_amd64.deb
- We need to extract the
tar -xzf control.tar.gz
- Using nano or your favorite text editor, we will edit the
controlfile. Look for
- Save the file. On nano, press
CTRL + O, then exit pressing
CTRL + X.
- We now need to recreate the
control.tar.gztar package to include the modified
controlfile. To do this, we will run the following command:
tar -czf control.tar.gz control md5sums postinst pr einst prerm
- Finally, we will replace the
control.tar.gzin the debian package file. We will run the following command to do so:
ar -r nodejs_10.19.0-1nodesource1_amd64.deb control.tar.gz
- We can now install the package with
dpkg. We’ll run the following:
sudo dpkg -i nodejs_10.19.0-1nodesource1_amd64.deb
After following the above steps, we should have Node.js installed on our operating system. We can confirm this by running
node -v and
And that’s it! We have successfully installed Node.js on our Ubuntu Focal installation.
Yesterday, I received some Pocket/Mini CD-R I purchased on eBay, which were being sold for cheap due to them not being branded or not having their specs listed.
The seller was selling 3 packs of 100 unbranded silver surface Mini CD-R, and since the price was lower compared to other branded media, I decided to buy all 3.
The discs were wrapped with no spindle.
The discs have a silver surface:
Here we can see a single CD-R:
They have the usual light green color on the data side.
The disc loaded fine on my LiteOn iHAS524 drive. I launched ImgBurn which says that the discs are made by Ritek. Their media ID is 97m15s17f:
They also have a capacity of 210MB or 24 minutes and a maximum write speed of 24x.
This is the first Mini CD I use with this LiteOn drive, which has the unique LabelTag feature to add labels to the data side. The software detected the disc and a label can be created:
I burned some of these CD-R with Nero Express, which allows the creation of the label on the same run. I also burned them at its maximum speed of 24x without any failure.
I ran a Disc Quality test using Nero DiscSpeed. Below you can see the results of those tests. I limited the test to the first session of it, as the second one is the label produced with the above software and contains unreadable data. This makes the test fail. By limiting it to the first session, we can get the actual data track quality.
The first test gave us a maximum of 14 C1 errors with a total of 58. The average was 0.11. There were no C2 errors reported. The Quality Score was 98%.
This test was perfect! No C1 or C2 errors were reported, making the Quality Score be 100%.
This disc had a maximum of 9 for the C1 Errors with a total of 13. The average was 0.07. No C2 errors were reported. The Quality Score was 99%.
This final disc I burned had a maximum of 13 C1 errors with a total of 27. No C2 errors were reported. The Quality Score was 98%.
These blank CD-R media seems to be good to write small amounts of data. This could be an MP3 album, some photos, or software you’d like to archive. The burns seem to be of good quality and the 24x burning speed is adequate. This sure was a great find on eBay!
Today, I have released Audio MD5 Checker v0.7:
This version adds the ability to change the Frame Size by clicking on the new Set Frame Size link:
Also, the Source Checksums and Frame Mistatches listbox are now resizable:
You can download this new version on GitHub by clicking here.
Today, I have released Audio MD5 Checker v0.5:
This release adds a FrameMD5 check in addition to the usual MD5 check performed to the audio stream. This makes it possible to see where the mismatches are in a file.
Here’s how to use the new MD5 feature of it:
- All files will be checked with both MD5 and FrameMD5.
- When the file checking finishes, double click on either the source or comparison file. The whole FrameMD5 information will be shown.
- To show only where the MD5 mismatches occur, double click on the number shown in the “Frame Mismatch” list.
You can download this release on GitHub by clicking here.