Warning Disk Already Unlocked, Not Stealth Compatible Options

[relaxxx]

I've looked and looked all over the internet and can't figure out what this means or how to fix it.

I flashed a spare TS-H943A ms25 with the 0800.bin file to try and backup some of my games. Flashed with jungle flasher which was a lifesaver as I spent about 10 hours messing with DOS boots to find and flash the drive.

First I tried XBC 2.9 and All I got was an error about invalid security sector and aborted the reading.
Then I tried XBC 2.7 and it seemed to read the SS fine but gives the message "not stealth compatible" and something about DVD files will be replaced with empty data or something and then goes on to read and make the game ISO.

Here's the start of my log file:
====================================================================
Xbox Backup Creator v2.7 Build:0265 By Redline99

Found ODD: HL-DT-ST DVDRAM GSA-H10A JL01 at [D]
Additional Info: 
Found ODD: TSSTcorp DVD-ROM TS-H943A ms25 at [F]
Nero API is not available
ImgBurn executable not found
Getting media info [F]
Media Type: Not Present
Getting media info [F]
Media Type: DVD-ROM
Bytes Used: 5.32 MB (5,578,752 bytes)
======================================
<-- Security Sector Details -->
Source Drive: TS-H943A
--------------------------------------

Do I need that Nero API and ImgBurn executable??
I've got a feeling if I try to burn this image I'm just going to have a coaster.
What do I do next? How Do I get the stealth part working?

[majinsoftware]

Are you sure your trying to copy the original, Iv only ever seen that happen when some ones tryed to use a back up.

[relaxxx]

Yes, this is my original Halo3 disk. It's pretty scuffed up but it reads the game ISO without any read errors, just the message about the stealth. I also have GTA4 but that one is really scratched and gets read errors. It won't install the 360 Hard drive either.

[relaxxx]

Seems to be working now. I rebooted my computer this morning to swap DVD Burners and now it is suddenly reading my game without any warnings at all. All stealth checks pass now. Strange, I can't see how changing my burner fixed it unless the Samsung drive just needed to be reset/rebooted itself for some reason. The Samsung 360 Drive I'm using has been modified to fit in my tower bay and is permanently connected to my PC and running off my ATX power supply.

[scuba156]

The drive wasnt unlocked.

more than likely, all you had to do was click on tools, and click on 'unlock drive'

[niccador]

I've looked all over for information on this error, also, and have found nothing but this thread....

As with the original poster, I've got a Sammie flashed with iXtreme 1.6 0800, using a RROD 360 for power (because I'm too cheap for a CK...heh), and connected with onboard NForce3 SATA.

The drive is detected in Windows, and appears to read the video partition, as it should. XBC also seems to have no issues reading the drive and disc.

But whenever I start a rip, it gives the same warning about being unlocked already, and fails to rip the video partition properly.

(AGBX appears to patch this missing data for me, but I'd rather not have to rely on it, right?)

Unlike to OP, a simple reboot did not fix the problem for me.

Can anyone help me get this sorted?



TO MODERATORS:
I was half asleep and distracted by children when I was trying to post this, and my stupid ass Reported it instead. Sigh. No idea why I thought the button on the wrong side of the screen was Reply, it's not like I haven't been here before. My humble apologies.

[niccador]

Okay, well perhaps I can add a little more detail that has come to light...

I failed to mention in my original post that accessing the drive with XBC using STPI on my XP system, fails. The drive only appears readable on my system using ASPI.

Just the other day, a friend had me flash his spare (identical) Samsung with 1.6 0800, and show him how to use XBC... This drive behaved the same as the other when hooked up to MY system -- worked only through ASPI, gave the warning, and failed to rip the video partition properly.

When he got home, he experienced something a little different... His system was running Vista rather than XP, and he did not have Nero (or any other) ASPI driver installed, so ASPI wasn't even an option for him. However, on his Vista system, the drive functioned properly using STPI, gave no warning, and as near as I can tell, was able to rip everything properly.

So, at this stage, I'm more or less of the belief that this warning is somehow due to using the ASPI interface over the STPI...

So now it seems my question has mutated into more than one, and may be growing still:

1) Why would STPI not be working properly on my XP system?
2) Why would ASPI not be allowing the drive to lock/unlock/rip properly?

...I'm about to give the drive a test on my other Vista system I have setup, and see if I experience the same results. In the meantime, I'd be most interested in hearing anyone's theories on the problem...