LIGHTNING UK!

Sounds like a windows default sound to me. My sound plays some fanfare type thing!

indeed, it does not work for audio images.

Sorry, I don't see the problem in the above pic. Isn't that how we men are supposed to dress?

You actually have the same chipset as me. The infinst file will just configure your devices properly, it won't do any harm. It is made by intel after all, not some tiny company who doesn't care! You can then install the intel maxtrix storage driver. That'll do your IDE/SATA bits. Hmm but that might only work if you have RAID enabled for SATA, I can't quite remember. Basically it will either install or tell you it's not needed. 1. Yes you can ignore it. It just means other programs can interrupt the burn if they try to access the drive. Locking it stops that. 2. DVD Dec will behave the same way so it's pointless reverting to it for burning. Also, you miss out on all the new cool stuff (that you obviously haven't found yet!).

Yeah, this is just a disc image (ISO) burning tool at the moment. The ability to burn a bunch of files etc will be added soon. Probably best you stick to Nero / Roxio.

Blimey these sony drives are being a pain in the arse of late! Shame you didn't manage to post the full log.

Yeah, and NOT in this topic! Put it in the 'ImgBurn Support' forum.

Just letting you know I've sorted both of these problems out now.

What type of files are you attempting to burn? ImgBurn burns disc images. So you would need something like an ISO, IMG, BIN etc file. If you don't have one of those, you need to search google for guides on how to make one from the files you DO have.

ImgBurn will never be a substitute for CloneCD and won't burn 'raw' images with subchannel data. Same for PXI images probably - as I'd expect they also contain subchannel data - all be it in a single file using 2448 sector size. PXI is also very uncommon. Why would you use PlexTools to make the image in the first place and then look to another app to burn them?

The thing is, that error is coming from the drive, it's not something I'm making up. I tell it to write some data, it returns that error. As there is only one way to issue these write commands I really don't see how Roxio can be working any differently. Maybe you've got some bad filter drivers installed that are messing up the communication path between my program (spti) and the drive itself. Roxio probably has it's own drivers and perhaps they're bypassing the problem.

The start of that cell will be the first thing on the 2nd layer.

PgcEdit can be found on www.doom9.org ImgTool Classic can be found on www.coujo.de

If the drive isn't formatting, it means it doesn't support the media you're using. The 500A is ancient now so that doesn't really surprise me. Try updating the firmware to v 2.1a http://forum.rpc1.org/dl_firmware.php?download_id=302 If it still fails once you've done that, try getting some other discs.

I'm glad I found it too, but you can't call it a bug because it's not actually doing anything wrong! It's perfectly allowable to read 256kb chunks, it's just a limitation of windows that it's tries to cache a 4GB file in memory! lol Anyway, just a couple more bits to sort out and then I'm ready to put another release out.

Ah yes, I see the problem now. It wasn't that I wasn't checking the box when I needed to, that code is all fine. The problem was that I reset the window inbetween images (so the box gets unchecked) and that in turn was triggering an event that actually turned off that 'delete image when done' option for the queued item. As for the tricky one you mentioned... I remember thinking about that during the development. It's a tough one to get around without just always leaving that button enabled. Maybe I'd be better off updating the main window with whatever drive is selected for the first image in the queue. I'll have a play around and see if I can come up with something I'm happy with. I WAS kinda hoping nobody would notice

Yup, that's right, I just upped and walked away.

ImgBurn burns images (at the moment), not files - i.e. of the VIDEO_TS / IFO / VOB variety. You need to make an ISO before ImgBurn can be used. DVD Shrink can do that, just tell it so via its settings and it'll make ISO files rather than a VIDEO_TS folder. With existing VIDEO_TS folders, use something like PgcEdit or ImgTool Classic to make an ISO from them.

I'm always happy to help those that are prepared to listen. Often it's just not what they want to hear and so all I get in return is abuse! Shame because that then ruins it for other people as I gradually learn to keep my mouth shut, especially when I detect a inhospitable poster.

Question Shamus, any reason for the FAT32? It?s what L_UK! suggested and have never thought to question it. Indeed, it's all my fault! lol I used to use Powerquest Drive Image about 20 times a day back in 2001 / 2002. It was a DOS based app that had it's own basic GUI. At that time, it was probably only on version 4 / 5 (or at least that's what I had to use) and it wouldn't write to an NTFS partition. It would READ one (to an image), but you couldn't write the the new image to one. From what you've said, maybe things have changed.

If that's the case, I think this drive must use the Panasonic chipset rather than the Philips one that the 1620/40/50/55 do. I guess that means it might be missing some of the normal BenQ features for scanning and in the new 'Advanced Settings' window. Can you confirm this?

dirio49, Ok that would fall in line with the old 3.47 version needing a 1GB file to go into DVD mode then. I guess it hasn't been changed after all Qyngali, I've tweaked it yet again but it's very hard to try and remove rogue values created by the drive caching data....especially when (for me anyway) it's very difficult to make them appear.

That's because it is Sony hasn't made its own drives for ages now. They're either BenQ or LiteOn now mainly.

According to the logs you posted, the MDS one is being seen as a CDROM. and the ISO as a DVDROM I can only go on the information given

It's really odd actualy, DT 3.47 always needed an image to be 1GB in size before it went into DVD mode. Perhaps in the newer one (which I assume you're using?), that's no longer the case. As you can see from the logs, on one occassion it thinks the media is CDROM (the MDS one) and the other DVDROM (the ISO one). As CD and DVD have different transfer rates for 1x, that's why you're seeing different 'x' ratings within ImgBurn.