Release memory and execute another program
I have a program which I have used in past, and which I wrote, which loads and executes other programs, after hooking interrupts of choice. When I recently had a problem with trying to format under FreeDOS, I found that this program does not work under FreeDOS. It reports that there is insufficient memory. Perhaps the free memory call doesn't work. Anyway, I'd like to pursue this a little bit more, if possible. Who is there who would be interested in trying to track down what the incompatibility is?
Also, I tried a different program which is part of Ralph Brown's package, and which completely locked up. It does direct writes to the memory area for the interrupt vectors. Is this not supported?
Mike
Signature · 5 lines
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!Re: SPAM:: Release memory and execute another program
Quoted 2 lines · Mike McCarty
Who is there who would be
interested in trying to track down what the incompatibility is?
FreeDOS bugzilla (see www.freedos.org) is a good place to report FreeDOS bugs.
Quoted 3 lines
Also, I tried a different program which is part of Ralph Brown's package, and which completely locked up. It does direct writes to the memory area for the interrupt vectors. Is this not supported?
What *exact* program in Ralf Brown's interrupt list (?) do you mean? It's easier if you mention explcitly what to reproduce rather than us having to do the guess work.
Bart
Re: SPAM:: Release memory and execute another program
Quoted 7 lines · Bart Oldeman
Quoted 2 lines · Mike McCarty
Who is there who would be
interested in trying to track down what the incompatibility is?FreeDOS bugzilla (see www.freedos.org) is a good place to report FreeDOS bugs.
Thanks for the pointer.
Quoted 6 lines
Quoted 3 lines
Also, I tried a different program which is part of Ralph Brown's package, and which completely locked up. It does direct writes to the memory area for the interrupt vectors. Is this not supported?
What *exact* program in Ralf Brown's interrupt list (?) do you mean? It's easier if you mention explcitly what to reproduce rather than us having to do the guess work.
You know, it would be nice to get an *answer* to the question. If it isn't a supported action, then what difference does it make what program it is? Only after knowing that bit of information does it make sense to try to go further.
So, care to answer the question?
I'll guess: it's intended to be a supported action.
The program is INTERCEP.EXE. I was trying to run my own program, but was unable to get the memory to load the target program, so I tried Ralph's, which didn't even run at all. Mine at least reported not enough memory, and managed (at least I suppose it managed) to intercept the interrupts and replace them. But mine uses the Borland C interface to the MSDOS set/get interrupt vector, while Ralph Brown's does direct writes to the memory vectors.
If you need a copy, I can supply it. The one I used is contained in interc2.zip version 39.
Mike
Signature · 5 lines
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!