INTERNAT.EXE - current directory

INTERNAT.EXE is reported by TASKINFO to have a current directory other
than C:, C:\WINDOWS, or C:\WINDOWS\SYSTEM.

It appears to be using a mozilla\GRE\version directory that shows up
as the first entry in a long autoexec.bat-looking path name in the
TASKINFO 'env' window. This env text string is not in the registry or
other familiar locations.

The executable is resident in the proper location, reports properties
that are normal and looks kosher. I'd like to correct the env readings
to look 'normal', at least temporarily, to check effects on the
system. Any advice on how to do so.

I am currently still battling non-fatal explorer faults that are
user-input-triggered, per the thread 'Explorer invalid page fault...'.

RL

Hi!

INTERNAT.EXE is reported by TASKINFO to have a current directory other
than C:, C:\WINDOWS, or C:\WINDOWS\SYSTEM.

isn't internat.exe that keyboard-language selector in the taskbar thing?
As long you really need that feature I guess it is ok to run...

if it not beeing in C:\WINDOWS\SYSTEM\ in win98 it is probably
a trojan instead I would guess

On Thu, 25 Jun 2009 10:47:51 GMT, teebo wrote:

Hi!

INTERNAT.EXE is reported by TASKINFO to have a current directory other
than C:, C:\WINDOWS, or C:\WINDOWS\SYSTEM.

isn't internat.exe that keyboard-language selector in the taskbar thing?
As long you really need that feature I guess it is ok to run...

if it not beeing in C:\WINDOWS\SYSTEM\ in win98 it is probably
a trojan instead I would guess

The only INTERNAT.EXE in the machine is correctly located in the
C:\WINDOWS\SYSTEM directory. It is not the version shipped native to
W98 2Ed (4.10.2222), but a later revision (4.80.3008.1), which I
suspect serves to produce legible Japanese and Chinese characters in
some applications, while operating within normal keyboard limits. It
dates from Jan'99 and cannot really be linked coherently in time to
the current explorer.exe problems.

This AM, the path statement starts with the Outlook Express directory.

This suggests that the path statement assumes the directory of the
first manually invoked executable, after boot, not exclusively the
Mozilla directory, as was first assumed from the earlier observation.

If this is to be expected as normal, I'll keep sniffing elsewhere for
the root cause of the non-fatal explorer faults.

RL