1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

3 Files after DVD Decrypter

Discussion in 'DVDR' started by CAR8624, Mar 4, 2004.

  1. chthomson

    chthomson Regular member

    Joined:
    Nov 26, 2003
    Messages:
    203
    Likes Received:
    0
    Trophy Points:
    26
    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
     
  2. herbsman

    herbsman Moderator Staff Member

    Joined:
    Sep 3, 2002
    Messages:
    3,377
    Likes Received:
    0
    Trophy Points:
    66
    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)
     
  3. CAR8624

    CAR8624 Regular member

    Joined:
    Feb 17, 2004
    Messages:
    96
    Likes Received:
    0
    Trophy Points:
    26
    [[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
     
  4. herbsman

    herbsman Moderator Staff Member

    Joined:
    Sep 3, 2002
    Messages:
    3,377
    Likes Received:
    0
    Trophy Points:
    66
    You will need to do a re-format [on at least operating drive]
    --------------------------------------------------
    [bold]NTFS Architecture Overview[/bold]

    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.
    [bold]NTFS Volume Boot Sector[/bold]

    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



    _X_X_X_X_X_[small][​IMG]
    Afterdawn Guides: http://www.afterdawn.com/guides/
    Afterdawn Rules: http://forums.afterdawn.com/thread_view.cfm/6346[/small]
     
    Last edited: Mar 9, 2004
  5. CAR8624

    CAR8624 Regular member

    Joined:
    Feb 17, 2004
    Messages:
    96
    Likes Received:
    0
    Trophy Points:
    26
    Eh reformat my computer? Maybe next time =p.

    Anyways, is there any reason why I have this problem with Socom 2?

    =>CAR8624
     
  6. herbsman

    herbsman Moderator Staff Member

    Joined:
    Sep 3, 2002
    Messages:
    3,377
    Likes Received:
    0
    Trophy Points:
    66
    Socom !!! I wouldn't have a clue ... you might wanna ask that in PS2 Discussion Forum (there is a known issue w/ online play of a back up of that game as far as I remember reading).

    It could be a problem with the DVD being more than 4Gb don't forget as you are restricted using fat32 file format !; ]
     
  7. CAR8624

    CAR8624 Regular member

    Joined:
    Feb 17, 2004
    Messages:
    96
    Likes Received:
    0
    Trophy Points:
    26
    I've got it!! I tried doing Test Mode for .MDS file and it worked. Though I cannot go online with Socom2, I just need a backup =)

    Thx a lot ppl for helping me =)

    =>CAR8624
     
  8. herbsman

    herbsman Moderator Staff Member

    Joined:
    Sep 3, 2002
    Messages:
    3,377
    Likes Received:
    0
    Trophy Points:
    66
    Glad you got it all sorted CAR8624 ;)
     

Share This Page