Re: [Freedos-user] EMM386 2.08/Nomyso 2.0 Available

[Bart Oldeman]

On Mon, 28 Nov 2005, Blair Campbell wrote:


PS:  If the C is ever to be compiled with Watcom C, as Bernd
suggested, the global functions in the asm would need to have a _ in
front instead of behind, as this is (for some weird reason) the way
OpenWatcom does things.


I think you have this the wrong way around.

The reason is not so weird, as it avoids severe bugs interfacing. The _ is 
put the other way because the calling convention is different, so just 
changing the _ isn't enough, you also need to convert stack to register 
parameter passing.


If you want a _ in front with OW, and stack calling conventions, like 
Turbo C, all you need to do is to decorate the function with _cdecl in the

C or H file.

Bart


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] EMM386 2.08/Nomyso 2.0 Available

[Michael Devore]

At 11:02 PM 11/28/2005 -0800, Blair Campbell wrote:


Speaking of bugfixes, a person on FreeDOS IRC has mentioned many times
that the latest versions of HIMEM/EMM386 won't work with certain hard
drives, but will work with others.  AFAIR, he also says that NOVDS
does nothing to change this.


Possibly one of the SCSI drivers, but without a test machine to see what's 
in conflict, nothing I can do.  All the SCSI drive machines I've been able 
to test with now work with EMM386.


Also, I've found some people allow too many memory areas in upper memory 
and trash BIOS drivers.  Either they I= include too much, or X=TEST can't 
catch quite everything.  Best way to determine if upper memory conflict is 
present is to temporarily X= the entire upper memory range and see if the 
problems persist or go away.  Then narrow down the range which needs to be 
excluded.



BTW, with NASM, does optimizing EMM386 or HIMEM for newer CPUs result
in smaller object files?


That would be a coding instruction-based optimization, rather than an 
assembler style based optimization.  I don't think there is all that much 
above a 386 instruction level which would help HIMEM/EMM386, plus you 
either ruin 386 compatibility or you get into CPU versioning of the 
programs, which sounds horribly messy.





---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user