#77 Access to COMDLL.dll denied

[Thomas Creedon]

There is a bug in the new self installing DLL code
(Frontier.data.DLLs.install). It works OK the first
time around (launch Frontier and quit). The second
time around and after it fails with an error message
Access to COMDLL.dll denied. If you click on the Go To
button you are taken to a line file.delete (adrPath^).

I've tried to come up with a fix but I'm not making
much progress. I thought that perhaps the dll was
active and so I did a dll.isloaded but it claims it is
not loaded. Attempting to do a dll.load causes a crash.

This indicates to me that something is active in the
dll and that the file can't be deleted until it can be
made inactive.

[Thomas Creedon]

Logged In: YES
user_id=1464347

I have come up with a work-around for this problem but I'd
still like some heavy hitters to take a look into this issue.

I'm leaving this open.

[Andre Radke]

Logged In: YES
user_id=1137587

IIRC, the COM DLL is loaded automatically by the kernel
when Frontier starts up. I think the function to look for
is COMStartup() or something similar.

Anyway, Frontier clearly shouldn't crash if you dll.load
the COM DLL, even if it's already loaded.

I'll try to look into this over the weekend unless you get
there first.