Jus boot straight to DOS and remove all traces of the app from there. That seems to work fine for me...
Jus boot straight to DOS and remove all traces of the app from there. That seems to work fine for me...
Some thing like that happened to me, except it was a different file. What i did was boot up in safe mode and remove the file and the trace of it in the registry and then restart. That worked just fine.
Enjoy the good things in life not the things made to be seem good.
The daemon tools is a vd driver. Boot into Safe Mode, go into Hardware, show hidden devices if you don't see it under , uninstall the device, which is a driver masquerading as a virtual device. Simple. Dang
If another moron posts rubbish bout format !!!!!!!!
btw. Netware's Client32 for Windows will do the same thing if the install fails.
Last edited by Nestersan; Dec 24, 2006 at 10:47 AM.
Let Them Hate, So Long As They Fear.
You do not know whereof you speak,and your words are empty things.
Listen and gain Wisdom.
http://twitter.com/nestersan
I would attempt to boot from MS's Recovery Console, and manually remove entries from the BOOT.INT, WIN.INI, and SYSTEM.INI files.
Doing a Windows repair, wouldn't solve the problem (taking the easy way out, thats bad for a techie).
Does this particular BSOD, display an actual error code long enough for you to read it?
HTML Code:PM or link me Smartphone: Samsung Galaxy Note 8 SM-N950F CompTIA A+ Certified Laptop: Apple MacBook™ Pro ITIL v3 Certified Tablet: DELL Venue 11 Pro Apple is still the best thing since sliced bread
Which version is this btw... cuz I realise daemon tools is no longer free in our sense but has alot of adware the last time i checked so i have the last version before they implemented the ads....
cell: 807-4523| email: mysonchug@yahoo.com | PM Me
Dude Win.ini,system.ini are throwback files for compatibility purposes with old Win 3.1x/95'ish apps.
Daemon tools is a near Kernel level Device driver, nothin to edit...
Don_corleone , you is REAL TECHIE FOR TRUE !!!
FIRST TO POST CORRECT ANSWER.
Noobies all aboard the bus...
Don_corleone need to tek unnu to school....
The Daemon tools exe file is not problem, the device driver is...
Last edited by Arch_Angel; Dec 27, 2006 at 11:33 PM. Reason: merged multiple posts. removed irrelevant comments.
Let Them Hate, So Long As They Fear.
You do not know whereof you speak,and your words are empty things.
Listen and gain Wisdom.
http://twitter.com/nestersan
Nestersan, please explain how Don Corleon solved the problem. Deleting the driver file alone will not be possible if you get a BSOD in safemode.
Don-Corleone, I guess you can now start the school bus then.
I still don't understand your soloution.
HTML Code:PM or link me Smartphone: Samsung Galaxy Note 8 SM-N950F CompTIA A+ Certified Laptop: Apple MacBook™ Pro ITIL v3 Certified Tablet: DELL Venue 11 Pro Apple is still the best thing since sliced bread
He said machine BSOD'd on normal startup, he didn't say it BSOD'd on safe mode. Even so, from my expereinces with XP, when you have kernel level driver like daemon tools, when you boot into safe mode, you are prompted if you want to load the non-M$ low level drivers that are listed to be loaded.
Let Them Hate, So Long As They Fear.
You do not know whereof you speak,and your words are empty things.
Listen and gain Wisdom.
http://twitter.com/nestersan
Before you close this thread, please help me solve my problem.
When ever I do a Windows repair, I get a BSOD even during safemode. The error message flahes for a breif moment before rebooting. Any suggestions?
I can't get into safemode at all.
PS: I was doing an OS repair, when this occured.
HTML Code:PM or link me Smartphone: Samsung Galaxy Note 8 SM-N950F CompTIA A+ Certified Laptop: Apple MacBook™ Pro ITIL v3 Certified Tablet: DELL Venue 11 Pro Apple is still the best thing since sliced bread
First off, you said whenever??!!. Does that mean whenever as in any machine, or that one in particular ?
LOL.
Seriously.
1) Why were u doing a repair ?
2) I find when you get BSOD in safemode it is generally a Hardware/Virtual driver issue. why?
Because according to M$ this is what is loaded in Safemode:
Drivers:
• Floppy disk drives (internal and USB)
• Internal CD-ROM drives (ATA, SCSI)
• External CD-ROM drives (USB)
• Internal DVD-ROM drives (ATA, SCSI)
• External DVD-ROM drives (USB)
• Internal hard disk drives (ATA, SATA, SCSI)
• External hard disk drives (USB)
• Keyboards (USB, PS/2, serial)
• Mice (USB, PS/2, serial)
• VGA display cards (PCI, AGP)
Services:
• Event logs
• Logical disk manager
• Plug and Play
• Remote procedure calls
• Cryptographic services
• Help and Support
• System Restore
• WMI (Windows Management Instrumentation)
VERY BARE.
Now when you do a repair install, M$ replaces the drivers/files/etc with the ones on the CD. It also re-initializes registry.
So either: RAM BAD/HD BAD, kernel level driver (SATA/DAEMON TOOLS) currupt.
The most important thing is to find what the BSOD error code is and look it up.
eg. I will get the "IRQ_LESS THAN EQUAL TO" BSOD if my PSU Misbehaving, cause i have one of those 6800 Powered AGP CARDS.
Is the machine stuck in a BSOD loop ?
Let Them Hate, So Long As They Fear.
You do not know whereof you speak,and your words are empty things.
Listen and gain Wisdom.
http://twitter.com/nestersan