PDA

View Full Version : Conflict with DT and O&O Defrag



CrendKing
15.01.2006, 06:30
I installed DAEMON Tools 4.03 (with SPTD 1.24), and found there is an error message about SPTD in Event Viewer -> System, said "Driver detected an internal error in its data structures for ." Although I can use DAEMON Tools normally, sometimes there will be a BSOD with message IRQL_NOT_LESS_OR_EQUAL (which may describing some driver fault) when I exit Windows.

And after installing DT4.03, I cannot use O&O Defrag (I tried almost every version, even the unpublished versions I get from O&O Support). For example, I open O&O, analyze one volume. After the analysis completes, I begin to analyze some volume (same volume or some other volume) again, the progress would stop at 0% forever, and the agent service cannot be stopped. And as for defragmentation requires analysis first, I can use O&O only ONCE every time I boot Windows.

I can assure it's a conflict with DAEMON Tools and O&O Defrag (manually delete SPTD, no problem), and SPTD is the most suspected component I think. Is there anyway to install DT4 without installing SPTD, and DT4 will work without installing SPTD? Thanks!

Andareed
15.01.2006, 09:24
I haven't tested O&O but I know dtools works fine with Perfect Disk and Diskeeper. I'll take a look at O&O defrag later today.

CrendKing
15.01.2006, 09:29
Yes, PD and Diskeeper works well, only O&O has the problem. Maybe there is some low-level difference in those core engines.

LooDos
15.01.2006, 09:32
i had this problem too a long time ago. i think with DT v3.47 and O&O defrag. could be quite interesting to solve this problem...

CrendKing
15.01.2006, 10:40
But DT 3.47 and StarForce... You know...

AnalCobra
15.01.2006, 12:00
I use DT 4.03 and O&O Defrag 8 and it works perfectly.

DomiOh
15.01.2006, 12:29
I used O&O Defrag 8 without problems with DT 3.47
Not tested with 4.03 yet.

LooDos
15.01.2006, 12:35
i had problems using DT 3.47 and O&O Defrag 8.
it simply didnt defrag automatically anything...

CrendKing
15.01.2006, 14:31
Yes, I do think that this is a system-related problem, and maybe SPTD first conflicts some other driver in my system, and becomes malfunction, then O&O would invoke some low-level disk driver, such as SPTD, and finally, this problem occurs.

I think the most important thing is to solve "Driver detected an internal error in its data structures for .", as this does NOT ONLY OCCUR in my computer.

Development
15.01.2006, 20:30
What are binary bytes in SPTD error message in system event log?

CrendKing
16.01.2006, 07:02
0000: 00 00 00 00 01 00 52 00 ......R.
0008: 00 00 00 00 04 00 04 c0 .......À
0010: 86 00 00 00 01 00 01 00 .......
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

This error raises each time when I boot Windows.

Development
17.01.2006, 04:19
There is somethng wrong with your storage controllers or some
"unusual" drivers used. Please report your configuration.

CrendKing
17.01.2006, 06:36
My Motherboard is Soltek SL-KT600-R, southbridge is VT8237. I have a SATA harddisk and an PATA harddisk. SATA driver is the "VT8237 Integrated Serial ATA RAID controller 5.20A" (http://www.viaarena.com/default.aspx?PageID=420&OSID=1&CatID=1180&SubCatID=143), and IDE driver is the "VIA IDE Accelerator Driver 1.21 BETA" (http://www.viaarena.com/default.aspx?PageID=420&OSID=1&CatID=1180&SubCatID=148).

In Computer Management, IDE controller is "VIA Bus Master Ultra ATA Controller", SCSI and RAID controller is "VIA SATA RAID Controller".

Anything else should I report?

Development
17.01.2006, 17:15
Please report your registry settings under HKLM\HARDWARE\DeviceMap\Scsi - which driver is shown
for every "ScsiPort X"subkey?

What is your OS version?

CrendKing
17.01.2006, 18:35
OS is Windows XP Pro with SP1

Registry:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi]

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 0]
"Interrupt"=dword:00000014
"IOAddress"=dword:0000e800
"Driver"="viamraid"

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 0\Scsi Bus 0]

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 0\Scsi Bus 0\Initiator Id 255]

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 0\Scsi Bus 0\Target Id 0]

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 0\Scsi Bus 0\Target Id 0\Logical Unit Id 0]
"Identifier"="ST3120026AS 3.18"
"Type"="DiskPeripheral"
"InquiryData"=hex:00,00,00,00,1f,00,00,00,53,54,33,31,32,30,30, 32,36,41,53,20,\
20,20,20,20,20,20,20,20,20,20,20,20,33,2e,31,38

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 1]
"Interrupt"=dword:00000009
"IOAddress"=dword:0000ffe0
"Driver"="dtscsi"

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 1\Scsi Bus 0]

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 1\Scsi Bus 0\Initiator Id 15]

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 1\Scsi Bus 0\Target Id 0]

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 1\Scsi Bus 0\Target Id 0\Logical Unit Id 0]
"Identifier"="JD1793W LBJ049G 1.0 "
"Type"="CdRomPeripheral"
"InquiryData"=hex:05,80,02,02,20,00,00,10,4a,44,31,37,39,33,57, 20,4c,42,4a,30,\
34,39,47,20,20,20,20,20,20,20,20,20,31,2e,30,20

Seems one is my harddisk, one is DT.

Development
17.01.2006, 23:27
Hmm, then where is your PATA harddisk?

CrendKing
18.01.2006, 05:05
PATA harddisk should not in the scsi subkey, right? In HARDWARE key, there are only FullScreenVideo, KeyboardClass, PointerClass, Scsi, VIDEO subkeys, no Disc, or IDE, or something else.

I am not familiar with the HKLM\HARDWARE\ key, and I do not know what exactly information you want. I think in HKLM\SYSTEM\CurrentControlSet\Services there are information about my computer's drivers.

Development
18.01.2006, 07:31
All IDE and SCSI devices must be under this key.
This just means the driver used is "unusual", i.e. not follows
common scheme. I think it is "VIA IDE Accelerator Driver 1.21".
I would recommend you remove it and use standard atapi.sys from Microsoft.

CrendKing
18.01.2006, 11:10
Yes, it solved the problem! Thanks very much!!!

Seems the beta version driver should not be used in common situations.

Thanks again.