On Wed, 11 Feb 2004, Luchezar Georgiev wrote: > ...and everywhere where fmemcpy is called? But isn't it better to fix > fmemcpy itself?!
the problem here is that fmemcpy wasn't broken, so your fix is not a fix, just a workaround. Yes, it affects the high word of eax, but that is not a bug in itself. The real problem *must* be somewhere else. Hence the suggestion of Tom to use softice or similar to figure out where and why you *really* crash. Bart ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
