Hello,

using the program with this command I get an error:

U:\Produits\LogInfo>TextFileSplitter -i=U:\Produits\LogInfo\U53\LogInfos_2008051
8.txt -o=d:\ -h -kbs=10000

====

System.rEflection.targetInvocationException: eception was generated --> System.UnauthorizedAccessException: acces to directory 'd:\' not allowed

in System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
....
====

I attach screen copy error box.

Version 1.5.0 with XPPro SP3

Problem is similar with any target directory.

It seems to be OK with GUI but I need command line control to integrate that in my personnal application. Is it possible to know the commande line used by GUI?

Regards

problem is the same with D:/ as target drive

I think that network drive are on a linux server, with Samba (to be confitmed). I have rwx rights in this directory and GUI doesn't generate error with same path.

May be a wrong management of / or \, simple ou double?

what happens if -o parameter is not mentionned? is it possible to consider source directory (-i) as default one?

New element, if I had list at the end of -o parameter (-o=U:/Produits/LogInfo/U53/list) I get a new error:

'Impossible to find file  U:\Produits\LogInfo\U53\list\xxxxxxxxxx.txt' where xxxxxxxxx is the first line of -i file...

ok, I hope you'll be able to push out an update in a few days, it would help me in my operations.

the problem is located in output directory, not input one. Now I've tested the command line:

U:\Produits\LogInfo\TextFileSplitter -i=U:/Produits/LogInfo/U53/LogInfos_200
90617_am.txt -o=D:/ -h -ls=1000 -regex:^\[ -boundaryasfilename

and got the same error message.

As it runs with GUI, it may be useful to extract somewhere (in a file text?) the command matching settings?

R1M,

I just attached a build that should take care of the command-line issues you are having. I changed the code so that it is using native .NET functions to deal with directory handling instead of manually doing it.

Could you please download the attached update and test it? I will release it to the public if it fixes your issue.

Regards,

Hector

I tried the new version and get the same error. I even put the batch file and the test file in the same directory with the .exe, so everything is running on C:. I have attached my error.

I was finally able to reproduce the error. Once that happened, I was able to find and fix this problem. I'm attaching a new test version for everybody to try.