Handler

That's pretty much how I do it :D Regards Candles lit: Check Soft music playing in background: Check Rose Petals on bed: Check Clothes off (socks optional): Check Female present: Damn it Talk about being in Safe mode and having the drive emptied.

The actual DS3 external enclosure specs say drive "capacities up to 750GB". I don't know what would happen if you stuck a 1TB drive in there, but if you decide to proceed then let us know how it went. With the exception of a couple brick and mortar stores, I do most of my tech purchases at NewEgg. It's not as if I haven't heard of eBay, that should tell you something. Attempting to be topical, like Taiyo Yuden and Verbatim discs these days there are only two brands of hard drives I would consider purchasing, Seagate and Western Digital. The last time I was looking for a new hard drive I did consider Seagate, but at the end I went with another Western Digital drive. My main reason for staying with Western Digital was tradition. I've always used Western Digitals in all my PCs and I know they work. IMO, stay away from Maxtor. This reminds me, because you would be placing the drive inside a DS3 you do not need to purchase a retail box, a static bagged OEM will work fine and you can save a few dollars. I hate when pictures poop up. Seriously, you don't need the USB 2.0 driver disc since USB support is already built into WinME and above. The disc is provided by a third party company so that USB 2.0 drivers can be installed on Win98se.

Please don't take my word for it. I recommend that you use Google to get other opinions about Iomega products. I do most of my tech purchases at NewEgg. All you have to do is loosen the two screws on the back of the DS3 and pull out the insert from the case. Place the hard drive on top of the insert so that both interfaces are facing each other. If it looks like it's going to bind when they slide together, loosen the screw in the hole of the power connector, adjust the power connector slightly, tighten the power connector screw and then push the two interfaces together. Make sure that they don't go together crooked and that they are firmly seated to one another. While holding the insert and the hard drive together tight like a sandwich, carefully flip it over and align the two holes on each edge of the hard drive with the four holes in the insert. With the provided screws, screw the hard drive to the insert. Make sure not to cross thread or over tighten the screws. Flip the insert over and slide it back into the case and tighten the two screws on the back. Again, making sure not to cross thread or over tighten the screws. The last thing to do is make sure the power switch on the back is in the off position and you're done with assembly. Plug the power supply into an available AC socket, plug the other end into the back of the DS3. Connect one end of the USB cable to the back of the DS3 and the other into an available USB port on the computer. With windows booted, flip the power switch on the back of the DS3. After a few moments the new hardware will be recognized. Go to Computer Management and do a Full format, then create a primary drive with a single partition[1]. When that completes and if I haven't forgotten anything, you should be ready to Rock-n-Roll. If you leave the USB cable connected, as well as the in-line power supply connected, all you have to do is flip the power switch on the back and within moments the drive is available. When you're finished with it, flip the power switch back to off and it goes away. Each signaled with a mount and unmount system chime (respectively). If you want you can also assign a permanent drive letter so that each time the hard drive is mounted it will always be the same letter. [1] For the purists out there who might be reading this, yes I know that technically it's not a single partition, but I found often it's easier to explain it as a single partition. The ones I have can be found HERE, although if you want one with USB and Firewire then you would probably want this one HERE. I can't answer the camcorder question. I'd also like to add that the ones I have work great. They were purchased at different times and I haven't noticed any production issues. Having said that, it's best to always be prepared and I recommend that you read the reviews before making any decisions one way or the other. USB is USB, even for Vista. You're welcome and good luck.

Anything Iomega should be taken with great apprehension. Particularly after the Click-Of-Death issue and the way the company handled the situation. Normally you would power off the external enclosure first, after Windows signals, then unplug the USB cable. But just as important, make sure all activity has stopped. A replacement cable would usually consist of a USB v2.0 Type-A Male to Type-B Male. Only you know for sure. USB cables are quite common. Typically the front USB ports are connected to the motherboard with a cable no more than 2 feet in length. Compared to the rear USB ports which are usually attached directly to the motherboard. Normally, there should be no difference between the two sets, but if you are constantly plugging and unplugging USB devices either can start to wear out. That's why it's important to try a different USB port. For that matter, that hard drive inside that enclosure should have been pulled out of there by now and tested on an empty or temporarily made empty, IDE controller inside your PC. It's a waste of time otherwise if it turns out the hard drive is dying or dead. If you see everything, then that would be a good time to make a backup, just in case. If you're looking for a new external enclosure and hard drive, I've had very good results with the Venus DS3 and 750GB Westerns. YMMV. They need to be purchased separately, but installation of the hard drive is very easy. The enclosure allows for you to set the correct physical separation between the IDE interface and the power connector as not all hard drives have the same spacing. Good luck.

