Re: where are .dll files written to?

Hello,

On several systems I ran starpacks/kits at, those files are written to the temporary folder of the 
current working environment, which is in most cases the current user's temp directory, to which the 
environment variable TEMP points to.

Just do a

cd %temp%

at the command prompt; this should lead you to the right place.

If a star pack is running as a service, the folder is probably c:\winnt\temp or so, but I think this 
is configurable.

It's possible to retrieve informationen about temporary locations not only via the environment 
(TEMP, tmp) but also via Windows Scripting and/or Win32 API.

Of cource windows cannot load dlls or exes out of a VFS because windows does not know anything about 
starkit/starpacks. So tclkit copies DLLs automatically to the normal file sys before LOADing them.

Unfortunally. for EXEs, this has to be done by the programmer before EXECing...

Matthias

Steve Blinkhorn schrieb:
> As I understand it, because Windows is not vfs-aware any .dll files,
> such as those required for extensions, that are included in a
> starkit/starpack are written out to the host file system and then
> loaded.
> 
> But where?   With running applications that depend on particular
> extensions that I know depend on particular .dll files I cannot find
> where they have been written to.   Or are they written and then
> instantly deleted?
> 
> This makes a difference if you are working in a heavily
> security-driven locked-down environment...
> 
> --
> Steve Blinkhorn <[email protected]>
> _____________________________________________
> Starkit mailing list  -  [email protected]
> http://www.equi4.com/mailman/listinfo/starkit
> 

-- 

Mit freundlichem Gruß,

M.Hoffmann
_________________________________________________________________________

D A K - Unternehmen Leben
Geschäftsbereich IT-Services
Client-Server-Systemtechnik (007460)

Nagelsweg 27-31, 20097 Hamburg
Tel.: (040) 2396-1784
mailto:[email protected]
http://www.dak.de