This medium is not writable Nero 5.5/Plextor 5224A

Okay, I’ve seached this forum and (virtually) 20 others, I’m hoping I can get some sage advice.

Had problems with my old Yamaha 20x CD-RW drive. Bought a new Plextor 5224A. Nice drive, IDE.

PlexTools Professional 2.01 writes to the CD-R’s (I’m using two different mfr’s, both supported by the drive); Roxio EZ CD 6 writes to the CD-R’s.

Then I decided that I want to use Nero because the other software, well, it’s a bit sophomoric. But Nero is giving me an error when I try to burn:

“This medium is not writable”

Doesn’t matter what disc I use, and it only happens with Nero.

Nero FAQ says that it’s because it’s a CD-RW disc, it’s not.

Normally I wouldn’t give a hoot, and would just use PlexTools Pro, but that particular piece of software doesn’t allow you to save sessions/compilations/projects - whatever one would like to call them. I’m familiar with Nero and have come to rely on it for the nearly 5,000 discs I burn a year. Frankly, I find Nero more powerful anyway, and would really like to continue using it.

The drive is supported by this version of Nero (5.5.10.24), and flashing the drive didn’t help. I upgraded to 5.5.10.52, no change.

Any ideas on why I’m getting this error?

Tia for any and all comments…

Peace,
YrbkMgr

By all means create another coaster but please paste the log here :wink:

Ah. Sorry, I wasn’t certain about forum rules with long posts and all.

Fwiw, I’m not burning coasters. It’s not burning them - as soon as I hit “burn”, it spits the CD out. Here’s the log:

Windows 98 4.10
IA32
WinAspi: File ‘Wnaspi32.dll’: Ver=4.60 (1017), size=48128 bytes, created 11/12/98 6:06:00 AM
Nero Version: 5.5.10.20
Recorder: <PLEXTOR CD-R PX-W5224A>Version: 1.02 - HA 2 TA 0 - 5.5.10.20
Adapter driver: <amdeide> HA 2
Drive buffer : 2048kB
Bus Type : via Inquiry data (1) -> SCSI, detected: ?
CD-ROM: <PLEXTOR CD-R PX-W5224A>Version: 1.02 - HA 2 TA 0 - 5.5.10.20
Adapter driver: <amdeide> HA 2
Bus Type : default (0) -> SCSI, detected: ?
PLEXTOR CD-R PX-W5224A (Target 0, E:): Autoinsert Off, DMA ?, Disconnect ?, SyncDataXfer ?
Excluded drive IDs:
CmdQueuing : 1
CmdNotification: 2
WriteBufferSize: 49283072 (0) Byte
ShowDrvBufStat : 0
EraseSpeed : 0
BUFE : 0
Physical memory : 318MB (326640kB)
Free physical memory: 0MB (16kB)
Memory in use : 89 %
Uncached PFiles: 0x0
Use Static Write Speed Table: 0
Use Inquiry : 1
Global Bus Type: default (0)
Check supported media : Enabled (1)
Wizard: Off

16.2.2004
CD-ROM (ISO)
10:12:55 AM #1 Text 0 File Isodoc.cpp, Line 7579
Iso document burn settings
------------------------------------------
Determine maximum speed : FALSE
Simulate : TRUE
Write : FALSE
Finalize CD : TRUE
Multisession : FALSE
Burning mode : DAO
Mode : 1
ISO Level : 1 (Max. of 11 = 8 + 3 char)
Character set : ISO 9660
Joliet : TRUE
Allow pathdepth more than 8 directories : FALSE
Allow more than 255 characters in path : FALSE
Write ISO9660 ;1 file extensions : TRUE

10:12:55 AM #2 Phase 157 File dlgbrnst.cpp, Line 1655
Buffer under run proof activated

10:12:55 AM #3 Text 0 File Reader.cpp, Line 115
Reader running

10:12:55 AM #4 ISO9660GEN -11 File geniso.cpp, Line 4563
First writeable address = 0 (0x00000000)

10:12:55 AM #5 Text 0 File Burncd.cpp, Line 3726
Turn on Disc-At-Once, using CD-R/RW media

10:12:55 AM #6 Text 0 File ThreadedTransferInterface.cpp, Line 672
Setup items (original item values)
0: TRM_DATA_MODE1 (CTransferItem)
2 indices, index0 (150) not provided
original CD pos #0 + 270078 (270078) = #270078/60:1.3
relocatable, CD pos for caching/writing not required/required, no patch infos
--------------------------------------------------------------

