LIGHTNING UK!
-
Posts
30,458 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by LIGHTNING UK!
-
-
blutach,
Yes you can make an MDS via 'Create DVD MDS file' in the tools menu. I assume that's what you're talking about?
It doesn't contain layerbreak info though... never did.
-
You're correct, there is no other way to get it.
-
If the LB is currently in a place that wont work on OTP discs... i.e. where Layer 1 is bigger than Layer 0, you'll need to recreate the image using something like PGC edit.
Unless of course ImgBurn itself can find another Cell in the PGCs that will meet the criteria.
Load the image, right click on the 'Sectors' text in the main window and get it to display IFO layer break. If it works, you'll be ok. If it doesn't, PgcEdit it.
-
SPTI can't be used by anyone other than Admin. Obviously it's also only available on NT based OS's.
Making your own means you can interrupt the standard flow of data and fake the results given back to the OS.
I also said nothing about performance, I said the quality of the burn has nothing to do with the I/O interface. All you're doing is sending digital info to the drive. If the I/O interfaces changed that data, they'd be bloody useless! So basically, it doesn't matter how you send it, the drive still get the same info and burns that same info. The interface doesn't come into it.
-
If you have a copy of the log handy (or remember to keep it in future), it helps with us helping you!
-
OTP is all you can get for DVD+R DL discs. If it's PTP, THAT is when you have a problem, OTP is fine.
If you mount an ISO made by another program, it won't have kept the info about track path and so will default to PTP, regardless of if that's correct or not.
-
Anything about closing tracks, sessions, discs etc is all down to the drive.
As you're normally right at the edge of the disc at this point, it's the most prone to failure.
As Shamus said, the 109 and ImgBurn DO work ok together.
Things to check are that you're running the latest firmware and you have decent media.
-
These I/O interfaces are mearly roads from A - B. They have NO effect on the burn quality, which is totally down to the drive / firmware / media combo.
-
going between two drives would be the same as just opening up another instance.
Within one instance, it would still only burn 1 disc at a time. If you opened a second and built up a second bunch of images in the queue, you could have it burning 2 sets of files to 2 different drives.
That's about the best I can do right now.
-
I've spoken with VSO, they changed something and I never updated my code to reflect that.
Will be done for the next release.
-
Hmm you're actually the second person to be having that issue with the Patin Couffin drivers. Maybe I need to look into it and speak with VSO to find the cause.
-
All DT is doing is loading it as a standard ISO image.
So it looks like burning as Mode 1, 2048 will work.
The rest is down to that MacDrive program. Perhaps it's not perfect!
Try burning properly using Nero and the method I mentioned earlier and then put that disc in your Mac. Use an RW or something if you're short of discs
-
Queuing is in for the next release.
There is nothing for multiple burners though.
-
It can't put it where it needs to be. You need to rebuild that image.
Load it (via DAEMON Tools or something) into PgcEdit and have that create a new layerbreak / iso file.
-
You're probably burning something that started off on a PTP type disc rather than OTP (as DVD+R DL discs are). As such, the original layer break position is probably no longer valid or usable.
Update your firmware to fix the other problem with it bombing out when burning sectors spanning the layer break position.
-
Well something must be using the drives, or something has installed a filter driver that's stopping me from getting exclusive access on them.
If you've just installed Nero 7 (and that's all you've done), I would guess that's the problem.
Did you put that InCD thingy on too? That normally causes this issue.
Of course the obvious thing to try is to remove Nero and see if it works again. You can put it back on afterwards, but it would be nice to know what's causing the problem.
I'd also visit http://www.bustrace.com/downloads/free_utilities.htm and check out their filter driver load order util. It'll tell you which drivers all your systems I/O has to go through before actually reaching the drive!
Without locking the drive, any other program can send commands to it and interrupt the flow of data - leaving you with a nice coaster. Even just opening up 'My Computer' or whatever can kill it if it sends the wrong command.
-
Will 8 do you?!
(Cus that's what I've allowed for)
-
Yeah they do but it's probably down to the cdrom to read them at that size. I kinda assumed going DMG to ISO would put 512 in 2048 but that's not the case. The ISOs you gave me still have data in the exact same places... ie. 4 x 512 bytes in a 'normal' 2048 byte sector.
It looks to me as if the OS itself must handle sector sizes and decompressing the files on the fly (unless Macs use weird drives that support reading 512 byte sectors).
Is there no virtual drive type tool you can use to mount these DMG files? Maybe this could show us if the generic cd/dvd rom driver can understand what's in the image - compressed or uncompressed.
I don't think I've got much chance of uncompressing the image, and I did say I'd only think about adding support for 'Basic' images
-
Hmm there's hardly any difference between the two! (DMG and ISO I mean)
You can't do it in ImgBurn at the moment, but have you tried burning the DMG file in Nero without any sort of conversion? (Maybe just a simple rename to *.ISO)
When it asks you for the foreign file format, just select MODE 1, 2048.
-
When it does that, press the F8 key and then post some of the log.
It'll tell you (or me) what the drive thinks it is doing. There must be some problem with finishing the disc off - and they're internal drive routines, not anything I can really help with.
-
You're very lucky then!
No question about it, they're the worst DL discs going.
-
I would say pgcedit.
-
Sony 710 firmware: http://forum.rpc1.org/dl_firmware.php?download_id=1917
Sony 800 firmware: http://forum.rpc1.org/dl_firmware.php?download_id=2074
You're way behind on both.
-
Just as in DVD Decrypter, ImgBurn's default settings are/work best. Leave them as they are.
FYI:
1. SAO and DAO are the same thing. DAO is the correct term for when talking about DVDs though.
2. This is how DVD Decrypter talks to your drives. The common method is to open them using the path '\\.\CdRomX' - where X is some number. That's the 'Cdrom' class. The alternative is via their drive letter using the path '\\.\X:\' where X is the drive letter. That was mainly added for linux users who use the program via Wine.
Any DL burning issues people are having with ImgBurn are exactly what they'd get from any program. They use crap media with crap firmware. The best they can expect from that combo is crap burns! No software can change that.
Yes of course it's better to use ImgBurn. You can see the list of changes from the changelog. Of course every version has new features and improvements over the last one.... pulling it further ahead of what it was in the good old days of DVD Decrypter.
OTP & PTP??!!
in ImgBurn Support
Posted
PgcEdit is based over at the doom9 forums.
I suggest you go take a look over there.