This is a repeat of previous post corrected for 8051 toolset. I can no longer use uv3 to generate an "HLL" (High Level Language) type file to run in a Metalink XF 8051 emulator. I must use "mixed" or "code" listings in the XF. The XF says "No source files available" after loading the executable. This feature has worked reliably for several months after initially failing & then magically curing itself. This latest anomaly began after I "saved as" one of the 4 source files in the project group in uV3. Also, the BL-51 linker sometimes generates an executable file of the type "Adobe Download Manager" which the emulator can usually identify and load. Other times there appears to be no target file created even as the linker says it has built the target. I am running this software under Windows XP. Is there some fundamental incompatibility with this OS & uV3? I also have difficulty in setting up "books" files in the IDE. It seems unable to find them even though their paths appear correct. This situation is extremely frustrating and disappointing. I ran the original Intel ASM-51 dpendably for 21 years until the platform on which it ran became totally unsupportable.
"There are no spaces in any of my file names." It's not just file names - ensure that there are no spaces anywhere in the path (ie, including folder names; eg, "My Documents", or "Program Files") "the absolute product of the BL-51 linker which should contain the source code" No, it doesn't actually contain the source code; what it contains is references to the source code. I'm not sure if these would be absolute (fully-qualified paths) or relative... "Can anyone refer me to a reliable basic relocatable assembler that can handle classic 8051 as well as Atmel 89C51ED2?" The instruction set is the same; therefore any assembler should do - that's the beauty of the 8051 "family". But what makes you so sure that it's the assembler that's at fault? How are you sure that it's not the Linker, the debugger, or something else? As Reinhard says, have you tried this with the uVision simulator and/or debugger? If it works with uVision, this must indicate that the build tools (Assembler, Linker, etc) are working correctly; so you need to look at the 3rd-party stuff... "The source code was available for several months on a reliable basis" Do you have backups of this. so you can go back and see what's changed?