10:12:59 AM #7 Phase 40 File dlgbrnst.cpp, Line 1655
Aborted by user

10:12:59 AM #8 Text 0 File DlgWaitCD.cpp, Line 215
Disc check failed: Medium not writable (Wrong CD)

10:12:59 AM #9 Text 0 File DlgWaitCD.cpp, Line 220
Write in overburning mode: FALSE

10:12:59 AM #10 Text 0 File DlgWaitCD.cpp, Line 1657
Recorder: PLEXTOR CD-R PX-W5224A;
CD type reading failed
ATIP Data: ?

10:12:59 AM #11 Text 0 File Scsicmd.cpp, Line 406
SCSI not using temporary buffers
20 out of 20 temporary buffers allocated

Existing drivers:
File ‘IoSubSys\SCSI1HLP.VXD’: Ver=4.10.1998, size=19270 bytes, created 4/23/99 10:22:00 PM
File ‘IoSubsys\NEROCD95.VXD’: Ver=4.5.0.14, size=39882 bytes, created 3/11/02 12:55:38 PM
File ‘IoSubsys\CDR4VSD.VXD’: Ver=6.1.1.7 , size=102128 bytes, created 6/25/03 12:18:48 AM
File ‘IoSubsys\CDRALVSD.VXD’: Ver=6.1.1.7 , size=20043 bytes, created 6/25/03 12:18:48 AM
File ‘IoSubsys\DRVWPPQT.VXD’: Ver=3.10.93a, size=260991 bytes, created 7/13/99 3:10:00 AM
File ‘IoSubsys\CDFS.VXD’: Ver=4.10.1998, size=59133 bytes, created 4/23/99 10:22:00 PM
File ‘IoSubsys\ESDI_506.PDR’: Ver=4.10.2222, size=24406 bytes, created 4/23/99 10:22:00 PM
File ‘…\System\Vmm32\Ios.vxd’: Ver=4.10.2222, size=69570 bytes, created 4/23/99 10:22:00 PM
File ‘IoSubsys\Disktsd.vxd’: Ver=4.10.2222, size=18809 bytes, created 4/23/99 10:22:00 PM
File ‘IoSubsys\AMDEIDE.MPD’: Ver=1.21 RC, size=30720 bytes, created 9/6/99 3:17:28 PM (Adapter driver for rec)

Registry Keys:

You have several issues. You’re running Win98 which has drivers that Nero does not like.

File ‘IoSubSys\SCSI1HLP.VXD’: Ver=4.10.1998, size=19270 bytes, created 4/23/99 10:22:00 PM
File ‘IoSubsys\CDR4VSD.VXD’: Ver=6.1.1.7 , size=102128 bytes, created 6/25/03 12:18:48 AM
File ‘IoSubsys\CDRALVSD.VXD’: Ver=6.1.1.7 , size=20043 bytes, created 6/25/03 12:18:48 AM
File ‘IoSubsys\DRVWPPQT.VXD’: Ver=3.10.93a, size=260991 bytes, created 7/13/99 3:10:00 AM
There’s no physical memory left

>Physical memory : 318MB (326640kB)
>Free physical memory: 0MB (16kB)

DMA status is also unknown

