The Big KProbe2 Thread

In fact, it installs ForceASPI in a subdirectory with that name in your windows directory. This is probably the most innocuous way to install ASPI: the script killaspi will deactivate the current ASPI layer, although the files still remain on your drive in a subdirectory of ForceASPI.

Have a look at the usage file (index.html) there for further information.

G

And it will run Forceaspi on reboot in order to install ASPI layer, if there isn't any. As Aspi is mostly useless today, this is an annoyance

Michael

I guess once I have it installed on one machine, I could just copy the extracted files from the KProbe folder to another machine.

Sorry to repeat this, but it's been a year so I figure perhaps someone new will see...

I am a frequent buyer of used console and PC games. I have started using KProbe2 to scan my new acquisitions to look for potential problems, such as damage from previous poor handling or disk rot.

However, XBox game disks pose a special problem. When inserted into my PC, they show up in KProbe2 as having only 10MB of information on them. Other tools report the same thing; the only thing they see is the tiny DVD movie that tells you you're trying to put an XBox game into something that's not an XBox.

Right now I'm putting in the last possible address for the first layer of a DVD disk - namely 31AAFh. Then I start the scan, and wait for the progress percentage to quit increasing. This is not a very satisfactory solution.

Does anyone know how I can tell what the actual data-bearing portion of an XBox disk is, so I can put the correct parameters into the LBA for PI/PO scanning?


Dan

Hi Dan,

I don't have experience with XBox myself, but you should be able to use Nero CD-DVD Speed to perform your quality scans instead, because IIRC it will include all the sessions of a multi-session disc.

Check it out and tell us if that solves your problem.

A cross-posted question and a reply were moved to this thread:

Kprobe won't work with SHM-165H6S

I am trying to use Kprobe on a Dell 9200 system with two SATA optical drives. My understanding is that Dell 9200 has an Intel P965-based motherboard that is a Dell design.

The DVD burner is a Lite-On SH-16A7S-06 (SATA). I also have a Sony CRX310S combo (SATA). When both are installed Kprobe locks up at the spash screen. If I remove the Sony combo (or go into the BIOS to disable the SATA port to which the Sony is connected), Kprobe works fine.

When both drives are enabled, I get the same problem with the Lite-On Smartburn (which locks up at the "Querying..." message) and Lite-On Bitsetting (which locks up at the "Found... Lite-On SH-16A7S" message) utilities.

Any advice on how I might avoid the lock up issue when both drives are enabled?

Figured it out. Killaspi and set Kprobe to use SPTI.

Why would KProbe2 scan CD-Rs slower than the drive's max speed?

I tried to scan a few CD-Rs today with KProbe 2.5.2 (using my Sony DRU800A, f/w KY06), and regardless of the speed I set (Max, 40x, 32x) KProbe did all the scans at "8.0x".

It's been 6 or 8 months since I scanned a CD-R, but I don't remember this happening before. KProbe was using ASPI, so I changed it to SPTI, but got the same slow scans.

Is it just a coincidence that 8x is also the fastest that this drive will read DVD+/-Rs (though it will write at 16x)?

Nero CD-DVD Speed scans at full speed, but I like KProbe (which means I'm used to it, and it's easier to compare to earlier scans).

Any suggestions? Thanks.

Can anyone provide information on using ATAPI Commander in KProbe 252?
It looks interesting, but I not sure how to use it.

Just a small question,

i just got my external samsung SE-S184M usb burner and i just did a test using the latest K-probe and all worked correctly?
Isnt k-probe supposed to only work with liteon, or can i do a media quality scann with every drive?

PS: So how can i be sure that the showed results are correctly? In terms of quality the results are resonable 5.0 PEF and 0.01 PIF on a 8x tayo Yuden disc.

Hi AndyIEG, welcome to CDFreaks!

KProbe will work with drives that use MediaTek chipsets, this includes LiteOn drives but also some other drives like your Samsung. Drives that use other chipsets will not work with KProbe, but some of them work with Nero CD-DVD Speed.

How can you be sure that the shown results are "correct"? Well, in reality you can't. At best a PIE/PIF or C1/C2 Quality Scan is just a subjective opinion by the scanning drive showing the amount of low-level errors seen during reading. At worst it might be completely misleading if the drive is defective or not fit for quality scanning.

It probably uses a Mediatek chipset like the Liteon drives.

ah oki thx did not know this

So i can use all function of K-Probe with my samsung drive too? cool


PS: btw thx cdfreaks for the nice review of this samsung SE-S184M, helped a lot choosing what burner to buy.
The only thing i was wondering is that my old Benq 1640 had this nice overspeed function and could burn most of my medias at higher rates, while the samsung "seems" not be able to speed things up (at least with the one i bought).

Is there somewhere a list with writer and many media's and the max. speed, since i know samsung can also overspeed burning but samsung dont have a list like benq what media code it can burn at what overspeed...

Quick question.... When you get a error theres a green line along with the red, are these errors correctable errors???

I have been wondering this for sometime but have been unable to find out.

These aren't items from the error correction (like C1, C2 or PI, PIF etc.). They're an indication that the drive isn't reporting these values or cannot follow the track. IIRC, Karr mentioned something about the PUH (pickup head) slipping.

I've seen these, for example, in an unburned part of a disc in cases where the burn was aborted after part of the disc (e.g. directories) was written, or in very badly deteriorated discs.

G

It does not give me the option of selecting my external USB DVD Writer (HP 940e) but does find my CD drive. Any solutions?

Not sure what your HP drive really is, but I have a LiteOn in an external box, and KProbe wouldn't pick it up unless I chose to use the SPTI driver. Hope that helps.

That did the trick. Thanks.

I have a new Samsung SH-S203B burner, which supposedly has a MediaTek chipset and so should work with KProbe. However, when I try to scan a disk KProbe 2.5.2 almost immediately pops up a results window for a non-scan, e.g.
This is in a new nForce 430 system, and I've tried using both nVidia and MS drivers. I've now got the burner on a separate SiI 3112 SATA PCI card, but I always get the same results.

I've used KProbe for a long time, with an LDW-411 and then a Sony DRU800A, and I'd rather use it than CDSpeed (which does work with this drive).

Is there some fix for this problem?

Thanks!

I've just bought a LiteOn LH-20A1P, and I'm running it over a USB 2.0 IDE-Controller. Everything works well, except that I can't run C1/C2 scans in KProbe. PI/PIF scans work fine, and I can do C1/C2-scans in CDSpeed, and my LiteOn SOHR-5238S can be used for C1/C2-Scans in KProbe over the same USB-Adapter.

Any idea what might cause this? KProbe recognises the CD and can detect the length, But when I try to start the test it just says "done" without reading anything.

Although I have no idea why KProbe won't scan your CDRs (maybe someone else can answer that), LiteOn DVD burners aren't reliable for scanning CDs anway (they only report certain types of error), you're better off using your Litey CD-RW for that.

Edit: Dug up a direct quote from DrageMester, who first alerted me to the shortcomings of LiteOn DVD burners when scanning CDs:

This was 3 years ago. Is it still recommended that you use the old ASPI driver rather than SPTI driver when doing scans with KProbe 2.5.2?

ASPI or SPTI?

Also it looks like most are using Nero CD-DVD Speed now instead of Kprobe?

Is this true even for older Lite-On drives like the 1653S?

Just use whatever works for you. There have been some reports of problems with the ASPI drivers, but I haven't seen any personally.

KProbe installs ForceAspi (there's a subdirectory with that name under your windows directory) so it's very easy to enable or disable ASPI with a simple command if you don't need it.

Personally, I prefer the combination of KProbe and DVDScan for checking DVDs and still use KProbe 1.29 for CD's. CD-Speed is being actively developed, though, and the combined PI/PIF and jitter scan for newer LiteOn drives is very convenient.

G