Re: DCOM security

From: Andrew Jarvis (someone_at_somewhere)
Date: 12/22/04 

Date: Wed, 22 Dec 2004 13:37:50 -0000

Finally figured it out.

In the environment path variable, the drive letter for the path of the
dependent DLL was assigned by "cmd /c subst ..." in the Startup folder!
Therefore it did not exist in the new user context.

Apologies for wasting your time.

AJ

Relevant Pages

  • Re: DCOM security
    ... the drive letter for the path of the ... dependent DLL was assigned by "cmd /c subst ..." ...
    (microsoft.public.windowsxp.network_web)
  • Re: bug in Win-XP-Pro with flash-drive and subst
    ... this is not a unique problem to SUBST. ... letter and no drive letter when such device is unplugged. ... > and create a shortcut for cmd-window. ...
    (microsoft.public.windowsxp.general)
  • Re: Conflict between Substd drive and USB storage devices
    ... I use subst to map the G: ... >assigns the drive letter that subst is using to the external device. ...
    (microsoft.public.windowsxp.configuration_manage)
  • Re: bug in Win-XP-Pro with flash-drive and subst
    ... I pretty much expected that the problem was not unique to SUBST. ... > drive letter and no drive letter when such device is unplugged. ... >> and create a shortcut for cmd-window. ... then maybe deleting that registry ...
    (microsoft.public.windowsxp.general)
  • Re: DCOM objects not found & Sharing error on SUBST drive
    ... Thanks again, Roger. ... the sefvice is not using some hard coded drive letter. ... only on my development environment: I run and test several versions of the ... same system, and to swap versions I run it from a SUBST drive, and change ...
    (microsoft.public.windowsxp.security_admin)
Quantcast