aaru-dps/Aaru-aaru-dps
1
0
Fork 0
mirror of https://github.com/aaru-dps/Aaru.git synced 2026-02-04 00:54:33 +00:00
Code Issues 657 Packages Projects Releases 19 Wiki Activity

Aaru claims Plextor 755SA does not support GigaRec #481

New Issue
Closed
opened 2026-01-29 15:19:58 +00:00 by claunia · 6 comments
claunia commented 2026-01-29 15:19:58 +00:00
Owner
Copy Link

Originally created by @RibShark on GitHub (Aug 14, 2020).

Prerequisites

  • Are you running the latest version?
  • Can you reproduce the problem in the debug version?

Check and fill as appropriate:

  • I was running Aaru under Windows 10 2004
  • I was running Aaru under Linux [version here]...
  • I was running Aaru under FreeBSD [version here]...
  • I was running Aaru under macOS [version here]...
  • ...using .NET Framework [version here]...
  • ...using .NET Core [version here]...
  • ...using Mono [version here]...
  • ...in 32-bit
  • ...in 64-bit

Description

When checking device information in Aaru, for the Plextor 755SA GigaRec is listed as unsupported despite being supported by the drive.

Exact command line used:

GUI used.

Expected behavior:

GigaRec should be marked as supported.

Actual behavior:

GigaRec is marked as not supported.

If command was expected to work with a device fill this out:

  • Manufacturer: Plextor
  • Model: 755SA
  • Bus:
    • Parallel ATA
    • Serial ATA
    • SCSI (any)
    • ATAPI (mark above if parallel or serial)
    • USB
    • FireWire
    • PCMCIA
    • SecureDigital
    • MultiMediaCard
Originally created by @RibShark on GitHub (Aug 14, 2020). ### Prerequisites * [x] Are you running the latest version? * [x] Can you reproduce the problem in the debug version? ### Check and fill as appropriate: * [x] I was running Aaru under Windows 10 2004 * [ ] I was running Aaru under Linux [version here]... * [ ] I was running Aaru under FreeBSD [version here]... * [ ] I was running Aaru under macOS [version here]... * [ ] ...using .NET Framework [version here]... * [ ] ...using .NET Core [version here]... * [ ] ...using Mono [version here]... * [ ] ...in 32-bit * [ ] ...in 64-bit ### Description When checking device information in Aaru, for the Plextor 755SA GigaRec is listed as unsupported despite being supported by the drive. ### Exact command line used: GUI used. ### Expected behavior: GigaRec should be marked as supported. ### Actual behavior: GigaRec is marked as not supported. ### If command was expected to work with a device fill this out: * **Manufacturer**: Plextor * **Model**: 755SA * **Bus**: * [ ] Parallel ATA * [x] Serial ATA * [ ] SCSI (any) * [ ] ATAPI (mark above if parallel or serial) * [ ] USB * [ ] FireWire * [ ] PCMCIA * [ ] SecureDigital * [ ] MultiMediaCard
claunia commented 2026-01-29 15:20:01 +00:00
Author
Owner
Copy Link

@RibShark commented on GitHub (Aug 14, 2020):

Requested files.
plextor_755sa.zip

