LIGHTNING UK!

lol I think you guys are underestimating the size of the project. Defining language variables and populating those from text files at runtime is probably how I'd do it, but it would take me forever and would be the most mind numbingly boring task I could ever hope to not do. Unless there's some magical way of clicking a few buttons and it doing all the string extraction for me, I very much doubt this will be done before the next millennium. Building a program from scratch with translations in mind is one thing, it's easy to keep up with them when the system is already in place. Converting what is basically a legacy application in one go is something entirely different.

Your drive must be having an issue with it. Copy + paste everything from the box on the right side of the main screen.

I think they're at 1000 now as the cpu is slightly overclocked to 3ghz (from 2.66). The next divider up took them over the 1066 rated speed and I really wasn't fussed about that bit extra - overclocking really isn't my thing. Takes far too much time to get things just right and I can't be doing with all the machine reboots / power cycles. I only really got them because I wanted 4GB in the machine and the 4GB of GSkill 6400 HZ I had were total crap and wouldn't work together in any of my boards. The GSkill are now sitting in my cupboard collecting dust

There's nothing to 'help' with. It's not possible to translate anything at this time - it'll all hard coded. All you can do is use a resource hacker / editor and manipulate stuff that way.

Oh dear, you had to take the bait didn't you

Not really, no. (and that's knowing it would only take me 2 seconds) Whilst screensavers might have been a problem in the windows 3.11 days, they're hardly taxing to a modern machine. So long as people aren't crazy with their screensaver timeout values (i.e. 1 minute), it really shouldn't be an issue. At 1 minute I'd find the continual interruptions more of an inconvenience than anything else! Mine is set at 15 mins (5 more than the windows default I believe) and I can honestly save I've never once seen it as a problem. Of course if your screensaver is set to play some mega 3D quake style timedemo, fair enough you might have a reason to want it disabled during burning! That said, I bet a lot of people are encoding etc whilst burning and I know from IBG graphs I've seen that it really isn't an issue even then.

It means Verbatim = Good, Ritek = Rubbish!

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.