Jump to content

doxola

Members
  • Posts

    23
  • Joined

  • Last visited

Posts posted by doxola

  1.  

    Forgot to mention the HD containing the source data connected to that machine is an external USB2.0 1TB made by Seagate. So I'm sure that also puts a squeeze on data xfer rate.

     

    Nope. USB2.0 has a much higher transfer rate than a 100 Mbit LAN. You should get at least 20 MB/sec from USB2.0. Your speed is being bottlenecked by the NIC.

     

    I mostly backup the kids' Wii games, so I can't comment on PS3 bluray playback at all.

     

    Having a modchip (which is illegal in some countries), for your Wii would theoretically allow you to attach a very large harddrive to store ISO images of your Wii games (which is illegal in some countries), and then theoretically use something called "USB LOADER" (which is illegal in some countries), to boot images from the attached USB harddrive (which is illegal in some countries). You could also theoretically use "WBFS Manager" (which is illegal in some countries), on your PC to theoretically copy your ISO images to a harddrive....(which is illegal in some countries), theoretically allowing playback without inserting a disk of any sort (which is illegal in some countries). Because this is illegal in some countries, I can't help you in any way regarding Wii backups, (which is illegal in some countries). Theoretically.

     

    Haha! That's why I like your responses...they crack me up, yet are informative at the same time!

     

    Looks like I'll be adding a gigabit NIC to that machine eventually...(plus incorporating the gigabit switch).

     

    Yeah, theoretically I could have a 500 GB Seagate drive connected to the Wii. In theory, all of the games we own could be backed up onto it, using USB Loader. No modchip in the Wii, though. I have contemplated using WBFS Manager 2.5 and 3.0, as well as Wii Backup Manager. I once had an idea that I might be able to back up the wbfs files to BDR, in case the theoretical Wii-connected HD should ever crash.

     

    :shifty:

  2. I burn a lot over the network and can't think of a time when I don't get those warning messages. Burns come out a-ok. Then again, I use mostly Verbatim & TY CDR and DVDR (which is a big +).

     

    AH! That'll be the problem if you're not running gigabit capable hardware. If you're already running gigabit, you have a problem which needs fixing. If you're on a 100Mb connection, it has a realistic throughput of around 8 MB/sec. A DVD trying to burn at 8x requires just over 10 MB/sec - which would cause a buffering problem if the write rate on your burner is set too high. Burning a Bluray at 2x would max the connection speed for a 100Mb network at 9 MB/sec.

     

    Options?

     

    Install gigabit hardware or you could copy the file from your network drive to a local drive before burning or slow your DVD burn to 6x which is just under 8 MB/sec or Bluray burn to 2x. Personally, I'd go for option number 1. A 5-port gigabit switch can be bought these days for around $50.

     

    While I do have a spare 8-port gigabit switch on the shelf, the PC (oldie dual Xeon 2.2GHz) that has the data has a 100MB integrated NIC. I'll look into maybe adding a gigabit NIC one of these days. I usually don't try to burn at the fastest speeds for bluray or regular CD/DVD so maybe that is why I don't have major issues.

     

    Forgot to mention the HD containing the source data connected to that machine is an external USB2.0 1TB made by Seagate. So I'm sure that also puts a squeeze on data xfer rate. Thanks for the additional insight, plus the options.

     

    I have yet to burn BD-DL like the OP. I just know I've seen that warning message a lot, and my burns have not suffered as a result (not that I can tell). I mostly backup the kids' Wii games, so I can't comment on PS3 bluray playback at all.

  3.  

    As I said above, they are *not* errors. This is ImgBurns' way of telling you that your burner is going too fast for the HD to keep up with it.

     

    10 years ago this was called buffer underrun and was a big problem because neither the software nor the hardware was able to deal with it, which meant you got alot of zeros burned to disk which made it unplayable. With newer drives and excellent software like this, it just doesn't matter anymore. It might be a minor irritation to see it in your logfile but it won't affect the quality of your burn.

     

    Excellent explanation. I burn a lot over the network and can't think of a time when I don't get those warning messages. Burns come out a-ok. Then again, I use mostly Verbatim & TY CDR and DVDR (which is a big +).

  4. I, too had a similar issue last night while trying to backup data.

     

    OS=XP

    Microboards 4-bay Bluray Copywiter w/ Pioneer BDR-101A drives

    Sony Accucore BDR-V1.1 2x

     

    Can't really tell if it was media, OS or hardware-related. The burning would start alright, but on 2 occasions stopped at different points during the process. Write rate went to 0.00x and just stayed like that. Had to power cycle the Microboards tower to recover. I was able to successfully burn 2 discs under XP. So, the sequence was 1 good, 1 bad, 1 good, 1 bad.

     

    Now that I think about it, it's probably hardware and/or OS-related, as I successfully burned what I needed to (over the network) on a Win7 machine with dual Matshita SW-5582 B110 units installed, using the same Sony media. I think the computer mode of that particular Microboards tower is a little buggy.

     

    Just posting to show that in my situation, 2 successful burns were achieved in an XP system with multiple Bluray drives (even though I also had 2 failures.) Sticking with burning from Win7 going forward.

  5. This software (or any other software) has no control over the quality of your burn. Bad burns are ALWAYS the fault of the hardware. Imgburn tells your drive what to do. From then it's up to your drive, your firmware and your media to do the job properly. Slow the burn down to 8x and see what happens.

     

     

    Shamus, as much as I love ya, I have to disagree with the 2nd sentence (by itself). Unless I am totally missing something, if one were to start out with bad/poor-quality media, that could result in a bad burn, and every other link in the chain (eg., hardware and software) could be A-OK.

     

    Maybe it was a given that "barring bad media, bad burns are always the fault of the hardware...?" Or, maybe media is included in the hardware "umbrella?" Granted, at some point error correction capabilities of the hardware may play a factor, but I just want to make sure that even if we are in a different classroom, we have the same book.

     

    :)

  6. An alternative would be to purchase/build* a multi-drive dupe tower, if your main goal is to burn to more than one drive at once. Three ways to work that would be:

     

    ..Burn initial disc in ImgBurn, take out, then insert in "master" drive of tower,

     

    ....or (if you have a dupe tower that connects to PC via Firewire or USB--allowing all drives to be seen simultaneously by the OS),

     

    ..Use a different program (something similar to Prassi/RecordNow) and burn to all drives at once,

     

    ....or (if you have a "carousel" duplicator that your PC connects to via a LAN),

     

    ..Use the software that comes with that equipment to send your iso (I don't think you can send anything else) over the network (or use the "batch" mode of the device, which allows you to dupe multiple physical masters at one time)

     

    Yeah, more money, but probably less problems if you are able to achieve what you want to get accomplished.

     

    :)

     

     

    * - would probably be much easier to purchase, rather than build, depending on your level of drive/IO/bus/electrical knowledge.

  7. yeah i think the Laptop drive is not that good at reading the ones i have burned...

    i totally agreed...

    i just realized that the verbs i use were mad in india...

    will try the Singapore ones...

     

     

    Verbatim originating from India is potentially asking for trouble, particularly on CDR and DVD5 (this, I know first-hand). I'd be willing to bet there are quality issues with DVD9, as well.

     

    When LUK stated: "Burn quality comes down to the drive/firmware/media combo. If yours isn't working out, you need to change one of the variables, the easiest of course being the media..." he was not kidding.

     

    :shifty:

  8. FFs bin your crappy dell or change disc's

     

    Anyone else is going to tell you the same. I did not type for the fun of it or to give you misinformation.

     

     

    If you want to be really adventurous crossflash you drive as there is a newer firmware on codekings page

     

     

    oh and buy your games to backup

     

     

    I was waiting for another Heinz-like link...(would have been warranted, I think.) I think all that's been said was all that needed to be said.

     

    :teehee:

  9. I can understand LUK's hesitation to make the project open-source...

     

    ...people would want the project to be ported to the three major OS streams (Mac, PC, Linux)...

     

     

    :thumbup:

     

    I think there are those of us who already use IMGBURN in Windows and Linux (via Wine, even if you have to do some minor tinkering to get it to work). If it's doable in the Mac's native OS, then that might be something else I'll try just to say it could be done.

     

    Great program (can't say that enough--moved me to donate some funds, as I use it quite a bit), and should be author's prerogative as to its direction.

     

    Again, I say :thumbup:

  10. Milx & Keiran,

     

    It looks like such an addition would be more of a hinderance or limitation, from where I sit.

     

    I guess cost is the big issue here. If you're interested in shared burners, they make multi-disc towers (and carousel-type units) that have their own HDs and are able to be connected or shared via the network. Some (carousel-types) have printers attached, and can hold a good deal of blank media for when you get ready to burn. Most have decent proprietary software that does a decent job of handling and queuing burns over the network.

     

    But you may have to shell out a good deal of $ for these... I've used quite a few different models, and I have nothing bad to say about their performance. One good thing was, you can use them from any OS that has a working network connection.

     

    The upside is that all that's usually needed is access to a web browser (unlike NeroNet, where each client machine has to have the full app installed--I read the server app is free if you plan on sharing your burner with 3 or fewer users--will cost if you want to share with more than that). You use a web browser interface in NeroNet, but only after you have installed the full app on the clients and the server app on the machine with the shared recorder. Maybe NeroNet is abandonware, because I had a hard time finding any details about it on the Nero site. (Most of what I read came from here.)

     

    As far as ToastAnywhere goes...not much to say. I don't think it proved to be all that high on people's list of "must-have" features for that app. Apparently you had to have the full app installed on each machine (as with NeroNet), but that could have been problematic if you intended on sharing your burner with a Mac with an OS earlier than Jaguar. I read about this at this site.

     

    ^_^

  11. I have been using ImgBurn with Wine & Feisty Fawn with no noticeable combo-box issues, so maybe they (Ubuntu and/or Wine folks) had made some changes between then and the release of Gutsy.

     

    Then again, I probably haven't used it as extensively as you have, Wild77. The only way I could get mine to work was using WinNT as the OS in Winecfg. I just wanted to be able to burn Blu-ray discs with ImgBurn under Linux.

     

    Just wanted to give a thumbs-up to you and the ImgBurn team for keeping a pulse on the ImgBurn/Wine/Linux combo.

     

    :thumbsup:

  12. When I need to make multiple copies at the same time I use Prassi Ones. I works very reliably, but it will only burn as fast as your slowest drive can burn. I've done 4 at a time with all different drives no problem. Everything else I use Imgburn (except audio cds :) )

     

     

    Prassi/RecordNow Max (as Moondogger & Lightning UK mentioned) work well for simultaneous multiple-drive CD or DVD burns.

     

    :thumbup:

  13. dont know about the recent ones shamus, but the one i had was purely a cd player , with the convenience of not having to change the cd.

    at the time, large hdd's where still expensive ( so was the 200disc player) , but with a large collection of cd's it made more sense for me to have the 200player.( must of been 4-5 years ago now)

     

     

    I think I have the same CD changer. Bought it from a pawn shop about 3 or 4 years ago. I like the sound it makes when the carousel is turning. I never had problems with it and still use it to this day. Other than occasionally forgetting to put discs in with the label side facing the correct way, that's the only trouble I've had (haha, user error). The remote that comes with that thing is huge.

  14. Hi all,

     

    I have problems burning games/backups for my WII.

     

    I work with a Samsung SH-S183A and my DVD's are Samsung Pleomax DVD+R 8x.

     

    I have read that i need to change my booktype into DVD-rom. I did that but i don't think it works.

    And i think that's because he doesn't see my current settings.

    When i change it, it says it's done succesfully but it doesn't stay in this position and when i burn a dvd i don't think it's dvd-rom.

    So ofcourse my WII doesn't take it.

     

    Can you help me?

     

    Thanx!!

    Sabrina

     

    Depending on your starting point, you might encounter more difficulty trying to do what you're doing.

     

    If you are starting with making backups of games you own, you need one of a handful of specific drives to read (properly extract data from) the Wii disc. If you are starting with an image of a Wii game that was created using one of those drives, then ImgBurn (and most other image burning software) will easily do the trick. I'm guessing you're probably starting without such an image to work with.

     

    Additionally, you can run the backups on a modded Wii only, if I'm not mistaken. ImgBurn is doing it's part, but you need more, unfortunately, if you're going to try to dupe/backup a Wii game starting from a Wii retail disc.

     

    About the only other advice I can give is, "Google is your friend."

  15. One more thing...my screen cap wasn't the greatest. I was VNC'd into the machine running Ubuntu, and I couldn't get it to refresh cleanly (apparent by the area above the "About ImgBurn" info window). I was trying to show the "Key Elements," and that was the best I could do when rearranging the windows. Even in the VNC instance, the screen was 90% of the original size, but I think that most can make out what's shown from the capture.

     

    To Keiran: even if you download Ubuntu and find that it doesn't work (as in you can't even burn the distro to CD), you might want to heed the advice of another poster: get a better writer and use better media (I think I saw your specs in another thread in the forum). Not to detract from the ImgBurn software, but even giving a couple more freeware burning apps a shot before making a major purchase couldn't hurt (to paraphrase dontasciime: "Google is your friend.") Maybe an issue specific to your current hardware setup is the source of the problem you are having with ImgBurn.

     

    Honestly, ImgBurn is one of the best apps (freeware or not) that I've used this year. I think it's awesome.

  16. This is a recent Wine problem. They did a patch for another unicode issue a few days (weeks) ago, and now it's broken other stuff.

     

    Take a look at the bugs page at winehq and you can see their progress with the issues.

     

    http://bugs.winehq.org/show_bug.cgi?id=7512

    http://bugs.winehq.org/show_bug.cgi?id=8963

    http://bugs.winehq.org/show_bug.cgi?id=8624

     

    So going by those, they've pretty much all been resolved now. Update to the latest version of Wine perhaps?

     

    I'm using Ubuntu 7.04 (Feisty Fawn) and ImgBurn 2.3.2.0; under WINE it runs like a champ, if you ask me. Granted, you might have to do a little "tweaking" from within winecfg to get your drive(s) properly recognized, but if you can make it past that hurdle, you're in business.

     

    imgburnonubuntu.jpg

×
×
  • Create New...

Important Information

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