Jump to content


  • Posts

  • Joined

  • Last visited

CompNetTeach's Achievements

ISF Newbie

ISF Newbie (1/5)

  1. I can't remember if this was done properly in a previous version of ImgBurn. I am currently using 2.4.2. I know that it is possible for multi-format ISO 9660, Joliet & UDF discs to have different volume labels. Upon insertion, Windows will display the preferred volume label. On a mixed disc, Wihdows should display the "higher quality" version. However, ImgBurn creates DVD discs for which Windows displays the 9660 label rather than the UDF label. There must be a byte or bit setting somewhere that isn't being changed when ImgBurn is builiding these discs. In the mean time, if you know where the changes need to be done and they are relatively simple, I could build an ISO, edit it with a hex editor and then burn it. Thanks. Simple feature request, please?
  2. Might not be a bug, but, some additional drive checking logic is a good idea. Just a heads up for another maintenance task. Sorry I don't have the log to post (ran ImgBurn in portable mode on a guest machine) - I thought I copied it to the flash drive, but got the wrong log. I'll try again when I get a chance to use this particular machine again. I tried to burn a large 4+GB ISO onto DVD-R with a Sony DW-Q58A slimline burner on a Dell laptop. I remember two semesters ago burning some CD ISOs successfully using this machine. However, in trying to burn this to a DVD-R, I am getting "invalid parameter" errors after a prolonged OPC write cycle (maybe the display didn't update, and it was trying to initialize writing the image). Ignoring the error and continuing fails to do anything. This then results in a drive that usually doesn't seem to respond properly afterwards - shutdown & reboot required. Letting ImgBurn try to close the disc may or may not do anthing (drive may be unresponsive). One attempt did result in a closed blank platter - what a wasted coaster! However, it does write to DVD+R with book type DVD-ROM fine (this is my preferred media & setting, however, I don't feel like subsidizing schools more than I have to, which is already too much ...) Since two semesters ago, the drive's firmware has been updated from UYS2 to UYS3. VSO Inspector shows that it only supports Track-At-Once writing (kind of strange for a major manufacturer's drive, even if it is OEMed from Lite-On, a reasonably good drive maker, n'est pas?). If I remember correctly, usually ISO burns are done using Disk-At-Once. The drive previously did write CD-TEXT, but does not do so now - I suspect that this drive did not fully support DAO, and the firmware upgrade disabled it along with whatever else was in the update. When trying other burning software with ISOs using DVD-Rs on the DW-Q58A, mixed results occur. Packeges using the StarBurn engine (which always defaults to TAO) does work. CDBurnerXP Pro crashes at the end of the write - if the ISO was a video, it does play in standalone DVD players. If an ISO write to DVD-R with ImgBurn does indeed attempt to use DAO mode, then some additional checking to see if the drive does support DAO properly should be implemented. What a stupid limitation of tlhe DW-Q58A!
  3. Umm.... Interesting. Like I said, this happens with multiple burners from more than one manufacturer - I can post similar results from the Benq and my buddy's Matshita but it's pretty much the same log. As mentioned previously, once the disc is formatted properly by something, ImgBurn will reformat (quick erase) and burn to the Sony DVD+RW no problem. The discs work well otherwise, in fact, one platter has been rewritten at least 50 times so far in the video recorder. (Unlike a certain major North American office supply retailer's private label that died on the 3rd & 7th reuse for 2 different discs - note that the staff had indicated that there was a warranty on the media, which there was not - painful, like getting stabbed by a staple.) I'll just leave this as a community advisory that there can be some finicky media that just doesn't like simple formatting and has to be force formatted by something else. Thanks for looking into it.
  4. As per your request: I 16:26:28 ImgBurn Version started! I 16:26:28 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2) I 16:26:28 Total Physical Memory: 261,616 KB - Available: 38,536 KB W 16:26:28 Drive D:\ (FAT32) does not support single files > 4 GB in size. W 16:26:28 Drive E:\ (FAT32) does not support single files > 4 GB in size. W 16:26:28 Drive M:\ (FAT32) does not support single files > 4 GB in size. W 16:26:28 Drive U:\ (FAT32) does not support single files > 4 GB in size. W 16:26:28 Drive W:\ (FAT) does not support single files > 4 GB in size. I 16:26:34 Initialising SPTI... I 16:26:34 Searching for SCSI / ATAPI devices... I 16:26:35 Found 1 DVD
  5. Merci Beaucoup! You ARE the authority. As I mentioned above, having some sort of help file with the distribution would really help all the users. The interactions between the various settings can be difficult to grasp...
  6. Well... The behaviour occurs on two different computers with different burners: Benq DW1625, Lite-On SHM-165H6S. I even once tried it on a borrowed Sony DRU-520UL with the same result. Since I got a stack of 15 of them (going to last a while...), I'll just have to remember to QuickFormat or use them with something else first.
  7. When burning on its own, Task Manager shows typically only a few % points more required by 2.4 vs 2.3 (under 25% if the computer is otherwise idle). However, the buffer emptying is more common when using a compressed NTFS volume as the source. I suspect that in this situation, Microshaft is shafting ImgBurn in terms of priority access to the drive with its background tasks? Might it be time to force a higher priority for ImgBurn?
  8. I may have stumbled upon a bug. I am trying to update a bootable CD. I have extracted the boot image into CourseBT.IMA. I have copied the entire regular contents of the CD into F:\CourseUP.CD. I have made changes to the files and directory structure within CourseUP.CD. To make things easier for the future, I have also copied CourseBT.IMA within a subdirectory in CourseUP.CD. When I build using ImgBurn 2.4, I add F:\CourseUP.CD (using add folder) as the only source location. With the "Don't Prompt Root Content" setting checked either ON or OFF (have done about 6 test burns), I end up with a CD that has CourseUP.CD as the only entry in the burned CD's root directory (and of course, booting fails, as autoexec.bat from the boot image can't find the continuation file on the regular part of the CD). Note that the boot image for this creation is set to F:\CourseUP.CD\Sources\CourseBT.IMA. Of course, when "Don't Prompt Root Content" is set for Disabled, I should get a pop-up asking Yes / No whether to proceed with F:\CourseUP.CD\ representing the root directory for the image content (my answer would be yes). But, this window does not appear. Since ImgBurn reads/writes settings to the registry, I don't have the luxury to identify the instantaneous value when using ImgBurn. Perhaps the wrong value is being stored /read, or accidentally being ignored or not properly updated... I do seem to remember it working in 2.3.?.? Could building a bootable CD with a doubly referenced boot image file be causing a hiccup? Now of course, if I use SUBST Z: F:\CourseUP.CD, and add Z:\ as the source location, ImgBurn works fine, and the result is as expected. That's what I'm doing right now. Suggestion: Add a copy of the "The ImgBurn Settings" as part of the distribution package, if necessary, in text form only - that will solve a lot of quick queries when not attached to the Internet. Suggestion: Add a more comprehensive Build feature (i.e. be able to create an actual virtual directory structure first). I realize that this would be a lot of work, and is something for the future... Kudos: The Optimization feature is EXTREMELY welcomed. Repeat EXTREEEEEMELY welcomed. Thanks in advance for looking into this.
  9. There does appear to be an increase in performance requirements for 2.4. I have ImgBurn installed on my older PIII laptop with WinXP Pro SP2 AutoUpgrade that I carry around to & from courses (the older laptop helps keep the students from trying to steal it, plus it was one of the ones with a privacy screen option). When burning with 2.4, from time to time, I notice that the buffers start emptying out (device & ImgBurn), under 2.3.x, ImgBurn's buffer only ever dropped to around 75%. Of course, as the buffers emptied, the drive slows down. I switched back to 2.3 (it was tough finding the old version on the Internet!) for the laptop, and the performance has returned to original levels. Suggestion: please leave a link up for an older version on the ImgBurn website! Some fine tuning required?
  10. I'll put in my two cents worth of info. There IS a problem with ImgBurn formatting Sony DVD+RWs. I have a small stack of them, and have been using them successfully with other software & standalone video DVD recorders. (These are real Sony DVD+RWs, not counterfeit, that came as a bonus with the Sony DVD recorder.) Nero will properly format the disk everytime. Once the disk is formatted (either quick or full), then ImgBurn will properly recognize the disk and will burn successfully. If the disk is formatted with the standalone DVD (TV video) recorder, ImgBurn will not successfully reformat & burn to the disk, UNLESS the disk has been completely filled and finalized on the standalone recorder. Could the Sony DVD+RWs be missing or have slightly different some piece of info in the identification area built into every piece of media than what ImgBurn is expecting? This can be a concern, as Sony was one of the main backers of the "plus" format and wrote much of the specs. I can't remember which brand, but a friend mentioned he had a similar problem with another brand with ImgBurn (they worked with Nero but not ImgBurn). Of course, he can't remember now, as the disks now work with ImgBurn after being first used with something else. So, this should be a low priority issue worth tracking down sometime...
  • Create New...

Important Information

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