Does anyone know how to prevent this situation? On my old celeron 400mhz, running windows 2000 pro, I compile a file and my app runs fine. On my brand new P4 1.8ghz running XP. I compile the same file and it stops with a NMAKE: fatal error U1077 'c51' : Return code 0x3. And in the .LST file, at the end I have this C51 FATAL-ERROR - ACTION: ALLOCATING MEMORY ERROR: MEMORY SPACE EXHAUSTED C51 TERMINATED. Thanks, Roger
Sounds like these isn't any memory left for the compiler when using NMAKE. Check to see if you have expanded and extended memory available to the compiler. Jon
How do I check that there is enough extended and expanded memory? I clicked on properties of nmake and switched to windows compatibility mode for windows 95. The same result, but now it atleast tells me the error is with c51.exe. I also clicked on properties for c51.exe. There are options to use extended and expanded memory. But I still get this error. If I split the file in 2 then it compiles. It doesn't make sence to me.
Just in case: what version of C51 is that? From the symptoms you describe, you seem to be using a rather ancient release, which ran as an extended DOS program instead of the current one, which IIRC is a Win32 console application. You may have to check DPMI memory allocation, too, in that case.
I'm not sure what version I have, I am working with a vender's sdk and all they have is the c51p directory. I'm using visual c++ as the editor. It probably is pretty old. I'm not sure where to look for the version. I'm not very familiar with windows XP DOS memory settings. Can you tell me how to configure it?
"I am working with a vender's sdk" Time to contact the vendor, then?!
The C51 version is 3.2, Should that one work ok with windows XP?
The C51 version is 3.2, That's extremely old. To give you an idea: it's now at 7.06. Should that one work ok with windows XP? If it does, then you should consider yourself an extremely lucky person. XP is definitely not the best platform to be running ancient DOS applications on. At the very least you'll have to double-check the settings you had for C51.exe on that Win2000 box very carefully, and duplicate all of them as closely as you can on your XP machine.
FYI: C51 V3.2 was released before Microsoft Windows 3.0. Jon
"On my old celeron 400mhz, running windows 2000 pro, I compile a file and my app runs fine." Perhaps you should just keep that old system as a Compile server?!
I know, I'm working with ancient techology. I have a lot of C files to compile in my project and with my celeron, it takes about 15 minutes to do a full build. It took about 2 minutes on the 1.8ghz pentium with all the code commented out on the problem file.