Hi Eric, Can you test whether the FAT16 trick would have worked as well? >
Sure, I will check it, I just need a few days to find the time for that. Also, do the FreeDOS fdisk and format commands have options/parameters to create FAT16 partitions/file systems? Because I am pretty sure that I went with the defaults the last time, and that's how I ended up with FAT32. (I believe the FreeDOS 1.4 installer creates a FAT32 partition/FS by default.) > And question to QEMU users, can QEMU be configured to not have LBA? > I used VirtualBox, but I doubt that there is any option to fine-tune the capabilities of the VM's BIOS at that level. > I understand that if you do NOT use JEMM386 or JEMMEX, DOS works? :-) > Yes, if I choose option 3 at boot, then FreeDOS loads OK, but I'm stuck with 640KB. > > Jemm386: exception 06 occured at CS:EIP-CA57=000009EE ... > For the sake of simplicity, I took a photo of the error message and ran it through an OCR. It wasn't flawless, but the bulk of stuff correct: CS:EIP=CA57:000009EE Exception 06 is illegal opcode and CA57:09EE is in the UMB area. > > > DS=CA57 ES=CA57 FS=DB36 GS=00D9 [CS:IP]=D6 0A C0 C3 86 Ε0 30 80 > Sorry, the OCR was not perfect here either. I double checked everything again, and originally it was: DS=CA57 ES=CA57 FS=DB36 GS=00D9 [CS:IP]=D6 0A C0 C3 86 Ε0 3D 80 (Notice the penultimate byte was 3D and not 30.) However it doesn't seem to change the overall picture, that the SALC opcode seems to be the one to blame. > However, doing SALC followed by OR AL,AL and RET indeed is a > legitimate way of using SALC. So what you see is not a crash > caused by having bogus data in your UMB area, but instead the > crash is caused by the processor of your Pocket 386 not having > support for the SALC opcode! > The Pocket 386 has an Ali M6117 SoC, which contains a 386 SX core clocked at 40 MHz. For me it is entirely plausible to assume that it doesn't have support for undocumented opcodes found in Inter CPUs. > Please let me know which drivers you are loading :-) > The funny thing is that this happened right after completing the FreeDOS installer: I turned off the VM, unplugged the CF reader with the card from my Linux machine. Then plugged the CF card into the Pocket 386 and selected 1, to run Jemm386 to make use of the upper memory, and there I was. So if there is anything that gets loaded, it was being put there by FreeDOS, not me. Looking at the screenshot, I see the following outputs: HimemX 3.38 ... KBC A20 method used Jemm286 v5.85 ... System memory found at c000-c7ff, region might be in use Jemm386 loaded Kernel allocated 46 diskbuffers ... 24472 bytes in HMA FreeCom version 0.86 - WATCOMC - XMS_Swap Performing actions: APMDOS ... APM not available, skipping APM setup Going resident. CuteMouse v2.1 beta4... Error: device not found DOSLFN 0.41 ... Jemm386: exception ... (we know this part already) Is there anything that stands out? > PS: It could be possible for JEMM386 to emulate SALC on systems > which do not support it in hardware. A sort of exotic solution. > Sounds a bit bizarre, especially if you say that the binary of Jemm386 itself doesn't contain any occurrence of SALC. Best Regards / Mit freundlichen Grüßen János
_______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
