ISO burning problem-incorrect block size

Discussion in 'CD-R' started by pofd66, Apr 2, 2003.

  1. pofd66

    pofd66 Guest

    I am trying to burn an .iso of jedi outcast with nero.When I attempt to do so I receive the following message:the entered block size does not correspond to the image length...the block size maybe wrong...do you wish to correct.
    I selected correct...then Data mode 1,raw and of course a block size of 2352 bytes.Burned and have an unreadable disk.
    Checking the image with winiso yielded the following:328912 sectors,sector size 2352 bytes ,single data track,Joliet cdrom file system.....the file size is 738 MB (773,913,840 bytes),size on disk 738 MB (773,914,624 bytes).

    Any suggestions please.Is it written in the wrong mode?Really a bin and not an .iso?Created with EZCD?As an alternative can you extract and burn(Prob not a good idea I wud assume)?

     
  2. aldaco12

    aldaco12 Active member

    Joined:
    Nov 6, 2002
    Messages:
    2,544
    Likes Received:
    0
    Trophy Points:
    66
    My calculation (simple math) brings 773,913,840 bytes / 2352 bytes/sectors = 329,045 sectors, so it seems WinISO is screwing up, dunno why (maybe it doesn't account the boot blocks and the pre-gaps).

    Anyway your image is an ISO/2352 image file, a.k.a. .BIN file - .RAW file - .IMG file (depending on the application you use to make it). I assume it has been dumped by Discdump and, very likely, it is NOT an EZCD image.

    Therefore Nero+Correct+MODE1+RAW data should have worked.. unless:
    - you have problems with Nero
    - the image is bad
    - the disc is protected (very likely)

    My suggestion is to scan the image to detect if it's protected and, if it is, use more sophisticated software.

    So, assuming your image name is "jedi.ISO", you have to write a CUE file with notepad like this:

    FILE "jedi.iso" BINARY
    TRACK 01 MODE1/2352
    INDEX 01 00:00:00

    save it in the same directory of the ISO file. Then follow the steps shown in the 'protect CD' thread:
    http://forums.afterdawn.com/thread_view.cfm/23699

    (that is: install Alcohol 120%, mount the image in Alcohol, scan it with ClonyXXL: follow the guide, with pictures, step by step)

    If the image is NOT protected, maybe it's broken. Scan it with CDMage.

    Report here the results ;)
     
    Last edited: Apr 2, 2003
  3. pofd66

    pofd66 Guest

    Thanks for the info.Will give it a try and report back.A quick question:if it is a bin file then should I rename it .bin and burn with a cue?Will report back on your suggestions.Thanks.
     
  4. aldaco12

    aldaco12 Active member

    Joined:
    Nov 6, 2002
    Messages:
    2,544
    Likes Received:
    0
    Trophy Points:
    66
    There is no need to rename if as long as you write correctly the CUE. For instance, you should have noticed the extension i put on the sample CUE file I wrote above:

    FILE "jedi.iso" BINARY
    ...
    ...

    that already takes into account an .ISO extension (I would have written "jedi.BIN" otherwise.
     

Share This Page