I too have Registry Mechanic installed. Two things I've found with any reported Registry cleaner type program is that, one, you can't just hit the 'Clean' button. You have to methodically go through every thing that is returned, even if there are hundreds of returns and choose wisely whether to keep it or delete it. Two, there is little benefit returned from cleaning the Registry and maybe hardly worth the time and potential problems doing so. Also, Sonic use to have good software back in the v4.5 days (v7.2 something wasn't too bad) and I've never liked Raxio, or for that matter Nero. All three currently suffer from extreme bloat as they pretend to be everything, for everyone. I avoid them like the plague.

Obviously this won't help the BD users, but I'm sill using v3.47 of Daemon Tools because I want to avoid all the problems that have been associated with the inclusion of Adware in their software.

Hi, Yes, the creation of the ISO first, then creating the PAR2 files from the mounted image and then copying the newly created PAR2 files back to the source Title Set in the form of a EXTRAS directory would definitely be the way to go since no matter how many times the ISO is created, the IFO/BUP files should always be adjusted identically. To give you an idea how long it's taken me to burn my first Dual Layer disc, the Singapore made Verbatim DVD+R DL (MKM-001-00) discs were purchased in I believe 2006 (box says 2005 on the back). Big thanks to LIGHTNING UK and blutach for all your time on this subject. Hopefully this thread will continue to help others who are trying to do the same thing. Thanks

Both discs, the one you started with and the one you later purchased at Circuit City, are both DVD5 discs. Recording times/modes such as 2 Hrs/SP and 6 Hrs/EP that are printed on the package are used to give an idea of time vs quality when the disc is used in such devices as a DVD Recorder (a STB type of device which can be directly hooked up to a cable box or satellite receiver which records the analog out to DVD). In other words, a DVD5 is a DVD5 and by changing the Bit-Rate quality (SP or EP) from the DVD Recorder's menu do those times become important. So, the recording time on the DVD package is irrelevant for what you are doing. You have a Title Set which is 7,338,014,720 bytes (6.83 GB) and both of your DVD-R media have a maximum capacity of 4,707,319,808 bytes (4.38 GB). So, something else has to change. You could re-encode the Title Set. You could remove items which are expendable from the Title Set. You could purchase DVD9 media which has a maximum capacity of 8,547,991,552 bytes (7.96 GB). Each of these have their own pros and cons. For example, re-encoding the Title Set and/or removing expendable items can be a time consuming venture, but, with the right software you can get your project to fit onto a single DVD5. Using DVD9 media or Verbatim DVD+R Dual Layer disc (#95166) is more expensive and requires a burner with +R Dual Layer burning capability, but you don't have to re-encode and/or remove expendable items to "shrink" it to fit. How you proceed from here is up to you. Good luck.

Just to clarify, IFOEdit did say "Corrected sector addresses in table [VMG_PPT_SRPT ]" and there were ten of those. Followed by three "Corrected sector addresses in table [VMGI_MAT]. Whether it was right or wrong of IFOEdit, IFOEdit found those sector "addresses" to be in "error". I used a slightly, but already explained, shorting of the terminology that IFOEdit used so that others would know, if they are familar with IFOEdit, what I was referencing. That makes sense. Unfortunately, that also suggests that there is no way to add PAR2 files to an EXTRAS directory on a Dual Layer disc without them immediately finding a checksum error as soon as the disc is burned. #39;( <sniff> Is there anyway to add PAR2 files to a Dual Layer disc without that happening? Yes. Got it. No. I have never had a DL disc not play properly. Stop worrying. Quid, Me Vexari? To tell you the truth, money is very tight and these Dual Layer discs are not cheep. I'm use to working on Single Layer discs, because Dual Layer discs are so different, I just wanted to do everything I could to avoid burning my first Dual Layer coaster, on my first Dual Layer burn.

Presuming that the Title Set was created and the disc was burned correctly; IF as you say above that your VIDEO_TS folder contains inside it yet another VIDEO_TS folder (which actually has the DVD files), then it's a file structure issue. From the root (top level) of the disc the VIDEO_TS should contain only the DVD files and nothing else. I don't know your purpose of keeping all those other files, but they have nothing to do with the actual DVD playing. IF you place the disc back into the PC's burner and look at the contents of the disc with Explorer, a typical DVD would only have an empty AUDIO_TS folder (for backward compatibility) and a VIDEO_TS folder (in this case containing your 8 files - total 3.57 GB) and nothing else. I would say that fixing the file structure would be one place to begin. To fix the file structure you have to be careful which files/folders you pick when you are adding files/folders to ImgBurn as it doesn't really give you a good idea of the layout of the disc prior. What I would do is switch to "Image file output" instead of directly burning to the media. Create an image, mount it, and look see what's there. If I liked what I see (file structure wise), then I'd toggle the creation type back to "Device output" and burn away. Hope this helps and good luck.

Hi, I don't have any experience with Dual Layer, only Single Layer discs. Using programs such as CDCheck (which also works with DVDs), I've never seen a Single Layer disc that didn't match exactly byte for byte unless the burn wasn't 100 percent successful. A DVD for the most part is just a data burn. So having discs not identical to their source files is new for me and I suppose it must be something specific to Dual Layer discs. However, it throws a monkey wrench into using PAR2 files as a means of securing future data integrity. At least the VOB files are identical. As a result of ImgBurn having to "correct certain pointers" "due to the layout and positioning of the files", IFOEdit is now reporting ~13 address errors. Is it possible that ImgBurn isn't doing a comprehensive job of correcting all the necessary pointer changes prior to the creation of the image? Thanks.

Wow! That was exactly what was needed to get the Title Set to load at the beginning. Thank you. I went ahead and created another test.ISO and while everything directory structure wise is correct, the CRC value of several, not all, of the IFO files are no longer identical to the originals. This is quite puzzling considering that the main purpose of the EXTRAS directory is to store PAR2 files should the disc become unreadable in the future. The files that do not match the originals do not show a different modification date or time. This occurrence has absolutely nothing what so ever to do with the EXTRAS directory. On the second test2.ISO I completely eliminated the EXTRAS directory and once again several of the IFO files had been internally modified. I should point out that the VTS_01_0.IFO file in the Title Set already included a Layer Break. When creating the test ISO I load the Title Set and the Layer Break window opens. Not sure why it's necessary to make the same Layer Break selection twice, but each time that the Layer Break window opens I select the same 'gold' Layer Break position that is already present in the IFO file (VTS_01, PGC: 1, Chapter: 13, Cell: 14). After the EXTRAS-less test2.ISO was created, I then use DT to mount the image. Using a binary comparing program, it shows that out of the eight IFO files, four of them are different (ie: VIDEO_TS.IFO, VTS_03_0.IFO, VTS_05_0.IFO and VTS_08_0.IFO). Loading the mounted test2.ISO VIDEO_TS.IFO file into IFOEdit results in 10 errors in the VMG_PPT_SRPT sector addresses table in 04, 05, 06, 07 and 08. Also IFOEdit tried to correct VMGI_MAT sector addresses in 03, 05, and 08. None of these errors are present in the original Title Set when loaded into IFOEdit. I don't know what this all means, but from my stand point, I would think that since the Title Set is now being added to the start of the disc and the Title Set's own Layer Break is being used, that the test2.ISO files should be identical to the original files. Can someone please explain why there are so many differences and why these differences result in many errors in the Title Set's structure? Thank you ever so much.

Hi, I did search, but couldn't find what I was looking for. I've always included an EXTRAS directory with the VIDEO_TS and AUDIO_TS directories in the root of a single layer disc. Up until now I've not had a problem but that was single layer, and when I tried to do the same thing with my first dual layer disc I ran into a Layer Break problem. As near as I can figure, the contents of the AUDIO_TS directory (empty) and the EXTRAS directory (100 MBytes) gets added alphabetically, followed by the VIDEO_TS directory and that seems to throw off the Layer Break by pushing it further into the disc. If I move the EXTRAS directory out, then add just the AUDIO_TS and VIDEO_TS directories then I'm presented with the Layer Break window, otherwise I get 'The End of The World' problem with the addition of the EXTRAS directory. I tried to add just the AUDIO_TS and VIDEO_TS directories first, then after picking a Layer Break cell, add the EXTRAS directory. The hope there was to get the EXTRAS directory to be burned on the remaining free area of the second layer, after the Title Set. But that seems to run into directory structure issues with the Test.ISO I've created placing the VIDEO_TS in a child directory off root and that's no good. Is it possible, and if so, could someone please explain how one goes about adding an additional directory to a Title Set with Dual Layer media (in this case Verbatim MKM-001-00 DVD+R DL) and the latest version of ImgBurn? Thanks.

Understood and thanks.

Perhaps a better way would be to say that a machine with only 2GB of RAM installed isn't enough for two 512MB buffers. After rebooting the machine there was over 1.6GB of RAM free available. Yet, testing ImgBurn again with the two 512MB buffers still caused the errors to happen. So apparently 1.6GB of free RAM isn't enough for 1GB total buffer space. Leaving the I/O Buffer at 512MB and slowly dropping the Build Buffer down 25MB at a time, there were finally no errors at 425MB. So apparently 1.6GB of free RAM will work with 937MB of buffered space. BTW, by not getting the errors I see the log showing "Filling Buffer... (512 MB)", so now it's clear which buffer that line in the log has been referring to. I presume this is the Build Buffer. I presume this is the I/O Buffer. I presume I now have that with the I/O Buffer at 512MB and the Build Buffer at 425MB. Because the hard drive can be a bottleneck at times and RAM is faster. By moving more data into RAM before burning start frees the hard drive and insures a better constant fill of the drive buffer. Maybe we both should for different reasons; seeing as how the error dialog said ImgBurn in the title and it appeared as though Microsoft was blaming ImgBurn. Seriously, thank you for your reply. I still don't understand why so much free RAM can be available and yet it can't be utilized. Even with the I/O Buffer at 512MB and the Build Buffer at 425MB, the system still had 600MB free. Odd. My next puzzlement is when a CD-RW burn is canceled and ImgBurn saying "Synchronizing Cache..." for 45 minutes and ultimately having to reboot the system in order to kill off the task. Which can only be equivalently described as the laborious task of stripping paint off a intricately turned table leg, layer by layer, with a toothpick, until the system finally reboots itself. But, I'll have to save that for another time after doing more tests. Thanks for your time. Edit: Winky emoticon doesn't work.

Hi, First and foremost I would like to thank the Devs for such a wonderful program. Secondly, I've searched the forums using FIFO, Buffer, VirtualAllco and many other keywords, and I couldn't find what I was looking for. Thirdly, I only use the "Writing files/folders to disc" mode. Finally, the problem happens just after the directory calculation finishes, but before any data is burnt to disc and there are no error messages logged, only error dialogs appear. I saw the change log for v2.4.2.0 and noticed that the "Max buffer size is now 512MB". Every once in a while I've watched the buffer get low, so I decided to try upping the buffer from 256MB to 512MB. First I changed the Build-Read Buffer Size from 256MB to 512MB, but the log still showed "Filling Buffer... (256 MB)". Thinking I needed to change the I/O-Buffer Size, I also changed it from 256MB to 512MB and that's when a problem occurred. After loading a directory, err, folder, I clicked the "Build" button and ImgBurn tells me that I've "only selected 1 folder" and whether this folder "represents the root directory for the image content". To which I click the "Yes" button. ImgBurn now does a calculation and displays a summary to which I click the "OK" button. That's when I get the following pair of ImgBurn error dialogs. First ImgBurn error dialog: "VirtualAllco Failed! Reason: Not enough storage is available to process this command." Click "OK", then a second ImgBurn error dialog immediately appears: "Failed to initialise<sic> FIFO Buffer (536,870,912 bytes)" Click "OK" and were back to the "Writing files/folders to disc" view. The system is running WinXP SP2 with 2GB of memory and at the time of the error there was just over 1Gb free. As to storage, there are over 70 de-fragged GigaBytes free on the DMA mode running hard drive. So, what I don't understand and maybe someone could please clarify this for me: 1) Why does it say "Filling Buffer... (256MB)" in the log when the Build Buffer is set to 512MB? 2) When changing the I/O Buffer to 512MB why do I get the above pair of errors every time? 3) What is the difference between the Build Buffer and the I/O Buffer, and which one is more important (to increase)? Final observations, when I set the I/O Buffer back to 256MB from 512MB I still get the same pair of errors mentioned above when clicking the "Build" button. It is not until I close and re-open ImgBurn does the errors stop appearing. Also taking this one step further, it does not help to set the I/O Buffer to 512MB and then close and re-open ImgBurn. Restarting ImgBurn only seems to fix the problem going back to a I/O Buffer of 256MB and not when trying to increase it. lastly, there are no error dialogs when toggling to "Image File Output" mode and then pressing the "Build" button. Thanks for your time.