Error: Unexpected ASPI Error: (04h 00h 00h) “Error ‘Write Command Failed On Device X:X:X”

Question:

Error: Unexpected ASPI error: (04h 00h 00h) “Error ‘Write command failed on device X:X:X”

Answer:

The Drive is going bad.

Try a different USB port if it is an external drive. If this still doesn’t work, then it could mean that the USB case is going bad or has gone bad. Try a new case to see if this fixes the problem, or try it on a different computer. If the drive is an Internal drive, then make sure you have all of the Windows Updates and the latest drivers for the Motherboards chipset drivers.

You should also update to the latest version of the software, as it no longer uses ASPI.

Error: Invalid CUE SHEET Command At Line xx. Previous File Is Not A Multiple Of The Specified Block Size

Question:

Error: Invalid CUE SHEET command at line xx. Previous file is not a multiple of the specified block size.

Answer:

This message appears when writing a CDR disc in the Custom Assembly Tab when you click the Write CD or Test Write buttons. You have added a bad .cdg file to the project.

SOLUTION #1: Be sure the project in the Open/Save project: field does NOT contain both .cdg karaoke files and .wav audio files. Only use one file Type. You should also updgrade to Version 4.00x as it supports this.

SOLUTION #2: One or more imported or created files added to project are bad (a file may be named .cdg, but only contain audio samples, which makes it a .wav file).

To find a bad file, click the New Button in the Custom Assembly Tab to create a new .lst project. Then, add one file to the project and click the Test CD button. If this file is damaged, you will see the error message. If it is good, you will not and you can add the next file to the project. Click the Test CD button after you add each new song track file. When you see the error message, delete that bad file from the project and from the hard drive.

If want the song, go to the Import Tracks Tab and re-import it again.

SOLUTION #3: Keyrite 1.302 would allow you to change the output file type from .wav to .cdg. Some users believed that would create a .cdg file, but it just renamed the audio-only file a .cdg filename extension. The lyrics/graphics data required to be in the .cdg file was missing, which would display this error. In later Keyrite versions, you can only write the file type you have opened for processing; i.e. an open CDG file will only write a CDG file. An open WAV file will only write a WAV file.

Error: Unexpected Failure Writing File { Disc Full }

Question:

Error: Unexpected failure writing file { disc full }.

Answer:

 You are trying to save to a CD-Rom or CD-Recorder drive, which can’t be done this way.

On the Duplicate Disc, the Custom Assembly, and the Import Tracks tab, click the Select Folder button and select a folder on your hard drive, not your CD-Rom or CDR drive.

Error: Please Select A Reading Device (CD ROM).

Question:

Error: Please select a reading device (CD ROM).

Answer:

This bug occurs on the Duplicate Disc Tab in Microstudio 2.605- 3.004 versions.  Please update to Version 4.00x or do the following.

Click the down arrow next to Reading drive in any screen where it appears. Then click your Plextor or other working drive. Do this each time that you get this error.

This will be fixed in a future version of Microstudio.

Error: Write Command Failed On Device 1:1:0 Read/Write Error Or Bad Medium Detected (04h 00h 02h 03h 73h 03h)

Question:

Error: Write command failed on device 1:1:0 read/write error or bad medium detected (04h 00h 02h 03h 73h 03h)

Answer:

 Your computer is not sending data to the CD-R drive fast enough.

 Find what is slowing down your computer.

  1. Run Windows Disc Defragmenter by going to the Start Menu\Programs\Accessories\System Tools\Disc Defragmenter.
  2. Run all of the Windows updates by clicking here.
  3. Run Spybot Search and Destroy to search for and remove Spyware from your computer.
  4. Update your Motherboard drivers from your computer manufacturer. These will be called the Chipset drivers or Motherboad drivers.

This should help, as you look for what is slowing down your computer.

Error Messages Dealing With ASPI

Question:

Error messages dealing with ASPI

Answer:

Upgrade to the latest version of our software, as this is no longer used.

Click the Start Menu, Search\All Files and Folders. Type in the filename WNASPINT.dll. Select to search only the C:\ drive. Once this file is seen in the right window, usually in the c:\Windows\System32 folder, Left click the file to select it and press the Delete Key to remove it from your computer.

Next, click the following link and go to Solution #2. Complete this solution to fix this ASPI problem. Click here for how to reinstall the ASPI drivers.

Error: ‘Start DAO Recording’ Command Failed On Device 3:0:0 Disc Type Is Not Supported.

Question:

Error: ‘Start DAO Recording’ command failed on device 3:0:0 Disc type is not supported.

Answer:

This error may also appear as:

Error: ‘TEST UNIT READY’ command failed on device 1:1:0. Device contains no disc or is not ready. (04h 00h 02h 02h 3Ah 00h

Upgrade to Microstudio 4.00x and this error will no longer occur. If you do not wish to upgrade, then the following should allow you to fix this problem.

This occurs with any of the DVD-/+R drives. This includes the Plextor PX-W708, PX-W712 Px-W716 DVD Recorder Models. Some users have seen this when installing some Printer software drivers.

Remove Roxio EZ CD Creator 6 and Nero 6 or any other Burning program from starting at boot. Most of the time you can go into the programs settings and turn off the option to start the program at Windows Startup. These programs are known to cause this error.

 

Question: Error: Unable To Read AUDIO Sectors 0 to 25 on device 0:0:0 ‘Illegal Command Request’ (04h 00h 02h 05h 24h 00h)

Question:

Error: Unable to read AUDIO sectors 0 to 25 on device 0:0:0 ‘Illegal command request’ (04h 00h 02h 05h 24h 00h)

Answer:

The CD-R drive doesn’t support the CD+G format correctly. If this is the problem, you would need to replace the drive for it to work.

One other thing to try is a different brand of disc, as this disc could also have copy protection on it, that can also cause this.