Re: C string array problems (again)

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance


This is ringing bells, I wonder whether the author of the DLL is
expecting the first entry to contain the full path and file name and
subsequent entries to consist of just the pathless file name


I guess that's possible. The cabinet.dll
operation expects a full path, but the code
is adapted from an MS command line sample.
In that case, the command line comes through
as:
testprogram.exe
file1.txt
file2.txt
.....etc...

And the MS sample code starts reading at array(1).

It may be that the sample program is just
setting current directory and sending file
names. That's odd, though, because the
cabinet.dll docs specifically say that the
FCIAddFile parameter should be a full path.
That would also mean that all of the CAB files
have to be in the same folder.
And that still doesn't explain why my path
is actually coming through chopped, before
it even gets to the cabinet.dll ops.

Anyway, thanks. Maybe I'll experiment with
building the path on the DLL side.



.

Relevant Pages

  • Re: cerdisp bug
    ... This is just sample code, ... The command line parameters were obviously not tested. ... html page with qfe information for us. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: check form open and bring it to front
    ... Marshall Barton wrote in ... if it opens then bring it to front. ... I just wonder any command to do the task. ... command in your sample code -- I've restored it in the quoted code). ...
    (microsoft.public.access.formscoding)
  • Re: check form open and bring it to front
    ... David-W-Fenton wrote: ... if it opens then bring it to front. ... I just wonder any command to do the task. ... command in your sample code -- I've restored it in the quoted code). ...
    (microsoft.public.access.formscoding)
  • Re: Command Line Arguments from a File
    ... Below is sample code. ... If I run with command ... default ALTERA file. ... elsif { ...
    (comp.lang.perl.misc)