![]() However, it also uses SPTD.sys (Alcohol & DT have a close working relationship), so if that's causing your DT problem then Alcohol isn't the solution (Homer Simpson: ".alcohol, the cause of, and solution to, all of life's problems."). Note that the free edition installs an IE toolbar (this cannot be de-selected at install time, but can be uninstalled after the fact). Note that a few people have suggested to use Alcohol 52% instead, which has a free-for-non-commercial-use edition. If the older DT 3.x will work for you (which I don't think works on Vista), then you have a way to avoid SPTD. This has been causing at least some level of problems with users, and is unavoidable with DT 4.x. There are 2 potential problems with Daemon Tools (DT), one of which is easy to fix, the other is an unavoidable aspect of its design:ġ) there is adware (not spyware) in the DT installer - the fix for this is to uncheck the option in the install wizard to have it installed Ģ) it uses a 'secure' SCSI transport driver (SPTD.sys), which I assume is something that helps DT deal with being blacklisted by copy protection schemes. I understand that 52% also comes with a toolbar, but forum users seem to say that can be "unselected" during the installation setup.can't confirm that for myself, however. But I haven't tried this new (reduced) version. I used to use Alcohol 120% for a long time and loved it as well. Seems to not be a drain on my system resources.Īlcohol 52% is now offered by them as freeware. Still have it on my W2K system, and it has been working great. Put DaemonTools back on and it was happy again. ![]() I got it off in safe-mode and all was well. I really liked how it performed on my Windows 2000 Pro system so I decided to remove DaemonTools from my XP Pro system (laptop) and load it on as well.Įnded up BSOD it. I recently heard about an alternative ISO mounter.MagicDisk from MagicISO. I generally have had no issues at all with Daemon Tools and am a long-time user of it, but I understand that some users have. I haven't blue screened yet as I type this post.but I don't know how I'll ever trust her again. It sure seems that mounting an ISO should just be built into the OS and not a whole series of selling one's soul to the device driver devil with fake devices and faux BIOs extensions. After rebotting and not blue screening, I removed all the SCSI devices from the Device Manager (right click on My Computer and click Manage, then Device manager) as well as the "PnP BIOS Extension" under System Devices. Amazing thing, it includes a version of Opera and will let you surf, but it won't allow you to delete a file.Īnyway, I went into c:\windows\system32\drivers and di a "dir /o-d" to see the most recently installed files. It's lovely, to be sure, but it doesn't let you open a command prompt. If you press it too early - like when the BIOS screen appears - you'll end up in their custom Windows Pre-Execution Enivronment. With the Lenovos, you have to be careful wit hF8. I started up in Safe Mode with Command Prompt, after pressing F8 before the Windows Splash screen. I looked all over the Daemon Tools forum and found dozens of folks having the same problem, but the support folks monitoring the forums were very unsympathetic and less than helpful.Īt this point, I was stuck in a BSOD loop, blue-screening after the desktop appeared. How can you ever trust the machine again? When your BRAND NEW MACHINE blue screens, it's like discovering your spouse is a spy with another life. In the middle of the install - bam - blue screen of death. I downloaded Daemon Tools, a great ISO mounter that I've used happily for years without so much as a peep of drama from it. I did VS2003, VS2005, etc.all from CD, but then I needed to mount an ISO. I started installing crap (they could drop an image on the machine, but I like things "just so"). I figured it was a sign to start over, so I got a Thinkpad T60p from our IT department. I even made a batch file to loop forever and repeatedly kill it. After having used it happily for a few years, suddenly WGATRAY.EXE decided to hang at 100% CPU forever, rendering the machine unusable. I recently had trouble with my work IBM Thinkpad T42.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |