Peculiar message

[andsome]

I decided to drag and drop several lots of photo's off an assortment of magazine CD's into folders on my D drive, with the intention of using them in presentations. When I inserted the C D's, every single one threw up the message shown below. It has not caused any problems as I just opened each CD in My computer and dragged and dropped the photo's in the usual way. No other C D's do this, only this batch, all made in 2002 and issued with Digital Photo magazine. The C D's all operated normally on my old computer at the time.

AS I said IT DOES NOT MATTER, I am just curious, any observations? Windows XP SP2.

[dadyassa]

Its just XP telling you it doesn`t like old stuff ;)

[andsome]

Its just XP telling you it doesn`t like old stuff ;)

YET, much older C.D's than this run with no bother at all. I can even run a Windows 98 installation CD to download sounds from it.

[ɹəuəllıʍ ʇɐb]

Have you checked your AUTOEXEC.NT (in C:\Windows\system32) if it contains DOSX.EXE ? If not, add this line

lh %SystemRoot%\system32\dosx

See also

• http://support.microsoft.com/?id=103104
  
• http://support.microsoft.com/?id=150420
  
• http://support.microsoft.com/?id=168925
  

[andsome]

THANKS, but I don't really understand what I am doing here. Where would I put this and how. I have made system 32 files visible, but haven't a clue what to do next. The MS articles apear to refer to Windows NT or 2000, not XP SP2.

[andsome]

I have now gone back using Acronis to mt original installation, when I reinstalled Windows in Jan. The message still comes up when I try to run these few C.D's. As this is causing me no problem, I will now revert to my latest settings using Acronis again, and ignore the problem.

[ɹəuəllıʍ ʇɐb]

THANKS, but I don't really understand what I am doing here. Where would I put this and how. I have made system 32 files visible, but haven't a clue what to do next. The MS articles apear to refer to Windows NT or 2000, not XP SP2.

I think support for 16-bit apps have not changed since NT4, so the articles are probably not specific for any NT system.

As for the AUTOEXEC.NT file in the system32 folder, you can right-click it, then select Edit to see its content.

[andsome]

I cannot see this folder.

EDIT. I have now found the folder, but right clicking does not give me an edit option. I also cannot open it as it wants to know what program to use. It appears from searching that this is a common fault after installing some updates.

[Scarecrow Man]

You must open it with notepad. Do not modify anything without knowing exactly what you are doing, and without making a back up first.

[andsome]

Think I'll leave well alone. Almost everyone must have this problem on their computers as it occurs with SP2. Microsoft's solutions are next to useless if you don't have a degree in rocket science.

[andsome]

I had further thoughts on this as I do like to have everything running correctly. It appears that this error occurs after SP2 is installed, so most people would have it, and would not be able to run the C D's in question. So I telephoned Microsoft. After quite a protracted argument with the operator wanting me to register for paid support, she eventually agreed that as this was a Windows SP2 error, to put me through to a support technician. The solution was a very protracted exercise in cmd entries, but now all the C D's will run perfectly. My next step is another Acronis backup of the system as it is now.