Jump to content

JohnthePilot

Members
  • Posts

    44
  • Joined

  • Last visited

Posts posted by JohnthePilot

  1. Oh please, ya don't need imgburn to open it or vcd to mount it. Firmwares are usually a special type of bin files. Check the instructions on the cameras manufacturers site. All u usually need to do is put the bin file on the root of the memory card and flash it from inside the the camera

    If you read my post above, you will see that I have already done that and successfully updated the firmware.

  2. I have been sent a .bin file, but when I try to open it in ImgBurn it says invalid or unsupported image file format, yet ImgBurn looks for .bin files when I search for the file to burn to DVD. Any suggestions would be appreciated.

     

    These are the contents of my log file:

     

    I 13:49:36 ImgBurn Version 2.5.8.0 started!
    I 13:49:36 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7601 : Service Pack 1)
    I 13:49:36 Total Physical Memory: 8,387,064 KiB  -  Available: 4,454,576 KiB
    I 13:49:36 Initialising SPTI...
    I 13:49:36 Searching for SCSI / ATAPI devices...
    I 13:49:37 -> Drive 1 - Info: LITE-ON DVDRW LH-20A1L BL06 (I:) (ATA)
    I 13:49:37 Found 1 DVD±RW/RAM

  3. Hi,

    I've just downloaded a film and it turns out to be a 7.7G iso file. I can't burn it to a single layer disc and I can't shrink it with DVD shrink because it's not a DVD. Is my only answer a dual layer disc?

  4. Yes, 'Continue' is the same as 'Ignore' - meaning 'Ah, don't worry about it, just burn away!'. That's fine until something else tries to access the drive or sends the wrong command and you end up with a nice coaster.

     

    You have to use Process Explorer to find out what's preventing ImgBurn from getting exclusive access over the drive - it's all detailed in the FAQ.

     

     

    Yes, I know. RTFM or in this case RTFFAQ :whistling: I only added to the thread because the topic was already open.

     

    Regards,

    Pilot

  5. At least you got a succesful burn, I am sticking with XP Pro for a while yet until some of the annoying niggles with Vista are resolved - thanks for letting us know.

     

    I've recently started getting the same problem in XP Home. As far as I can make out, nothing else is trying to access the burner. I pressed continue and ImgBurn carried on as normal. Strange.

  6. I think the problem for you was that in Build Mode ImgBurn will let you select either files or folders (as LUK said above ;) ) dependant upon the button you push.

     

     

    I think you are right. If Write is selected then the only option is to select a file, but Build lets you select both a file or folder, and that's what I must have done. At least I got the job done in the end.

    Regards,

    Pilot.

  7. Hi Lighting,

    Thanks for your reply.

     

    It all depends on which button you click in build mode.

     

    One browses for files, the other browses for folders.

     

    I must have pressed the wrong button, but when I tried again, Build would only let me select a folder.

     

    If you ended up with an ISO as a file on the last cd/dvd you burnt, either you used Build mode or the ISO you burnt (in Write mode) DID actually contain another ISO file!

     

    Reburning in Write mode gave me the right result, so the ISO file was OK. At least everything is OK now.

    Thanks to you both for your help.

    Regards,

    Pilot.

  8. Hi,

    Cornholio

     

    thats what she said last night :P

     

    Lucky you :)

     

     

    it sounds like you did it from build mode to me , but lets see after your r/w test :)

     

    It worked, but I don't understand this. I tried again, this time selecting the file with Build selected, and it would only let me select a folder, so I must have had Write selected originally.

    Regars,

    Pilot.

  9. Hi cornholio,

    My God! That was quick.

     

    just to check , you chose write mode and navigated to your iso?

    you didnt navigate to it in build mode?

     

    Can't remember which way I did it. Could that be the problem? I'll try again making sure I select write first. Gonna use a +RW this time just in case. :)

    Regards,

    Pilot.

  10. Hi,

    Apologies. I've asked this before, but can't remember what the answer was and the topic has been deleted.

    I tried to burn an ISO file and selected "Write", but ended up with a coaster with the same ISO file on it instead of a playable DVD. What have I done wrong?

    Sorry to ask again.

    Thanks,

    Pilot.

  11. JohnthePilot, Thanks for getting back to us....... happy burning :)

     

     

    Hi Kev (and others who have contributed to this thread),

    Have been using Verbatim +R discs for last two weeks and no problems. It may be of interest to UK users that Maplins are selling 100 packs for ?40. Good value.

    Regards,

    Pilot.

  12. Hi Cornholio,

    With Nero BurningRom I simply burn the VOB and IFO files to the DVD. Am I right in assuming that with ImgBurn I first have to create an ISO file on my hard drive using the Build Mode then burn this to the DVD using the Write Mode, cos all the guides seem to be about create ISO files or am I missing something?

    Cheers,

    Pilot.

     

     

     

    JohnthePilot, Your above statement is correct. Burn the image from your harddrive to media and you should not have any problems. Let us know what happens :)

     

    Hi Kev,

    Sorry it's taken so long to reply to this particular post (and to da Clown's suggestion) but have been having problems with my machine.

     

    I've tried both methods and they both work fine. Also find no problems with Verbatim and, strangely enough Tesco's own brand +RW, so I'll stick with those.

    Many thanks,

    Cheers,

    Pilot.

  13. Ignore the names the program gives the info, those names are taken from the MMC specs.

     

    The manufacturer id (on minus format media) and disc id (on plus format media) ARE the dye manufacturer/type.

     

    Thanks Lightning. That's all I wanted to know. It seemed such a simple question yet caused so much confusion.

    Regards,

    Pilot.

  14. If I were you, I would only be looking for Verbatim media or Taiyo Yuden with ID of either TYG02 or TYG03. :)

     

     

    Hi ifcrule,

    I've taken your advice and got some Verbatim discs. Incidentally, the manufacturer is given as YUDEN000-T03-00. Are Verbatim and Taiyo Yuden the same?

    Further to my earlier posts, is the dye manufacturer the same as the disc manufacturer? This is what what was confusing me when I asked how you knew who the dye manufacturer was, cos you seemed to suggest my TDK discs were fakes cos of the dye manufacturer, but there is no information in my log (or the ImgBurn information) other than disc manufacturer.

    Regards,

    Pilot.

  15. Its a little window below Imgburn, that is called a "log" copy everything in that window so we can see whats going on.

     

    Wasn't sure if you were being sarcastic or not, but I'll give you the benefit of the doubt :/

    In case you hadn't noticed I had already posted my log and it wasn't where you said.

    Regards,

    Pilot.

  16. If you're referring to this as the increased size...

     

    I 03:09:52 Source File Size: 4,681,465,856 bytes

     

    ... that value is in bytes, not MB. You can't just move the decimal point and call it 4.68GB, it's not.

     

    You have to divide by 1024 each time, not 1000.

     

    So it's actually 4.36 GB

     

    Doh! I've been up all night and my brain isn't working :sleeping:

  17. Thanks to you both.

    I'll try and stick with Verbatim (never seen Taiyo) for +R discs, but if what ifcrule says is true, then it's worth perservering with Tesco's +RW discs. At least if something goes wrong I don't end up with a coaster. I can simply reformat it :)

    Cheers,

    Pilot.

     

    PS Nobody has explained why ImgBurn has increased the size of the image file from that created by DVD Shrink.

×
×
  • Create New...

Important Information

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