Paragon file system drivers for QNX enable fast and seamless sharing of multimedia data between QNX powered hardware and other external and internal devices, which use NTFS, exFAT, HFS+, ext4 (ext2, ext3).
Vendor
Paragon Software Group
Company Website
Paragon QNX file system driver comes with a set of utilities and tools which include, but not limited to mounting, unmounting, verifying, formatting, checking, and fixing errors. The automotive, marine, aviation, and other high-technology industries are in a growing demand for seamless interoperability of different file systems. The File System Drivers for QNX is here to help. With our File System Drivers for QNX 7.x or 6.5, manufacturers can significantly reduce BOM (bill of material) and add value to their customers.
Seamless interoperability Read/write access to storage devices without reformatting Best performance Higher data throughput and reduced CPU, memory load and footprint BOM Optimization Significant BOM reduction Faster time-to-market Long-term experience in integration of automotive and embedded systems
Features
Supported Operating Systems QNX 6.5 – 7.х Supported File Systems All Microsoft NTFS versions are supported (from Windows NT 3.1 to Windows 10), as well as exFAT, HFS+ and ext4, ext2 and ext3 MISRA & AUTOSAR Standards Depending on the set of requirements, Paragon File System Drivers for QNX are available as optional Misra & Autosar compliance Supported CPU Architecture Platforms Runs on every architecture, supported by QNX 6.5 – 7.х: x86, x86_64, ARM, ARM64 and others Write Access When a volume is mounted in write mode, you can do everything with the files and folders it contains: read, edit, delete, rename, create new. Volume Management File System Drivers for QNX utilities easily format, check integrity, identify and repair corrupted volumes errors. Internationalization File System Drivers for QNX components and utilities support all alphabets supported by your operating systems, including those that use non-Roman and non-Latin characters, so you will never face the problem of not getting access to file names on volumes mounted in non-native OS.