Re: old binary works not with 2.2.18 (fwd)

Hi, I tried a little further, 2.2.19p2 still works, 2.2.19p3 not. /usr/SCULPTOR/bin/sage: Microsoft a.out separate pure segmented word-swapped V2.3 V3.0 386 small model executable I *did* rebuilt my iBCS each time after building (and rebooting) a different kernel version. Kees - To unsu

old binary works not with 2.2.18 (fwd)

Hi, I have an old 4GL application (from SCO3.2v4) that is a neat database tool. Under 2.2.17 with iBCS this works well: schoen3:~ # file /usr/SCULPTOR/bin/sage /usr/SCULPTOR/bin/sage: Microsoft a.out separate pure segmented word-swapped V2.3 V3.0 386 small model executable I did some checkin

Re: old binary works not with 2.2.18

kees wrote: > > Hello, > > Yep, *After* I build a new kernel I _always_ build a new iBCS module. > > I have an old utility 'hd' (hexdump) from SCO3.2v4.2 that also needs iBCS > but has a slightly different format, *that* works under 2.2.18 > > Kees Kudos!!! I use the same utility but from 5.

Re: old binary works not with 2.2.18

Hello, Yep, *After* I build a new kernel I _always_ build a new iBCS module. I have an old utility 'hd' (hexdump) from SCO3.2v4.2 that also needs iBCS but has a slightly different format, *that* works under 2.2.18 Kees On Mon, 18 Dec 2000, John O'Donnell wrote: > kees wrote: > > > Hi, > >

Re: old binary works not with 2.2.18

kees wrote: > Hi, > > I have an old 4GL application (from SCO3.2v4) that is a neat database > tool. Under 2.2.17 with iBCS this works well: I am just curious. Did you re-compile the iBCS2 module after upgrading to 2.2.18 to did you force the module to load up... With Slackware and kernel upgr

old binary works not with 2.2.18

Hi, I have an old 4GL application (from SCO3.2v4) that is a neat database tool. Under 2.2.17 with iBCS this works well: kees@renske1:~ > cat /proc/version Linux version 2.2.17 (root@renske1) (gcc version 2.95.2 19991024 (release)) #10 Wed Dec 6 20:16:39 CET 2000 kees@renske1:~ > sage sage : Sc