Announcement

Collapse
No announcement yet.

SPTD 1.43 problems

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

  • SPTD 1.43 problems

    After installing SPTD 1.43, my Windows XP SP2 automatically reboot whenever running:
    1. WinAMP 4.53
    2. Roxio Easy Media Creator 9

    Now revert back to daemon 3.47

  • #2
    Install SPTD 1.47 Beta (forum.duplexsecure.com)
    Make something idiot proof, but then they just make a better idiot
    Peace Through Power

    Comment


    • #3
      When I installed the latest Deamon Tools (SPDT 1.43) the first extremely annoying thing was that it breaks compatibility with my TV tuner Terratec Cingery 600. When I tried to load the included Terratec recording software my PC was automatically rebooted.
      Even with SPDT 1.47 final was the same and not only that problems just got worse. Booting process took ages to complete. While I could see the desktop wallpaper, there was no start bar and icons for at least 30 to 40 sec and even then I must wait for another 20 sec to fully load all background apps.
      C'mon, my PC is C2D 6400, 2GB ram, WinXP Pro (32 bit) motherboard Asus P5B Deluxe. Well, I have one extremly non standard solution for my pc config. I use PCI-IDE controller for my 2 IDE disks (onboard IDE is used for 2 DVD-RW drives).
      But I still could not understand how the hell, can that SPTD driver mess with my TV tuner and causes PC to reboot (hangs) when I start the program. With 4.08 and SPTD 1.38 I had no such problems.

      Comment


      • #4
        Either upload and post the link to your latest minidump, or send it to support@daemon-tools.cc for review. It may shed some light on what's causing the BSOD.

        Comment


        • #5
          @XPunter: Such issues are not so unusual as you might think,
          as SPTD is a driver!! It is deeply in system architecture.

          Apart from that it must not mean that SPTD is guilty, only
          that it conflicts with other drivers.

          Although I can admit that Duplex do mistakes ALSO some time,
          in >90% of all cases(!!!) it is other, poorly written driver who
          conflicts because authors had not slightest idea how to
          write absolutly standard-conform drivers or do not have
          enough coding-practice, some of them are buggy as hell. They
          cause corruptions and other sideeffects. Now, when some
          "critical" driver like SPTD, who must RELY! on fact that other
          guys maked no shit with system, is added to system and
          - just as an example - for whatever reasons read in
          memorypage that is not belonging to this specific driver but
          other apps, it could damage whole system stability.

          Or, to make long story short:

          It doesnt matter how good SPTD is matured and designed
          if only ONE shitty driver is in system.

          It is my sad duty to tell you that especially TV-tuner drivers
          are very often designed by above mentioned coders.

          As a matter of fact: when we made most parts of driver-
          design ourselfs (in old DT 3.XX) we implemented ~400(!)
          workarounds and usually got requests of MATURE firms
          (some issues you can even read for yourself here at our
          board, e.g. Roxio and some others) with sometimes
          thousands of employees asked us for support to get THEIR
          driver compatible with ours. And mostly BECAUSE we are
          so wellknown they couldnt ignore old bus/prt driver. Thats
          how business works nowadays.

          Not that this means it is also true for your case, it is only
          some "insight" so you see how CURRENT situation is and
          that it is only <10% fault of SPTD - currently. And as
          SPTD is not designed by us but Duplexsecure, I cant
          check it without "minutes" now..

          BTW; And not every time Duplex writes "Bug fixed:" it means
          that they had a bug! It means: Problem fixed - whatever
          caused it. I guess you got my point. Nevertheless, I reported
          your problem to them as it could indeed be possible bug!
          Thank you for notifying us!

          Comment

          Working...
          X