PDA

View Full Version : Log file name


johnfaris
19-Jan-2006, 10:33 AM
I have a windows service that uses a DLL called MasterImportProcessor.dll. For some reason the logfile produced by EurekaLog has the name MASTER~1.elf. Any ideas why the filename is getting truncated in this way? It is strange because it seems to be using DOS (8 character) filenames, but other dlls apps I use have more than 8 character names and get given a proper log file name.

Thanks.

Jouni Aro
19-Jan-2006, 03:31 PM
johnfaris wrote:
> I have a windows service that uses a DLL called
> MasterImportProcessor.dll. For some reason the logfile produced by
> EurekaLog has the name MASTER~1.elf. Any ideas why the filename is
> getting truncated in this way? It is strange because it seems to be
> using DOS (8 character) filenames, but other dlls apps I use have more
> than 8 character names and get given a proper log file name.

I've seen a similar thing to happen with my own logging, when used from
a COM server, instantiated by a client. Application.ExeName (equals to
ParamStr(0) in Delphi) contains the short name in this case (an my log
name generated from that also), but if I launch the app manually,
Application.ExeName (and the log name) contains the long name...

admin
24-Jan-2006, 02:41 PM
Hi,

johnfaris wrote:
> I have a windows service that uses a DLL called
> MasterImportProcessor.dll. For some reason the logfile produced by
> EurekaLog has the name MASTER~1.elf. Any ideas why the filename is
> getting truncated in this way? It is strange because it seems to be
> using DOS (8 character) filenames, but other dlls apps I use have more
> than 8 character names and get given a proper log file name.
>
> Thanks.

I have just fixed this little bug in the last EurekaLog 5.1.1 RC 2.

Try it and tell back to me your result, ok? ;)

--
Best regards...

Fabio Dell'Aria.
----------------
http://www.eurekalog.com
Catch every BUG, every time!

Jouni Aro
27-Jan-2006, 11:09 AM
admin wrote:
> I have just fixed this little bug in the last EurekaLog 5.1.1 RC 2.

How did you do it (what was the problem)?

admin
30-Jan-2006, 11:20 AM
Hi,

Jouni Aro wrote:
> admin wrote:
>> I have just fixed this little bug in the last EurekaLog 5.1.1 RC 2.
>
> How did you do it (what was the problem)?

Now the Log File name is stored in long format (not old DOS 8.3 format). :)

--
Best regards...

Fabio Dell'Aria.
----------------
http://www.eurekalog.com
Catch every BUG, every time!

Jouni Aro
30-Jan-2006, 12:56 PM
admin wrote:

> Now the Log File name is stored in long format (not old DOS 8.3 format). :)

So you convert it in the code to ensure that it is using the long format?

admin
30-Jan-2006, 06:51 PM
Hi,

Jouni Aro wrote:
> admin wrote:
>
>> Now the Log File name is stored in long format (not old DOS 8.3
>> format). :)
>
> So you convert it in the code to ensure that it is using the long format?

Yes, it's so! :)

--
Best regards...

Fabio Dell'Aria.
----------------
http://www.eurekalog.com
Catch every BUG, every time!

johnfaris
02-Feb-2006, 08:05 AM
I have compiled the new version into my application but I'm still waiting for an Exception to occur so that I can see if the problem is fixed :D

Will let you know as soon as I get one!

johnfaris
03-Feb-2006, 09:20 AM
This issue is resolved now thanks! Interestingly it also uses the old style dll name in the exception message e.g.

"Access violation at address 07DA8091 in module 'MASTER~1.DLL'. Read of address 07DF4000."

admin
03-Feb-2006, 11:29 AM
Hi,

johnfaris wrote:
> This issue is resolved now thanks! Interestingly it also uses the old
> style dll name in the exception message e.g.
>
> "Access violation at address 07DA8091 in module *'MASTER~1.DLL'*. Read
> of address 07DF4000."

I have just fixed this little issue too, in the version 5.1.2 RC 2. :)

--
Best regards...

Fabio Dell'Aria.
----------------
http://www.eurekalog.com
Catch every BUG, every time!