@RibShark commented on GitHub (Aug 14, 2020): Requested files. [plextor_755sa.zip](https://github.com/aaru-dps/Aaru/files/5076694/plextor_755sa.zip)
claunia commented 2026-01-29 15:20:03 +00:00
Author
Owner
Copy Link

@claunia commented on GitHub (Nov 6, 2020):

Can you confirm if it says it is supported in the command line?

@claunia commented on GitHub (Nov 6, 2020): Can you confirm if it says it is supported in the command line?
claunia commented 2026-01-29 15:20:04 +00:00
Author
Owner
Copy Link

@claunia commented on GitHub (Nov 7, 2020):

Protected commands and the PX-755/760
Plextor does obviously not tolerate that anyone can use the unique functions of the PX-755/760 drive on Linux or other "alternative" operating systems, or that anyone uses alternative applications on Windows. Plextor has introduced "protected commands" into these drives. Commands like enabling/disabling GigaREC or SilentMode, as well as all quality check commands, now require to retrieve a code and send another one that is calculated from the received one back to the drive, otherwise those commands will be rejected by the drive. Please note that I have bought the drive to find out what means Plextor is using in order to force people into using PlexTools, and even to force people into using Windows.
From https://www.alexander-noe.com/cdvd/px/index.php

See also https://qpxtool.sourceforge.io/problems.html (firmware links dead).

Closed as firmware lockdown by manufacturer.
Command output is correct.

@claunia commented on GitHub (Nov 7, 2020): > Protected commands and the PX-755/760 > Plextor does obviously not tolerate that anyone can use the unique functions of the PX-755/760 drive on Linux or other "alternative" operating systems, or that anyone uses alternative applications on Windows. Plextor has introduced "protected commands" into these drives. Commands like enabling/disabling GigaREC or SilentMode, as well as all quality check commands, now require to retrieve a code and send another one that is calculated from the received one back to the drive, otherwise those commands will be rejected by the drive. Please note that I have bought the drive to find out what means Plextor is using in order to force people into using PlexTools, and even to force people into using Windows. From https://www.alexander-noe.com/cdvd/px/index.php See also https://qpxtool.sourceforge.io/problems.html (firmware links dead). Closed as firmware lockdown by manufacturer. Command output is correct.
claunia commented 2026-01-29 15:20:05 +00:00
Author
Owner
Copy Link

@RibShark commented on GitHub (Nov 7, 2020):

Protected commands and the PX-755/760
Plextor does obviously not tolerate that anyone can use the unique functions of the PX-755/760 drive on Linux or other "alternative" operating systems, or that anyone uses alternative applications on Windows. Plextor has introduced "protected commands" into these drives. Commands like enabling/disabling GigaREC or SilentMode, as well as all quality check commands, now require to retrieve a code and send another one that is calculated from the received one back to the drive, otherwise those commands will be rejected by the drive. Please note that I have bought the drive to find out what means Plextor is using in order to force people into using PlexTools, and even to force people into using Windows.
From https://www.alexander-noe.com/cdvd/px/index.php

See also https://qpxtool.sourceforge.io/problems.html (firmware links dead).

Closed as firmware lockdown by manufacturer.
Command output is correct.

I am using unlocked firmware that reenables the commands. I can't test with the latest Aaru build due to #425.

@RibShark commented on GitHub (Nov 7, 2020): > > > > Protected commands and the PX-755/760 > > Plextor does obviously not tolerate that anyone can use the unique functions of the PX-755/760 drive on Linux or other "alternative" operating systems, or that anyone uses alternative applications on Windows. Plextor has introduced "protected commands" into these drives. Commands like enabling/disabling GigaREC or SilentMode, as well as all quality check commands, now require to retrieve a code and send another one that is calculated from the received one back to the drive, otherwise those commands will be rejected by the drive. Please note that I have bought the drive to find out what means Plextor is using in order to force people into using PlexTools, and even to force people into using Windows. > > From https://www.alexander-noe.com/cdvd/px/index.php > > See also https://qpxtool.sourceforge.io/problems.html (firmware links dead). > > Closed as firmware lockdown by manufacturer. > Command output is correct. I am using unlocked firmware that reenables the commands. I can't test with the latest Aaru build due to #425.
claunia commented 2026-01-29 15:20:06 +00:00
Author
Owner
Copy Link

@claunia commented on GitHub (Nov 7, 2020):

Me and @SilasLaspada checked and the command is send correctly, and returns correctly the value in other drives, but not on the 755 and 760.

We then checked qpxtool and wodim and they return not supported as well.

I checked both cdrkit and qpxtool source code and they are using the same command.

If you want to reverse engineer how PlexTools sends the command, I will implement that, but for a merely aesthetical indicator, that fails only on a single model of drives, due to manufacturer locking, I will not start to reverse engineer it.

@claunia commented on GitHub (Nov 7, 2020): Me and @SilasLaspada checked and the command is send correctly, and returns correctly the value in other drives, but not on the 755 and 760. We then checked qpxtool and wodim and they return not supported as well. I checked both cdrkit and qpxtool source code and they are using the same command. If you want to reverse engineer how PlexTools sends the command, I will implement that, but for a merely aesthetical indicator, that fails only on a single model of drives, due to manufacturer locking, I will not start to reverse engineer it.
claunia commented 2026-01-29 15:20:07 +00:00
Author
Owner
Copy Link

@RibShark commented on GitHub (Nov 7, 2020):

Me and @SilasLaspada checked and the command is send correctly, and returns correctly the value in other drives, but not on the 755 and 760.

We then checked qpxtool and wodim and they return not supported as well.

I checked both cdrkit and qpxtool source code and they are using the same command.

If you want to reverse engineer how PlexTools sends the command, I will implement that, but for a merely aesthetical indicator, that fails only on a single model of drives, due to manufacturer locking, I will not start to reverse engineer it.

QpxTool returns supported for me, I am using unlocked firmware.

@RibShark commented on GitHub (Nov 7, 2020): > > > Me and @SilasLaspada checked and the command is send correctly, and returns correctly the value in other drives, but not on the 755 and 760. > > We then checked qpxtool and wodim and they return not supported as well. > > I checked both cdrkit and qpxtool source code and they are using the same command. > > If you want to reverse engineer how PlexTools sends the command, I will implement that, but for a merely aesthetical indicator, that fails only on a single model of drives, due to manufacturer locking, I will not start to reverse engineer it. QpxTool returns supported for me, I am using unlocked firmware.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
archive
beginner
bug
bug
dependencies
device
device
dump image format
duplicate
Epic
feature request
filesystem
filter
gui
gui
gui
help wanted
invalid
invalid
media
needs triage
partitioning scheme
pull-request
Mirrored from GitHub Pull Request
 upstream
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: aaru-dps/Aaru-aaru-dps#481
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?