Jump to content

Ken852

Members
  • Content Count

    82
  • Joined

  • Last visited

About Ken852

  • Rank
    ISF Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. As I recently started working with DVD Decrypter for my DVD video discs I discovered that it uses capital letters for file name extensions, like in the example below. The New World.ISO The New World.MDS I was wondering if I may change this afterwards without breaking the file name reference? I don't know about other programs, but ImgBurn seems to accept it regardless. I like my extensions all in lower case, so ".iso" rather than ".ISO" and so on. Looking at the MDS file in a hex editor I can see a reference to the original ISO file at the end: The New World.ISO I have manually edited this to say: The New World.iso Do I have to repeat this for all such files? Will these files otherwise fail to load in other programs that use MDS files? Looking at the files I created previously using ImgBurn, I can see that asterisk is used in place of the file name prefix ("The New World") and the suffix or file name extension ("iso") is in lower case. For example, here are my files from the first disc of Ask Video tutorial series on Cubase SX. Ask Video Cubase SX3 Level 1 Tutorial.iso Ask Video Cubase SX3 Level 1 Tutorial.mds The MDS file contains: *.iso Rather than: Ask Video Cubase SX3 Level 1 Tutorial.iso I take it this part is not important then?
  2. Ken852

    Enable remote SPTI access

    Reinstalling ImgBurn worked like a charm, and I did not lose any of my settings as far as I can tell. Thank you!
  3. Ken852

    Enable remote SPTI access

    This seems to be related to admin rights? Running without admin rights: I 10:39:16 ImgBurn Version 2.5.8.0 started! I 10:39:16 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200) I 10:39:16 Total Physical Memory: 16,688,180 KiB - Available: 13,333,732 KiB I 10:39:16 Initialising SPTI... I 10:39:16 Searching for SCSI / ATAPI devices... E 10:39:18 CreateFile Failed! - Device: '\\?\scsi#cdrom&ven_elby&prod_clonedrive#1&2afd7d61&0&000000#{53f56308-b6bf-11d0-94f2-00a0c91efb8b}' (D:) E 10:39:18 Reason: Access is denied. E 10:39:20 CreateFile Failed! - Device: '\\?\scsi#cdrom&ven_tsstcorp&prod_cddvdw_sh-224db#5&df55e28&0&040000#{53f56308-b6bf-11d0-94f2-00a0c91efb8b}' (E:) E 10:39:20 Reason: Access is denied. W 10:39:20 Errors were encountered when trying to access 2 drives. W 10:39:20 These drives will not be visible in the program. E 10:39:20 You need Administrative privileges to use SPTI. Running with admin rights: I 10:40:26 ImgBurn Version 2.5.8.0 started! I 10:40:26 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200) I 10:40:26 Total Physical Memory: 16,688,180 KiB - Available: 13,320,744 KiB I 10:40:26 Initialising SPTI... I 10:40:26 Searching for SCSI / ATAPI devices... I 10:40:26 -> Drive 1 - Info: ELBY CLONEDRIVE 1.4 (D:) (SCSI) I 10:40:26 -> Drive 2 - Info: TSSTcorp CDDVDW SH-224DB SB00 (E:) (SATA) I 10:40:26 Found 1 DVD±RW/RAM and 1 BD-ROM/HD DVD-ROM! I will try reinstalling ImgBurn...
  4. Thanks for clarifying LUK. Another option would be to disable a few options. On the Registry tab in DVD Decrypter settings, you can remove the following checkboxes. Under "Shell Extensions": "AutoPlay (XP / Server 2003)" "DVD (Me / 2000 / XP Server 2003)" Under "File Associations": CDR, DVD, IMG, ISO, MDS All of these are enabled by default, and disabling all of them will prevent DVD Decrypter from attempting to write to the Windows Registry. This is a tip that @dbminter shared with me in a PM and it worked wonders. Thanks to both of you!
  5. I just recently noticed the option "Enable SPTI access in Remote Sessions" as I was installing ImgBurn in a VM. I also noticed that it's not enabled by default during installation. This may explain a problem I was running into previously as I was trying to access my PC using Remote Desktop from another PC. I was trying to do this because my main PC does not have any optical drive. But ImgBurn logged some error or warning, I don't remember now. Do I have to reinstall ImgBurn to enable this? Will I lose my current settings?
  6. Ken852

    Two instances of ImgBurn running?

    Maybe that's where the authors of Wikipedia got their idea from? The limitation they are describing? But then the duplicator would have to run some kind of Windows? It's needless to say, but being able to instantiate ImgBurn makes it very powerful and flexible. And of course, you are not going to be burning more than one disc at a time per drive. Also, you will probably not want to do things that could affect the overall performance like burning a disc from an ISO file while at the same time reading that same ISO file in a second instance of ImgBurn and burning it to a second drive.
  7. Ken852

    Two instances of ImgBurn running?

    A duplicator? Is that one of those tall tower machines that cost $$$$ and have several trays for discs, with little monochrome LCD displays at the top? That word "session" is confusing me. Is that the same as to say "instance"? In all fairness, I don't think you can compare one of those expensive duplicator machines to ImgBurn. Because ImgBurn runs on a much more powerful platform where you can install almost any number of drives, and with the ability to instantiate ImgBurn, that's like having 1 to 1 duplicators times 10 (that's 10 small duplicators, with each cloning only 1 disc to 1 drive at a time). You can build this at a fraction of the cost for a massive duplicator machine.
  8. I haven't used DVD Decrypter much, almost not at all. I never had a need for it, not until now. I wouldn't know how to check to see whether a disc has Macrovision protection on it or not. Also, each time I exit out of DVD Decrypter it prints out the following error messages. After I click to close the program it displays the first message 1 time, followed by the second message 1 time, followed by first message 6 times. I don't know what it's blabbing about, but none of this seems to affect the quality of the ISO files it produces. It's just annoying. I suspect the number of times it displays the first message has to do with the number of drives in the system (I have a few mounted network drives here). Also, the same messages will appear if I run DVD Decrypter in a VM with Windows 7, but not in a VM with Windows XP. So any Windows version above Windows XP will produce these errors on exit, but it does not seem to affect the image quality, as they are identical to those made with ImgBurn (given the right amount of tweaking the settings). I must say, it's quite impressive to see such an old program still doing quite well on a modern operating system.
  9. I thought so too. But the disc I'm using for testing ("The Others" original from 2001) does not appear to have any sort of copyright protection. ImgBurn for example does not complain about "CSS/CPPM" when I insert the disc, like it does with the other discs when I insert those. The only kind of restriction it does have is Region 2 restriction, as far as I can tell. There is the option "Remove Macrovision Protection" under the General tab in DVD Decrypter. It's ON by default, and turning that OFF has no effect on the ISO file I get. Presumably because there is no Macrovision to remove. As long as DVD Decrypter detects the region code of the disc correctly (Region 2), settings can be left on default with exception for "Remove IFO RC Protection" which needs to be OFF, the ISO file will be identical to that made in ImgBurn. And to detect the region code correctly, Any DVD needs to be either uninstalled, inactivated or at very least its "Software Region Code" option needs to be set to OFF.
  10. Testing is done and the results are in. Assuming that 7135BF384C5E666AAE6873EB3FF33D98 is the hash value for unchanged image (as made by ImgBurn), then the same can be had with Any DVD by disabling the removal of following features in Video DVD - Settings. Software Region Code Hardware Region Code Region Code Scripts Analog Protection System Prohibited User Operations PC-Friendly Copy Protection based on unreadable Sectors All of these are enabled by default in Any DVD, which results in BF6B0935CBC9D13FA8C6523A34F8B123 value when imaging the disc using either one of the two programs, Any DVD or DVD Decrypter. In other words, Any DVD interferes with operation of DVD Decrypter. Same results can be had with DVD Decrypter. It changes what is in fact a "Region 2" disc and makes DVD Decrypter detect it as a "Region 1, 2, 3, 4, 5, 6, 7, 8" (any region) disc. See screenshots of DVD Decrypter below for comparison. In the screenshots above, you are looking at the images made by ImgBurn as they appear in DVD Decrypter when attached to a virtual drive (Virtual CloneDrive), with Any DVD inactive (first screenshot) vs. Any DVD active in the background (second screenshot). I have used a virtual drive to speed up the reading and testing process. So one way to get around this and to get the same results with DVD Decrypter is to simply inactivate or exit out of Any DVD when using DVD Decrypter. In addition, to get the same hash value as with Any DVD, you have to disable the option "Remove IFO RC Protection" in DVD Decrypter. This has made me wonder, what does " Remove IFO RC Protection" do? It's not enough to just inactivate Any DVD. You only do that to make DVD Decrypter detect the disc properly as a Region 2 disc which it is. But you also have to disable this "Remove IFO RC Protection" option, or in other words you have to NOT remove IFO RC Protection. That way you will get 7135BF384C5E666AAE6873EB3FF33D98 value, same as with ImgBurn. Any DVD is somehow able to simulate as if the inserted disc is an all region disc. It appears to be triggered by the Software Region Code option. DVD Decrypter doesn't seem to have any such option. To get BF6B0935CBC9D13FA8C6523A34F8B123 (touched) Using Any DVD: Default settings (simulates Region 1, 2, 3, 4, 5, 6, 7, 8) Using DVD Decrypter: Default settings (Remove IFO RC Protection: ON) Any DVD active (simulates Region 1, 2, 3, 4, 5, 6, 7, 8) To get 7135BF384C5E666AAE6873EB3FF33D98 (untouched) Using Any DVD: Remove DVD Video features: none selected Using DVD Decrypter: Remove IFO RC Protection: OFF Any DVD inactive (Region 2) OR active but no DVD Video feature removed (Failure to turn Remove IFO RC Protection OFF results in hash 03BAB370EB2D46CE327E0D7C092D756B, as opposed to BF6B0935CBC9D13FA8C6523A34F8B123.)
  11. No need to @daysinnfan52 I already have the files here on my computer. This reminds me of other popular programs, like Winamp and its famous startup sound! Adding sounds was quite common at the time to spruce up a program. It's no surprise. In fact, this was the prime time of the "Multimedia PC". So what better way to make use of on-board sound cards and monitors with built-in speakers than to introduce sounds in just about every program you can think of. This still does not answer the main question, where did the ImgBurn "success" and "error" sound clips come from? Since DVD Decrypter pre-dates ImgBurn, I think it's safe to assume that DVD Decrypter had these sounds first. But then how did they end up in DVD Decrypter? It's unlikely we will ever learn this. Not if LUK doesn't remember. A lot of these sound clips were floating around on the Internet. I remember downloading sound packages for Windows for example. I used P2P programs like Kazaa and Napster for that. And if I found some fun sound clips in a given program, I would extract it and add it to my own collection. In fact, I think I still have that somewhere in my archives. I also very much enjoyed extracting chip tunes from key generators and other obscure programs I encountered.
  12. A cloning program? You mean copying from one disc to another on the fly, without imaging to hard drive first? You wrote "I'm burning some PS1 Isos to CD-R" so I assumed you meant proper ISO files. Thank you for clarifying! And if I understand correctly, we can see that by the offset number 2076 and 2254. Those are relative offsets for the problem sectors. However, as it turned out, he has in fact BIN/CUE files and not ISO files. So if he has imaged the games to BIN/CUE then he would have the raw 2352 byte CD sectors, right? OK, so as far as I understand this @Chem the problem arises from writing what is essentially a raw CD image of the game (2352 byte sectors) in a write mode that expects something else (2048 byte sectors presumably). The raw image contains 304 bytes more per sector than the optical drive is anticipating so to speak. This is mainly error correction data that was copied over from the original disc when it was imaged or created. If I understand correctly, given the write modes that ImgBurn supports (SAO, TAO and Incremental), the drive must write its own error correction when you write or burn a new disc. So when the drive receives such data (2048 byte + 304 byte), it eats the flesh of the apple (2048 byte) so to speak and throws away the core (304 byte) because it makes up its own as it goes, for each sector. Then, when you do the verification at the end of the writing process, it compares each of the 2352 byte sectors on disc to each of the 2352 byte sectors in the image file. The first 2048 byte of each sector on disc and in the image file will match assuming the write operation went well, but as for the remaining 304 bytes, it's a lottery! The numbers on the disc will disagree with the numbers in the image file, in the offset range above 2048. You can see evidence of this by reading the log and the part where it says "Offset: 2342" for example. Each of these reported mismatches are to be between 2048 and 2352. If they are at 2048 or below, then you may have a proper problem. Sorry for the lengthy reply. I'm no expert at this, but that's the lesson I'm taking away from all of this. Also, I think this message may be misleading. The mismatch happens not because L-EC is wrong in the image file, most likely not. But because the drive has written its own L-EC, because it could not write it to disc, given the available write modes. So there are 2 solutions to this. Solution 1: Ignore these mismatches if they are above offset 2048. Solution 2: Instead of using ImgBurn, use a program that can write CD discs in RAW write mode. I think it's also called RAW DAO mode. DAO is short for Disc At Once. Unfortunately, ImgBurn does not support RAW write mode: https://forum.imgburn.com/index.php?/topic/14285-burning-in-raw-mode/ It supports SAO (Session At Once), TAO (Track At Once) and "Incremental" (never heard of this one before). Using a program that supports RAW write will allow you to write your game images "as-is", that is, without having the drive write its own 304 byte segments, but replicate whatever is in the source image file. It will essentially make an exact copy of the original disc. It looks like you should be able to use CloneCD for this. But it does require you to have a CD burner that supports RAW write mode.
  13. I managed to turn the MD5 hash BF6B0935CBC9D13FA8C6523A34F8B123 from Any DVD into 7135BF384C5E666AAE6873EB3FF33D98 which is the same MD5 hash that the image I made with ImgBurn has. I simply disabled a number of features within Any DVD and made a new ISO image. I'm not sure what exactly triggered it, I will have to do more testing to narrow it down. But it does support the hypothesis that Any DVD (and most likely DVD Decrypter as well) changes the content in some way. I have not done any closer comparison between the ISO images.
  14. Is this type of problem caused by having ISO files rather than BIN/CUE for example? Would this not have happened if he had BIN/CUE files? I recall our earlier discussions about 2048 byte vs. 2352 byte sector sizes. Is it not possible to disable these smart features of the drive within ImgBurn? How else are you to let the drive know you don't want it to "correct" things?
  15. Ken852

    Two instances of ImgBurn running?

    Ah OK... it says "each session of the software". I seem to have misinterpreted this. The statement says nothing about the number of instances of ImgBurn you can run, or how many optical drives you can write to by instantiation. It just says that a single instance of ImgBurn can only writ to a single optical drive, that's it. It means that each instance can writing to only one optical drive. I'm not sure I would want it any other way? Not if you can achieve simultaneous writing to different optical drives by simply instantiating ImgBurn. So the way I see it now, this is not a limitation at all, even though it's listed as a limitation of ImgBurn. By storage devices you mean the hard drive? What about using a SATA SSD with about 500 MB/s read speed, would that suffice for writing ISO files to 2 optical drives at the same time?
×

Important Information

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