Burning error, cannot write medium

error says cannot write medium incompatable format, any ideas?
G5 Mac OS X (10.3)

Hi HGW2:
Look at these articles.
http://docs.info.apple.com/article.html?artnum=25750
http://docs.info.apple.com/article.html?artnum=151900
http://docs.info.apple.com/article.html?artnum=%2025480
Also, this is regarding high-speed media:
http://docs.info.apple.com/article.html?artnum=86130
Sue

Similar Messages

Formatting Failed: Cannot Write Medium...

Hi There,
I've been trying to burn a particular DVD now for some time. I've had nothing but problems with Compressor and DVDSP creating video artifacting (and yes, my audio is an AC3 file). This was never a problem in the older version though.
Anyways, I bought Sorenson Squeeze because it will encode MPEG 2 files as well as I need it for Flash. After I created a .MPV file from Squeeze I brought it into DVDSP and everything seems fine - until I went to format the disc I got the following error:
Formatting Failed
The recording device reported the not ready error:
Cannot write medium - incompatible format (0x30, 0x05.)
I tried burning the disc in Toast and got a formatting failed error there too. I'm trying to burn picture only right now so there are no audio files to screw any of this up.
Does anyone have any suggestions?
Thanks,
K

Hi Kristin:
Before trying to burn directly from DVDSP, did you build the project in your hard drive? I mean go to Format and select Destination > Output Device > Hard Drive. That will create an .img file (a DVD image file) that first: you can mount double clickig it and test it with DVD player, and second, you can take it and just drop into Toast icon (or drop the .img file into the Copy section of Toast)and burn the final video DVD.
In that way you use DVDSP for creating the complete final DVD structure and Toast to burn it. It could help in case that DVDSP doesn't "like" your media.

Cannot write medium

I used sony dvd-r. when i attempted to burn a project that was previously burned this is the message i get: Formatting failed- the recording device reported the not ready error: cannot write medium- incompatible format.(0x30),(0x5). I used i'd compressor to encode the video. i trahed the prefs. i am using fcp hd
thanks in advanced
scott

Are you sure this was a writable DVD you were using
and not a CD??
After an awesome weekend of troubleshooting, trips to the genius bar, and alot of reinstalling. problem solved the super drive could use only 8x or lower dvds
thanks for your replies, i really appreciate them
scott

Cannot write medium - incompatible format

Keep getting this message "the recording device reported the not ready error. Cannot write medium - incompatible format (0x30, 0x05)
Any suggestions?

If you more details on the project, the burner you are using, how you are writing the project, the DVD-R (is that what it is?), the set up of your computer (says PowerMac 7.3? and which OS of 10.4) it can help narrow it down
Also some threads
http://discussions.apple.com/thread.jspa?messageID=1090247&#1090247
http://discussions.apple.com/thread.jspa?messageID=1192904&#1192904
http://discussions.apple.com/thread.jspa?messageID=1087561&#1087561

IDVD cannot write medium !!!!

