Subject:
|
Re: LDAO DOS Boxes
|
Newsgroups:
|
lugnet.cad
|
Date:
|
Wed, 13 Jun 2001 07:44:16 GMT
|
Viewed:
|
509 times
|
| |
|
|
"Steve Bliss" <steve.bliss@home.com> wrote in message
news:bf1aits5s9rq6rfph39ea2i7ih844t136d@4ax.com...
> Once upon a time, I considered distributing the .PIF files along with
> LDAO, but I think I ran into problems with the path (Windows likes to
> put the complete path into PIF/shortcut files).
>
> On my machines, I always have the default DOS behaviour set to close
> windows, so I don't notice the problem...
Steve, is LDAO written in VB? Have you considered using the CreateProcess
API call? I can send you some sample code over for running a DOS program
with a hidden or visible window that will always automatically close as it's
being handled differently using this call than something like Shell, so if
you launch these DOS programs from LDAO you can control exactly what will
happen to them.
Dan
|
|
Message has 1 Reply:
 | | Re: LDAO DOS Boxes
|
| (...) Yes. (...) No, I hadn't. (...) Hmm. Actually, what I really need to do is dig into the VEC code, and rewrite it from scratch, and get rid of the DOS calls. Now, if anyone has some sample code for rapid retrieval of directories (filename and (...) (23 years ago, 13-Jun-01, to lugnet.cad)
|
Message is in Reply To:
| | Re: LDAO DOS Boxes
|
| (...) Thanks to Heather for posting the fix to this. Once upon a time, I considered distributing the .PIF files along with LDAO, but I think I ran into problems with the path (Windows likes to put the complete path into PIF/shortcut files). On my (...) (23 years ago, 11-Jun-01, to lugnet.cad)
|
6 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
