Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,515
  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. Do you need Alcohol due to its advanced features? If not, Virtual CloneDrive from Elaborate Bytes is much more computer friendly. (Alcohol's SPTD driver causes issues and slowdowns with certain drives/machines) You can get the latest beta via this thread - http://forum.slysoft.com/showthread.php?t=29061
  2. The PM's were from an annoying spamming bot and nothing to do with me. The matter has been dealt with.
  3. It was a spam message sent by a bot that signed up and spammed everyone via the PM system. http://forum.imgburn.com/index.php?s=&...ost&p=91556
  4. If you want an image of an existing disc, use Read mode, not Build mode.
  5. Did you click 'Load Queue' ?! An image file is not a queue file. Use the correct method to load image files and you'll be fine. As for the burning error, we need to see the complete log for that session. You can access saved logs via the Help menu in the program. Just copy + paste the entire log session where you were had that error whilst burning.
  6. It's not burning again, it's verifying. Why is the program unable to close the tray on your drive... does it not have a tray?
  7. I wonder if there's perhaps a bug in the firmware's code with controlling the speed via the 'SET CD SPEED' command rather than the 'SET STREAMING' one (which gets used when burning DVDs etc). I can email you a version which sends both for CD's if you like and you can give that a try? You can turn on test mode so as to not waste any discs.
  8. What type of disc do you have in the drive? The drive should only report it's in progress of becoming ready for a matter of seconds just after you insert the disc whilst it initialises it. If it's saying on for ages, eject the disc again because it must be having trouble reading it. When you do that, does the message change back to 'Medium Not Present' ?
  9. Do you actually have a disc in the drive? Did you look for other software that could be using it? Try 'Unlocker' or 'Process Explorer' to see what it might be. You can find more info on these tools in the FAQ.
  10. It has been dealt with now. All the PM's have been pruned from the database, the bot's accounts (5 in total) have been banned and I've black listed the IP. A patch has been implemented which applies flood control to the PM system. I apologise for any inconvenience caused.
  11. I've pruned them all from the database now and put in a some patch that applies basic flood control to the PM system. Sorry for any inconvenience caused.
  12. It's just the translation to the error code Windows is reporting when ImgBurn tries to access the drive. The error code is 1381 = ERROR_TOO_MANY_SECRETS I have no idea why the OS would be reporting that but let's hope you can track down whatever's causing it.
  13. If possible you should try the drive in another pc. After that, you might like to consider getting a new one.
  14. It's probably something like packet writing software that's messing it up. Go through the add/remove programs thing again in Control Panel.
  15. This is something you need to fix, not me. The program cannot access your drives because something else is using them. Find out what it is and stop it. You could try using 'Unlocker' or 'Process Explorer' to find on what it is exactly.
  16. Something else probably IS accessing the drive. What other burning software do you have installed?
  17. Try cleaning the drive. Are your current verbatims the exact same dye as the old ones?
  18. Are you using the program in English?
  19. Does your drive recognise original (pressed) DVD-ROM discs?
  20. It wasn't the file but a reboot might have fixed it anyway.
  21. lol does the drive have power going to it?!
  22. Update ImgBurn Update Virtual CloneDrive to v5.4.2.8 beta Remove GEARAspiWDM from the filter list (this is the iTunes one) Remove PxHelp20 from the filter list
  23. I need a debug log from this one please. Press F8 before you hit the 'Write' button. Press it again once you've accepted the write params error, save the log and upload it.
  24. Nope, tried firmware 4L11 and 16x still works fine.
×
×
  • Create New...

Important Information

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