error message:
the recording device reported the illegal request
cannot write medium + incompatible format. (0x30,0x05)
I have ibook G4 bought in 2004 November. OS is OS10.3.9
I burned DVD by iDVD (iLife '04 I guess) then I get this error:
I used DVD -R 8x for medium
What is wrong ??

Welcome to discussions.
Could it be a defective disc? Try another. Most people seem to use DVD-R 4X but 8X should work if it is good quality.

The "alsa audio output error: cannot write: Broken pipe" problem

[Solved]
(No place for this word in the Subject field, so I put it here.)
Hi Arch community!
I noticed I have this problem and not sure when in started. Several months ago I bought and installed new videocard "GeForce GT 630". Right after installation I lost sound in the system. Having internal sound card (in mainboard) and SB Audigy2 (PCI), I searched for solution and found I had to disable "snd_hda_intel" module to restore sound to work through PCI sound card. Did it.
echo "blacklist snd_hda_intel" >> /etc/modprobe.d/no-nvidia-sound.conf
After that sound was working as it should. And I noticed recently that during playing of any sound file the sound interrupts. If run VLC from CLI I get "alsa audio output error: cannot write: Broken pipe" message. And my system hasn't been upgraded since I don't know when. I still ran Firefox 26. So googled again and found it's a bug in a kernel or somewhere else.
==========================================
https://bugs.freedesktop.org/show_bug.cgi?id=69942 :
2013-10-01 01:39:40 UTC
I ran a system update last night, and this issue appears to have been corrected.
==========================================
And so I thought upgrade would fix my problem since mainstream bug is fixed. After upgrade sound interrupts again, maybe even more often.
Do you guys have this issue and does anyone have a solution?
Last edited by Mr. Alex (2014-06-26 18:55:59)

Not particularly wise to blacklist the module, since it probably is also used by the integrated sound card. With vid and pid you could just disable the nvidia card alone using parameter enable=0. Unless you do not mind having both disabled.
Where do I need to input "enable=0"? When I was searching for solution to make my Creative card work with new nVidia card I installed, the only way I found was blacklisting the module.
dmesg says:
[ 20.448086] nvidia 0000:02:00.0: irq 42 for MSI/MSI-X
[ 21.112331] NVRM: Your system is not currently configured to drive a VGA console
[ 21.112340] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
[ 21.112345] NVRM: requires the use of a text-mode VGA console. Use of other console
[ 21.112349] NVRM: drivers including, but not limited to, vesafb, may result in
[ 21.112352] NVRM: corruption and stability problems, and is not supported.
Then:
lsmod | grep 'snd'
snd_ca0106 36242 0
snd_ac97_codec 114896 1 snd_ca0106
ac97_bus 1270 1 snd_ac97_codec
snd_rawmidi 20278 1 snd_ca0106
snd_seq_device 5244 1 snd_rawmidi
snd_pcm 83207 2 snd_ac97_codec,snd_ca0106
snd_timer 19294 1 snd_pcm
snd 60780 6 snd_ac97_codec,snd_timer,snd_pcm,snd_rawmidi,snd_seq_device,snd_ca0106
soundcore 5551 1 snd
I guess my card is "snd_ca0106". If yes,
# systool -v -m snd_ca0106
Module = "snd_ca0106"
Attributes:
coresize = "36242"
initsize = "0"
initstate = "live"
refcnt = "0"
taint = ""
uevent = <store method only>
Parameters:
enable = "Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y"
id = "(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)"
index = "-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1"
subsystem = "0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0"
Sections:
.bss = "0xffffffffa0814780"
.data = "0xffffffffa0813300"
.exit.text = "0xffffffffa0811a1e"
.gnu.linkonce.this_module= "0xffffffffa0814500"
.init.text = "0xffffffffa0817000"
.note.gnu.build-id = "0xffffffffa0811a30"
.rodata = "0xffffffffa0811a80"
.rodata.str1.1 = "0xffffffffa08123dc"
.rodata.str1.8 = "0xffffffffa0812130"
.strtab = "0xffffffffa0818c10"
.symtab = "0xffffffffa0817020"
.text = "0xffffffffa080d000"
__mcount_loc = "0xffffffffa0812f98"
__param = "0xffffffffa0812f18"
__verbose = "0xffffffffa0814460"
Where would I look for "max_buffer_size" parameter?

10.1 upgrade install error message: "error cannot write file"

I have just installed a clean copy of os 9.2 onto my powerbook g4. When I try to upgrade with the included cd mac os x 10.1 it errors out about half way through the install. I get the error message : "installition could not continue due to errors" " error cannot write file". I am mainly a pc guy, but want to be fluent with macs to. Has anyone seen this error before and/or know a resolution? Thanks. All help is greatly appreciated!

Hi Again atadams77!
Tiger is available for purchase at The Apple Store (U.S.).
Panther, is no longer available directly from the Apple Online Store, as Tiger 10.4.x is the most up to date OS.
If you know what to look for, a Full Retail Version, of the Panther Install CDs, or a Full Retail Version, of the Tiger Install DVD, can also be purchased rather inexpensively, at some online Apple retailers, Amazon, eBay, AppleRescue, FastMac, etc.
Be sure not to purchase grey, upgrade or machine specific CDs or DVDs.
Panther is only on CDs, not DVDs.
Unless purchased from AppleRescue, the discs should look exactly like the images in the above links, and not say Upgrade on them.
Additional info in these links.
Using OS X Install CDs/DVDs On Multiple Macs
What's A Computer Specific Mac OS X Release
Software Update, Upgrade: What's The Difference?
Once Panther 10.3.x is installed, you can use the 10.3.9 Combo Update, to upgrade to the final version.
As has been posted, your Mac meets the Tiger System Requirements.
If you install that, use the PPC 10.4.9 Combo Update, to upgrade to the current version.
Additionally, "Tiger ships on a DVD, but if your Mac doesn’t have a built-in DVD-ROM player, you’ll need CD media."
AppleRescue, sells a Tiger installation set on CD
Shop Carefully, Examine All Documentation, And Good Luck!
ali b

Weird error: "Cannot write file summary in a read-only environment"

Disclaimer: We are using an old version of bdb - 3.2.76 but are not able to easily upgrade.
We see this occasionally in production. From looking at the code it looks like critical eviction is happening since more memory is used then the limit we set then eviction is happening but then failing since the env is read only. I'm just wondering how it got to this point. we set the max size (je.maxMemory) to 1572864 bytes.
This is not urgent but is adding noise to logs so any suggestions would be welcome...
<application specific exception>
…causedBy com.sleepycat.je.DatabaseException: (JE 3.2.76) Cannot write file summary in a read-only environment
at com.sleepycat.je.cleaner.UtilizationProfile.putFileSummary(UtilizationProfile.java:720)
at com.sleepycat.je.cleaner.UtilizationProfile.flushFileSummary(UtilizationProfile.java:708)
at com.sleepycat.je.cleaner.UtilizationTracker.evictMemory(UtilizationTracker.java:120)
at com.sleepycat.je.evictor.Evictor.evictBatch(Evictor.java:314)
at com.sleepycat.je.evictor.Evictor.doEvict(Evictor.java:253)
at com.sleepycat.je.evictor.Evictor.doCriticalEviction(Evictor.java:279)
at com.sleepycat.je.dbi.CursorImpl.close(CursorImpl.java:690)
at com.sleepycat.je.dbi.CursorImpl.close(CursorImpl.java:660)
at com.sleepycat.je.Cursor.endRead(Cursor.java:1820)
at com.sleepycat.je.Cursor.retrieveNextAllowPhantoms(Cursor.java:1616)
at com.sleepycat.je.Cursor.retrieveNext(Cursor.java:1397)
at com.sleepycat.je.Cursor.getNext(Cursor.java:456)
...

Hi Nick,
It is strange to me also that this is happening in a read-only env. Looking at the code, we don't prevent this sort of eviction in the 3.2 release or later releases. Yet we've never seen this problem before.
This sort of eviction only happens when writing is occurring. Of course, in a read-only env there is no writing. The only way I can think of for this to occur in a read-only env is when there is a very large recovery interval -- the amount of log between the last checkpoint start and the end of the log. This can occur if you didn't close the env cleaning when you last wrote to it, or if the last checkpoint just happened to be very large.
So one thing you could try is to ensure that you have a small checkpoint when you write to the log, before opening it in read-only mode. To do this, just before you call Environment.close, call Environment.checkpoint(new CheckpointConfig().setForce(true)). This will do one checkpoint before closing the env, and then another during the close. The last checkpoint should be small.
If you can't do this, or it isn't sufficient, you could increase the je.cleaner.detailMaxMemoryPercentage env config property. This is the max amount of memory (% of total cache) used for the information that is being evicted. Since nothing can really be evicted in read-only mode, there is no harm in setting this to a much higher value than the default (2). I would try 10. This doesn't reserve or waste any memory, it just prevents this sort of eviction from occurring until a larger part of the cache is used. This is probably the simplest solution.
A third approach is to simply accept that this sort of eviction will be attempted, but try to prevent the exception. If you're willing to rebuild JE (and you're not a supported Oracle customer -- please contact us if you are), then you could simply replace the 'throws' statement with a 'return null' in src/com/sleepycat/je/cleaner/UtilizationProfile.java:
    private synchronized PackedOffsets putFileSummary(TrackedFileSummary tfs)
        throws DatabaseException {
        if (env.isReadOnly()) {
            throw new DatabaseException
                ("Cannot write file summary in a read-only environment");
        }--mark

Every time I download a large file in safari (mavericks version) at the end i get the error cannot write file. help

evrytime i dowload a file on my macbook pro it tells me at the end that it cannot write the File. Small files download Ok but Large files do not.
Help Please.
mackbook pro 13 late 2012 upgraded to Mavericks restored backup from M lion with time Machine.
Thx

I am experiencing this as well. I've found a workaround. Once you know the file has stopped (the Safari download menu says it cannot write the file) then do the following:
1. Open the Downloads folder.
2. Open Terminal.
3. In Terminal type "cd " and then drag the "incomplete" .download file to terminal (this just copies the path), then hit "Return" and you will change into the directory.
4. Type "ls -l" and you should see within the .download bundle, the complete file is actually there and complete.
5. Now, let's say the file name is "file.mp4" type "mv file.mp4 ../" and it will be moved out of the bundle one level up into the Downloads folder. You may need to enclose the file name in quotes if it has any special characters.
6. You can now drag the .download container to the trash, and the file should be fine.

Cannot write medium-incompatiable format

I have recieved this error message both times trying to burn a music cd with toast 7.1. The error happens at the same time both times. Right near the end of the cd. The cd will still play when its ejected and tried in a stereo. Near the end however you get digital distortion noise. Im using sony cd-r discs which I believe are good quality and have the speed set to best in my toast pref box. Applecare lady I got today had no solution and told me to burn with itunes. I would rather a software application specific for burning myself. I hope its not a matter of what kind of disc etc. etc. even my crappy pc burns fine everytime on any disc. Any help would be much appreciated my friends!
thanks

You haven't said if your drive will burn successfully using iTunes or a different application. Until you try this we won't know if the problem is with your drive or just your software.
First you should check the source material to make the mp3/aiff/wave file is not corrupted and plays correctly. If it is ripped from a cd make sure the cd still plays all the way through. If it turns out to be software related you should check if there is an upgrade for your version of Toast. If you cannot burn anything satisfactorily then get in touch with Applecare again and tell them your drive fails to burn anything.
One point to be aware of is that even though you consider your blanks to be good quality they might just be a bad batch. I've returned whole spindles of blanks after five or six have failed in a row, replaced them with the same brand (and from the same store) and had no problems with the new batch.
Hopefully this is all your problem is.
MacBook Pro 15" Mac OS X (10.4.9) 1.83 GHz Intel Core Duo

Time Machine Error cannot write to sparse bundle -- file in use.

We're having trouble with a Time Machine backup. Twice in the last three days, the backups failed with the error message that the backup disk image is already in use. I noticed that the partition containing the backup sparse bundle is mounted twice in /Volumes -- /Volumes/X and /Volumes/X-1. The error message refers to /Volumes/X-2.
The icon that appears on the desktop has not cleared as if it's still doing a backup.
Looking at the sparsebundle directly gives me the "verificationstate" as 1 -- I recall reading that this is supposed to 0. Other values:
verificationdate == 2012-06-05, and VerificationExtendedSkip == false.
Note that the backup drive is attached to another Mac still running Leopard. This is run fine for years over a gigabit network.
Any ideas?

OK, we fixed this for now with the simple, but common Mac way of
throwing something in the trash.
In this case it seems to be a temporary network connection to the remote Time Machine partition. When Time Machine balks, the icon for the temporary mount gets stuck on the Desktop. We threw it in the trash (unmounting it) and then Time Machine can resume.
Apple networking is annoying, but then on the other, it's easy. We lose printing in a similar way.
Anyway, although we seem to be OK, I'd like to understand this a bit better. I can see in the "/Volumes" folder (in Terminal) three Time Machine mounts, not one as I would have expected, and they all appear to point to the same place:
drwx------   9 root                   wheel 264   Jun 22 10:23 TM-2
drwx------   9 root                   wheel 264 Jun 22 10:23 TM-1
drwx------   9 MYUSERNAME staff   264 Jun 22 10:23 TM
On the remote machine, the disc TM appears only once.
If you look at the listing of all three, they are identical. What gives?
Is this a consequence of the fact that we are putting the time machine backups on a remote machine (that is not a Mac OS server). We have to mount the remote disc before Time Machine will run, but from that point it works perfectly -- or as perfectly as any mac networking thing seems to work.

Cannot Write or Read to disk Error during iPhone 3g 3.1 sync

Searched the forum with no luck. Just upgraded to 3.1 on my 3G and I cannot sync without it stopping with the error - Cannot write or read disk. It seems like its almost random on what file it picks to stop on - the file plays fine in iTunes 9. Any suggestions?

Hi,
Restore the Touch. There is no easy way to remove files from an iPod as it classes media on the iPod as "read-only" - There are software products that can be used to remove media from an iPod, but it is not an official method and you risk causing more damage.
If you really need the files on the Touch then use Google to find a program to remove files, there are a few, but do so at your own risk!
Kind regards,
Peter.

MS Query...cannot write sorted rows error

I have an MS Query report crated and it was working well until i tried to remove a Criteria Filter within the query. I get an error "Cannot Write Sorted Row". If I acknowledge the error, the change to the criteria is not saved and it reverts to
the original setting. I had several columns sorted, of which i deleted the SQL code for sort thinking that may help. I also tried to delete the Criteria Filter via the wizard and directly in SQL but that did not help.
Any suggestions of what may be the issue?

This is a Power Query forum and so it's unlikely you'll find MS Query experts here. That being said, did you try using Power Query for your scenario?

DVD burn error - SOLVED!

I recently had errors when burning DVDs and noticed many people on this forum shared the exact same problem, but no solutions were posted. However, I've recently solved it, and decided to make a whole new thread so that it is easier for people to find.
First of all, the error is this: Since owning my laptop I've done 1 or 2 successful DVD burns, but then suddenly it wouldn't do it anymore. It would begin but then fail, somtimes at around 42%, other times before it got to 1%. and this happened no matter what software was used. I tried Finder and Toast 8. The error codes output from Toast are as follows:
The drive reported an error:
Sense Key = HARDWARE ERROR
Sense Code = 0x03, 0x01
http://www.bilious.org/filez/forums/Apple/Drive%20Error%2001a.png
Followed by:
Sense Key = ILLEGAL REQUEST
Sense Code = 0x30, 0x05
CANNOT WRITE MEDIUM - INCOMPATIBLE FORMAT
http://www.bilious.org/filez/forums/Apple/Drive%20Error%2001b.png
(Thankyou to user: billious, for the images)
The error code you get from Finder is 0x80020022.
Now, the information about my system and my drive are as follows:
Apple MacBook (Intel Core Duo, 2Ghz) in white
MATSHITA DVD-R UJ-857:
Firmware Revision: HBE4
Interconnect: ATAPI
Burn Support: Yes (Apple Shipped/Supported)
Cache: 2048 KB
Reads DVD: Yes
CD-Write: -R, -RW
DVD-Write: -R, -RW, +R, +RW
Burn Underrun Protection CD: Yes
Burn Underrun Protection DVD: Yes
Write Strategies: CD-TAO, CD-SAO, DVD-DAO
Media: No
Now, I know a lot of people here have said "Use highest quality DVDs, your cheap ones are bound to fail!" but in actual fact, it doesn't matter. People all across this forum have said that they've used the most expensive brand DVDs on the market, right down to the cheapest, and it's failed on all of them. Even the Apple brand ones. Here are a just a few that people have tried: TYG03 (Taiyo Yuden 1-12x DVD-R), TTH02 (TDK 1-16x DVD-R) and TDK003 (TDK 1-16x DVD+R). Taiyo Yuden are widely thought of as the highest quality on the market.
Also, I know people on this forum have said "Check the Mac is on a flat surface" and "Check the Mac is at a comfortable temperature". These may be factors, but it's very unlikely and are certainly not how I resolved the issue.
I took mine to my local Apple store and told them about the issue and they said they'd test it and if they found a fault, do whatever was needed. They tested and sure enough, it wouldn't burn so they decided to replace the DVD drive. I tried to tell them that loads of people on this forum said that doing that hadn't helped, but they weren't going to take our word for it, and so they replaced the drive. 2 days later I got a call to say they'd done it but it hadn't resolved the issue (fortunately they'd re-tested it and not just told me to come and collect it!) and so they decided to replace the motherboard. 2 days later they called to say the work was done and it was burning fine, and I can confirm that it now burns full DVDs successfully.
So there it is, a motherboard fault. I dont know why, perhaps a manufacturing error. Anyways, so if you're having this problem, go tell Apple to replace your motherboard (I believe you can send your laptop to them if there isn't a store near you).
Oh, and if you do this and it works (or if it doesn't) please post it here, as it will help keep this solution on the front page of the forum.

Hi Vai,
I'm quite pleased to read your post, I'll even forgive the linking to my error messages because the news is that good.
Any information whatsoever as to the actual repairs undertaken would be very much appreciated, as I am interested in twisting Apple Australia's arm over this issue - my DVD drive may as well not be there. Any information from the service receipt, or if your could contact the service staff for a specific description of the error and service method, I'd very much appreciate it.
Congrats on the repair, and now I've got five months to fight the machine that is Apple to see that my drive actually works.
Thanks.

IDVD 5.0.1 mulitplexing/burning errors

Here goes, my factory installed combo drive broke, so I got a new CD/DVD Burner : (company installed)
Manufacturer:     _NEC
Model:     _NEC DVD_RW ND-1300A
Revision:     1.05
Drive Type:     CD-RW/DVD-RW
Disc Burning:     Vendor Supported
My iDVD 3 worked once, then would not work, it wouldn't open properly and had to force quit every time.
I asked our IT dept to re-install it. They couldn't find the software re-install disc. Sooo they got out the iLife disc and installed iLife with iDVD 5.0.1.
It won't work either.
When I try to burn a DVD, it proceeds like it is encoding, then at the end, it gives me an error message; Errors in Burning Process. I hit ok then it says: Multiplex Error, problem during multiplexing/burning. I am left with a blank DVD and lots of frustration.
I try to bring up old DVD projects I've previously made with iDVD 3, but it keeps trying to find files that it cannot find. Even though I have all the files saved.
I have Quicktime 7.0 that I installed a while ago and iDVD 3 did fine with those exported files.
I have FCP HD 4.5, I usually export as a Quicktime file, same as source, creating new media (stand alone file). Never had a problem before with iDVD 3 and my old combo drive.
I have Mac OS X (10.3.9). I have 40 Gb available on my start up drive (Mac HD).
As I said before, I sucessfully burned one or 2 discs before iDVD 3 started acting up on me and led me to install iDVD 5.0.1.
Here's my console report from today's attempt:
Contents:     Mac OS X Version 10.3.9 (Build 7W98)
2005-10-21 10:13:17 -0700
iDVD: Burn started, Fri Oct 21 10:39:55 2005
iDVD: Burning to DVD-R media with DAO strategy in _NEC DVD_RW ND-1300A 1.05 via ATAPI.
iDVD: Requested DVD burn speed was 2x, actual burn speed is 1x.
iDVD: Burn underrun protection is supported, and enabled.
iDVD: Burn failed, Fri Oct 21 10:39:56 2005
iDVD: Burn sense: 5/30/05 Illegal Request, Cannot write medium, incompatible format
iDVD: Burn error: 0x80020022 The device failed to respond properly, unable to recover or retry.
I've read some of the threads on this problem already, with no luck so far.
Any suggestions appreciated.
Thanks,
JBT

I am having a similar problem burning via IDVD 4. However, in my case the Superdrive in the installed original on a year old PowerMac G5. This is the second of two similar FCE projects each 90min. The first burned fine but the second one gets to stage 4 and stalls. The striped progress bar moves but the burning never takes place even after hours. Hitting the cancel button has occasionally given the message "errors were found during the burning process. Logical end-of-file reached during read operation".
I have tried the follwing remedies without success:
1) taping the video back to the camcorder and reimporting it into IMovie. It looked fine even in the IDVD preview but would not burn
2) I did an archive and install of the OS including the ILife apps
Even more perplexing is the fact that a short segment of the project in question burned just fine did a two hour long video saved as a disc image.
I would greatly appreciate any assistance. Thanks, Jay

Burning error, cannot write medium

Similar Messages

Maybe you are looking for