Announcement

Collapse
No announcement yet.

SPTD.sys and other .sys problem

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • jmk
    replied
    Originally Posted by shdwsclan
    The problem is inter-related with the following software.

    MacDrive
    Nero
    Daemon Tools 4.x

    USB Hubs
    CD Roms
    Satas

    SPTD.sys is basically the virtualization portion.
    It is a rootkit as to conceal itself from software looking for virtualization software.

    Looking at gov't legislation, the possesion of rootkit-based virtualization software is illegal in some countries. Not in the US though, as of yet...

    Also, since daemon tools is rootkit based, it makes it that much harder to delete and re-install where this problem comes in.

    Basically, seen a descent solution which says that you must delete all the sptdXXXX.sys files, or at least rename them to sptdXXXX.old before reinstalling.

    Deletion of the keys and sptd.sys is a good start but not a finish.
    From speculation, sptd.sys seems to reference other sptd.sys files.....

    I scoured the web looking for this....though....

    I have all software mentioned, including XP SP2.

    Hope this problem gets a resolution soon since i use this software to test my hybrid ISO images.
    Do you have any proof(or a proper source) of what you are saying about inter-related programs messing the system up?

    Would this help do you think?:
    1. de-install Nero 6.06
    2. install DT4.03HE
    3. Find another program to burn DVDs/CDs

    I am courious about your reply.

    Greetings jmk

    Leave a comment:


  • Jito463
    replied
    Daemon Tools is not a rootkit, nor does it contain a rootkit. It uses some features that are "similar" to a rootkit, but not quite the same thing.

    Leave a comment:


  • shdwsclan
    replied
    The problem is inter-related with the following software.

    MacDrive
    Nero
    Daemon Tools 4.x

    USB Hubs
    CD Roms
    Satas

    SPTD.sys is basically the virtualization portion.
    It is a rootkit as to conceal itself from software looking for virtualization software.

    Looking at gov't legislation, the possesion of rootkit-based virtualization software is illegal in some countries. Not in the US though, as of yet...

    Also, since daemon tools is rootkit based, it makes it that much harder to delete and re-install where this problem comes in.

    Basically, seen a descent solution which says that you must delete all the sptdXXXX.sys files, or at least rename them to sptdXXXX.old before reinstalling.

    Deletion of the keys and sptd.sys is a good start but not a finish.
    From speculation, sptd.sys seems to reference other sptd.sys files.....

    I scoured the web looking for this....though....

    I have all software mentioned, including XP SP2.

    Hope this problem gets a resolution soon since i use this software to test my hybrid ISO images.

    Leave a comment:


  • minimaus
    replied
    I wrote to www.duplexsecure.com who seems to be the programmer of SPTD, I send them a minidump, but didn't get any answer yet. They also have a very little forum.

    Leave a comment:


  • Thorz
    replied
    The stupidest thing is that Alcohol has only answered me that they know about the problem but that there is a small number of users that are presenting it! They don't have an ETA for a fix (if this will exist one day!). They work together with Daemon Tools team for finding the solution following what the support guy wrote to me.

    Leave a comment:


  • AndreWilson1982
    replied
    what does this mean."Press ESC to cancel loading SPTD.sys"

    hi guys for some reason my pc wont boot into windows. it restarts when the xp logo appears. if i go into safe mode then the "Press ESC to cancel loading SPTD.sys" appears. i press ESC and then it restarts again. what do i do.PLEASE HELP!!!

    Leave a comment:


  • Tomkin
    replied
    My story...

    Hi guys,

    I had the same problem, it came suddenly, as I haven't installed anything, computer just stopped responding. Reboot, then black screen. Tried reinstalling DT, deleting sptd.sys and dtscsi.sys, registry...and still nothing. Then I noticed SonicStage (sw for mp3 player) has some SCSI driver which boots with Windows, I deleted it and now it all works! Maybe this will be helpful to somebody.

    Leave a comment:


  • jmk
    replied
    I'll wait for fix and OK by D-Tools staff

    Hi,

    I've read this whole thread and it seems to me this is the result of a WIndows XP SP2 Update.
    Everyone(98%) has WINXP SP2 dealing whith this problem!
    I tried to install DT 4.03 and BSOD etc etc...

    Apperently, there are more than one fix around here, but I'm not convinced this will permentantly fix the problem.
    1. With some fixes, some games/images work, some don't anymore. (That's what I can readout from some posts...I could be wrong)
    2. At a later point, maybe a new MS update, the OS may become increasingly unstable.
    3. If the fixes posted here were all that great the D-Tools staff would have OK'd it. They didn't. So maybe I'll better wait.

    This is not critisism! All fixes and bug reports help the staff to fix this, so all help they are getting is great, you are helping to get a stable OS using DT-4.

    As much as I like to use disk emulation software right now, I don't want an unstable OS.

    specs:
    P4 2.66 Ghz
    1 GB RAM
    WIN XP2
    NVIDIA 5200 FX

    Greetings jmk

    Leave a comment:


  • Thorz
    replied
    Originally Posted by seekerX3
    doesnt work

    Thanks for posting.
    I have not installed Alcohol again for testing.

    Leave a comment:


  • seekerX3
    replied
    Originally Posted by simcoder
    1. uninstall daemon tools and the sptd.sys using sptdinst_x64.exe remove
    2. reboot
    3. run regedit delete ALLE! referance to sptd and dtscsi (for those keys you can't delete, just delete the content eksept the (Default) key)
    4. reboot in safe mode
    5. run sptdinst_x64.exe add
    6. install daemon tools v4.03
    7. you are done and happy

    it might work for xp 32 as vel eksept use a defrent sptdinst

    sorry for eny bad spelling i am a Dane

    doesnt work

    Leave a comment:


  • minimaus
    replied
    same prob. as all of you BUT: ...

    But the difference is that I never have used DT, not even known of its existence.

    So, NO version of DT is the origin of the problem.

    I first got the prob. when I installed a virtual drive in Alcohol120%. During the instal the screen got black and my pc rebooted without ending. Alcohol120% was running on my system for several years but was not used very often.

    My system:
    Pentium 4 2,4 Ghz
    win2000
    promise raid controler
    Nero 6 with virtual drive
    alcohol120% some old version (now deleted)

    2 month ago all microsoft updates were done and I did not use Alcohol120% since this time.

    To get my comp running again I deleted Alcohol120 drivers in "secure mode" and now pc runs fine. But as I install alcohol120 again the prob comes up again. I used 4 different vers. of alcohol120 -> all the same prob.

    Depending on the alcohol120 the sys files to be deleted were:
    xmasbus.sys
    a347bus.sys
    vax347b.sys
    sptd.sys on the latest alcohol120% 1.9.5.3823

    I agree with vimes, who thinks there is a problem with microsoft updates, as the alcohol is running fine on my win2000 notebook without latest updates

    I hope this may help you solve the problem

    Leave a comment:


  • Ythan
    replied
    I just encountered this problem on my system. I may or may not be able to help since I think I know exactly what led up to it. I was playing Tomb Raider Legend 1.1 with the handy Deviance no CD patch so I don't have to dig out the CD every time I want to play. The TRL image was *not* mounted as it's not required with the patch. While I was playing, the game hung at the end of a level. On reboot, I encountered this problem. No safe mode, couldn't run CHKDSK from the recovery console (hung at 12%). Tried to repair my existing installation. Setup didn't delete or copy any files, just rebooted and hung with the XP splash. Tried chkdsk again from the recovery console, worked this time. Another repair install got further and hung on the blue desktop with cursor. At this point I was getting frustrated and finally found this thread. Renamed stpd.sys and dtscsi.sys from the recovery console. The repair install appears to be proceeding normally, although I now realize it was unnecessary. To the best of my knowledge I hadn't made any changes to my system since the last reboot. This is what leads me to believe that the game crashing had something to do with it. Anyway, awesome software but this bug sucks. If I can do anything to help track it down please let me know. Unfortunately I have no logs from when the problem occured though.

    Leave a comment:


  • Thorz
    replied
    Originally Posted by simcoder
    1. uninstall daemon tools and the sptd.sys using sptdinst_x64.exe remove
    2. reboot
    3. run regedit delete ALLE! referance to sptd and dtscsi (for those keys you can't delete, just delete the content eksept the (Default) key)
    4. reboot in safe mode
    5. run sptdinst_x64.exe add
    6. install daemon tools v4.03
    7. you are done and happy

    it might work for xp 32 as vel eksept use a defrent sptdinst

    sorry for eny bad spelling i am a Dane
    Takk!
    I will test this.

    Leave a comment:


  • simcoder
    replied
    i solvd it for xp x64

    1. uninstall daemon tools and the sptd.sys using sptdinst_x64.exe remove
    2. reboot
    3. run regedit delete ALLE! referance to sptd and dtscsi (for those keys you can't delete, just delete the content eksept the (Default) key)
    4. reboot in safe mode
    5. run sptdinst_x64.exe add
    6. install daemon tools v4.03
    7. you are done and happy

    it might work for xp 32 as vel eksept use a defrent sptdinst

    sorry for eny bad spelling i am a Dane

    Leave a comment:


  • Thorz
    replied
    Originally Posted by vimes
    Now one set of tests doesn't mean that my findings are accurate or correct. BUt it might be a clue that something with Windows updates could influence the way that SPTD.sys interacts with the system...?
    I suspect exactly the same. It has to be some update that is triggering the problem.

    Leave a comment:

Working...
X