Jump to content

jvimgburn

Members
  • Content Count

    5
  • Joined

  • Last visited

About jvimgburn

  • Rank
    ISF Newbie
  1. jvimgburn

    Invalid Field in CDB (?)

    Thank you, again, mmalves. As I said in the previous post about "How to know the disc capacity using Build Mode?", you solved all my questions. BTW, even ImgBurn refusing to burn that compilation, Nero 6 (an old one) burn it on the fly, without questions. I was migrating to ImgBurn, but after some troubles like this, I think I'll keep both, ImgBurn and the old Nero. I like very much ImgBurn and I'm impressed how this tool is very well coded (written). Congrats for all your team. There were a little delay for this post because the system (forum) did not alert me via e-mail that there would be an answer here, althought I clicked to subscribe this thread.
  2. jvimgburn

    How to know the disc capacity using Build Mode?

    Thank you, mmalves. You solved all my questions. There were a little delay for this post because the system (forum) did not alert me via e-mail that there would be an answer here, althought I clicked to subscribe this thread. Thx
  3. jvimgburn

    Invalid Field in CDB (?)

    Hi I'm trying to test a compilation (TestMode checkbox checked). I have an ISO image with DVD movie inside. Size is 4.706.598.912 bytes. I'm confused with the available space on the media. When I open ImgBurn for the first time it shows the follow information: _____________________________________ HL-DT-ST DVD-RAM GSA-H22N 1.00 (ATA) Current Profile: DVD-R Disc Information: Status: Empty State of Last Session: Empty Erasable: No Free Sectors: 2.297.888 Free Space: 4.706.074.624 bytes Free Time: 510:40:38 (MM:SS:FF) Next Writable Address: 0 Supported Write Speeds: 4x; 8x Pre-recorded Information: Manufacturer ID: TYG02 Physical Format Information (Last Recorded): Book Type: DVD-R Part Version: 5 Disc Size: 120mm Maximum Read Rate: Not Specified Number of Layers: 1 Track Path: Parallel Track Path (PTP) Linear Density: 0.267 um/bit Track Density: 0.74 um/track First Physical Sector of Data Area: 196.608 Last Physical Sector of Data Area: 2.495.103 Last Physical Sector in Layer 0: 0 Performance (Write Speed): Descriptor 1... -> B0: 0x00; B1: 0x00; B2: 0x00; B3: 0x00 -> EL: 0 (0x00000000) -> RS: 11.080 KB/s (8x) - WS: 5.540 KB/s (4x) Descriptor 2... -> B0: 0x00; B1: 0x00; B2: 0x00; B3: 0x00 -> EL: 0 (0x00000000) -> RS: 11.080 KB/s (8x) - WS: 11.080 KB/s (8x) _____________________________________ If I eject and load again the same media, the information window is the follow: _____________________________________ HL-DT-ST DVD-RAM GSA-H22N 1.00 (ATA) Current Profile: DVD-R Disc Information: Status: Empty State of Last Session: Empty Erasable: No Free Sectors: 2.298.496 Free Space: 4.707.319.808 bytes Free Time: 510:48:46 (MM:SS:FF) Next Writable Address: 0 Supported Write Speeds: 4x; 8x Pre-recorded Information: Manufacturer ID: TYG02 Physical Format Information (Last Recorded): Book Type: DVD-R Part Version: 5 Disc Size: 120mm Maximum Read Rate: Not Specified Number of Layers: 1 Track Path: Parallel Track Path (PTP) Linear Density: 0.267 um/bit Track Density: 0.74 um/track First Physical Sector of Data Area: 196.608 Last Physical Sector of Data Area: 2.495.103 Last Physical Sector in Layer 0: 0 Performance (Write Speed): Descriptor 1... -> B0: 0x00; B1: 0x00; B2: 0x00; B3: 0x00 -> EL: 0 (0x00000000) -> RS: 11.080 KB/s (8x) - WS: 5.540 KB/s (4x) Descriptor 2... -> B0: 0x00; B1: 0x00; B2: 0x00; B3: 0x00 -> EL: 0 (0x00000000) -> RS: 11.080 KB/s (8x) - WS: 11.080 KB/s (8x) _____________________________________ If I restart Windows (XP-SP3) and run ImgBurn again, the first window is showed (I mean, the one with less space available). If I eject and load again the same media, the information window change to more space available and always shows the same info: 4.707.319.808 bytes, no matter I eject and load again. Afterall, what is the real free space available? 4.706.074.624 or 4.707.319.808 bytes? As we can see, Free Space is greater than the file (4.707.319.808 > 4.706.598.912). But I got the follow error: I/O error ScsiStatus:0x02 Interpretation: Check Condition CDB: 53 00 00 00 00 00 23 11 20 00 Interpretation: Reserve Track - Sectors: 2.298.144 Sense Area: 70 00 05 00 00 00 00 0E 00 00 00 00 24 00 00 00 00 00 Interpretation: Invalid Field in CDB So, I have the questions below: 1 - Why I got 2 different info windows about the same media? 2 - What is the real space available to write? 3 - Why I got such error (Invalid Field in CDB) and what it means? 4 - How to fix it and test the compilation? thx
  4. jvimgburn

    How to know the disc capacity using Build Mode?

    Sorry for the dumb topic posted here. I realized that there is a Device Tab at Build Mode. The problem is because I couldn't find the info about the media because the media was not inserted yet... Sorry, folks. Topic is almost solved. The other question remains: Is there a way to overextend the official limit, just with a few amount of data? And why I cannot reply some topics? Thx
  5. Congratulations for the people who keeps the forum interesting and very useful for who is coming right now. Is there a way to find out how many bytes fit exactly on the currently inserted media? I know, I know, at Build Mode there is a Calcultator just to inform the bytes remaining after I do my compilation. But, how to know the disc capacity at Build Mode? Do I have always to quit Build Mode and go to Write Mode to know that? Is there a way to overextend the official limit, just with a few amount of data? For the moderators: I tryed to reply to this topic: http://forum.imgburn.com/index.php?showtopic=18990&st=0&p=136582&hl but I could not. The system didn't allow me to do that, I don't know why. YOU CANNOT REPLY TO THIS TOPIC, is what it says... Is it's because I'm just arrived? I insist with this question because the answer given there wasn't clear enough. Why Build Mode cannot inform the capacity? Sorry if it sounds like dumb question (and after the attempt of answer it). Thx
×

Important Information

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