LIGHTNING UK!

I'm pretty sure you answered this yourself in your other thread?! Your player can't play discs with the wrong TV system type - i.e. NTSC or PAL. If it's a region free disc, there can't really be any other reason for it to not work.

Windows always caches files as programs read them. Recently however, they stopped doing it if you read in 64kb chunks at a time - size may also be a factor, I don't know, I didn't code windows Because I switched to reading 256KB at a time - in an attempt to lessen the workload - I made windows think it wanted to cache the files again. It's a shame I didn't notice the ram going on my pc.... but then like I said earlier, I have 2gb and never burn off my C: drive. It has been fixed for a couple of days now, just doing some other little bits and then I'll release 1.2.1.0. Sorry for any inconvenience caused

Look at all the logs in the media forum - yes, there's about 250 of them. Oh funny, it shows the names for all of them just fine! Hmmm strange that it just doesn't work for you drive. Must be a glitch. LOL Feedback is valuable to me, yes. I take bug reports and suggestions very seriously unless I know them to be complete bullshit. Again, take a look in those forums and see for yourself. What you're accusing ImgBurn of doing (stuffing up your drive) is total nonsense. I don't send any nasty commands to the drive and so if it messes up, it only has itself to blame. It's like me asking you to walk forwards and you taking it upon yourself to walk in the direction of an oncoming bus. If you get run over, that's your fault, not mine. Does it not occur to you that something as serious as killing drives MIGHT just have been reported elsewhere if it were a real issue?! Software that's been around for 3 years would have generally had something written about it if that was the case. I have about 40 drives in total now, testing the program on a daily basis. Not once have I had anything go wrong with them. Going back to the media forum, those 250 odd logs prove it works with several drives without killing them, and on pretty much every bit of media we could find. You can see that with your own eyes. I'm sorry but all that really doesn't work in your favour.

No, it says it doesn't support cue files A bin can be a simple disc image. ImgBurn examines the bin to see if it's a data one. If it is, chances are it can burn it. It knows it can't do audio and the image won't pass the internal checks. Audio CDs are burnt differently to Data and one would have to consider multiple tracks - something ImgBurn doesn't currently support. I think it says single session / track images. Like I said 2 seconds ago, ImgBurn doesn't support multiple tracks (or sessions). The number of files going to make up that image is not really relevant. Normally, the second (small) file that these other programs produce is just a file that describes the data in the bigger one. The most common being the CUE file. No, a mono audio file is not a single file... you're totally lost here You cannot in any way, shape or forum burn a CDDA disc/image with ImgBurn. If I ever get around to adding support for multiple tracks... THEN it may well be possible. Until that time, best stick to using whatever read the audiocd in the first place.

The program follows the MMC specs. All drives since about 2000 are supposed to follow them. As such, there is no need for a compatibility list. Oh and according to the log, your drive reports its name as ATAPI DVD RW 8XMax 150D I see no 'name' in there, nor do I see 160D firmware. Like I said earlier, I don't like guessing games so I can only go on the info you provide. Recommended media is what 9 out of 10 forums tell you to buy. i.e. Verbatim (MCC dye), Taiyo Yuden etc. Drive wise, go for the big names. NEC, BenQ, Plextor, Pioneer, LiteOn. Those makes are popular for a reason... they tend to work and generally have decent firmware with frequent updates! This arguing is getting us nowhere. If the program isn't working for you, and you're still looking to blame the program rather than anything else, go find some other tool to do your burning. It's free to use so just cast it aside and forget you ever set eyes on it.

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.