Jump to content

rasheed

Members
  • Posts

    53
  • Joined

  • Last visited

Posts posted by rasheed

  1. You can move your profile folder, if that is what you're trying to do.

     

    First, move your profile to a location you want, then edit profiles.ini and change the path to your profile:

     

    [Profile0]
    Name=default
    IsRelative=0
    Path=D:\Path\to\your\new\Profile
    

     

    Note that you have to change "IsRelative" setting to zero.

     

    I do not know if you can change the folder where firefox looks for profile.ini

     

    Yet another possibility would be to start firefox with "-profile" option. I didn't try it, so can't tell if it will work. See Firefox command line arguments.

  2. Can ImbBurn burn a 24 gig data folder (with re-cursed sub-folders) to DVD disks?

     

    It appears to be trying to add it all onto one track of a single DVD without prompting for another.

     

    How do you get it to span a large file onto several DVD's without having to hunt an pick it all?

    CDBurnerXP supports simple disc spanning.

  3. Assume I have a DVD+RW with some (old) stuff on it.

    Then I want to overwrite the DVD+RW with some new files.

     

    When I start the burn process in ImgBurn then at first the user is informed that the old stuff has to be erased.

    And yes, there is a big, big erase phase prior to burning the really new files.

     

    Why does ImgBurn need such an additional time consuming "erase" step?

    Due to this unnecessary operation the burn process takes twice as much time as other programs

     

    Other burning programs like Nero or CDburnerXP just overwrite the existing data.

    Thats it.

     

    Can ImgBurn not just overwrite the content table entries?

     

    Maybe ImgBurn could offer the user an additional "full erase". But the default should be "quick erase"

     

    Peter

    ImgBurn by default prefers properly formatted DVD+RW discs (can be turned off in options). Other software, CDBurnerXP included, does not. If you use a disc that has been previously used by CDBurnerXP, then ImgBurn will offer you to properly format it. After it has been properly formatted, it won't require formatting again, and ImgBurn will just overwrite the data on disc, just as other programs do.

  4. Can someone help? I have the DVD movie copied to my hard drive and saved as an .ISO file. I can browse to it and select it as the source and then I insert a blank DVD (Memorex) to use as the destination. The area where you click to "write" the file is grayed out and will not allow me to make a selction to start writing the file. I have the write speed set to auto. What am I doing wrong?

     

    Does the line in the status bar say "Device Not Ready (Medium Not Present)"?

  5.  

    What do you mean? UDF support or packet writing support?

     

    ImgBurn supports UDF filesystem, but ImgBurn is not packet writing software like InCD.

     

    ISO-13346 is, according to http://en.wikipedia.org/wiki/Universal_Disk_Format, a change in on-disk format. As the Wiki points out, it is a successor to ISO-9660. Irrespective of whether data is written in packets or not, its the format that's the issue.

     

    I'm curious whether the Data Type in ImgBurn 2.5 of "MODE2/FORM1/2542" is related? If so, what would be UDF Revision number to best select?

     

    What I know is that a Dell-supplied Windows 7 Pro DVD is in ISO-13346 format. I have successfully read in and created an on-disk ISO of some 6,170,824,704 bytes. ImgBurn reports that intermediate file with File Sys: ISO9660 (Bootable), UDF (1.50). It has 3,013,098 sectors, LB=2,084,960, and size is 6,170,824,704 bytes. Clearly, an ISO9660 DVD has 4,700,372,002 bytes max, so the intermediate ISO I made of the original DVD won't fit. (I have successfully recorded it, in ISO9660, on a Dual-Layer DVD.)

     

    It does not appear that ImgBurn recognizes the source ISO properly (reporting it as ISO9660, when it is known to be ISO13346.

     

    I'm trying to figure out if this is an issue (ISO-13346 as successor to ISO-9660) that our honorable designer and implementer, LIGHTNING UK!, is conversant with, and has plans to add to ImgBurn, or not.

     

    --Carol Anne

     

    As I have told you before, ImgBurn supports UDF, versions 1.02, 1.5, 2.0, 2.01, 2.5 and 2.6, to be exact.

     

    Regarding ISO 9660, the filesystem itself has no disc size limit, it has a single file limit of 4 GB, because a 32 bit value is used in the file descriptor table to represent file size. For example, ISO 9660 disc can be 25 gb in size, but no file on that disc may be larger than 4 gb.

     

    As mmalves pointed out, a single disc may have multiple filesystems on it, including ISO9660 + UDF, which ImgBurn correctly reported.

  6. Now that Windows 7 is being ditributed with more than 6GB on a single DVD, we need to be able to read/write ISO-13346 media. Is there any chance of that being included in a future version?

     

    For now, I'm using Nero's InCD v6.6; clumsy, but it appears to work.

     

    What do you mean? UDF support or packet writing support?

     

    ImgBurn supports UDF filesystem, but ImgBurn is not packet writing software like InCD.

  7. I don't generally mess with anything linux and ImgBurn is hardcoded to only patch the file if it's where I mentioned earlier (i.e. the OS path to the image's '\isolinux\isolinux.bin' file must be identical to the boot image file's OS path) - This is by design.

     

    I can of course add additional checks for those other locations.

     

    I don't know if taking a copy of the isolinux.bin file, patching it and inserting it as the boot image whilst leaving the one in the file system alone would work properly.

    Thanks for clarification. isolinux actually doesn't load itself from the filesystem on the cd, so it can be safely moved out of it (just tried it, and it boots ok). AFAIK, isolinux loads itself from the CD using BIOS functions, even if you set "Sectors to load" to 28 (28*512 = 14336, the size of the loader as of version 3.83).

    This is a comment from isolinux.asm, line 399

     

    ; Some BIOSes apparently have limitations on the size
    ; that may be loaded (despite the El Torito spec being very
    ; clear on the fact that it must all be loaded.)  Therefore,
    ; we load it ourselves, and *bleep* the BIOS.
    

     

    Regarding the boot info table, isolinux can work without one patched in, it just assumes "single session disc and one boot entry" (comment, isolinux.asm, line 361). AFAIK, this "boot info table" is actually not standard stuff, I haven't seen it mentioned in the El-Torito specification.

     

    Taking all into consideration, leaving everything as-is in ImgBurn is the safest option.

     

    Thanks.

  8. If you set the appropriate boot image file, yes it patches the boot info table.

     

    The boot image file must be set to the same 'isolinux.bin' file as is found in the 'isolinux' folder (also present in the image / 'source' box).

     

    LUK, I was experimenting today with my boot disc, and was trying to find out why boot info table wasn't patched in on my discs, well, the reason is that I put the files in boot/isolinux, instead of just /isolinux.

    So, ImgBurn correctly patches the boot info table only if the loader resides in /isolinux. Putting files in /boot/isolinux caused ImgBurn not to patch the table in (0xDEADBEEF). Is this by design, should it be marked as a bug, and will it change in the future? I'm aware that this feature is not high-priority, but isolinux documentation states that config file can reside in either /boot/isolinux, /isolinux or /, in that order. Would it be possible to patch isolinux.bin pointed to by a path in "Boot Image" text box in "Bootable Disc" options, regardless of its location in the source filesystem (this would allow moving isolinux.bin out of the source filesystem altogether), or, perhaps, just patch the boot loader in imagefile / on disc, leaving the copy in the source filesystem untouched?

     

    Thanks in advance.

  9. I always wondered if I should hit the button (which is hard to find in the dark recess where my pc lives) or if it's ok to gently push the drawer in by hand. I know it's designed to be able to do that, but is it wearing it out?

    Thankee,

    No, there is nothing to wear out. When you push the tray (gently), it will trigger an opto-mechanical (usually, like the ones that were used in mechanical mice) switch in the drive, which will activate the tray motor, pulling the tray into the drive.

    Initial force you feel when you push the tray is from the electric motor your hand turns through a system of gears.

     

    Since I do not like the feeling like I'm forcing things, I never push the tray by hand, I always push the button :)

  10. I bought a dvd burner and hooked it up to my computer. it is not playing on my dvd player or the new dvd burner. ????

    Sorry, none of the logs you posted shows a dvd writer attached to your computer. What you seem to have is a combo drive, meaning cd-r/cd-rw writer/reader and dvd reader only.

     

    /****************************************\\

    ; ImgBurn Version 2.4.4.0 - Log

    ; Tuesday, 16 June 2009, 12:50:16

    ; \\****************************************//

    ...

    I 12:41:37 Building Image Tree...

    I 12:42:09 Checking Directory Depth...

    I 12:42:09 Calculating Totals...

    I 12:42:09 Preparing Image...

    I 12:42:09 Checking Path Length...

    I 12:42:09 Contents: 0 Files, 2 Folders

    I 12:42:09 Content Type: DVD Video

    I 12:42:09 File System(s): ISO9660, UDF (1.02)

    I 12:42:09 Volume Label: VIDEO_TS

    I 12:42:09 IFO/BUP 32K Padding: Enabled

    I 12:42:09 Region Code: 1, 2, 3, 4, 5, 6, 7, 8

    I 12:42:09 TV System: NTSC

    I 12:42:09 Size: 0 bytes

    I 12:42:09 Sectors: 0

    I 12:42:09 Image Size: 1,245,184 bytes

    I 12:42:09 Image Sectors: 608

    I 12:42:47 Operation Successfully Completed! - Duration: 00:01:10

    I 12:42:47 Operation Started!

    I 12:42:47 Image Contents: 0 Files, 2 Folders

    I 12:42:47 Image Sectors: 608

    I 12:42:47 Image Size: 1,245,184 bytes

    I 12:42:47 Image Single Layer Profile: DVD-R/RW (Media Capacity: 2,297,888)

    I 12:42:47 Image Volume Identifier: VIDEO_TS

    I 12:42:47 Image Volume Set Identifier: 3AD0653200000257

    I 12:42:47 Image Application Identifier: IMGBURN V2.4.4.0 - THE ULTIMATE IMAGE BURNER!

    I 12:42:47 Image Implementation Identifier: ImgBurn

    I 12:42:47 Image File System(s): ISO9660, UDF (1.02)

    I 12:42:47 Destination File: C:\Documents and Settings\Jessica Haeuptle\My Documents\slideshow.pdm.iso

    I 12:42:47 Destination Free Space: 125,294,534,656 bytes (122,357,944 KB) (119,490 MB) (116 GB)

    I 12:42:47 Destination File System: NTFS

    I 12:42:47 File Splitting: Auto

    I 12:42:55 Writing Image...

    I 12:42:55 Operation Successfully Completed! - Duration: 00:00:07

    This log shows that you successfully created an iso (image) file.

     

    Actually, none of the logs show that you ever burned something to a device, so you may have been putting empty media into your players.

  11. I burned a slideshow dvd to a dvd+r dvd and both my dvd players say "unsupported file" or cannot play this disk. What is the deal, and can I fix it without having to buy a new dvd player? How do I know which dvd players will play burned dvds???

    ; //****************************************\\

    ; ImgBurn Version 2.4.4.0 - Log

    ; Wednesday, 17 June 2009, 20:25:25

    ; \\****************************************//

    ;

    ;

    I 20:25:22 Found 1 DVD-ROM/CD-RW!

    You couldn't have burned your slideshow to a dvd+r disc, since you have a combo drive, which supports writing to cd-r & cd-rw discs only.

  12. Thanks so far.....

     

    I can see the following

    (All 8 files have addition buffers to bring them to 2048 multiples)

     

    Bytes Difference

    Size 3,706,789,888

    Size on disk 3,706,806,272 16,384

     

    System files like TOC and buffering

     

    Image File 3,707,404,288 598,016

     

    Its the System files and buffering bit I want to calculate

    I'm afraid you can't do that. Different file systems need different amounts of data. For example, disc with ISO 9660 only file system will have different size than a disc with UDF file system on it, also, file names are encoded differently, so, without all that data, you won't be able to calculate image size correctly.

     

    Note that "Size on disk" information given by Windows is in multiple of file system's allocation units, which, for NTFS disks, vary in size, but generally are 4096 bytes (4 KB).

     

    Anyway, if you want to do it, you will need to read all the specs about disc layouts and file systems.

  13. Size means size of all the files that you included in the image.

    Image size means size of the image itself, which includes all files + filesystem data structures + rounded to multiple of 2048 bytes, which is the size of the physical sector on cds / dvds.

     

    Btw, in build mode, if you press the button with calculator on it, ImgBurn will tell you what is the minimum required media.

  14. I followed the guide to the letter but only got a bunch of warnings from imgburn that wanted to change things. First it didn't like the ISO9660 + joliet and wanted to change it, I looked back at my nero tutorial and it had ISO9660 + joliet so I ignored that warning only to be warned more near the end with all kinds of irregularities found by imgburn itself so I quit and reinstalled nero just to make my boot cd. I was using the latest version of imgburn and it ticked me off with all its warnings. Between your over simplified tutorial and imgburns refusal to accept it, I got turned off on imgburn as any kind of replacement for anything let alone Nero. Someone needs to update this Tutorial with one that works, or at least tell you when to tell imgburn what it can do with all its changes.

    Use nLite for service pack integration, it will also make an iso image for you.

×
×
  • Create New...

Important Information

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