LIGHTNING UK!

If the manual method of configuring the bootype isn't working, the auto way won't either. There's obviously some generic issue with the commands simply not working on your drive. If updating the firmware didn't fix it (original + crossflashing), pretty much your only option is to buy a new drive that supports bitsetting out of the box.

I got some 8500 Crucial Ballistix from Misco the other day for

I'm talking about the ones they list as '1+1'. The connectors are virtually on top of eachother so they 'just' reach two drives if they're also on top of eachother. http://www.acryan.com/_roundcables/ACR-RC30901.shtml

I use AC Ryan cables where the 2 connectors are right next to each other - which is of course perfect for optical drives. They do 30cm, 60cm and 1m (or 90cm, I can't remember exactly). I'm using 60's at the moment. I could probably get away with 45's from where my board connector is, but they'd need to develop them first. My Silicon Image card couldn't handle the 60cm cables and gave me the same UDMA/32 CRC errors as the JMicron controller. The onboard Intel one (on my old board) worked fine with them, as does my ITE card.

What motherboard did you buy again? Was it one that doesn't have a proper IDE port on the southbridge, but instead uses one by a 3rd party - i.e. JMicron? My new board has a JMicron one that gives me the same Ultra DMA 32 CRC error so I just don't bother using it. I think my problem is that I'm using a cable that's longer than normal though.

It's nothing like the same error! Keep to your own threads

Look at the 'available' ram though!! That's just crazy low. If you think it's been running 'so good' so far, stick a couple of gig in it and it'll seem like a totally different beast.

You have DMA issues. Change the cable connected to the drive with a decent 40 pin, 80 wire one. Make sure the jumpers are configured correctly so that it's set as a master / slave (NOT cable select) and then put it in the correct position on the cable. The master should be at the end of the cable, slave in the middle, motherboard on the other end. Update your motherboard chipset drives and the ide controller ones. Then follow the post in the FAQ about DMA. You should also update the firmware on the drive.

You're getting timeouts all over the place. Either the drive really is having problems dealing with the requests to provide info about the media or something on your computer is messing things up. As this is nothing to do with ImgBurn, you're the only one who can fix the problems.

There's not much you (or anyone else) can do if the bus (or something on it - i.e. the drive) resets. As with most of these odd errors, you just have to try a million and one different things to find the cause and hopefully a solution. i.e. update the drives, update the firmware, update the bios, change the cable, change the media, clean the drive, put the drive on it's own channel, try the drive in a different pc, try a different drive in your pc. You get the idea

Hi, Sound is nothing to do with the burning stage, you need to fix your source files. Your best bet would be to go searching on Google. Off the top of my head, it could be that the files contain an audio stream that your player can't decode. Try pressing the 'audio' button (or equivalent) on your remote control/software player and try to force the audio stream to one that does work.

tweakui is also quite useful for that (and a lot of other things!). http://www.microsoft.com/windowsxp/downloa...ppowertoys.mspx

You don't have a DVD burner, it only burns CDs.

I fixed ImgBurn - but it won't be available to you (or anyone else) until I release the next version (v2.4.0.0 or whatever). Fingers crossed that won't be too long now.

I'm somewhat surprised you've never seen a PTP disc blu, back when I actually used to mess around with them, loads of mine were! I guess you only really notice it when L0 L1), it might aswell be OTP for all the difference it makes.

When output is set to device, the program knows if it can (re)position the layerbreak or not. You cannot move it if you're using DVD-R DL media, so you're far less likely to get a decent match or be offered various points (cells) the LB could be aligned to. So even if you've managed to build a DL image (as an ISO file), it's not going to help at all when it comes to burning if you're not using the media the image was designed for (by default, DVD+R DL).

Yes fixed as far as Joliet goes. The images ImgBurn creates now are read properly by SMS without the random 'empty' folders as you drill down through the directory structure and without it finding the next layer's files. As for UDF, he's obviously made (planning to make) some sort of attempt (or someone else has) or that CDVD_UDFS.C source file wouldn't exist. Oh and when I mentioned email, I was talking about you doing it. I don't use the app so it doesn't bother me

All fixed This was a very obscure problem though, it must do some odd stuff with the figures when it parses the filesystem. Very glad you kept coming back to the topic though or I'd never have found the problem - it's actually kinda nice when certain software points out problems with code that no other apps seem to notice / care about! btw, this v2.3 (rev 2) appears to support the UDF filesystem. Well, I say that because I've just looked at the source code pages over here http://svn.ps2dev.org/listing.php?repname=...;rev=0&sc=0 Within the 'drv' -> 'SMSCDVD/' folder there's a file dealing with parsing UDF. So I wonder why it doesn't work??! Might be worth emailing the author or something and seeing what's up with it.

If you have the actual files, just use Build mode - read the Guides forum. If that's not working (I'm a little confused now as to what you're trying exactly!), you've no choice but to make the files smaller and/or create new cells (by splitting existing ones).

v2.3.2.0 is the latest version and is the one you should be using. You'll probably find the dvd content was built for a PTP layout disc rather than OTP. Sometimes when that's the case, it's not possible to correctly align a cell where it needs to be for OTP layout (which is what the DL writable discs are). All you can really do is insert some more cells in the hope it will then work. The more space used (or going to be used) on the disc, the less ImgBurn has to play with for getting the correct alignment.

http://home.casema.nl/eugene_plotnikov/

The burning part is very simple - and if you've already done it once, you probably did it ok. Those files you listed should be in a VIDEO_TS folder on your hdd somewhere. Just drag + drop the said VIDEO_TS folder into the Source window within ImgBurn and then click go. If your player can't play the disc, it either doesn't like the source files or it doesn't like your discs. Neither of which are really anything to do with ImgBurn.

2. As mentioned in my previous post, that's to be expected. I don't do anything with the content of the AUDIO_TS folder (well, apart from a little file ordering). I don't parse any of the files and hence there's no chance of the LB dialog coming up based on AUDIO_TS content. If the content of the VIDEO_TS folder has to span the LB, only then will it pop up. 3. DVD+R DL are better because the physical LB position can be moved. That's not possible on DVD-R DL, hence there's much less chance of ImgBurn finding a cell that'll fit with it exactly. +R also support bitsetting. Verbatim DVD+R DL discs are the only ones to use. I'm not at all surprised that the other brands caused your players to hang, they probably couldn't read the disc.

Once the drive is locked, the OS shouldn't even attempt to access it - and anything that does should just fail. For some reason it appears that's not happening on your pc. Some other program is sending commands to the drive that are killing the burn. This isn't really anything to do with ImgBurn as it's perfectly able to recover from interruptions - i.e. I can 'pause' the burn for 30 mins and it'll still resume just fine. Until you find out how these commands are getting through to the drive, there's nothing much you (or anyone else) can do. Try this little experiment.... start burning something (enable test mode if you like or use a rewritable) and then open a 2nd instance of ImgBurn. See if the 2nd instance can see the drive you're currently burning to or if you get errors in the log about a device not being accessible. Obviously you'll need to make sure explorer isn't involved when loading ImgBurn for the 2nd time - i.e. don't browse to it, just click the shortcut on the desktop or something.

Nope, that would be far too easy You'll need to mount the MDS in DAEMON Tools so it creates a virtual dvdrom drive out of the image. Then point Recode at that drive.