Jump to content


  • Posts

  • Joined

  • Last visited

Everything 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. CDBurnerXP supports simple disc spanning.
  3. 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. Does the line in the status bar say "Device Not Ready (Medium Not Present)"?
  5. 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. What do you mean? UDF support or packet writing support? ImgBurn supports UDF filesystem, but ImgBurn is not packet writing software like InCD.
  7. Frankenstien, try WinCDEmu, maybe it won't cause BSODs, also, try disabling anti-virus software, sometimes it causes conflicts.
  8. 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.
  9. 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.
  10. 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
  11. There is a FAQ describing what casuses this problem, and how to cure it.
  12. 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. 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.
  13. 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.
  14. 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.
  15. 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.
  16. Use nLite for service pack integration, it will also make an iso image for you.
  17. 1. Guide to writing image files with ImgBurn. 2. .iso 3. Yes.
  18. Try Verbatim media.
  19. Writing speed depends on media, drive model and firmware revision. It seems that your drive minimum supported writing speed for that media is 4x. If it verifies ok, I would not worry about disc being written faster than selected.
  20. ImgBurn does not install any drivers, so it can not screw things up.
  21. No, it is not a bad sector on the original HDD, it seems that media (disc) has failed.
  22. What you're talking about is called simple disc spanning.
  • Create New...

Important Information

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