Re: [Freedos-kernel] 2034rc feedback (and EMM386)
At 02:58 AM 4/16/2004 +0200, Bernd Blaauw wrote: >Michael Devore schreef: > EMM386: FDISK /REBOOT causes Invalid Opcode, FDAPM WARMBOOT does the same >> >>Both using mov ecx,CR0 opcode. No big deal to add emulation for that. Let me grab >>Tom's copy of EMM386 and stick in there. > >hope Tom then updates his package. >Compressed version is pretty essential due to bootdisk size limits, but for the >moment he's the only one who can reduce binary's size by using his sys/exe >packer/compressor. Looks like it's not those applications which are generating the failing opcodes during the crash, so we don't need to bug Tom to do any opcode emulation updates on EMM386 after all. Of course, exactly why and where it's failing remains a problem. Reboot-related, obviously. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] 2034rc feedback (and EMM386)
Michael Devore schreef: EMM386: FDISK /REBOOT causes Invalid Opcode, FDAPM WARMBOOT does the same Both using mov ecx,CR0 opcode. No big deal to add emulation for that. Let me grab Tom's copy of EMM386 and stick in there. hope Tom then updates his package. Compressed version is pretty essential due to bootdisk size limits, but for the moment he's the only one who can reduce binary's size by using his sys/exe packer/compressor. Bernd --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] 2034rc feedback (and EMM386)
At 02:47 AM 4/16/2004 +0200, you wrote: >Bernd Blaauw schreef: > >>EMM386: >>FDISK /REBOOT causes Invalid Opcode, >>FDAPM WARMBOOT does the same Both using mov ecx,CR0 opcode. No big deal to add emulation for that. Let me grab Tom's copy of EMM386 and stick in there. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] 2034rc feedback (and EMM386)
Bernd Blaauw schreef: EMM386: FDISK /REBOOT causes Invalid Opcode, FDAPM WARMBOOT does the same FDAPM COLDBOOT does reset the computer FDAPM HOTBOOT works like good old QEMM: reboot to bootsequence immediately. (not that it has that great effect, but OK..) anything that can be done about it? don't know if the mentioned applications need to change, or EMM386, to accept warmboots. I'll check against MS EMM386. Bernd just checked against MS emm386.exe : this is an FreeDOS EMM386 flaw I'm not using EMM386 on bootdisk, but a fix in EMM386 would be nice (but not essential) to allow warmboot Bernd --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] 2034rc feedback (and EMM386)
> >EMM386: >FDISK /REBOOT causes Invalid Opcode, >FDAPM WARMBOOT does the same Need to know the Invalid Opcode data to do anything about it, if can be. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
[Freedos-kernel] 2034rc feedback (and EMM386)
I'm continuing this in public so I don't have to address everyone. *Kernel: DOS=LOW,UMB does *NOT* work (everything goes low, and SHELLHIGH does not function. UMBs are only made available when DOS=HIGH is found, somehow. same might go for FILES= for example. *Kernel: see Bugzilla entries. just as trivial (enhancement-level) as above mentioned bug. will definately not go into 2034. *Kernel: Detect unformatted partition (like just having run FDISK). Bart might have a solution for this, but I still have to try. Reproduction process: *Make primary partition *Download Eric Auer's tool called WHICHFAT (www.auersoft.org) *Boot desired kernel *WHICHFAT C: *ECHO %ERRORLEVEL% on MSDOS this delivers "1", on FreeDOS "12" (FAT12)where it should be 1 I'll report back on this, but it might cause a problem with Format, at least that's what Bart said. EMM386: FDISK /REBOOT causes Invalid Opcode, FDAPM WARMBOOT does the same FDAPM COLDBOOT does reset the computer FDAPM HOTBOOT works like good old QEMM: reboot to bootsequence immediately. (not that it has that great effect, but OK..) anything that can be done about it? don't know if the mentioned applications need to change, or EMM386, to accept warmboots. I'll check against MS EMM386. Bernd --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] kernel 2034rc for testing
> So, by all means, if you want to test it, download it. > If not, wait until the final release and then the next cycle of > improvements can be made. I think the largest test population in the > wild would be if Erwin Veermans included the testing kernel on his > Nwdsk (Netware bootdisk). I successfully performed full test-runs of my FreeDOS bloated NwDsk NetWare boot disk (including the always picky NIOS.EXE) using the combination of kernel 2034rc, himem/emm386 from emm386rc, freecom 0.82pl3, udma 7.0, lbacache 14apr04, cdrcache 07apr04, shsucdx 2.1a, cutemouse 1.9 (all installed/loaded). Optionally I added/tested fdapm 27nov03 and mkeyb 0.39. Michael has provided me with some special himem testversions to tackle problems with DELL PowerEdges with big ram (2GB). Himem-rc is jamming on those. We are currently busy to pinpoint the chipset/bios or the huge size of ram as the culprit using some extra himem-switches. When Michael releases his final himem/emm386 and Tom makes that official (and compresses it as hard as he can !) I will submit a new NwDsk containing all above updates (including kernel) at the Novell site while hoping that it behaves just as smooth for my users as it does on my own test-machines ;-) Or I will get more NwDsk-email than spam for once ... As with Bernd: we can test as good as we can but only when it gets out on all exotic hardware/software of our end-users we know where we stand. For my NwDsk I expect little impact from 2034 but I will be closely whatching the acceptance of switching from UMBPCI to EMM386 (though it looks very promising!). Erwin --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
