Greetings All!
I asked this once before, but many moons and many hard
drive replacements later, I managed to lose the
information. :-|
LOADDSKF.EXE appears to run as a native process,
regardless of whether it is launched from a DOS or and
OS/2 command prompt. Is it possible to duplicate this
with Borland C++ 1.0? If so, how?
Sleep well; OS/2's still awake! ;)
LOADDSKF.EXE appears to run as a native process, regardless of whether
it is launched from a DOS or and OS/2 command prompt. Is it possible
to duplicate this with Borland C++ 1.0?
If so, how?
LOADDSKF.EXE appears to run as a native process, regardless of whether
it is launched from a DOS or and OS/2 command prompt. Is it possible
to duplicate this with Borland C++ 1.0?
LOADDSKF.EXE appears to run as a native process, regardless of
whether it is launched from a DOS or and OS/2 command prompt. Is
it possible to duplicate this with Borland C++ 1.0?
LOADDSKF.EXE appears to run as a native process, regardless of
whether it is launched from a DOS or and OS/2 command prompt. Is it
possible to duplicate this with Borland C++ 1.0?
No, you can't - as asked! You can however use BC 3.1 for the DOS part
and BCOS/2 for the OS/2 part under your option two.
Hi, Don! This is on my "things to try" list, but as I haven't yet had
need for such a program I haven't actually tried it for myself.
I think that I saw it in my Borland C for OS/2 package, but I'm sure
that I've got a copy of Bind around here somewhere.
I quick search found a copy on the Internet at ftp://ftp.nfbnet.org/bbsfiles/os2-prog/FAMAPI.ZIP.
Create a module definition file named PROG1.DEF that includes the statement STUB PROG1D.EXE. Finally, compile your program using
Borland for OS/2 and the module definition file for the link step.
Create a module definition file named PROG1.DEF that includes the
statement STUB PROG1D.EXE. Finally, compile your program using
Borland for OS/2 and the module definition file for the link step.
I gave it a shot just now, but something must be a bit off--the
console output is garbled when the final product is run from a DOS
window.
JdBP> I urge you to not encourage the continued use
of DOS by making more
JdBP> DOS programs.
While I prefer OS/2 over the alternatives, I'm not
about to ignore the needs of those who choose
alternate operating systems.
-Don
Sleep well; OS/2's still awake! ;)
I gave it a shot just now, but something must be a bit off--the
console output is garbled when the final product is run from a DOS
window.
Have you run your DOS code all by itself (i.e. before linking it to
the OS/2 code) in a window?
I gave it a shot just now, but something must be a bit off--the
console output is garbled when the final product is run from a DOS
window.
Have you run your DOS code all by itself (i.e. before linking it to
the OS/2 code) in a window?
Aye, and it behaves properly. Are there any tricks to module
definition files that I should know about?
I looked around for Bind on my system but could not find it. I think
that I saw it in my Borland C for OS/2 package, but I'm sure that
I've got a copy of Bind around here somewhere.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,028 |
Nodes: | 17 (0 / 17) |
Uptime: | 181:04:06 |
Calls: | 503,706 |
Calls today: | 9 |
Files: | 158,903 |
D/L today: |
13,752 files (4,211M bytes) |
Messages: | 444,341 |
Posted today: | 2 |