Search results for query: *

This is what I found... http://www.eventid.net/display.asp?app=Top10&eventid=7000 I would go into the registry and do a search of the entire registry for "icfinst.exe". It should find at least one entry. Once you find the entry that is executing the .exe, delete it and reboot. This...

Another note... disk(0) refers to the partition and not the physical drive. rdisk(0) refers to the physical drive and not the partition. Hope this clarifies.

I have a dual boot XP system utilizing two different HD's on my laptop. Both OS's are XP Pro. Below is my boot.ini. I believe that you just have to change the RDISK value. [boot loader] timeout=10 default=multi(0)disk(0)rdisk(0)partition(1)\WINNT [operating systems]...

Have you tried GhostExplorer (Symantec Program). Also, do you know what software was used to create the .img image. That would help answer the question.

Look in the event viewer under either application or system to see if it gives you the EventID for the error. Let me know what it is if it is in the event viewer.

I would try running ghost as shown below from a DOS prompt. ghost -ntic -ntil I have seen numerous issues when ghosting to an NTFS partition and this has corrected them all. For more useful ghost commands, type ghost /? at a dos prompt.

I have seen this problem with CDRW's and XP Pro. To resolve the problem, I deleted the drive from the Device Manager and rebooted the computer. This forced the OS to re-install the hardware and resolved the problem. I am still not sure what the cause to this is.

Ghost 2002 will not write to the NTFS partition. Ghost 2003 will do this. (Couldn't believe it until I tried it myself. Works really well) You have two options. 1. Make the second partition FAT32. 2. Upgrade to Ghost 2003. Hope this helps.

I would look at two different locations to fix this. 1. Look at your startup folder to see if this is where the executable is being called from. If it is, delete it. It should still be located elsewhere on you hard drive if you really need it. 2. If it is not located in the startup folder, look...