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.
Continuing... Is the "Adobe Download Manager" the correct type of file as the executable? The linker does not always generate this file.
Again, we did no change any output format with the Assembler. So you should still contact MetaLINK and ask if you are using current software for the emulator. The Linker output file has by default no extension (some people give *.ABS. It does not relate to Adobe products at all.
"Is the 'Adobe Download Manager' the correct type of file" This is just a name that your Windows Explorer has associated with the File type; you need to check the actual extension in the filename; eg, .abs, .obj, etc... In Windows Explorer, You should go to 'Folder Options', then the 'View' tab, then ensure that 'Hide extensions for known file types' is not checked.