No announcement yet.

Permission problems continue with v 1.25

  • Filter
  • Time
  • Show
Clear All
new posts

  • Permission problems continue with v 1.25

    I have exactly the same problem with Alcohol 52 and Daemon tools4.03 so I will concentrate on Daemon tools 4.03
    Win XP SP2. McAfee installed. I can't turn it off (password protected).

    I have installed sptd 1.25. In Safe mode I completely removed all traces of sptd (even deleting all registry keys).
    Then I log on as my domain user (member of the local administrator group) and install Daemon Tools 4.03. Installation goes fine, Daemon Tools works.
    Reboot and log on again as the domain user. Now, Daemon tools will not start: there is a warning message saying the at least Windows 2000 and SPTD v 1.24 is required. The Event log gives the usual Error about internal data structures of the sptd driver.

    Start Daemon Tools as "run as..." and choose a user local to the machine (and also a member of the administrator group). Daemon tools works, and there is no entry recorded in the event log. So this is a work around. But it is annoying.

    There are no starforce drivers installed.

  • #2

    An update.
    If I choose "run as..." and run the program explicitly as the domain user, it works. This seems weird because I am running the program (daemon.exe) "as" the user I am already logged in as. But with this approach, no error.
    Of course, double clicking the file to launch it does not work, as described above.
    I don't know enough about Windows to understand this.


    • #3
      So you are running SPTD layer v1.25 now?
      Can you post the complete eventlog message (with all binary bytes)?


      • #4

        I think the standing theory is that Group policy permissions were preventing the install.


        • #5
          Yeah, I think it is something to do with policy settings or some other kind of security layer that is above the kernel. However, the previous poster wrote "preventing the install". I got it installed ok and when I start it as "run as" Daemon Tools works fine. The software is there and working, but I can't run it normally.
          blackbox.exe does not work when run as an administrator, but when the same user does "run as" then blackbox.exe works. If it was a matter of kernel permissions, surely it would not work under the second approach.

          Anyway, here is the error I get when executing daemon tools by double clicking:

          First, the dialog box text from Daemon Tools:

          DAEMON Tools
          Initialization error.
          This program requires at least Windows 2000 with SPTD 1.24 or higher.
          Kernel debugger must be deactivated.

          and the event log entries:
          from system log

          Type: error
          Event id: 4
          Driver detected an internal error in its data structures for .

          For more information, see Help and Support Center at

          0000: 00 00 00 00 01 00 52 00 ......R.
          0008: 00 00 00 00 04 00 04 c0 .......
          0010: 9b 00 00 00 00 00 00 00 ›.......
          0018: 00 00 00 00 00 00 00 00 ........
          0020: 00 00 00 00 00 00 00 00 ........
          Last edited by timrichardson; 07-12-2006, 10:20 PM.


          • #6
            And one more thing: it has nothing to do with McAfee I think because I killed McAfee by disabling all services and startup entries, but the problem did not change (after rebooting to take advantage of the disabled McAfee services and disabled startup entries)

            And it is v1.25
            Last edited by timrichardson; 07-12-2006, 10:22 PM.


            • #7

              Can you load up regmon or filemon and look for permission denied kind of entries when trying to load the daemon-tools tray icon without using "Run As..."? Or maybe just look for the entries that occur right before the warning message (about kernel debuggers, sptd 1.24, etc). It's strange. Members of the Users group should be able to use the tray icon program (not even power users is required).


              • #8
                Regmon doesn't tell me anything. Both methods generate very many entries in the log, and there are no failure messages. There are plenty of key not found and buffer overflow results, but this seems to be the same for both methods.

                filemon also shows no errors. In the normal execution mode I can see entries in filemon when the system log is locked, written to and released (reporting the error message about the SPTD driver) but there are no error messages nearby that help me understand what is going on.