Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,521
  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. I missed this, sorry. It's on the website now. Were you going to fix the traditional one too? I recall you fixing it for a previous version of the program.
  2. Like I said, the problem before was that the install hung (became unresponsive) for a while before the consent page ever showed up - and people were having multiple clicks logged against the 'next' button because it wasn't progressing (maybe 'click happy' was the wrong way of putting it). That doesn't happen now I've rewritten the toolbar code and false positives should be far far lower. Sometimes you won't get the toolbar consent page because the toolbar checker has determined you shouldn't get it - like when it's already installed or you don't have any supported browsers. Going by the logic I posted in my previous message, that still means it's impossible for it to get installed automatically.
  3. Do your homework. Read an xbox news site that deals with this stuff.
  4. You must have enabled the 'Preserve Full Pathnames' checkbox on the options tab. Turn it off again.
  5. This is an authoring question and nothing to do with burning or ImgBurn. You'll get more assistance over at a more appropriate forum. Doom9, Digital Digest, VideoHelp etc.
  6. iomega is just a brand name, I very much doubt they make their own drives. Buy the real thing. Panasonic would be Matshita wouldn't it? They're normally just supplied with laptops - and you shouldn't ever buy/use a slimline drive if you have a choice in the matter.
  7. If it's meant to be on one disc then it needs to go on one disc. It's not going to be aware of the 2nd disc and so it'll never ask for it. It'll just treat the missing files as errors and the install will probably fail. If your drive can't burn DL disc (is it really that old?!), it's probably about time you got a new drive. If you just want to use the image to install, mount it in a virtual drive program and install it from there.
  8. Slimline drives are all pretty rubbish. Try burning at the other supported write speeds. Try cleaning the drive with a cleaning disc. After that you're left with things like forcing a firmware update to RR09, trying another spindle of discs (make sure they're Verbatims from Singapore) or getting another drive (external half height one).
  9. All the toolbar threads are quite old now - I've rewritten all the toolbar code in the installer since people first mentioned it was installing without consent - it wasn't even really doing it then, but the 'hang' whilst the consent page was displayed made people get click happy and it ended up just flashing by. Nope, none of that toolbar code is anything to do with upgrading from and to certain versions. The installer starts by setting a variable to 0. It can't ever be anything other than 0 unless the toolbar consent page is shown, the checkboxes remain checked and the user clicks the 'Next' button. Only when that variable is set to 1 does the toolbar get installed. There's nothing more I can do to it.
  10. Wow, 2 VIA controllers - that's just bad luck! If no drivers get your machine working correctly, get yourself a Silicon Image chipset (Sil3512) based PCI card and put the drive on that.
  11. You've messed with the eeprom settings... restore them to their default values. (FHT / OHT / OS off, SB on) If your drive still reports a 'Write Error' after that, try enabling Overspeed in the eeprom settings, clear OPC history and then try burning at 4x. After that I'd try some MKM-003-00 discs.
  12. Ah, try using the proper wavpack directshow filter - as per the Audio CD guide. http://forum.imgburn.com/index.php?showtopic=5555 The info is in the 2nd post.
  13. I don't see it as a track 1 issue (a small 'index 0 -> index 1' is ok), it looks like the entire wv file is decoding to some really tiny size. Any idea which decoder your system is using for wavpack files? Open the 'Create CUE File' window from the Tools menu and add the WV file to the 'Layout' box. Then right click the wv file and select 'DirectShow Filter List'. Press CTRL+C whilst the messagebox is on the screen (to copy its contents to the clipboard) and then 'paste' that info into your reply.
  14. open the cue in notepad and copy+paste its contents please.
  15. You need to make it into a proper Blu-ray video structure if the PS3 can't just play M2TS files. You can use something like multiAVCHD for that (or go direct to tsMuxeR).
  16. Fixed in the new 1.3.34 release - or at least it's working ok here now !
  17. Why can't you just stick the file on a usb stick and play it from there? Not saying the sound would work (it still shouldn't) but it's quicker and easier than burning! Use something like mediainfo to find out the format of the audio in the avi. It could be using a codec the PS3 doesn't support.
  18. Yes, I'm quite sure. The audio is in the AVI file and the AVI file on the disc is identical to the one on your hdd.
  19. It looks like a USB 1.0 (rather than 2.0) issue to me. Try another USB port/cable.
  20. This is a problem with the file or the way your ps3 is configured, it's nothing to do with the burning tool. See if you can pick / swap audio streams on the ps3 or something - oh and make sure it supports whatever format is being used in the file.
  21. You can only use Mode 2 on CD. It's not valid on anything else and the program will tell you that (when burning direct to disc). It doesn't matter which file systems you use for computer use but UDF is better for long files names and unicode etc. I wouldn't worry too much about the revision. 1.02 is the most compatible. 2.50/2.60 are better for redundancy and coping with errors (at there's a mirror copy of all the descriptors). Standalone players might want a certain file system for a certain type of disc/content... look in the manual to see what it wants.
  22. Do you actually have a VIA controller on your motherboard or is the drive plugged into a PCI card that uses a VIA controller?
  23. Can you get it off the via controller?
  24. It's never a good sign to get an error and your drive return 'No Additional Sense Information' as the error. What controller is your drive attached to? Right click the drive drop down selection box and click 'Family Tree'. Close the prompt and copy + paste that info from the log window. Please also post the filter driver info - use the feature in the Tools menu. You might find you get better burns at 4x with 'Force HyperTuning' enabled in the EEPROM settings. i.e. as per my findings in this post... http://forum.imgburn.com/index.php?showtopic=18871&view=findpost&p=136519 Look at 'Attempt 8'.
  25. I think you'd have to load the MadDog 2510 2.FA firmware to get bitsetting support.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.