The HyperScan is a home video game console from the toy company Mattel . Marketed towards tweens, the console is unique in that it includes a 13.56 MHz radio-frequency identification (RFID) scanner that reads and writes to special cards called "IntelliCards" which, in turn, activate features in and save data from the game. Players are able to enhance the abilities of their characters by scanning cards.
44-449: Games retailed for $ 19.99 and the console itself for $ 69.99 at launch, but at the end of its short lifespan, prices of the system were down to $ 9.99, the games $ 1.99, and booster packs $ 0.99. There were only five titles known to have been released, with two canceled games. The HyperScan became critically panned upon its release for having outdated 2D-only graphics, a weak game library, and being less capable than other similar consoles such as
88-455: A UDF 2.01 volume that does not use Stream Files (introduced in UDF 2.00) but uses VAT (UDF 1.50) created by a UDF 2.60-capable implementation may have the revision declared as 0x0201 , the minimum read revision set to 0x0150 , the minimum write to 0x0150 , and the maximum write to 0x0260 . The UDF standard defines three file system variations, called "builds". These are: Introduced in
132-416: A UDF partition formatted by Windows cannot be written under macOS. On the other hand, a partition formatted by macOS cannot be directly written by Windows, due to the requirement of a MBR partition table. In addition, Linux only supports writing to UDF 2.01. A script for Linux and macOS called format-udf handles these incompatibilities by using UDF 2.01 and adding a fake MBR; for Windows the best solution
176-715: A disk controller for a hard drive. The tools and drives that do not fully support revision 1.5 of UDF will ignore the sparing table, which would lead them to read the outdated worn-out sectors, leading to retrieval of corrupted data. An overhead that is spread over the entire disc reserves a portion of the data storage space, limiting the usable capacity of a CD-RW with e.g. 650 MB of original capacity to around 500 MB. The UDF specifications allow only one Character Set OSTA CS0 , which can store any Unicode Code point excluding U+FEFF and U+FFFE. Additional character sets defined in ECMA-167 are not used. Since Errata DCN-5157,
220-499: A file is deleted on the disc, the file's data still remains on the disc. It does not appear in the directory any more, but it still occupies the original space where it was stored. Eventually, after using this scheme for some time, the disc will be full, as free space cannot be recovered by deleting files. Special tools can be used to access the previous state of the disc (the state before the delete occurred), making recovery possible. Not all drives fully implement version 1.5 or higher of
264-504: A file or directory overall, not by a class, though in the symbolic notation (see below) the setuid bit is set in the triad for the user, the setgid bit is set in the triad for the group and the sticky bit is set in the triad for others. These additional modes are also referred to as setuid bit , setgid bit , and sticky bit , due to the fact that they each occupy only one bit. Unix permissions are represented either in symbolic notation or in octal notation. The most common form, as used by
308-399: A fourth digit is present, the leftmost (high-order) digit addresses three additional attributes, the setuid bit , the setgid bit and the sticky bit .) Each of these digits is the sum of its component bits in the binary numeral system . As a result, specific bits add to the sum as it is represented by a numeral: These values never produce ambiguous combinations; each sum represents
352-403: A new group – a "user private group" – for each user. Assuming that each user is the only member of its user private group, this scheme allows an umask of 002 to be used without allowing other users to write to newly created files in normal directories because such files are assigned to the creating user's private group. However, when sharing files is desirable, the administrator can create
396-403: A permission is not set, the corresponding rights are denied. Unlike ACL-based systems, permissions on Unix-like systems are not inherited. Files created within a directory do not necessarily have the same permissions as that directory. Unix-like systems typically employ three additional modes. These are actually attributes but are referred to as permissions or modes. These special modes are for
440-655: A permission scheme similar to that of Unix. There are four categories (system, owner, group, and world) and four types of access permissions (Read, Write, Execute and Delete). The categories are not mutually disjoint: World includes Group, which in turn includes Owner. The System category independently includes system users. HFS , and its successor HFS+ , as implemented in the Classic Mac OS operating systems, do not support permissions. macOS uses POSIX-compliant permissions, and supports them in both HFS+ and APFS . Beginning with version 10.4 ("Tiger"), it also supports
484-440: A single pass. But when packet writing to rewritable media, such as CD-RW , UDF allows files to be created, deleted and changed on-disc just as a general-purpose filesystem would on removable media like floppy disks and flash drives . This is also possible on write-once media, such as CD-R , but in that case the space occupied by the deleted files cannot be reclaimed (and instead becomes inaccessible). Multi-session mastering
SECTION 10
#1732782780772528-426: A specific set of permissions. More technically, this is an octal representation of a bit field – each bit references a separate permission, and grouping 3 bits at a time in octal corresponds to grouping these permissions by user, group, and others. These are the examples from the symbolic notation section given in octal notation: Some systems diverge from the traditional POSIX model of users and groups by creating
572-408: A while, meaning that their data becomes unreliable, through having been rewritten too often (typically after a few hundred rewrites, with CD-RW). The plain and VAT builds of the UDF format can be used on rewriteable media, with some limitations. If the plain build is used on a -RW media, file-system level modification of the data must not be allowed, as this would quickly wear out often-used sectors on
616-435: Is also possible in UDF, though some implementations may be unable to read disks with multiple sessions. The Optical Storage Technology Association standardized the UDF file system to form a common file system for all optical media: both for read-only media and for re-writable optical media. When first standardized, the UDF file system aimed to replace ISO 9660 , allowing support for both read-only and writable media. After
660-1063: Is experimental support for NFSv4 ACLs for ext3 and ext4 filesystems. FreeBSD supports POSIX.1e ACLs on UFS, and NFSv4 ACLs on UFS and ZFS. IBM z/OS implements file security using RACF (Resource Access Control Facility) The AmigaOS Filesystem, AmigaDOS supports a permissions system relatively advanced for a single-user OS. In AmigaOS 1.x, files had Archive, Read, Write, Execute and Delete (collectively known as ARWED) permissions/flags. In AmigaOS 2.x and higher, additional Hold, Script, and Pure permissions/flags were added. OpenHarmony operating system alongside its client side ecosystem in Oniro OS and HarmonyOS with HarmonyOS NEXT versions and also Linux-based openEuler server OS natively uses its Harmony Distributed File System (HMDFS) that supports access token manager ( role-based access control ) and Core File Kit API capability-based with granular permission management with exception to openEuler. Permissions on Unix-like file systems are defined in
704-424: Is functionally equivalent to ISO-8859-1 , and the 16-bit storage is UTF-16 in big endian. 8-bit-per-character file names save space because they only require half the space per character, so they should be used if the file name contains no special characters that can not be represented with 8 bits only. The reference algorithm neither checks for forbidden code points nor interprets surrogate pairs , so like NTFS
748-502: Is referred to as permission-driven . Two types of permissions are widely available: POSIX file system permissions and access-control lists (ACLs) which are capable of more specific control. The original File Allocation Table file system has a per-file all-user read-only attribute. NTFS implemented in Microsoft Windows NT and its derivatives, use ACLs to provide a complex set of permissions. OpenVMS uses
792-420: Is represented as 0x0260 . In addition to declaring its own revision, compatibility for each volume is defined by the minimum read and minimum write revisions, each signalling the requirements for these operations to be possible for every structure on this image. A "maximum write" revision additionally records the highest UDF support level of all the implementations that has written to this image. For example,
836-408: Is using the command-line tool format /FS:UDF /R:2.01 . File system permissions Most file systems include attributes of files and directories that control the ability of users to read, change, navigate, and execute the contents of the file system. In some cases, menu options or functions may be made visible or hidden depending on a user's permission level; this kind of user interface
880-516: Is very well suited to incremental updates on both write-once and re-writable optical media . UDF was developed and maintained by the Optical Storage Technology Association (OSTA). In engineering terms, Universal Disk Format is a profile of the specifications known as ISO/IEC 13346 and ECMA-167. Normally, authoring software will master a UDF file system in a batch process and write it to optical media in
924-522: The VAT build to the UDF standard in its revision 1.5. The VAT is an additional structure on the disc that allows packet writing ; that is, remapping physical blocks when files or other data on the disc are modified or deleted. For write-once media, the entire disc is virtualized, making the write-once nature transparent for the user; the disc can be treated the same way one would treat a rewritable disc. The write-once nature of CD-R or DVD-R media means that when
SECTION 20
#1732782780772968-644: The VAT build, CD-RW/DVD-RW media effectively appears as CD-R or DVD+/-R media to the computer. However, the media may be erased again at any time. The spared build was added in revision 1.5 to address the particularities of rewriteable media. This build adds an extra Sparing Table in order to manage the defects that will eventually occur on parts of the disc that have been rewritten too many times. This table keeps track of worn-out sectors and remaps them to working ones. UDF defect management does not apply to systems that already implement another form of defect management, such as Mount Rainier (MRW) for optical discs, or
1012-597: The VTech V.Flash , which was released the month prior. Critics also raised concerns about the number of IntelliCards needed to complete a set, and the potential financial burden towards its target audience. Following disappointing sales, Mattel discontinued the HyperScan the following year, and canceled all upcoming game and card releases. The console uses UDF format CD-ROMs and has two controller ports. Only five games were released, with two games having been canceled due to
1056-605: The plain build and not necessarily either the VAT or Spared UDF builds. Mac OS X 10.4.5 claims to support Revision 1.50 (see man mount_udf ), yet it can only mount disks of the plain build properly and provides no virtualization support at all. It cannot mount UDF disks with VAT, as seen with the Sony Mavica issue. Releases before 10.4.11 mount disks with Sparing Table but does not read its files correctly. Version 10.4.11 fixes this problem. Similarly, Windows XP Service Pack 2 (SP2) cannot read DVD-RW discs that use
1100-453: The POSIX.1-2017 standard, which uses three scopes or classes known as owner , group , and others . When a file is created its permissions are restricted by the umask of the process that created it. Files and directories are owned by a user. The owner determines the file's user class . Distinct permissions apply to the owner. Files and directories are assigned a group , which define
1144-546: The UDF 2.00 sparing tables as a defect management system. This problem occurs if the UDF defect management system creates a sparing table that spans more than one sector on the DVD-RW disc. Windows XP SP2 can recognize that a DVD is using UDF, but Windows Explorer displays the contents of a DVD as an empty folder. A hotfix is available for this and is included in Service Pack 3. Due to the default UDF versions and options,
1188-445: The UDF, and some may therefore be unable to handle VAT builds. Rewriteable media such as DVD-RW and CD-RW have fewer limitations than DVD-R and CD-R media. Sectors can be rewritten at random (though in packets at a time). These media can be erased entirely at any time, making the disc blank again, ready for writing a new UDF or other file system (e.g., ISO 9660 or CD Audio ) to it. However, sectors of -RW media may "wear out" after
1232-406: The command ls -l , is symbolic notation . The first character of the ls display indicates the file type and is not related to permissions. The remaining nine characters are in three sets, each representing a class of permissions as three characters. The first set represents the user class. The second set represents the group class. The third set represents the others class. Each of
1276-556: The disc (such as those for directory and block allocation data), which would then go unnoticed and lead to data loss. To allow modification of files on the disc, rewriteable discs can be used like -R media using the VAT build. This ensures that all blocks get written only once (successively), ensuring that there are no blocks that get rewritten more often than others. This way, a RW disc can be erased and reused many times before it should become unreliable. However, it will eventually become unreliable with no easy way of detecting it. When using
1320-407: The file's group class. Distinct permissions apply to members of the file's group. The owner may be a member of the file's group. Users who are not the owner, nor a member of the group, comprise a file's others class . Distinct permissions apply to others. The effective permissions are determined based on the first class the user falls within in the order of user, group then others. For example,
1364-669: The first version of the standard, this format can be used on any type of disk that allows random read/write access, such as hard disks , DVD+RW and DVD-RAM media. Metadata (up to v2.50) and file data is addressed more or less directly. In writing to such a disk in this format, any physical block on the disk may be chosen for allocation of new or updated files. Since this is the basic format, practically any operating system or file system driver claiming support for UDF should be able to read this format. Write-once media such as DVD-R and CD-R have limitations when being written to, in that each physical block can only be written to once, and
HyperScan - Misplaced Pages Continue
1408-428: The game in separate "red" and "black" series; the latter went unreleased due to the console's cancellation. Though not much development for homebrew games was done on the console, several programmers have created demos and proofs-of-concepts. Some of the programs include a CD-Door demo, 3D wireframe demo, and a Bluescale demo. The system was sold in two varieties: a cube and a 2-player value pack. The cube box version
1452-427: The overall file, not only users in one class, the setuid attribute modifies the executable character in the triad for the user, the setgid attribute modifies the executable character in the triad for the group and the sticky or text attribute modifies the executable character in the triad for others. For the setuid or setgid attributes, in the first or second triad, the x becomes s and the - becomes S . For
1496-431: The range of code points was expanded to all code points from Unicode 4.0 (or any newer or older version), which includes Plane 1-16 characters such as Emoji . DCN-5157 also recommends normalizing the strings to Normalization Form C. The OSTA CS0 character set stores a 16-bit Unicode string "compressed" into 8-bit or 16-bit units, preceded by a single-byte "compID" tag to indicate the compression type. The 8-bit storage
1540-551: The release of the first version of UDF, the DVD Consortium adopted it as the official file system for DVD-Video and DVD-Audio . UDF shares the basic volume descriptor format with ISO 9660. A "UDF Bridge" format is defined since 1.50 so that a disc can also contain a ISO 9660 file system making references to files on the UDF part. Multiple revisions of UDF have been released: UDF Revisions are internally encoded as binary-coded decimals ; Revision 2.60, for example,
1584-401: The sticky or text attribute, in the third triad, the x becomes t and the - becomes T . Here is an example: Another method for representing Unix permissions is an octal (base-8) notation as shown by stat -c %a . This notation consists of at least three digits. Each of the three rightmost digits represents a different component of the permissions: owner, group, and others. (If
1628-536: The string may be malformed. (No specific form of storage is specified by DCN-5157, but UTF-16BE is the only well-known method for storing all of Unicode while being mostly backward compatible with UCS-2 .) Many DVD players do not support any UDF revision other than version 1.02. Discs created with a newer revision may still work in these players if the ISO 9660 bridge format is used. Even if an operating system claims to be able to read UDF 1.50, it still may only support
1672-507: The system's poor sales and reception. The games for the system were sold as $ 20 "Game Packs", which consisted of a game disc accompanied by six game cards (seven for Spider-Man ). Additional cards which contained characters, abilities, moves and levels when scanned were part of a six-card "Booster Pack", available for $ 10/pack. As with most trading card packs, the cards were randomized. Multiple booster packs were intended for certain games. X-Men intended to have 102 cards to unlock parts of
1716-407: The three characters represent the read, write, and execute permissions: The following are some examples of symbolic notation: In some permission systems additional symbols in the ls -l display represent additional permission features: To represent the setuid , setgid and sticky or text attributes, the executable character ( x or - ) is modified. Though these attributes affect
1760-471: The unnecessary usage of cards to select characters, and was officially discontinued in 2007. It is featured as one of the ten worst systems by PC World magazine. Universal Disk Format Universal Disk Format ( UDF ) is an open , vendor-neutral file system for computer data storage for a broad range of media. In practice, it has been most widely used for DVDs and newer optical disc formats, supplanting ISO 9660 . Due to its design, it
1804-606: The use of NFSv4 ACLs in addition to POSIX-compliant permissions. The Apple Mac OS X Server version 10.4+ File Services Administration Manual recommends using only traditional Unix permissions if possible. macOS also still supports the Classic Mac OS's "Protected" attribute. Solaris ACL support depends on the filesystem being used; older UFS filesystem supports POSIX.1e ACLs, while ZFS supports only NFSv4 ACLs. Linux supports ext2 , ext3 , ext4 , Btrfs and other file systems many of which include POSIX.1e ACLs. There
HyperScan - Misplaced Pages Continue
1848-401: The user who is the owner of the file will have the permissions given to the user class regardless of the permissions assigned to the group class or others class. Unix-like systems implement three specific permissions that apply to each class: The effect of setting the permissions on a directory, rather than a file, is "one of the most frequently misunderstood file permission issues". When
1892-422: The writing must happen incrementally. Thus the plain build of UDF can only be written to CD-Rs by pre-mastering the data and then writing all data in one piece to the media, similar to the way an ISO 9660 file system gets written to CD media. To enable a CD-R to be used virtually like a hard disk, whereby the user can add and modify files on a CD-R at will (so-called "drive letter access" on Windows), OSTA added
1936-522: Was the version sold in stores. It included the system, controller, an X-Men game disc, and 6 X-Men cards. Two-player value packs were sold online (but may have been liquidated in stores) and included an extra controller and 12 additional X-Men cards. The included game was rated "T" and the remaining titles were rated "E10+" by the ESRB . The system was universally panned by critics for its clunky design, broken controls, poor library, long loading screens, and
#771228