Windows XP forum: downloading Kodak easyshare software on XP

Some report that is some CDRW as a disk drive software is installed, all heck breaks loose. But details are a little slim in your post.

Bob

If some versions of DirectCD or INCD are installed, a post like yours happens. Kodak's tech support usually tells you about this.

bob

When you uninstalled Kodak Easyshare, do the thinkgs you have done, BUT also check the registry for stray entries and make sure that your camera is not connected. I know, I had this problem myself. The best thing is to rownload it to a safe location, but DON'T try to load it just yet. Make sure everything is ready, then load it from the download (you'll also need your internet connection active at this time since the loader only really starts the process and gets the rest of the programme for Kodak's site)

Ignore the warning aboout Fax machines, I don't have one but still got the warning. Your printer, if it's parallel, yo should be ok, but it may still be worth unplugging it.

Now you can connect your camera (and printer again if necessary) - be warned though, Easyshare likes to put an icon in the systray, you can shut it down permanently easily enough - then use the destop icon to put it into your quickstart menu. Otherwise it will always be turned on in the background. To stop it recurring, you may have to delete it from msconfig.

click Start/Run, typ in ''msconfig'' (without the quotes) and look on the Startup tab, near the bottom of the page you should see an entry relating to Easyshare, just uncheck it.

Make sure your internet connection is closed and restart the computer, it should be ok now.

After all that the program wouldnot open. I just got an error message report to microsoft.

And the gist of that was? With that information perhaps something will be more useful to help troubleshoot.

1. Error Reporting which is enabled by default displays an error dialog box prompting the user to indicate whether or not they want to report the problem. When choosing to report the problem, technical information about the problem is collected and then sent to Microsoft over the Internet. If a report is rendered and if a similar problem has been reported by other people and more information is available, a link to that information will be provided the user. Turning it ON or turning it OFF is the user's call. For assistance and resolution, we would need to know WHAT cause(s) is/are reported.

a. Were there no links or anything else provided should you submit the report?

b. Please. For your benefit, always report the error information this report contains when wanting our analyses.

2. When a system error occurs, the computer displays a blue screen containing error codes and all computer operations stop. When an illegal operation or other error occurs in a program, that program stops working. System and program errors may be transmitted to Microsoft which allows them to track and address operating system, Windows component, and program errors. Error Reporting configuration is outlined in, [Q310414]:

a. Enable or disable
b. Enable for the operating system
c. Specify the program for which a report is generated
d. Remove programs from the list
e. Send an error report to Microsoft

3. Supplemental reading:

a. "Description and Availability of Internet Explorer Error Reporting Tool (Q276550)."

b. "No Date or Time Information Available When Program Stops Responding in Windows 98 or Windows Me (Q280660)."

c. "How to Disable or Redirect Internet Explorer Error Reporting (Q310116)."

d. "How to Perform a Clean Boot in Windows XP (Q310353)."

e. "HOW TO: Configure and Use Error Reporting in Windows XP (Q310414)."

f. "Preparation Before You Contact Microsoft After Receiving a STOP Message on a Blue Screen (Q314103)."

g. "You Receive a "System Has Recovered from a Serious Error" Message After Every Restart (Q317277)."

4. Many users question what the file "Appcompat.txt" is, besides assuming that IT is the error itself, which is a file generated by the WinXP compatibility mode when a program crashes unexpectedly -- a small XML file that lists which executables and dynamic link libraries (DLLs) were running at the time of the failure (name, version, size, checksum, and other technical details) -- and is an addendum submitted to M$ when applicable. Isn't the complete information concerning this file information something like: "The following files will be included in this error report:" -- which you shouldn't be concerned with anyway? Have you tried opening the file to see what information it contains?

Application instructions being executed at the time of a crash

Data values stored temporarily by the application

Program files and drivers that have been loaded into memory

Full memory dump (dependent on type of error encountered)

Note: IMO, to circumvent such notices from occuring and the file being created, simply do not use "Error Reporting" (image) or Dr. Watson [#2 reference above] and then simply submit the full context of any system error received in your request for help.