FreeDOS 1.0 gives more debug information on such problem while newer FD1.1 just cycle with "Invalid opcode" or reboot.
This is kind of memory corruption during moving dos from it's location to HIGH. It's a kernel bug, but I have no idea how to debug it on a real hardware. I'll try to contact AMD guys.
16.01.2014, 02:55, "Rugxulo" <rugx...@gmail.com>:
Hi,
On Tue, Jan 14, 2014 at 2:18 AM, Anton D. Kachalov <mo...@yandex-team.ru> wrote:- rugxulo@
I use PXELINUX 4.05 20130513. It works fine with MS-DOS (Win98) with MS
HIMEM, but fails with FreeDOS / any XMM. That is why I don't point to PXE
loader's problem.
I can give it a try with latest pxelinux or try iPXE to be burned into ROM.I'm no kernel developer, but the various DOS kernels are not 100%
identical behind the scenes. I think they load to different initial
segments, too. Unfortunately, most people don't test very well (or
only MS-DOS and not FreeDOS, etc.), hence just because it works in one
doesn't mean it will work in both. If anything, I would rather they
tested FreeDOS first (as a more available target), but they don't do
so, don't ask me why. So bugs remain.
Yes, it could be something else, of course, but I still blindly guess
it's a bug on their end.
--
Anton D. Kachalov
<<attachment: H8DGU-FD1.0-himemx-dos-high.png>>
------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