>PLEXTOR CD-R PX-W5224A (Target 0, E: Autoinsert Off, DMA ?, Disconnect ?, SyncDataXfer ?

What’s the state of play with your chipset drivers? Old or recent?
Go to the Nero website and sift through the Help File on 3rd party drivers; some will need to be disabled *.VXD —> *.VX_

Scan through this announcement as well for some more tips

http://club.cdfreaks.com/announcement.php?s=&forumid=79

You’ll also find some previous posts with Nero/Win98, too

Thanks Future,

In regards to Win98, I understand your point, but I’ve been running Nero with the old Yamaha 20x drive since June 2001, it just died, so the only thing that’s really changed is the drive (Plextor). Duly noted though.

As far as DMA status, it’s the most perplexing thing. I’m using an AMD AMDEIDE.MPD on a Kadoka MOBO (Gateway circa 2001) which is supposed to be DMA/Ultra DMA; there is no check box in the drive properties for DMA. From what I’ve read (I’ve spent about two weeks on this), it’s only for Intel chipsets.

Anyhoo found this:
Q: Why has the DMA box disappeared in the hard disk Device Manager under Windows 95/98?

A: The DMA box can only be used with the standard Microsoft driver. When a third-party driver is installed (such as the AMD EIDE Driver), the DMA box will no longer appear. However, the driver is programmed to use all devices in their most optimal configuration. Therefore, if DMA is available for that particular device, the driver will use it.

Again, DMA has been that way since I installed the Yamaha moons ago, and PlexTools as well as Roxio don’t tell me the media isn’t writable. <shrug>

In regards to the memory, that was the first log file I’ve seen that in, I have dozens of others showing between 13 and 35MB of free memory, and the same problem.

Don’t get me wrong, I’m not being argumentative, I’m just saying that while you’re right on many points, nothing prevented me from burning discs prior to installation of the new plextor.

I’ll take your advice and see about disabling some VXD’s; I remember reading about them at one point on the Nero site, but wasn’t having a problem, so <shrug> didn’t worry about it. Now I’ll have to find them again.

In sum, I cannot imagine it’s win98, and as I say, the other apps burn CD’s, so it’s not as straightforward as I would hope. But you’ve pointed me in a direction, so thank you. If it makes sense, and I find a resolution, I’ll post back the results.

Peace,
YrbkMgr.

Though I’m no expert here, and I’m more than willing to bow to superior knowledge, might it not be better to uninstall the Roxio software rather than just disable its VxDs?

Is the Roxio software still likely to work with bits of itself disabled? If not, I wonder whether it is better to uninstall it - in the hope you get a clean uninstall!

David

David,

Thank you kindly for the reply. I seem to remember reading that even though one uninstalls Roxio, those VXD’s remain. I have been searching high and low for the reference to those VXD’s on the Nero site, and am coming up short, but I’m not certain that’s where I saw the reference - it may have been here or another forum, I’m continuing to look.

That said, there is a certain amount of probity to uninstalling Roxio and trying it, so thanks for the suggestion, I’ll try that today, while I continue my search.

Thanks again!

Peace,
YrbkMgr

Originally posted by YrbkMgr
I have been searching high and low for the reference to those VXD’s on the Nero site, and am coming up short,
http://www.nero.com/us/631941507584102.html

specifically

drivers of other CD burner programs
The following is a list of drivers which either belong to other CD burner programs or can cause problems. If you want to test to see if the problems with Nero no longer occur if the corresponding drivers are no longer there, then there are 2 possibilities:

Deinstall the attached program. Unfortunately in some cases the pertinent drivers are not also removed. Then the drivers have to be removed manually. The drivers can be found in the Windows\System\IOSUBSYS directory.
Rename the drivers. Do Please not change the name itself but the name extension, change .VXD , e.g.: to .VX_ Please bear in mind that drivers are also loaded with a file extension such as .VXD.OLD or .OLD.VXD. The drivers can be found in the Windows\System\IOSUBS directory.
The following is a list of the drivers:

Drivers which belong to software from CeQuadrat :
ATAPIZER.VXD
C2APIX.VXD
C2REC.VXD
C2UDFFS.VXD
C2SCSI.MPD
C2UDFVSD.VXD
CDD2000.VXD
TOEXTNDR.VXD
UDF_200.VXD
UDF_920.VXD
UDF_JVC.VXD
There are systems with which WinOnCD and Nero can be installed in parallel without problems ocurring. This can also be encouraged: See Nero and WinOnCD.

Drivers which belong to software from Adaptec:
CDR4VSD.VXD
CDUDFRW.VXD
CDUDF.VXD
CDRPWD.VXD
Drivers for Gear:
MINIASPI.VXD
GEARCDR.VXD
The HP Support Hotline recommends removing the following drivers if problems should occur:
ADPINSTR.VXD
ATAPICHNG.VXD
ATAPIZER.VXD WinOnCD / PacketCD
This driver is necessary to be able to contact
IDE devices with WinOnCD, which include recorders
as well as CD-ROMs (Audio reading and CD copy)
BLITZ95.VXD
C2REC.VXD WinOnCD / PacketCD
Disables the auto insert notification
while writing.
CD_READ.VXD Iomega RecordIt: Causes problems with
Direct CD (On starting Windows you get
a blue screen)
CDRASPI.VXD Corel CD Creator / HP Software
CDREXIFS.VXD for PacketWriting with CDR-Extensions
can cause problems with Multisession-burning,
to prevent this before starting Nero insert a CD in the
burner and click on or update
CDREXUNL.VXD to read CD’s with CDR extensions in the
backup format can cause problems with audio CDs in the
CD-Reader, to prevent this problem remove and don’t use this
format.
CDRFS_R0.VXD
CDRHROM.VXD
CDRH92X.VXD
COREL*.VXD
DRVSPACX.VXD Seagate Backup Exec
DRVWPPQT.VXD Seagate Backup Exec. Is included in Windows 98.
There are problems if an HP 7100e is attached to the parallel
port as the driver sees the HP 7100e as a
Tape Device.
DRVWQ117.VXD Seagate Backup Exec
HDLED.VXD Hard Disk LED: can Windows
Protection Error Device IOS: please restart
Windows cause:
-> download the newest driver:
http://ourworld.compuserve.com/homepages/bohdan/hdled.vxd

IMG_IDE.VXD
INFRAIOS.VXD Driver from Creative Infra 1800 CD-ROM. Download
newest version, as it causes problems with e.g.
Microsoft Home Series:
NECATAPI.VXD Driver for older NEC CDROM drives. This
driver sometimes causes buffer underruns.
SCSI1HLP.VXD Windows 95/98
Is required to play VideoCDs by IDE-CD-ROM
devices. Causes conflicts with the
Adaptec driver CDR4VSD.VXD
SCSIPWR.VXD presumably for Power-Down for SCSI devices.
It also exists under NT (SCSIPWR.SYS)
SCSIWCDR.VXD
SCSIWCDR.VXD driver for read with XR-W2001/2010/2020
is normally compatible with Nero .
SISVSD.VXD SIS chip set
TOEXTNDR.VXD WinOnCD / PacketCD
This driver extends the TimeOut. This
driver not being there can cause
a TimeOut error or a Bus Rest error
for certain recorders.
VXDASPI.VXD HP Software / Corel CD Creator
VSD_CUNI.VXD HP Software / Corel CD Creator
PIIXIDE.SYS IDE Busmaster driver. Causes a total crash of
Windows NT shortly after the burning process.
(At least the version 2.05 dated 07.12.98)
Driver of Prassi / CD Right! Plus
PTASPI.VXD
PTVSD.VXD Provides the function called CD Blocking
which blocks access to a drive for all
programs.
Driver of CD Wizard (VOB)
ASAPI.VXD Driver to release IDE devices via the ASPI
interface.
In one customer’s case, this driver caused a
2s pause to be inserted between the first and the second track on newly
burned audio CDs.
After deleting this file (and REGTAPE.VXD
and DRVW*.VXD from Windows98), the
problem was resolved.
other drivers:
CDFS.VXD This is actually an original Windows 95/98 driver.
Problem: There is a program called CDFS
which overwrites precisely this driver. This
program causes problems in ORIGINAL Windows 95
(Audio track 1 can not be read).
This driver enables the CDA files to be
shown in Explorer as
playable WAV files.
The program comes from Microsoft itself and has
the version 4.00.1030 -> from Windows 98 which use
files CDTSD.VXD and CDVSD.VXD
(in Win98 Cab 47)
ezbtnvxd.vxd This driver belongs to the IBM Rapid Access keyboard.
this driver causes problems. It is possible
that this problem can be solved with V1.3.
PIIXVSD.VXD Removing this driver is what actually made it
possible for some users to access the CD-ROM
drive at all.
If you can identify a driver as the cause of a certain problem and it doen’t appear in this list, we would be grateful if you could let us have the name of the driver including the problems it causes.

Future,

Thank you so much for going to the trouble to find that information and post it. I’ve now bookmarked it. Since I’ve been trying to solve this problem, I’ve been all over the map and as you might imagine, where I find what is now beginning to blur (grin).

This is a MOST perplexing issue. I have uninstalled Roxio (which I cannot stand anyway), I have disabled all questionable VXD’s. I just cannot understand why Nero refuses to recognize the disc as writable.

Here’s the latest log, and a screenshot. The screenshot is what appears just as I start to write to the disc, I’ve attached it. Oh, and another point, when you choose Recorder|Medium Info from the Nero menu, it shows the disc as a 750 mb blank CD.

AND, the screenshot says it needs a CD-R and the media type is a CD-R. If you notice in the log it says “(Wrong CD)” - impossible.

This completely rots - I have no idea why nero is refusing to write to ANY media I put in. Thoughts?

Windows 98 4.10
IA32
WinAspi: File ‘Wnaspi32.dll’: Ver=4.60 (1017), size=48128 bytes, created 11/12/98 6:06:00 AM
Nero Version: 5.5.10.54
Recorder: <PLEXTOR CD-R PX-W5224A>Version: 1.03 - HA 2 TA 0 - 5.5.10.54
Adapter driver: <amdeide> HA 2
Drive buffer : 2048kB
Bus Type : via Inquiry data (1) -> SCSI, detected: ?
CD-ROM: <PLEXTOR CD-R PX-W5224A>Version: 1.03 - HA 2 TA 0 - 5.5.10.54
Adapter driver: <amdeide> HA 2
Bus Type : default (0) -> SCSI, detected: ?
PLEXTOR CD-R PX-W5224A (Target 0, E:): Autoinsert Off, DMA ?, Disconnect ?, SyncDataXfer ?
Excluded drive IDs:
CmdQueuing : 1
CmdNotification: 2
WriteBufferSize: 49283072 (0) Byte
ShowDrvBufStat : 0
EraseSpeed : 0
BUFE : 0
Physical memory : 318MB (326640kB)
Free physical memory: 23MB (23928kB)
Memory in use : 72 %
Uncached PFiles: 0x0
Use Static Write Speed Table: 0
Use Inquiry : 1
Global Bus Type: default (0)
Check supported media : Enabled (1)
Wizard: Off

18.2.2004
CD-ROM (ISO)
6:36:40 AM #1 Text 0 File Isodoc.cpp, Line 7604
Iso document burn settings
------------------------------------------
Determine maximum speed : FALSE
Simulate : TRUE
Write : FALSE
Finalize CD : TRUE
Multisession : FALSE
Burning mode : DAO
Mode : 1
ISO Level : 1 (Max. of 11 = 8 + 3 char)
Character set : ISO 9660
Joliet : TRUE
Allow pathdepth more than 8 directories : FALSE
Allow more than 255 characters in path : FALSE
Write ISO9660 ;1 file extensions : TRUE

6:36:40 AM #2 Phase 157 File dlgbrnst.cpp, Line 1655
Buffer under run proof activated

6:36:42 AM #3 Text 0 File Reader.cpp, Line 115
Reader running

6:36:42 AM #4 ISO9660GEN -11 File geniso.cpp, Line 4571
First writeable address = 0 (0x00000000)

6:36:42 AM #5 Text 0 File Burncd.cpp, Line 3769
Turn on Disc-At-Once, using CD-R/RW media

6:36:42 AM #6 Text 0 File ThreadedTransferInterface.cpp, Line 672
Setup items (original item values)
0: TRM_DATA_MODE1 (CTransferItem)
2 indices, index0 (150) not provided
original CD pos #0 + 270078 (270078) = #270078/60:1.3
relocatable, CD pos for caching/writing not required/required, no patch infos
--------------------------------------------------------------

6:37:15 AM #7 Phase 40 File dlgbrnst.cpp, Line 1655
Aborted by user

6:37:15 AM #8 Text 0 File DlgWaitCD.cpp, Line 229
Disc check failed: Medium not writable (Wrong CD)

6:37:15 AM #9 Text 0 File DlgWaitCD.cpp, Line 234
Write in overburning mode: FALSE

6:37:15 AM #10 Text 0 File DlgWaitCD.cpp, Line 1703
Recorder: PLEXTOR CD-R PX-W5224A;
CD type reading failed
ATIP Data: ?

6:37:15 AM #11 Text 0 File Scsicmd.cpp, Line 406
SCSI not using temporary buffers
20 out of 20 temporary buffers allocated

Existing drivers:
File ‘IoSubsys\NEROCD95.VXD’: Ver=4.5.0.14, size=39882 bytes, created 3/11/02 12:55:38 PM
File ‘IoSubsys\CDFS.VXD’: Ver=4.10.1998, size=59133 bytes, created 4/23/99 10:22:00 PM
File ‘IoSubsys\ESDI_506.PDR’: Ver=4.10.2222, size=24406 bytes, created 4/23/99 10:22:00 PM
File ‘…\System\Vmm32\Ios.vxd’: Ver=4.10.2222, size=69570 bytes, created 4/23/99 10:22:00 PM
File ‘IoSubsys\Disktsd.vxd’: Ver=4.10.2222, size=18809 bytes, created 4/23/99 10:22:00 PM
File ‘IoSubsys\AMDEIDE.MPD’: Ver=1.21 RC, size=30720 bytes, created 9/6/99 3:17:28 PM (Adapter driver for rec)

Registry Keys:

By the way, thanks for your efforts so far. I don’t want to become one of those PITA’s, but there MUST be something I can do to be able to use Nero - I cannot believe that for as powerful an app as Nero is, that it “just falls short”. Something’s amiss…

Thanks,
YrbkMgr:confused: