|
3 Files after DVD Decrypter
|
|
|
CAR8624
Member
|
4. March 2004 @ 12:00 |
Link to this message
|
|
After Decrypting one of my DVD [GASARAKI], it gave me three files:
GASARAKI_VOL_1.I00
GASARAKI_VOL_1.I01
GASARAKI_VOL_1.MDS
Just to let you kno, this is 4.3 Gigs.
I try converting in CMD, but I do not know how should I put it into directory. Also - I have forgotten what to type in order to convert.
Is there any other way besides converting if conversion does not work?
=>CAR8624
|
|
Advertisement
|
|
|
|
|
CAR8624
Member
|
5. March 2004 @ 18:47 |
Link to this message
|
|
'up' - Please help me?
|
Moderator
3 product reviews
|
5. March 2004 @ 19:23 |
Link to this message
|
|
you should have 2 files :
GASARAKI_VOL_1.ISO
GASARAKI_VOL_1.MDS
The .ISO file would be the one that you would then burn as ISO Write under Mode tab
I take it you did an ISO read on your DVD ??
|
|
CAR8624
Member
|
5. March 2004 @ 19:53 |
Link to this message
|
|
Yes - I did ISO Read on the DVD. But it came out to be three files instead of two. What should I do in order to have an ISO file?
=>CAR8624
|
Moderator
3 product reviews
|
5. March 2004 @ 21:12 |
Link to this message
|
What Operating system are you using btw ?
Check the settings/options within DVD Decrypter to make sure .ISO file extension is checked : )
|
|
CAR8624
Member
|
6. March 2004 @ 08:04 |
Link to this message
|
|
I have Windows XP. Before decrypting this DVD, I have decrypted other DVD before and they have an .ISO extension. But this particular DVD will only give me three files.
Anyways - the settings [.ISO extention] is checked. What else should I check?
=>CAR8624
|
Moderator
3 product reviews
|
6. March 2004 @ 11:34 |
Link to this message
|
Decrypt it in File IFO Mode instead , so you have loads of VOB BUP IFO files
Then if it is more than 4.36Gb you can compress it or if smaller then burn VOB BUP IFO files to a VIDEO_TS folder..
|
|
CAR8624
Member
|
6. March 2004 @ 19:33 |
Link to this message
|
|
I've tried doing IFO Mode, but it says the following:
UDF File System Parsing Failed!
Reason: Unable to find 'VIDEO_TS' folder.
-Well I have VIDEO_TS folder, it is that it's not reading it. I don't know why this is happening. Is there anyway to Convert my I00 into ISO?
|
Moderator
3 product reviews
|
6. March 2004 @ 23:24 |
Link to this message
|
|
If your GASARAKI_VOL_1.I00 is 4.36 Gb or so , then try renaming it GASARAKI_VOL_1.ISO & see if Decrypter will 'ISO Write' it for ya...
|
|
CAR8624
Member
|
7. March 2004 @ 00:04 |
Link to this message
|
|
It won't read it as ISO even after renaming.
|
Moderator
3 product reviews
|
7. March 2004 @ 00:06 |
Link to this message
|
|
Right okay first things first...
What kind of system are you running , and get as technical as you like mate ;-)
|
|
CAR8624
Member
|
7. March 2004 @ 06:34 |
Link to this message
|
|
Well here's what I know so far about my computer [hey, I didn't bought the computer + I do not know a lot about computers =p]
Dell Dimension 8100 series
Windows XP [originally Windows ME]
My DVD-/+RW is from SONY [forgot which series or set - just know the brand] and it is external drive.
=>CAR8624
|
Moderator
3 product reviews
|
7. March 2004 @ 07:08 |
Link to this message
|
hhmmm , not a lot of help
I would suggest maybe trying SmartRipper now then as it is also freeware.
It'll be VOB BUP IFO and not ISO...
|
|
CAR8624
Member
|
7. March 2004 @ 08:50 |
Link to this message
|
|
After I download Smart Ripper, what should I actually do? Rip my DVD into one of the files [VOB BUP IFO]? If so, do I burn that image/file [VOB BUP IFO] into DVD Media?
=>CAR8624
|
Moderator
3 product reviews
|
7. March 2004 @ 09:47 |
Link to this message
|
If you want Full-Disk (ie; Menu + Extras) then tick all VOB , BUP , IFO files in FILE mode.
If all files total no more than 4.36Gb , then you can burn VOB/BUP/IFO files in a VIDEO_TS folder in something like Nero.
DVD Decrypter wont burn these files...
|
|
CAR8624
Member
|
7. March 2004 @ 16:02 |
Link to this message
|
Okay - if it's less than 4.3 gigs, I could burn into one DVD-R right? If so, I have to burn all of the VOD files into the disc? How in Nero?
Also - I have the same problem with PS2 game. Smart Ripper will not read PS2 game for some strange reason [I know that the PS2 game I'm trying to copy is a DVD-Rom format, yet it gave me 3 files - similar to GASARAKI]. Please help me with that.
=>CAR8624
|
Moderator
3 product reviews
|
8. March 2004 @ 05:14 |
Link to this message
|
|
Right lets get PS2 out of the way first :
DVD Decrypter ISO Read > ISO Write ... has not failed me on any PS2 DVD Game yet !!
----------------------------------------------------
As to movie if it is less than 4.3Gb then you can burn to VIDEO_TS folder in Nero , as long as all the VOB/BUP/IFO files that are needed are included.
You didnt explain if you ripped Movie-Only or Full-Disk , this matters a lot !
As to why you're getting 3 files instead of ISO & MDS is unknown to me , are you running WinXP on NTFS ?
This message has been edited since posting. Last time this message was edited on 8. March 2004 @ 05:16
|
|
CAR8624
Member
|
8. March 2004 @ 15:13 |
Link to this message
|
herbsman - Your a great help so far. I'm sorry if I have not given enough information in order for you to help me.
[[As to movie if it is less than 4.3Gb then you can burn to VIDEO_TS folder in Nero , as long as all the VOB/BUP/IFO files that are needed are included.
You didnt explain if you ripped Movie-Only or Full-Disk , this matters a lot ! ]]
Full-Disk - I've tried it [and somehow got like 5 VOB]. The Full-Disk is less than 4.3 [actually 4.13] GIGS. Another question: In Nero, do I have to burn the files with the folder [because it is in a Folder], or can I just take our the 5 VOB files in that folder and burn it into a DVD-R disc? In other words, what should I do with the 5 VOB files in my VIDEO_TS folder?
[[As to why you're getting 3 files instead of ISO & MDS is unknown to me , are you running WinXP on NTFS]]
I was trying to decrypt Socom 2 for PS2 with ISO READ then ISO Write. For some PS2 in the past I have decyrpt, they all have ISO file. But this particular one [and the other - Final Fantasy X] has the same problem with GASARAKI [3 files].
In other forum [actually DVD Decrypt's Support Forum], they have told me to just burn MDS file [even though it's 5KB]. I've tried it on FFX, it worked. But I have received an error [and thus creating a coaster] with Socom 2. Error has something to do with illegal writing or some sort. Is there anyway to fix Socom 2? If not, is it possible to do the same with GASARAKI with Smart Ripper [you know, VOB files etc]?
=>CAR8624
|
|
chthomson
Member
|
8. March 2004 @ 18:11 |
Link to this message
|
|
Hi CAR8624
Fat 32 file system has a file limitation of 4GB. Windows ME used Fat 32 for its file structure. Decypter has split the image into two files ISO I00 and I01 so the ISO files will be under that limitation. The MDS file would then be used to to set up the burn using Decrypter ISO write. I use it all the time on single layered discs.
I hope this helps
|
|
CAR8624
Member
|
8. March 2004 @ 18:34 |
Link to this message
|
|
But how come on one of my PS2 game [Socom2], it says that I have an error [illegal writing I think - something like that] when burning that MDS file into a DVD-R? Is it just a bad day or some sort?
Take it into factor that my media blank is TDK 2x [Writing at a Speed of 1x]. Since I need to make a good PS2 backup, I must have the Write Speed 1x.
=>CAR8624
|
|
chthomson
Member
|
8. March 2004 @ 18:53 |
Link to this message
|
|
Hi CAR8624
I am not a game specialist - yet. I understand that there is copy protection on some games. I have been able to make backups of my PC games with copy protection with Blindwrite. I do not know how this applies to PS2 games.
I hope this helps
|
Moderator
3 product reviews
|
9. March 2004 @ 08:22 |
Link to this message
|
|
chthomson picked up on something I was trying to ask earlier on in the thread , you need to be running NTFS and not fat32 file system [if your not already in WinXP] !!;-)
I never burn the .mds file , ONLY the .ISO file ... 100% success
That is for either copy of a copy (movie) and also PS2 games (about 40-50 , so far)
|
|
CAR8624
Member
|
9. March 2004 @ 10:26 |
Link to this message
|
|
[[you need to be running NTFS and not fat32 file system [if your not already in WinXP] !!;-)]]
Eh - then how should I run in NTFS? BTW - what is NTFS?
=>CAR8624
|
Moderator
3 product reviews
|
9. March 2004 @ 11:02 |
Link to this message
|
|
You will need to do a re-format [on at least operating drive]
--------------------------------------------------
NTFS Architecture Overview
Most of the weaknesses of the FAT file system result directly from the rather simplistic and outdated architecture it uses. No provisions were made in the internal structures of FAT partitions to allow for security and reliability features, making it very difficult to add such capabilities later on. In contrast, NTFS has a special architecture that not only allows for these advanced abilities, but also uses a simple conceptual scheme that makes it easier for more features to be added in the future with a minimum of changes. (In fact, this characteristic was employed when NTFS 5.0 came out with several new options.)
The elegance of the NTFS architecture can be seen in how information is stored in an NTFS partition. Virtually every structure in NTFS is a file, including the structures used to manage the partition and maintain statistics and control information about the partition itself. The control information is stored in a set of special files that are created when an NTFS partition is first created; these are called metadata files and include such items as lists of files on the partition, volume information, cluster allocations, and so forth. One exception to the "everything is a file" rule is the partition boot sector, which precedes the metadata files on an NTFS partition and controls the most basic of NTFS operations, such as loading the operating system.
The same simple conceptual model used for files and control structures is extended to the internal level of files as well. Every file in an NTFS partition is a collection of attributes; this even includes the data that the file contains, which is just considered one of many attributes. Other attributes include items such as the file's name and size. This arrangement really a database-like setup--the operating system view files as being objects with various characteristics, and manages them accordingly. This makes it easy to manage files and add attributes if needed in the future.
Internally, NTFS stores all files (including metadata files) using a cluster system--each file is broken into clusters, each of which contain a binary number of 512-byte sectors. On the surface, this is somewhat similar to how FAT stores data, but the implementation of clusters in NTFS is somewhat different.
NTFS Volume Boot Sector
When an NTFS partition is first created, the first block of information created on the partition is the volume boot sector. This fundamental structure, which is part of a very small block of NTFS management information that is not stored within the master file table on an NTFS volume, is very much the analog of the volume boot sector under the FAT file system. Like volume boot sectors in FAT, the NTFS volume boot sector is sometimes called the partition boot sector, volume boot record or other similar names.
Note: Despite the use of the word "sector" in the name of this structure, the volume boot sector can in fact be up to 16 sectors (8 kiB) in length.
The NTFS volume boot sector begins in the first sector of the partition, and consists of two different primary structures. Again, these are similar to the structures in a FAT volume boot sector:
BIOS Parameter Block: This is a block of data that contains fundamental information about the volume itself. This block identifies the volume as an NTFS partition, and includes such information as the volume label and its size. In addition, NTFS provides for an extended BIOS parameter block, which contains additional information about the volume such as the location of the key metadata files.
Volume Boot Code: This is a small block of program code that instructs the system on how to load the operating system. With an NTFS volume, this code will be specific to Windows NT or 2000, whichever is installed on the system. It will generally load NTLDR, the NT loader program, and then transfer control to it to load the rest of the operating system. Note that this code is also present in the partition as a system (metadata) file.
The volume boot code on a FAT file system partition is a favorite target of virus writers, as changing this code can allow a virus to automatically load whenever the system has started. The higher-security design of Windows NT and 2000, however, makes it more difficult for viruses in the boot sector code to spread, due to the fact that the operating system maintains tighter control over disk access routines once it has loaded. (Viruses are still possible on Windows NT/2000 systems, of course.)
etc etc
This message has been edited since posting. Last time this message was edited on 9. March 2004 @ 11:04
|
|
Advertisement
|
|
|
|
CAR8624
Member
|
9. March 2004 @ 13:23 |
Link to this message
|
|
Eh reformat my computer? Maybe next time =p.
Anyways, is there any reason why I have this problem with Socom 2?
=>CAR8624
|
