Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by Dstruct

  1. Calm down. All relevant information can be seen on the screenshot. So if you're not extremely dumb you should be able to reproduce it with EASE. I also don't need YOUR help but the one of the developer ("LIGHTNING UK!"). Thanks! FIXED (
  2. Maybe your browser fucks it up (resizing to smaller size) when viewing it!? No problems here with it. If you're using Firefox -> click on the image to view it at original 1:1 size ... or hit CTRL+0 to reset the website scaling to original size ... or ...
  3. Come on. You can see all this on the screenshot, don't you?
  4. & isn't allowed in filenames? That's simply not true. FIXED (
  5. Here a screenshot of ImgBurn on Windows XP SP3: Why doesn't ImgBurn display "1 & 2" properly in the Image Information window? FIXED (
  6. I didn't say it's a technical problem. More a cosmetic issue.
  7. I know. That's not what I'm talking about. I'm talking about the Write Speed dropdown menu which lists speeds which make no sense at all.
  8. Currently if you have an empty CD-R in your drive, ImgBurn still lists speeds from 1x up to 56x. Why? Wouldn't it be nice if the "Write Speed" dropdown only would show the speeds that your drive is capable of, minus the not supported speeds for the media? Say I have a drive which can write 2x, 4x, 8x, 16x and 32x. The media I want to write just supports 4x, 8x and 16x: => now ImgBurn should only show AUTO MAX 4x 8x 16x Makes sense?
  9. yeah, it's great to have so many options! big ups for that!
  10. i don't know as i don't use the new design themes in xp. no as this doesn't fix the flickering menus and checkboxes. the "fix" with this manifest file does.
  11. I just found the reason. My own mistake, sorry. I've put a imgburn.EXE.MANIFEST text file with this <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> <assemblyIdentity processorArchitecture="x86" version="" type="win32" name="imgburn.exe"/> <description>ImgBurn</description> <trustInfo xmlns="urn:schemas-microsoft-com:asm.v2"> <security> <requestedPrivileges> <requestedExecutionLevel level="asInvoker" uiAccess="false"/> </requestedPrivileges> </security> </trustInfo> </assembly> content into my ImgBurn folder. And this caused the tooltip problem. I've did this because I got this hint from the developer of Total Commander to solve/workaround a flickering problem with Nvidia graphiccard drivers on rotated displays. This flickering also is there in ImgBurn and it was "fixed" by my imgburn.EXE.MANIFEST too. But obviously it introduced new problem(s) http://www.ghisler.ch/board/viewtopic.php?t=19033 (if you can read german - my username is "Dandruff" there)
  12. Sorry, already explained in the settings guide http://forum.imgburn.com/index.php?showtopic=6232
  13. What's the new "Don't Use Immediate I/O" option for?
  14. Ok. But the question is: Is this the official recommended update procedure?
  15. What's the recommended update procedure? Shall I deinstall first? Will the settings be removed if I uninstall
  16. RealPlayer and PlexTools Professional XL (AudioCD Player) can read CD-Text too.
  17. yeah, i usually do this all with virtualdub and the fcchandler mpeg-2 plugin. no problem with these.
  • Create New...

Important Information

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