Jump to content

killjoy

Members
  • Posts

    19
  • Joined

  • Last visited

Posts posted by killjoy

  1. polopony Apr 9 2006, 03:16 AM Post #19

     

     

    ISF Advanced Member

     

     

    Group: Beta Team Members

    Posts: 451

    Joined: 9-September 05

    From: West Palm Beach

    Member No.: 13

     

     

     

    there aren't any real release dates its more like test the betas try to find stuff that doesn't work right or in many cases have forum members find things from a release, post a bug then Luk works on that checks his coding then double checks stuff, impliments suggestions from members where he can then that gets checked again with beta testers and IMGburn members using all sorts of different drives and then when all looks good a newer version is released and the process basically starts again so its not like an anouncement stating the new version will be out on such and such a date its no different than the old forum

  2. I'm sorry, but Memorex media surely isn't the best available.

    You'd be better off with Verbatim or Plextor media, Ricoh is also a good choice.

    I do not know which movies you are trying to backup, but it could also have to do with some kind of copy protection.

     

    edit: Can you check out the mediacode of your Memorex discs?

    You can read it out with Imgburn and looks like this for example:

     

    Pre-recorded Information:

    Manufacturer ID: TYG03

  3. It should be out already.... once I've got my head together (out on the beers lastnight!), I'll update the website and post it up.

     

    Thanks LUK! Can't wait to test the new version :thumbup:

  4. lol, I remember that one of my first cd-writers did not support burn-proof technology and I ended up with many buffer underrun errors.

    Indeed you could throw away the disc if the buffer was empty :P .

    Nowaydays every writer has some sort of burnproof technology. Some say that Seamless Link technology works even better (Philips/BenQ drives), because it is part of the firmware and it is impossible to turn it off accidentely. Don't know if that is only a fairytale though... :thumbup:

  5. I am sorry, but I just thought this question was about making an ISO file from a collection of files already present on the Harddisk.

    If the question was 'how to rip' then ofcourse this thread would be closed as we speak. :P

    Maybe it's a good idea to close this thread anyway, I think I gave enough suggestions already. :blush:

  6. Hi Here, Welcome to the forum. NO, NOT EVER. Imgburn will remain a image write program only. It will never be able to read just write. In saying this though, it is the best write program out there ............ :thumbup:

     

    I would agree it is the best writing program out there. If it won't ever support ISO creation. Could you recomend a good program that will, even if I need to use it in combination with AnyDVD, etc?

     

    Thanks!!!

     

    You can use ImgTool Classic for creating an ISO-file. Use Google to find it.

    Alternatively you can use Folder2Iso.

  7. About LUK telling everyone when the new version will be out if he said 6 months then you would say ok 6 months and if he released it in 4 he'd be everyones hero if he said 2 weeks and it was 15 days then he's the goat, a kind of no win situation theres been 20 -30 versions released if you count betas thats a lot of work in a short time

     

    polopony that is not the case. I just expected a release a bit sooner, if you would please check postnumber 13 of this topic before delivering this comment.

    And it's not the queue function, it is just the most important function I was referring to: the writing process itself.

  8. polopony I partly agree with that.

    LUK already told in this forum that the buffer underrun error was one of the first things that was fixed. Then he said a new version was SOON to be released with that issue fixed.

    Now what is the definition of soon? Will that be some days or some weeks? Now everyone is waiting eagerly for the new release.

    So maybe some clarity about when the new release is coming surely can't hurt? I know it is impossible to give an exact releasedate, but an announcement of some kind would be gladly appreciated.

  9. Cynthia, I have to agree with you.

    I think that solving bug fixes have priority over implementing new functions. Considering many people are dealing with a version containing some bugs I think they must have the chance of getting a fixed version instead of going back to a prior version (like I did).

    I know Lighting UK puts a lot of work in it, so please take this as positive criticism.

    If it's not too complicated, why not release a new beta version AND a final version alongside.

    Take for example Utorrent, they continiously release new beta versions with added functionality, and also having a final version for users that want stability. :thumbup:

  10. Killjoy, That problem will be/ is fixed in the next release of Imgburn. Unlike others though, I have not had any issues with this problem. :/ I'm sure it won't be too long before the next version is released and everyone can update to the latest version. :)

     

    I sure hope so, considering that was fixed almost instantly :P

  11. Nope, it's max 4,37 GB.

    You should configure the program to set output file to max 4,35 GB or 4464 MB, that works best to burn your ISO to dvd.

    That it shows 4,7 GB on the package means nothing, just like when you buy a new hard disc. Windows always 'wastes' a bit of the full capacity.

  12. Use the queue function with some images loaded...

     

    Oh, so this only happens if you are burning images from the queue? I admit I don't do that - I only burn an image to one disc at a time, and don't find myself burning several different images consecutively in a short period.

     

    However, if the source of the issues is the size of the data "chunks" being read from the hard disk, I don't see how using the queue would be any different than burning a single image...

     

    However, I'll give it a try. Do I need to load several images, or will just one image in the queue be enough to test this?

     

    No, this applies to single images too. This has been fixed already in version 1.2.1.0

  13. For me, the 'Available' counter in the 'Physical Memory (K)' box on the 'Performance' tab showed a drop in value every second that matched the write speed of my burner.

     

    Once I'd noticed this pattern I didn't bother to keep an eye on it right until the end. What I did see was that it took me down from about 1.2gb free to 400mb. I may have gone beyond that, I don't know.

    Switched back to 64k transfers and it wasn't even noticable after that.

     

    As it's not actually ImgBurn using the memory, memory for the ImgBurn.exe process stayed at 30 odd MB as normal.

     

    Strange, I didn't seem to see ANY decrease during burning in the performance tab, and definitely not by that much even when the burn started! Hmmm, perhaps it depends on the version of Windows (I'm using XP Home SP2 with all critical updates), and possible differences in memory management?

     

    Maybe so, I am wondering what amount of RAM you have?

    Lightning UK, what about that fix you would release for this issue? I thought a new version would be released two days ago (correct me if I am mistaken).

  14. I haven't noticed this issue, been surfing, burning and printing all weekend with no probs, but I have a fair amount of memory if that helps?

     

    Yep, I do have an older system with 512 MB RAM. I think you have more, haven't you? With big specs you probably do not notice the problem at all ;)

  15. I don't want to be rude, but when is the version without the caching problem expected for release? :pray: I really love the new options in this version so much that I do not want to install the older version again. This was the only problem I noticed almost instantly. Respect to Lightning UK for putting so much effort in the program :thumbsup:

  16. I noticed the problem too. Maybe it's a windows problem, but I did not have this problem with imgburn 1.1.0.0. So why suddenly it eats all available RAM? Didn't imgburn work with a buffer before, because if Windows tries to store a 4GB file in RAM, that would be just plain silly.

    I know some programs use a buffer to process the image, and take for example max 128 MB of the available memory. I am not a programmer, but is this something that can be implemented in the next version perhaps? I always loved imgburn so far, but the caching problem forces me to use other applications at the moment.

×
×
  • Create New...

Important Information

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