Mail Archives: djgpp/2012/08/05/13:00:17
In article <301af96d-3710-4a4e-8328-85101cc04a06 AT googlegroups DOT com>,
rugxulo AT gmail DOT com says...
>
> Hi, yet again,
>
> On Friday, August 3, 2012 12:03:15 AM UTC-5, rug DOT DOT DOT AT gmail DOT com wrote:
> >
> > 00146023: 5D 80
> > 00146024: C3 63
> > 00146025: 8D FF
> > 00146026: 76 58
>
> That should probably be "DF" instead of "58" here. Not sure why I didn't catch that (or why it mostly worked without it). That was the whole point, to uppercase it!
>
> 00146023: 8063FFDF and byte [ebx-1],0xDF
>
> And, of course, this changes the md5sum, so here's the newer one:
>
> ==newemacs.md5===================
> 51a76c475ccfc50d341cee9990655808 *emacs.exe
> ==newemacs.md5===================
>
> BTW, here's a quick sed operation to avoid the compile problem when using FreeDOS' FreeCOM (untested but should work, heh):
>
> ==fcomfix.bat====================
> @echo off
> if not exist mainmake.v2 set MOO=msdos
> gsed -i "s/subst.*shell.*)/CURDIR)/" %MOO%.\mainmake.v2 %MOO%.\sed*.inp
> set MOO=
> ==fcomfix.bat====================
>
> P.S. I still feel like I need to kick the tires a lot more. I guess I'll keep playing with it, and see what I can find out.
I haven't had time to do much, and don't know enough yet to understand
most of what you've written. I was able, however, to modify callproc.c
as per your instructions, and then recompile emacs with the modified
file. It worked. Ispell now works in DOS Emacs with the new EXE, in an
SFN environment.
I'll try to figure out the rest of what you posted as can, but it may
take some time.
Thnaks.
Steve Bullington
- Raw text -