search for: __intcall0x13

Displaying 2 results from an estimated 2 matches for "__intcall0x13".

2019 Jan 16
2
A bug in command localboot was introduced in version 6.03.
A bug in command localboot was introduced in version 6.03. This bug was created because of inserting memsets in core/localboot.c. The third memset before /* Read one sector */ clears the field ireg.edx, which was assigned earlier and is required for subsequent __intcall0x13. So localboot type works as localboot 0. I think, this third memset in core/localboot.c is useless and excessive.
2019 Jan 19
0
A bug in command localboot was introduced in version 6.03.
...gt; a ?crit : > > A bug in command localboot was introduced in version 6.03. > This bug was created because of inserting memsets in core/localboot.c. > The third memset before /* Read one sector */ clears the field ireg.edx, > which was assigned earlier and is required for subsequent __intcall0x13. > > So localboot type works as localboot 0. > > I think, this third memset in core/localboot.c is useless and excessive. > _______________________________________________ > Syslinux mailing list > Submissions to Syslinux at zytor.com > Unsubscribe or set options at: > ht...