I'd try unloading EMM386[64] altogether and see if you still have crashes. It's the most likely compatibility culprit at first, particularly since you said the HIMEM64 original also crashed so the new changes aren't at fault.
At 02:29 AM 2/1/2004 +0800, you wrote: >Hello All, > >I've tried to replace HIMEM64C/EMM38664 instead of FDXXMS/UMBPCI and >during test I crash the PC with following configuration: > >-----CONFIG.SYS----- >!version=6.22 >!break=on >!dos=high,umb >!dosdata=high >!files=50 >!buffers=10,0 >!lastdrive=z > >device=c:\freedos\himem64c.exe (himem64.exe crashed also) >device=c:\freedos\emm38664.exe >devicehigh=c:\freedos\udma.sys (ver 6.8, loading low this can pass) >devicehigh=c:\freedos\nansi.sys /s > >!shell=c:\freedos\command.com c:\freedos /e:1024 /p >-----END----- > >When I've tried to swap the UDMA and NANSI line by load 'NANSI' first, >FreeCOM corrupted and keep asking for COMMAND.COM's path (hard disk >seems disappeared), even reload the COMMAND.COM from floppy the boot >partition have nothing (0 files). > >Loading low the UDMA won't cause any problem. > >I wonder where the problem is, when running FDXXMS/UMBPCI all program >can loadhigh. ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
