Jump to content

Disco Makberto

  • Posts

  • Joined

  • Last visited

Disco Makberto's Achievements

ISF Newbie

ISF Newbie (1/5)

  1. Dear e-group, First of all, happy "Valentine's Day" to all members and readers! Please be so kind to excuse me for not having responded before, but here I am. So, yes, "Lighting UK!", using Build mode solved all problems. Now I can use my "RAMdisk .img" on optical discs via "Dataram RAMdisk" without any issues. Kindest regards, Carlos Albert "Disco Makberto"
  2. I will try that, and I will keep you posted. Carlos Albert "Disco Makberto"
  3. Hi, one more time! After re-checking the disc that I have, I noticed that what PBurn did was to burn the .img file as an .img file. In other words, it didn't burn the contents of the .img file, just the plain .img file. On the other hand, based on what I have noticed, ImgBurn tries to burn the "contents" of an image file, whether we are dealing with an .img file or something like an .iso file. I believe I am correct, aren't it? At any rate, DataRam RAMdisk needs an .img file to mount it, not the contents of an .img file. It is like an .iso mounter such as PowerISO or MagicISO that need an .iso file to mount it, not the contents of the .iso file. About the new little project, if it is still of help, I will do it as soon as possible. But again, the burn is a simple file to file burn. Kindest regards, Carlos Albert "Disco Makberto"
  4. My pleasure, Lighting UK! Just please allow me some extra days as I am dealing with otitis externa with some fever and mild headaches. I think that by next weekend I will be in good spirits to undertake the little project. As for "both files", you mean the original .img image file (the one for the project) and the new ISO created by ImgBurn, am I right? See you soon, Carlos Albert "Disco Makberto"
  5. Great idea, dbminter! I had not thought of that. Yes, it is a little cumbersome, but its one way to deal with it (: Carlos Albert "Disco Makberto"
  6. Not so fast! (; One problem with PBurn is "volume label". When burning files onto an optical disc, the volume label is always "CDROM" whether the files are on CD/DVD/BD. I am not sure why....With ImbBurn, indeed, personalizing volume labels is always a breeze (: Best to all, Carlos Albert "Disco Makberto"
  7. Thanks for the responses! Yes, the RAMdisk .img file created by DataRam RAMdisk is like an HDD image file formatted, for instance, with FAT32. So, indeed, in this case, this is not an optical disc image file. At any rate, Nero uses a similar .img file for optical discs, sometimes called Nero .img file and, since this Nero .img file is a proper optical disc image, it should be compatible with ImgBurn. As dbminter was saying, another member of the .img "family" is the floppy disk image from back in the day. All these images, whether proper optical disc images or not, can be burned onto optical discs using something like PBurn from Puppy Linux. As for mounting, DataRam RAMdisk can mount a RAMdisk .img file. Carlos Albert "Disco Makberto"
  8. Hello, e-group! It seems that there is a problem with ImgBurn, or perhaps there is something wrong somewhere else. I used Dataram RAMdisk to create a RAMdisk drive, added some data to it, and then I saved the RAMdisk drive to my hard drive in the form of an .img image file. The size was 500mb. Then, I tried to burn this .img image file to a DVD+R in my Windows 7 using ImgBurn, but it didn't work. Thinking that there could be something wrong with my Windows 7, I tried to burn this .img image file to a DVD+R in a Windows XP system using ImgBurn again, but it didn't work, one more time. Thus, I decided to use my Puppy Linux and PBurn. To my amusement, the process worked perfectly fine in my Puppy Linux, and the .img image file was burned to a DVD+R. Does anybody know what's going on here? Could it be that ImgBurn is not compatible with a RAMdisk .img image file? Carlos Albert Disco Makberto
  9. LUK, I definitely second pstein. This would be a wonderful addition to ImgBurn. You see, I have had the same experience as him in more than one ocassion. Sometimes, while directly burning files/folders to optical media, filenames are cut. For instance, if I use relatively long filenames, and I forget to include the Joliet extension (or UDF) or, in other words, if I erroneously use just plain ISO9660, filenames are cut. And the worse part of this is that I become aware of it only after the optical media is burned. Cheers, Carlos Albert Disco Makberto
  10. Hi, LUK & e-readers! I am confused about something. I understand that the Joliet filesystem is an extension of the ISO9660 filesystem, and as such, it ought to have a directory depth limit of 8 levels since the ISO9660 filesytem has a directory depth limit of 8 levels. I think that ImgBurn works this way. However, some people claim that this is not applicable when the Joliet extension is used. If you go to: http://www.controlledvocabulary.com/imagedatabases/filename_limits.html , you can read: "note that ISO 9660 has an explicit directory tree depth limit of 8, although this depth limit is removed when using the Joliet extensions." Even Microsoft has something to say at: http://support.microsoft.com/kb/125630 . There, when Joliet is compared to ISO9660, you can read that Joliet "is designed to resolve some of its restrictions and ambiguities including:"..."Directory Tree Depth limitations." I understand that this limitation can be unofficially broken, but why are these people implying that this possiblity of breaking it is an official position? As a matter of fact, what is the official position? If it is possible to have more than 8 levels, what is the maximim that can be had (within compliance)? Regards, Carlos Albert Disco Makberto
  11. RicHieRich, One thing that you can do is to extract the ISO, let's say to your hard drive, and then copy or cut/paste the resulting files and/or folders to your micro SD card. As for the extraction, probably PeaZip can do this. Now, if your ISO is bootable, that is another thing. If so, you would also need to extract the boot info from the ISO and find a way to inject it into your SD card (each uses different boot parameters). To achieve this, perhaps either ISOtoUSB or ISO2USB (different applications) can help. Best of luck, Carlos Albert Disco Makberto
  12. Hello, LUK! Thanks for your new message. Please excuse me if I misguided you. It was not my intention at all. The ISO I have (as it pertains to my Linux OS discussed here) is not on a disc, but on an external hard drive. I downloaded it from the Internet from the author's Website. Of course, it is possible to buy it on disc or even on a memory card (I think) via alternative vendors. This OS has a mechanism to save to itself on disc (after burning the ISO, of course). However, if the resulting disc is not left open to continue with subsequent burnings, then of course it won't be possible to save a customized new session on disc. Since I was confused about the terms "multisession ISO" (or "multi-session ISO"), I thought that what I downloaded was indeed a "multisession ISO" (or "multi-session ISO"). Now thanks to your prime help, I understand that what I downloaded was a "regular ISO". It is the burner that creates a multisession on disc. Nobody created a "pre-existing multisession ISO" as my title implies because, as you are explaining, such a thing doesn't exist. Conclusively, my title is misleading and confusing. I agree. Hence, if you have any other questions to expand on the issue, it would be my pleasure to try to answer them. All the very best, Carlos Albert D-Mak P.S.: If I am permitted to say this, the Linux OS I am talking about is Puppy Linux.
  13. Hey, LUK! Thank you kindly for clarifying the issue to me. If you search under Google (or any other search engine) for the terms "multisession ISO" (or "multi-session ISO"), you will get many references for those terms, and some even coming from burner tools. That is the origin of my confusion. You see, I don't undertand why those people use the terms "multisession ISO" (or "multi-session ISO") if such a thing doesn't exist. Strange!.... As for what I have as ISO, it is a Linux OS that saves to itself on disc after the user customizes it. This is done via multisession burning. In closing, thank you again for your invaluable help! Thumbs up, Carlos Albert D-Mak
  14. Dear LUK, Thank you for your fast response, but I think there is a misunderstanding, or perhaps I didn't express myself correctly (please excuse me if that is the case). Please let me explain myself furtherly. For the purposes of this task, I don't have any already-recorded CD/DVD, and I am not interested in making or creating any ISO. What I have is a pre-existing ISO (which I got via online means), and this pre-existing ISO is a multisession ISO. My question is, if I use this multisession ISO with ImgBurn to create (that is, to extract and burn the contents of this multisession ISO into) a CD/DVD, is this CD/DVD a mutisession disc (based on the fact that the initial ISO is a multisession ISO)? Additionally, so as to express myself better, please note that I am talking about one burning task done one time; I know that if I want to add more files to the resulting disc (if it is multisession), I would need to use something different than ImgBurn. Take care, Carlos Albert D-Mak
  15. Dear readers, Greetings to LUK and all community members! If I understand correctly, ImgBurn doesn't support multissesion burning as in incremental burnings with successive burnings. However, let's say that I have a data multisession ISO created with a different application. If I burn this data multisession ISO to CD/DVD using ImgBurn, is the resulting CD/DVD a multissession disc? I know that if I need to add something to the resulting multisession disc (assuming that is what is created), I would still need to use something different than ImgBurn. However, what I am addressing here is the first burning via ImgBurn using the pre-existing data multisession ISO. Best, Carlos Albert D-Mak
  • Create New...

Important Information

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