[shinryuu]

Ok, I was chatting with vortex from the unofficial tech support channel, and he suggested that my hotfixed SP2 build was confusing the program. Is there any way to skip the OS check?

[SCVirus]

I doubt it, if the OS check could be disabled then the other protections could be too.

[shinryuu]

Originally Posted by SCVirus

I doubt it, if the OS check could be disabled then the other protections could be too.

I'm sorry, what? I'm talking about the Daemon installer.

[mwb1100]

Originally Posted by shinryuu

Ok, I was chatting with vortex from the unofficial tech support channel, and he suggested that my hotfixed SP2 build was confusing the program. Is there any way to skip the OS check?

Here's something you might try:

Go to the properties sheet for the installation .exe and then to the 'Compatibiliy' tab.

Check the box to run it in Compatibilty mode and set it to Windows 2000 compatibility.

NOTE: This should make the installer think that it's running on Win2k, which may well screw-up any part of the install that's different between Win2k and WinXP. But maybe there aren't any and it'll work.

[Underheaven]

I don't think there's actually an issue with the OS check. But anything is worth a try.

[Bladeinger]

@ i k a r i: Did you use the DT 3.47 before and unistalled it?

[born_wild]

Hello there! Im having the same problem as all the others!
I get the deactivate karnell...or what ever error...

And yes bladeinger, I was running Daemon tools 3.47 when i installed daemon tools v4!
I know it wasn't such a good idea...But...anywho! Now Im stuck with that error message!!=(

Help?!....anyone?=)

[Enviro]

Ok this is what you got to do!

Uninstall Daemon 4.0 if you can if not its ok
Right click on my computer and select properties
click the Advanced tab
Under start up and recovery select settings
Under write debugging information set it to none
Hit all the oks and applys on the way out
You can try and run the program if installed but i suggest reinstalling!

After running daemon for the first time you can set the debugging information back to whatever you want!

ENJOY!

[shinryuu]

Enviro, thank you. You are a prince among men. A saint. A God. You are Jesus, Mohammed, Confucius and Shakyamuni rolled into a ball and smothered in a creamy sauce of really great guy. I have lost nights of sleep over this. I have tried everything and spoken to everyone who would listen. Not only that, but you fixed a random error on my computer that had been happening since the day I bought it, through at least 3 reformats. I'm so happy, I'm nearly crying. Sweet blessed relief.

Ok, enough gushing, here's what I did:
1. Disabled debugger logging, as per Enviro's instructions
2. Opened the DT4 installer
3. With the installer open, copied SPTDinst.exe from the temp
4. Ran SPTDinst.exe from the command line with the /add switch (it refused to work any other way)
5. Rebooted, reinstalled DT4 and now it's humming away happily.

I saw at least one other person getting exactly the same error I was (entry_point_not_found), and plenty of people are getting the kernel debugger error, so hopefully Enviro's inspired advice will spread joy to the masses, and not just me

[Bladeinger]

Ok, everyone with this Problem, pease try this out (I had the same Problem on my Server):
- Run the Uninstall-Routine, either of the 3.47 or the 4.0.
- Reboot the System.
- Remove manualy all Registry Entries and Files from the previous Version, as described by VeNoM386 in the Section "Commmon Problems and Solutions", again either of the 3.47 or the 4.0.
- Reboot and check Event Log for Errors related to missing Files of DT.
- If everything is ok, install the new Version.
That was the way to solve the Problem on my System.